ERP Selection Consultant, Kenya

What Kenyan shortlists look like at different sizes

A Kenyan ERP shortlist should follow the shape of the business, not the vendor who called first. I start from your branches, product range, customers, entities and the people who will administer the system.

• Smaller traders and service firms often run on QuickBooks, Sage or Zoho Books with spreadsheets alongside. Their real choice is frequently between strengthening that setup and moving to a suite such as Zoho with inventory and CRM included.
• Distributors and manufacturers with depots usually compare Odoo, ERPNext and locally developed ERP products that bundle point of sale and eTIMS handling.
• Regional groups and subsidiaries of international companies often add Dynamics 365 Business Central or the parent company's standard, then test whether Kenyan needs are met.
• Programs and grant-funded organizations need donor and grant tracking, which narrows the field quickly.

A locally built system can be a sensible choice when its vendor is stable and its support is strong; an international platform brings a wider ecosystem but relies on connectors for Kenyan features. I score both on the same evidence. Platform notes for Kenya sit on the Odoo in Kenya and Zoho Books in Kenya pages.

The demo script every Kenyan bidder runs

Standard demos show clean sales orders and dashboards. The scenarios that matter in Kenya are messier, so I put them in the script and ask every bidder to run them live with your sample data:

1. Issue a sales invoice, send it through eTIMS and show the validated details printed on the document.
2. Raise a credit note against that invoice and show it transmitted correctly.
3. Simulate a failed transmission and show what the user sees, how the document is held and how it is retried.
4. Receive an M-Pesa payment that covers part of an invoice with a phone number as the only reference, then match it.
5. Record a customer who deducts withholding VAT and later sends the certificate.
6. Invoice an export customer in dollars and show the shilling posting and exchange difference.
7. Capture an order at a depot with no connection, then synchronize it when the link returns.

Your process owners rate every step by how it was achieved: out of the box, through settings, with an add-on or only with development. When a bidder leans on a third-party connector, I record who built it and who maintains it. eTIMS rules and integration options change, so confirm current requirements with your tax advisor and KRA guidance before design is signed. Scores feed the weighted model described under ERP evaluation.

Judging Kenyan implementers, not just products

In Kenya, different firms offering the same platform can deliver very different projects. The market includes established implementers with several teams, small specialist firms and independent developers. Each can be the right choice, but each carries a different kind of risk.

Before proposals are compared, I look at the implementer behind each one. How many people know your platform well enough to support it? Who built the eTIMS and M-Pesa connectors they propose, and who updates them when KRA or the payment provider changes something? Where does the source code for any custom work live, and can you take it to another firm if the relationship ends? How do they test, and how much testing do they expect your staff to do?

Reference calls are worth the time. I ask the implementer for customers of similar size and industry, then run structured conversations about delivery, support response, change requests and what those customers would insist on if they started again. Small firms with a single key developer are not ruled out, but the contract then needs stronger protection on code access and documentation.

If proposals are already on your desk, the freelance ERP consultant page for Kenya explains how a bounded review works, and the vendor proposal review page covers the method.

Hosting, connectivity and data protection questions

A Kenyan ERP decision has to account for where users actually work. Head office may have reliable fiber, while depots, farms and upcountry branches depend on mobile data and backup power. I ask each bidder how the system behaves when a branch loses its connection, which tasks continue offline on mobile apps and how data synchronizes afterwards.

Hosting choices follow from that. A cloud service hosted abroad, a local data center and an on-premise server each have trade-offs in access, backup, support and cost. Kenya's data protection law also governs how personal data about customers, staff and agents is handled, and some organizations have registration or reporting duties under it. I collect written answers from every vendor on data location, subprocessors, access logging, backups and exit, then pass them to your legal advisor and whoever owns data protection. I do not give legal opinions; I make sure the questions are asked before signature.

Integration is the other half of this. eTIMS, M-Pesa, bank files and any point-of-sale or route-sales app all need a connection that copes with outages, queues transactions and alerts someone when something fails. I score each bidder on how clearly it explains those routes. The ERP consultant page for Kenya covers the wider design questions.

Contract terms that protect a Kenyan buyer

The last step of selection is making sure the contract reflects what you tested. Proposal, scope document and support terms are read against what bidders actually demonstrated and against your requirement list, and the gaps become a negotiation list.

• Pricing currency. Licenses and services are sometimes quoted in dollars while your books run in shillings, which moves cost with the exchange rate. That exposure belongs in the comparison.
• Connector responsibility. The contract should say who updates the eTIMS and M-Pesa connections when requirements change, and whether that is covered by support or billed separately.
• Code and documentation. Custom work should be documented and accessible to you, with clear terms if you change implementer.
• Migration and testing. Data cleansing, trial loads and user testing should be scoped explicitly, not assumed to fall on your staff.
• Support after go-live. Response expectations, coverage across branches and how issues are logged should be written down.

Your legal advisor owns the final drafting. After signing, delivery is held to the same promises through my implementation oversight for Kenyan projects. The Kenya overview explains the wider remote engagement, which runs during hours Kenya and India share.