Software · 8 min read
Custom Software Development in Kenya: Cost, Timeline and Vendor Checklist
Custom software makes sense when off-the-shelf tools force your team into workarounds. This guide shows what drives the cost in Kenya, what stretches the timeline, and how to score vendors before you sign.
Groow editorial team · Reviewed
Key takeaways
- Buy custom software only when a ready-made tool can't fit a process that makes or saves you money.
- M-Pesa payments, KRA eTIMS invoicing and data protection rules often add more scope than the screens themselves.
- Kenyan approvals have their own lead times, such as Safaricom go-live and a data protection impact assessment filed 60 days before high-risk processing.
- Score vendors on questions they answer in writing, and own your code, accounts and M-Pesa credentials from day one.
Custom software in Kenya: the short answer
Custom software is a system built for your business alone, rather than a product you rent. In Kenya, it is worth paying for when your process is unusual or when M-Pesa and KRA eTIMS must work inside one flow. It also helps when you serve customers on basic phones.
The cost depends on how many user types, integrations and reports you need, not on the number of screens. The timeline depends on how fast you decide, plus outside approvals from Safaricom, KRA and sometimes the data protection regulator.
Below you'll find a cost-driver table, a realistic phase plan, a vendor scorecard and the contract questions to settle first.
Who needs custom software, and who doesn't
Most small firms should start with ready-made tools. Accounting, payroll and simple stock systems are mature and cheap to rent. You only move to a custom build when the ready-made route starts costing you more than it saves.
Watch for these signals before you decide to build:
- Your team re-types the same data between M-Pesa statements, spreadsheets and your invoicing tool every day.
- You run a process no product supports well, such as a SACCO loan workflow, a school fee plan or field agents collecting cash.
- Your customers or agents use feature phones, so you need USSD or SMS rather than an app.
- You pay per user for several tools, and the total now rivals what a focused system would cost.
- You want to sell the software itself, for example as a subscription (SaaS) product for other businesses.
If only one of these applies, try configuring an existing tool first. Custom software pays off when two or three are true at once.
What people search for
Our analysis of Google Ads keyword data shows about 30 searches a month for “custom software” in Kenya, with low advertiser competition and top-of-page bids of up to €9.52.
What drives the cost of custom software in Kenya?
A quote is mostly people multiplied by time. Anything that adds decisions, testing or outside approvals adds time. The table shows the drivers that move Kenyan quotes the most, and how to keep each one in check.
Budget in shillings, but check which costs are really in dollars. Cloud hosting, app store accounts and many software tools bill in US dollars, so a weaker shilling raises your running costs. Ask each vendor to list those items separately.
Here is an illustrative example. A private school wants parents to pay fees by M-Pesa and see balances online. Version one needs three roles: parent, bursar and head teacher. It also needs STK push payments, automatic receipts and one fee-balance report.
Now add eTIMS invoices, a USSD menu for parents without smartphones and five years of old fee records. The screens barely change, but the testing, approvals and data cleaning can double the effort. That is why two quotes for "a school fee system" can differ so much.
| Cost driver | Why it adds cost | How to keep it down |
|---|---|---|
| Number of user types | Each role needs its own screens, permissions and tests | Launch with the two or three roles that matter most |
| M-Pesa (Daraja) payments | Callbacks, failed payments and reconciliation all need handling | Start with one payment type, such as STK push, then add payouts |
| KRA eTIMS invoicing | System-to-system links need testing with KRA before going live | Ask if a KRA-certified integrator can connect your system |
| USSD or SMS channel | Separate menus, a shortcode and telecom partners | Keep USSD menus short; put complex tasks in the web app |
| Low-end Android and patchy data | Offline storage and sync logic take extra work | Decide early which tasks must work offline |
| Moving old data | Cleaning years of spreadsheets is slow | Migrate only active records at first |
| Reports and dashboards | Every custom report is small, but they add up | Agree on five reports for launch, not twenty |
| Data protection work | Consent, access logs and impact assessments | Build them in from the first sprint, not at the end |
Which Kenyan integrations and rules belong in the brief?
Three local items change scope more than anything else. Put them in your brief so every vendor quotes for the same thing.
M-Pesa. Safaricom's Daraja portal is how software connects to M-Pesa. Safaricom's own FAQ says a developer needs a Lipa na M-PESA shortcode to register, and Daraja offers a sandbox for testing. The paybill or till should be in your company's name, not the vendor's.
KRA eTIMS. KRA says all persons in business must onboard eTIMS and issue electronic tax invoices. If your system raises invoices, it can link to eTIMS through an online (OSCU) or virtual (VSCU) sales control unit. You can self-integrate after KRA certification, or use a KRA-verified third-party integrator.
USSD. A USSD menu needs a shortcode and a telecom partner to run it. Ask each vendor who will hold the code, who pays its fees and how long setup usually takes. Keep the menu to a few short steps, because sessions time out.
Data protection. Under the Data Protection Act 2019, you may not act as a data controller or processor unless registered with the Office of the Data Protection Commissioner (ODPC). The ODPC exempts firms only if turnover is below KES 5 million and staff are fewer than ten. Some sectors, such as health, education and financial services, must register whatever their size.
The Act also asks for data protection by design (section 41). In plain terms, privacy controls are part of the build, so ask vendors how they handle consent, access rights and deletion.
How long does a custom software project take?
Timelines slip in Kenya for the same reasons they slip anywhere: slow decisions and scope that keeps growing. Local approvals add a few fixed waits you can plan around.
Moving from the Daraja sandbox to live M-Pesa payments is a separate go-live step with Safaricom. KRA eTIMS integrations go through testing and certification. If a data protection impact assessment is needed because processing is high-risk, the Act says the report must be submitted 60 days before that processing starts.
Start these tasks in the first weeks, alongside design. Don't wait until the code is finished. A vendor who leaves Safaricom or KRA steps to the end is handing you a delay.
- Fast: you have one clear process, one decision-maker and data ready to move.
- Average: two or three departments give input and one outside integration is needed.
- Slow: several integrations, legacy data to clean and approvals that start late.
The biggest speed-up is free. Name one person on your side who can approve screens and answer questions within a day or two. Projects without that person often wait weeks for feedback that takes an hour to give.
Delivery phases for custom software in Kenya
Good vendors break the work into phases, each with something you can see and approve. Pay by phase, not by calendar month, so money follows progress.
- 1Discovery: interviews with the people who will use the system, a process map and a written scope with a priced list of features.
- 2Clickable prototype: screens you can test on the phones your staff and customers really use, before any code is written.
- 3Build in short cycles: working features every two weeks or so, shown to you in a live demo.
- 4Integrations: Daraja sandbox, eTIMS test environment and any USSD shortcode set up in parallel with the build.
- 5User testing: your own staff try real tasks with real data, and every bug is logged in a shared tracker.
- 6Launch: move payments and invoicing to live, migrate data and train staff, ideally in Swahili and English if your team works in both.
- 7Support: a fixed period of bug fixes, then a monthly plan for hosting, updates and small changes.
Ask for the prototype before you commit the full budget. It is the cheapest point to discover that a workflow was misunderstood.
Vendor scorecard for Kenyan software companies
Send the same written brief to three vendors. Score each answer from 1 to 5, multiply by the weight and add up. The weights below are our suggestion; change them to match your risks.
To see how a build partner approaches this, our custom software development services page lists what a typical engagement includes. Our guide to building software for your business explains the options.
| Criterion | Weight | What a strong answer looks like |
|---|---|---|
| Understanding of your process | ×3 | They restate your problem in their own words and challenge weak points |
| M-Pesa and eTIMS experience | ×3 | They name the Daraja products and eTIMS route they would use, and why |
| Data protection approach | ×2 | They explain consent, access control and how they support your ODPC duties |
| Delivery plan | ×2 | Phases, demos and who from their team you'll speak to each week |
| Ownership and exit | ×2 | You own the code, hosting accounts and credentials from day one |
| Support after launch | ×2 | Clear response times and a monthly price in KES |
| References you can call | ×1 | Past clients who agree to speak with you, not just logos |
Contract questions to settle before you sign
Most disputes come from things the contract left vague. Settle these in writing before any deposit leaves your account.
- Who owns the source code, designs and documents? It should be you, once each phase is paid.
- Whose name are the cloud, domain, app store and Daraja accounts in? They should be yours, with the vendor invited as a user.
- How are changes priced? Ask for a written change request with a cost and time impact before any extra work starts.
- What does "done" mean for each phase? Agree on acceptance tests you can run yourself.
- Which currency and payment milestones apply? Link payments to approved phases, and state which costs are billed in dollars.
- What happens to personal data? The vendor usually acts as your data processor, so the contract should cover security, breach notice and deletion.
- What is the warranty period for bugs, and what does support cost after it ends?
- How do you leave? Ask for a handover plan, full documentation and a notice period.
- Who fixes things when M-Pesa or KRA change their systems? Agree whether updates to integrations fall under support or count as new work.
Next steps before you ask for custom software quotes
Write one page that describes the problem, the people who will use the system and the integrations you need. Add the reports you check every week. That page gives every vendor the same starting point, so their quotes become comparable.
Then check your ODPC registration status, confirm your paybill or till is in the company's name and ask your accountant how invoices reach eTIMS today. Those three answers will shape the scope more than any feature list.
Custom software is a long-term asset, so choose the partner you can work with for years. Our Kenya market page shows how we support businesses there. If you're ready, scope a custom software project with a written brief and three comparable quotes.
Frequently asked questions
Is it cheaper to hire freelancers than a software company in Kenya?
Freelancers usually charge less per hour, and a good one can be the right choice for a small, well-defined tool. The risk grows with the project. A system with payments, tax invoicing and several user types needs design, testing and long-term support that one person rarely covers alone. If you use freelancers, keep the code and accounts in your own name.
Can we start with a small version and grow it later?
Yes, and it is usually the safer route. Build the smallest version that solves the most expensive problem, put it in front of real users, then fund the next phase from what you learn. Ask the vendor to design the data structure with later phases in mind so you don't pay to rebuild it.
Should the vendor host the system for us?
They can manage it, but the hosting account should belong to your company. That way you keep access if the relationship ends. Ask where the servers are located and include that in your records of processing, since data protection law asks you to know where personal data goes.
Do we need a mobile app, or is a web app enough?
Many business systems work well as a mobile-friendly web app, which avoids app store reviews and runs on most phones. A native app makes sense when you need offline work, the camera or push notifications. If your users have basic phones, USSD or SMS may matter more than either.
How do we protect ourselves if the vendor disappears mid-project?
Pay by approved phase, keep the code in a repository your company owns and ask for documentation at each milestone. With those three habits, another team can pick up the work. Without them, you may have to start again.
Sources
- Daraja developer portal — Safaricom
- M-PESA business channels and portals: frequently asked questions — Safaricom
- Learn about eTIMS — Kenya Revenue Authority
- eTIMS system to system integration — Kenya Revenue Authority
- Frequently asked questions (registration of data controllers and processors) — Office of the Data Protection Commissioner
- The Data Protection Act, No. 24 of 2019 — Republic of Kenya (copy hosted by KenTrade)