
Most Kenyan businesses run on a patchwork: a spreadsheet for stock, a WhatsApp group for orders, an M-Pesa statement for payments, a notebook for customer balances and one staff member who knows how it all fits together. It works until it doesn’t. When the business grows, that patchwork becomes the bottleneck. This is the complete guide to choosing between software companies in Kenya and getting custom software built: what custom software actually is, when you need it, how a proper project works step by step, what drives the cost, the red flags to avoid, how to pick the right software development agency, a realistic timeline and a practical plan to get started.
The short version: you’re not buying code. You’re buying a system that removes manual work, cuts errors and lets your business grow without hiring more people to push paper. If a software company can’t explain how its system will do that for your business, in plain language, keep looking.
What Software Companies in Kenya Actually Build
“Software company” covers a lot of ground. Some sell ready-made products. Others build custom systems from scratch. Many do a mix. For a typical Kenyan SME, school, clinic, NGO or SACCO, the most common projects are:
- Business management systems: stock, sales, purchasing, customers and reporting in one place.
- Point of sale (POS) systems: for shops, restaurants, pharmacies and hardware stores, often with M-Pesa and receipt printing.
- School management systems: admissions, fees, M-Pesa fee payments, exam results, timetables and parent communication.
- Customer portals and booking systems: letting clients book, pay, track orders or download documents themselves.
- Mobile apps: for customers, field staff, delivery riders or sales teams.
- Integrations: connecting systems you already use, such as M-Pesa, accounting software, SMS gateways, eTIMS-compliant invoicing tools and websites, so data flows without retyping.
- Specialist platforms: such as live audience-voting systems like our own E-TAM audience-voting platform, used for events and shows.
The point of all of these is the same: turn work that people do by hand into work the system does for them.
Off-the-Shelf Software or Custom Software?
Before you approach software companies, decide which you actually need. Both have a place.
When off-the-shelf software is enough
- Your process is standard: basic accounting, payroll, simple invoicing or email.
- A well-known product already fits most of what you do.
- You’d rather pay a subscription than own and maintain a system.
- You need something running this week.
When custom software makes sense
- Your process is what makes you different, and generic tools force you to work around it.
- You’re paying for several subscriptions that don’t talk to each other.
- Staff spend hours a day copying data between spreadsheets, WhatsApp and systems.
- You need local features that international tools handle poorly, such as M-Pesa reconciliation, Kenyan SMS, shilling pricing or county-level reporting.
- You want to own the system and the data, not rent them.
Many businesses end up with a hybrid: off-the-shelf tools for standard jobs, plus custom software or integrations that tie them together. We explored how this gives smaller businesses an edge in our piece on why Kenyan SMEs are losing to bigger competitors and how custom software changes that.
Signs Your Business Needs Custom Software
If three or more of these sound familiar, it’s time to talk to a software development agency:
- You can’t say exactly how much stock you have without someone counting.
- Matching M-Pesa payments to customers or invoices takes hours every week.
- Reports for management or the board take days to put together.
- One staff member is the only person who understands “the system”.
- Customers call to ask questions a portal could answer: balances, order status, results, documents.
- Errors in orders, fees or invoices keep costing you money or goodwill.
- You’ve opened a second branch and the old way of working has started to break.
- You’re turning down growth because the back office can’t cope.
How a Custom Software Project Works, Step by Step
Good software companies in Kenya follow a clear process. If a provider jumps straight to “we’ll start coding on Monday”, that’s a warning sign. Here’s what a proper project looks like.
1. Discovery
The team learns how your business really works: who does what, where data comes from, where things go wrong, and what success looks like. Expect workshops, interviews with staff and a look at your current spreadsheets, forms and tools.
2. Requirements and scope
Everything learned in discovery is turned into a written list of what the system must do, who’ll use it, and what’s included in the first version. This document protects both sides and is the basis of the quote.
3. Design and prototyping
Before any real code, you see screens: how staff will log in, add an order, run a report or take a payment. Clickable prototypes let you catch problems when they’re cheap to fix.
4. Development in stages
The system is built in short cycles, with working features shown to you regularly. You test as it grows instead of waiting months to see anything.
5. Testing
The software is tested against real scenarios: busy days, wrong inputs, failed M-Pesa payments, slow internet and the staff member who’ll click everything. Security testing protects your data and your customers’ data.
6. Data migration
Your existing data, such as customers, products, balances and history, is cleaned and moved into the new system. This step is often underestimated and deserves its own plan.
7. Training and launch
Staff are trained on the system before go-live, ideally with simple guides they can refer back to. Many projects launch to one branch or team first before rolling out everywhere.
8. Support and improvement
After launch, the system needs bug fixes, updates, security patches and new features as the business changes. Agree this support in writing before the project starts.
The Software Project Checklist
Use this before you sign anything:
- ☐ We know the exact problem the software will solve and how we’ll measure it
- ☐ We’ve named one internal owner for the project
- ☐ The scope for version one is written down and agreed
- ☐ We’ve seen designs or a prototype before development starts
- ☐ We know who owns the source code, the data and the hosting accounts
- ☐ The contract covers payment milestones tied to delivered features
- ☐ There’s a plan for moving our existing data
- ☐ Staff training is included
- ☐ Support, maintenance and response times after launch are agreed
- ☐ Backups and security are covered, including how customer data is protected under Kenya’s Data Protection Act
What Drives the Cost of Custom Software in Kenya
Ask five software companies for a quote on a vague idea and you’ll get five wildly different numbers. That’s because cost depends on detail. The main drivers are:
- Scope and complexity: the number of features, user types, workflows and reports.
- Integrations: M-Pesa, SMS, email, accounting tools, eTIMS-compliant invoicing systems, banks’ or partners’ systems, and existing software each add work.
- Platforms: a web system, an Android app, an iOS app, or all three.
- Design: a simple functional interface versus a polished, customer-facing product.
- Data migration: how much existing data needs cleaning and moving.
- Security and compliance: handling payments, health records, student data or personal information needs extra care.
- Hosting and infrastructure: cloud hosting, on-premise servers, or a mix.
- Support and maintenance: ongoing fixes, updates and new features after launch.
- The team: experience, seniority and whether you’re getting a full team or one developer.
The best way to control cost is to start with a focused first version that solves the biggest problem, then add features once it’s proving its worth. Ask for the build cost and the yearly running cost separately, so there are no surprises.
Common Mistakes When Buying Software
- Starting with features instead of problems. “We want a dashboard” isn’t a brief. “We spend two days a month reconciling fees” is.
- Trying to build everything at once. Huge first versions run late, cost more and are harder to adopt.
- Leaving staff out. The people who’ll use the system every day know where the real problems are. If they’re not consulted, they won’t use it.
- Choosing on price alone. The cheapest quote often leaves out testing, data migration, training or support, which come back as extra costs later.
- No internal owner. Someone on your side has to make decisions, answer questions and test features quickly.
- Skipping the contract details. Ownership of the code and data, payment milestones and support terms should never be assumed.
Red Flags When Choosing a Software Development Agency
- They quote a fixed price before understanding your process.
- They can’t show you working systems they’ve built, or let you speak to past clients.
- They won’t confirm in writing that you own the source code and data.
- They host everything on their own accounts with no handover plan.
- There’s no mention of testing, documentation or training.
- They promise to deliver a complex system in an unrealistically short time.
- Communication is slow and vague before you’ve even signed. It won’t improve afterwards.
- Payment is demanded mostly upfront, not tied to delivered milestones.
How to Choose Between Software Companies in Kenya
Shortlist three providers and put the same questions to each:
- What similar systems have you built, and can I see them working?
- Can I speak to two clients you’ve worked with?
- How will you learn how our business works before you quote?
- Who will actually work on our project, and who is our main contact?
- How often will we see working software during the build?
- Who owns the source code, the data and the hosting accounts?
- How do you handle changes to the scope once the project has started?
- How do you test, and how do you protect our data?
- What happens after launch: support, response times, updates and costs?
- What would you build first if we could only afford one phase?
The last question is the most revealing. A good software development agency will tell you what to leave out. A poor one will try to sell you everything.
Look for a team that understands both technology and business. Software that’s technically impressive but doesn’t fit how your staff work will gather dust. It also helps when the same team can handle your website, hosting and marketing, so your systems and your customer-facing presence work together. Our approach to digital strategy and consulting starts with exactly that question: what should technology actually do for this business?
How Custom Software Connects to Your Website and Marketing
Software doesn’t live in isolation. The best results come when your systems connect to your customer-facing channels:
- Your website takes orders or bookings that drop straight into your management system. Our guide to web design in Kenya covers how to plan a site that does real work for the business.
- Your online shop updates stock automatically when an order comes in. See our complete guide to building an ecommerce website in Kenya.
- Customer data from your system powers targeted marketing, follow-ups and loyalty offers. Our guide to hiring a digital marketing agency in Kenya explains how good agencies use that data.
- Your hosting, domain and email are set up properly, so the whole system stays secure and online. We covered why that matters in your domain, your hosting, your reputation.
Custom Software by Sector: What Kenyan Organisations Commonly Need
The right system looks different in every sector. These are the patterns we see most often.
Schools and colleges
Fee collection is usually the first pain point. Parents pay by M-Pesa from different numbers, with references that don’t match admission numbers, and the bursar spends days reconciling. A school management system can issue each learner a payment reference, confirm M-Pesa payments automatically, send fee balances by SMS and produce report forms and class lists without retyping.
Clinics, pharmacies and health providers
Patient records, appointments, stock of medicines, billing and insurance claims all need to connect. Because health data is sensitive personal data, security, access controls and audit trails matter as much as features.
Retail, wholesale and distribution
Stock across branches, sales reps in the field, credit customers and supplier orders. A POS and stock system that syncs between branches, takes M-Pesa at the till and shows real-time stock stops the classic problem of selling items you don’t have, or holding stock you can’t find.
NGOs, SACCOs and membership organisations
Member registers, contributions, beneficiary tracking, field data collection and donor reporting. Systems that let field staff capture data on a phone, even with poor connectivity, and produce reports at the click of a button save weeks of work at reporting time.
Events, media and entertainment
Ticketing, accreditation and live audience interaction. Voting platforms, for example, need to handle huge spikes of traffic in a few minutes, count accurately and display results live, which is a very different engineering challenge from a business back office.
Cloud or On-Premise: Where Should Your Software Live?
Software companies in Kenya will usually offer two hosting options, and the choice affects cost, reliability and access.
- Cloud-hosted: the system runs on servers in a data centre and staff log in through a browser or app from anywhere. You avoid buying and maintaining servers, backups can be automated, and multiple branches share one system. It needs a reliable internet connection at each site.
- On-premise: the system runs on a server in your own building. It can keep working when the internet goes down and keeps data physically in your hands, but you’re responsible for the hardware, power backup, security and backups.
- Hybrid: some systems run locally and sync to the cloud when a connection is available, which suits branches or field teams with patchy connectivity.
Whichever you choose, ask who manages backups, how quickly the system can be restored after a failure, and what happens to your data if you ever change providers.
A Realistic Timeline for a Software Project
Every project is different, but a typical SME custom software project moves through these phases:
- Discovery and requirements: understanding the business and agreeing scope.
- Design and prototype: screens and flows you can click through and approve.
- Development: building in short cycles, with regular demos.
- Testing and data migration: real scenarios, real data, fixing what breaks.
- Training and launch: often to one team or branch first.
- Support and phase two: fixes, improvements and the next set of features.
A small integration or a simple internal tool moves much faster than a full management system with mobile apps. A good provider will give you a phased timeline after discovery, not a guess on the first call.
A Practical Plan to Get Started
Step 1: Map the pain (week 1)
List the three most time-consuming or error-prone processes in your business. For each, write down who does it, how long it takes and what goes wrong.
Step 2: Define success (week 1)
Decide what better looks like: hours saved, errors reduced, faster reporting, fewer customer calls. This is how you’ll judge the project.
Step 3: Gather what you have (week 2)
Collect the spreadsheets, forms, receipts and reports you use now. They show a software team more than any description.
Step 4: Shortlist and question (weeks 2 to 4)
Speak to three software companies, ask the ten questions above and compare their thinking, not just their prices.
Step 5: Start with a paid discovery phase
For anything beyond a simple tool, a short paid discovery phase produces a clear scope, designs and an accurate quote. It’s the cheapest insurance you’ll buy against a project that goes wrong.
Step 6: Build version one, then grow
Launch the smallest version that solves the biggest problem, get staff using it, measure the result, then plan phase two.
Frequently Asked Questions
How much does custom software cost in Kenya?
It depends on scope, integrations, platforms, data migration, security needs and support. A simple internal tool and a multi-branch management system with mobile apps are very different projects. A proper discovery phase is the only way to get an accurate quote, and you should always ask for build and running costs separately.
Should I hire a freelancer or a software development agency?
A freelancer can suit a small, well-defined job. For business-critical systems, an agency gives you a team covering design, development, testing and support, so the project doesn’t stop if one person becomes unavailable.
Can custom software integrate with M-Pesa?
Yes. Systems can trigger M-Pesa payment prompts, receive payment confirmations and match them automatically to customers, invoices or fees, which removes much of the manual reconciliation many Kenyan businesses still do by hand.
Who should own the source code?
You should, or at minimum you should have a clear written licence and full access to your data. Agree ownership of the code, data and hosting accounts in the contract before work starts.
Do I need a mobile app or a web system?
Many businesses only need a web system that works well on phones. A dedicated app makes sense when customers or staff use it daily, need offline access or need phone features such as the camera or GPS.
Build Software That Works the Way Your Business Works
The right software turns a business that depends on manual effort into one that runs on systems. The wrong software becomes another tool nobody uses. The difference comes down to choosing a partner who learns how your business works, builds in stages, tests properly and stays with you after launch.
Ready to replace the spreadsheets, notebooks and WhatsApp groups with a system built for your business? See our software development and solutions, look through our portfolio of projects, call or WhatsApp us on +254 717 806 693, email hello@twelvecitydigital.com, or book a consultation with Twelvecity Digital.
Disrupt. Build. Dominate.
