Repeated data entry
Customer, order, or payment details are copied between spreadsheets, email, and separate applications.
Custom business systems for Kenyan teams
ERP software and workflow automation for Kenyan businesses
When orders, stock, approvals, payments, and customer records sit in separate tools, staff end up copying data and chasing updates. Statum builds business systems that connect those steps around your actual process. The scope can be one well-defined workflow, a customer or staff portal, or a broader ERP platform.
Before choosing software
Find where the work gets stuck.
01 Follow a real request from start to finish.
02 Note where people re-enter data or wait for approval.
03 Decide which records and systems must connect.
04 Choose a first release the team can test in daily work.
Signs a better system may help
Where spreadsheets and disconnected tools start to cost time.
A team does not need a custom ERP just because it has grown. It may be time to review the process when the same information is entered in several places, approvals depend on follow-up messages, or staff cannot tell which record is current.
Unclear approvals
Requests wait in inboxes or chats, and it is difficult to see who approved a change or what is still pending.
Records that do not agree
Finance, operations, and sales work from different figures for stock, balances, invoices, or customer history.
Reports that take too long
Someone has to combine several exports by hand before managers can review activity or exceptions.
Workarounds for important rules
Staff maintain side spreadsheets because the current software cannot represent a real approval or business rule.
No clear owner for the next step
A hand-off between teams is easy to miss, so requests sit without an assigned person or clear deadline.
Business system modules
Choose the modules your operation actually needs.
An ERP can bring related work into a shared system, but it does not have to replace every tool. We agree which records should be managed in the new system, which can stay where they are, and how the hand-off between them should work.
Customers, orders, and service
Keep account details, enquiries, orders, service requests, and follow-up history connected so a team can pick up the conversation without searching several systems.
Inventory and purchasing
Track items, locations, stock movements, supplier details, purchase requests, and reorder decisions with a record of what changed.
Billing and payment records
Link invoices, receipts, payment references, and outstanding balances to the customer or transaction they belong to.
Approvals and internal requests
Route expenses, purchases, discounts, leave, or operational requests according to agreed roles and approval limits.
Staff and field operations
Give office and field teams a shared view of assigned work, status updates, required details, and issues that need a supervisor.
Management reporting
Build reports from operational records, with agreed definitions for measures such as outstanding work, stock position, or payment status.
The right design depends on how the organisation works. A school, distributor, property manager, and service company may all need approvals and reports, but the records and rules behind them are different.
Choosing an approach
Custom ERP or an existing product?
A custom build is not automatically better. Established accounting, payroll, or CRM products can be a sensible fit when their workflows match your needs. The decision should account for the cost of configuration, workarounds, integrations, data access, and ongoing ownership.
Use an existing product when
Your processes are common, the product covers required controls, and its integration and reporting options are acceptable.
Consider a custom system when
A business-critical workflow depends on rules the product cannot handle, or repeated workarounds are causing errors and delays.
Consider a connected approach when
A current finance or payroll tool works well, but your team needs a separate operational system that shares selected records with it.
Map one real process and compare the options against it. That gives the team a practical basis for deciding what to keep, configure, connect, or build.
System integrations
Connect the services around the workflow.
A business system may need to exchange information with M-Pesa, SMS providers, accounting software, a CRM, or an older internal application. Each integration needs a clear answer about which system holds the final record, which fields move, and what happens when an update fails or arrives late.
For example, a payment workflow should distinguish a payment request from a confirmed transaction, retain the provider reference, and flag unmatched payments for follow-up. The exact setup depends on what the provider supports and who handles reconciliation.
Explore API integrationQuestions to settle for each connection
- What moves? Identify the records and fields that need to pass between systems.
- Where is the final version kept? Decide where a change is made and how other systems receive it.
- What if an update fails? Make retries, duplicates, delays, and manual review visible.
- Who supports it? Agree who manages credentials, provider changes, alerts, and reconciliation.
Delivery and rollout
Build in stages, with the people who do the work.
The people handling orders, approvals, payments, or stock know where the exceptions are. Their input helps turn an initial process map into rules the software can support and the team can verify.
See custom software delivery1. Map the process
Follow a real request through its steps. Record who acts, what information is needed, where approval happens, and what can go wrong.
2. Agree the first release
Choose the workflow and user groups to include. Set boundaries for integrations, reports, and later work so the first release has a clear purpose.
3. Design records and access
Define the key records, their relationships, permissions, status changes, and the reports staff need to carry out their roles.
4. Build and review
Review working software with the people who will use it. Test normal cases, exceptions, permissions, integrations, and the information shown in reports.
5. Prepare rollout and handover
Plan data transfer, user guidance, deployment, support responsibilities, and checks for the first days of use.
Data and permissions
Plan the records and controls before go-live.
Moving to a new ERP is also a records exercise. Old spreadsheets may contain duplicates, inconsistent codes, or balances that need review. A controlled sample migration helps uncover those issues before they affect day-to-day work.
Agree these points with the project team
- Which system owns each important customer, product, payment, or stock record.
- Which historical information must move and which should remain available in the old system.
- Who can view, create, approve, export, or correct each type of record.
- How changes and failed transactions will be reviewed and resolved.
- Who maintains user access, backups, support, and provider credentials after launch.
Prepare for a useful first conversation
Bring the real process, not just the software wish list.
A few practical examples make it easier to understand the work and identify what a first release should cover.
A sample spreadsheet, form, invoice, or report the team uses today.
The people involved and the decisions each person is allowed to make.
A recent example where a request, payment, or record needed manual follow-up.
The names of current systems and any API or data export documentation you have.
Related work
See the kind of systems this work can include.
See examples of a school management system and an M-Pesa payment integration. Each case study explains the records, workflow decisions, and operational details involved without publishing client names.
ERP project questions
Frequently asked questions
How much does custom ERP software cost in Kenya?
The cost depends on the modules, integrations, data migration, user roles, and reporting the system needs. We first clarify the workflow and agree a defined scope so the estimate reflects the work involved.
Should we customise an existing ERP or build a new one?
If an existing product handles most of your work, configuration or a focused integration may be the better choice. A custom build is worth considering when important rules cannot be represented cleanly, or when workarounds have become a source of errors. We can compare the options before recommending a direction.
Can an ERP connect to M-Pesa, SMS, or accounting software?
It can, when the provider offers a suitable integration route and the required access is available. The design should specify which system keeps the official record and what happens when a payment callback is late, a message fails, or two records do not match.
Can we start with one module or workflow?
Yes. A first release can focus on one department or process, such as approvals, stock movements, or payment reconciliation. The scope should still account for the records and integrations that later modules will depend on.
What happens to data in spreadsheets and existing tools?
We identify the current sources, agree which records should move, map the fields, and test a sample import. Before a full migration, the team should check record counts, balances, duplicates, and any history that must remain available.
How do you control access to business records?
Access is planned around job responsibilities. The system can separate permissions by role and record type, keep a history of important changes, and limit sensitive information to the people who need it. Backup, retention, and review requirements should be agreed for the organisation.
How long does ERP implementation take?
There is no reliable timeline based on the word ERP alone. The number of workflows, integrations, condition of the data, and time available for review all affect delivery. Once the scope is understood, we can set phases, review points, and acceptance criteria.
Need to make a business process easier to manage?
Tell us what your team does today, where work slows down, and which systems are involved. We can help you assess whether to configure, integrate, or build a business system for the job.
Discuss your ERP projectTalk to the team
Choose the contact that best matches your question.
