Planning & implementation decisions
Should you build a custom ERP or integrate existing software?
Choose custom development when essential business rules, approvals or reporting cannot reasonably fit existing software. If the current ERP performs its core tasks well, configuration or integration may be simpler. Assess workflows, data ownership and maintenance before choosing.
| Situation | Starting approach | Check before commitment |
|---|---|---|
| ERP works; teams re-enter records | Integrate systems | API access and authoritative record owner |
| Most requirements are standard | Configure an established ERP | Fit of real tasks and upgrade constraints |
| One specialized workflow is missing | Build a custom module | Integration boundary and module ownership |
| Core processes cannot fit current tools | Consider a bespoke ERP | Lifecycle cost, migration and support capacity |
| Data and processes are undocumented | Requirements discovery first | Named owners and agreed process map |
- Step 1 →
Request
Capture the operational need and owner.
- Step 2 →
Approve
Check role, limits and required evidence.
- Step 3
Record and report
Update the authoritative system and preserve the decision history.
Exception & recovery path
Rejected or incomplete requests return to the requester with a reason. A failed downstream update is queued for recovery instead of marked complete.
How do we define the first ERP release?
Select one complete operational journey, such as request → approval → receipt → reporting. Name users and acceptance criteria at each handoff. Defer modules that are not needed to complete that journey, while documenting their future data dependencies.
What must happen before data migration?
Assign an owner to each source, map identifiers, identify duplicates and agree control totals. Rehearse migration with representative data, compare balances and record exceptions. Set a cutover window, rollback decision and sign-off owner before moving live records.
How should ERP proposals be compared?
Ask each supplier to price the same workflows, integrations, migration, training and support scope. Separate licences, implementation and recurring operation costs. Require demonstrations of permissions, correction paths and exports, not only dashboards.
Who owns and maintains the ERP after launch?
Document ownership or licence terms for source code, configuration and data. Agree hosting access, backup restoration, integration updates, security fixes and support escalation. Delivery timing depends on these responsibilities and third-party access as well as development.
Take this into your project discussion
- Demonstrate the five highest-priority tasks.
- Document source-of-truth and access rules for each module.
- Rehearse migration and reconcile control totals.
- Compare full ownership costs and exit/export terms.
- Agree acceptance, training, rollback and support responsibilities.
Planning content reviewed . Confirm current provider requirements and project-specific assumptions before implementation.
What Your ERP Needs to Connect
ERP projects often touch financial records, departmental approvals, staff responsibilities, procurement, inventory, asset information and management reports. We map which modules belong together, where information originates, who can approve changes and how data moves through the organization.
Choose Between Configuration, Integration and Custom Development
Where existing software meets most requirements, configuration or an API integration may be more efficient than starting again. When your organization has specialized processes or information structures, we can define custom modules or a bespoke ERP architecture. The recommendation should follow real workflows, not a generic feature checklist.
Manage Access, Audit Trails and Reporting
ERP data is operationally sensitive. We design role permissions, approval steps, event records, reconciliations and exports around the responsibilities of actual teams. Reporting should answer management questions rather than simply fill a dashboard with charts.
Plan Migration, Rollout and Support
Before delivery, we identify existing data sources, validation requirements, departments joining the first phase, staff training and support arrangements. Staged deployment makes it easier to test key processes before expanding across the organization.
Frequently asked questions
Can an ERP integrate with M-Pesa or an existing accounting package?
Where suitable APIs, provider permissions and accounting rules exist, we can design the required payment and data connections.
Is a custom ERP always the best option?
No. A configured or integrated existing platform can be the better choice; discovery determines the appropriate approach.