12 Questions to Ask Before Choosing an ERP in Kenya

The proposals arrive on the same afternoon. One is two pages long with a single number at the bottom. Another runs to forty pages and somehow never says what happens to your data if you leave. A third looks perfect until you notice the licence fee is per user, per year, and goes up every January.
Choosing an ERP is rarely about features. Most systems can post a journal and print an invoice. What matters more is the scope, the assumptions, the people and the small print. These are the twelve questions we would ask if we were in your seat.
Cost and Commitment
1. What will this cost over three years, not just year one?
Ask for every recurring cost in writing: licences, hosting, support, and any annual increases. Listen for a clear split between one-time costs and monthly or annual ones. Be wary of a low first-year price that hides per-user licences which grow every time you hire.
2. Is the price fixed, and what are the assumptions behind it?
Every quote rests on assumptions: how many users, items, locations and companies; how much data moves across. Good vendors write these down so you can confirm or correct them. Without them, a fixed price is only fixed until the first disagreement.
3. What is not included?
Customisation, integrations, extra training days, travel and third-party fees are the usual exclusions. A vendor who lists them clearly is easier to work with than one who discovers them halfway through the project.
Your Data
4. Who owns our data, and how do we get it out?
The answer you want is short: it is your data, and you can take a full copy at any time, including if you leave. Ask what format it comes in and whether another provider could run it. With open-source systems such as ERPNext, any capable provider can host your database, which keeps everyone honest.
5. What exactly will be migrated?
Opening balances only? Current-year monthly balances? Full transaction history? Customer and supplier lists with KRA PINs? Each option has a different cost. Agree it upfront and agree who cleans the data, because migrating messy records only moves the mess.
6. Where will the system run, and what happens when the internet goes down?
Cloud, on-premise or hybrid each suit different businesses. Ask how backups work, where copies are kept, and how your team keeps working during an outage. If a vendor offers only one option, ask why it is right for you specifically.
Ask Us These Questions
We'll answer all twelve in writing, with an itemised quote and every assumption listed.
Request an Itemised QuoteKenyan Compliance
7. How is eTIMS handled, and who is responsible for what?
Connecting a business system to KRA's eTIMS involves an approved integration. Ask who provides it, who supports it when an invoice is rejected, and how its fees are charged. A clear answer names each party's role: your team, the ERP vendor, the integrator and KRA.
8. Who updates payroll when the law changes?
PAYE bands, NSSF limits, SHIF and the Housing Levy have all changed in the last few years, and they will change again. Ask whether updates are included in support, how quickly they are applied, and whether you can see the rules the system is using.
The Project
9. Who will actually do the work?
Meet the people who will configure your system and train your team, not only the person who sold it. Ask how many other projects they are running at the same time as yours.
10. What does the plan look like, and when do we go live?
A good plan has dates, owners and sign-off points. Ask when they recommend going live and why. For most Kenyan businesses, the start of the financial year is cleanest: payroll begins with the PAYE year and opening stock comes from the year-end count.
11. How much customisation are you proposing?
Custom code can be useful, but every piece of it has to be maintained through future upgrades. Prefer a vendor who shows how standard features cover your process first, and prices anything custom separately so you can decide.
12. What happens after go-live?
Ask what support covers, how you raise an issue, how fast they respond, and whether there is a named person who knows your setup. The first month-end close on a new system is where support matters most.
Red Flags
- A single number with no breakdown or assumptions.
- Vague answers about data ownership or exporting your data.
- Claims that compliance is handled with no explanation of how, or by whom.
- Pressure to sign before you have seen the system set up for your business.
- Heavy customisation proposed before standard features have been explored.
Before You Send Your Request
Vendors can only quote accurately on what they know. Include the number of system users, employees on payroll, legal entities, currencies, stock items and locations, your current system, the modules you need, and your target go-live date. Rough figures are fine. The more you share, the more comparable the quotes will be.
To see how we answer these questions, read how we implement, what's in our quotes, and where your system can run.