ERP Systems Development & Integration

Most operations software starts as spreadsheets and a handful of disconnected tools. I build ERPs that replace them with one system: a module for each department, shared data underneath, and reports that agree with each other.

I've built this for schools, microfinance NGOs and rental fleets. The School ERP covers admissions, academics, students, parents and staff, finance, campus services, communication and reporting. The microfinance core banking system runs group lending, savings, loan disbursement, repayment schedules and field-agent collection for 3 organisations across 20 branches, with HR, payroll and MIS reporting alongside. At CodePal I architected Drivus, a CRM/ERP for car-rental and rent-to-own operators covering fleet, vehicle tracking, contracts, payments, tolls and fines, and financial reporting.

I start with the domain: the entities, the rules that must always hold, and who is allowed to see what. In multi-tenant systems the database enforces tenant isolation itself, with PostgreSQL row-level security, instead of trusting every query to remember a filter. Branches, roles and permissions are modelled up front, because retrofitting them later is where ERPs tend to break.

Reports get the same care. At Semicolon I cut ERP report generation from around 40 seconds to under 5 through query optimisation and backend refactoring. On Drivus, automated accounting and payroll workflows cut manual reconciliation time by 35%.

An ERP also has to fit the tools you already use: Drivus, for example, bills through Pay Advantage and sends event-driven notifications for payments, contracts and compliance. Every deployment comes with documentation, and the microfinance rollout included training and technical support for the teams using it.