Custom Business Software vs Spreadsheets: When to Switch (2026)

Almost every Kenyan business runs on spreadsheets at some point. They are cheap, flexible and everyone knows how to use them. For a small team they are often the right tool.

The trouble starts as the business grows. Three people edit the same file. Someone saves a copy on their laptop. Payments arrive by M-Pesa and somebody types them in at the end of the week. Before long, nobody is sure which version of the numbers is correct.

This article explains when spreadsheets stop being enough, what the alternatives are, what custom software costs and how to make the switch without disrupting the business.

Signs you have outgrown your spreadsheets

None of these on its own means you need new software. Three or four together usually do.

• Version confusion. Files called "Stock FINAL v3 (2)" exist, and people argue about which one is right.
• Re-typing. The same information is entered in more than one place: an order in a WhatsApp chat, then a spreadsheet, then an invoice.
• Manual payment matching. Someone spends hours each week matching M-Pesa or bank statements to customers or invoices.
• No audit trail. When a number changes, you cannot tell who changed it, when or why.
• Access problems. Everyone with the file can see everything, including salaries, margins or customer details they should not see.
• Reports take days. Month-end means rebuilding figures from several files before you can answer simple questions.
• Key-person risk. One person understands how the workbook works, and things stall when they are on leave.

What spreadsheets do well

It is worth being fair. Spreadsheets are excellent for one-off analysis, budgets, forecasts and trying out a new process before you know exactly how it should work. Many businesses that move to proper software still use spreadsheets for analysis; they just stop using them as the system of record. The aim is not to ban Excel. It is to stop running daily operations on it.

Your three options

1. Off-the-shelf software

Ready-made software, usually paid monthly, covers common needs such as accounting, point of sale, payroll and customer management. It is quick to start and the cost is predictable. The downside is fit: you adapt your process to the software, and features that matter in Kenya, such as M-Pesa reconciliation, may be missing or need a third-party add-on.

2. Industry software built for Kenya

Some products are built for a specific Kenyan sector and already handle local needs. Our own products are examples: School Manager for schools, Microfin for lenders and SACCOs, and Edgecom CRM for sales and invoicing. If a product like this fits 80% of what you need, it is usually cheaper and faster than building from scratch.

3. Custom software

Custom software is built around how your business actually works. It makes sense when your process is what makes you different, when no product fits without awkward workarounds, or when you need several systems to work together. It costs more upfront, but you are not paying per-user licence fees forever, and the system grows with you.

What custom software gives you

One source of truth

All your data lives in one database. Sales, finance and operations see the same figures, updated as things happen. There is no "latest version" to hunt for.

Roles and permissions

Each person sees and edits only what their job needs. A sales rep sees their own customers, a branch manager sees the branch and the director sees everything. This is far harder to enforce with shared files.

An audit trail

Every change is recorded with who made it and when. Mistakes can be traced and corrected, and disputes are settled by looking at the record rather than arguing about memory.

Automation that fits Kenya

• M-Pesa. Payments to your Paybill can be received through Safaricom's Daraja API and matched to customers or invoices automatically, using the account number they enter. STK push lets the system send a payment request straight to a customer's phone. Our article on M-Pesa integrated websites explains how this works.
• KRA eTIMS. Kenyan businesses must issue electronic tax invoices through KRA's eTIMS. A custom system can be designed to work with your eTIMS set-up, so invoices are not keyed in twice. Agree the approach with your accountant first.
• SMS and email. Reminders, receipts and statements can go out automatically when something happens, not when someone remembers.

Data protection: a reason to move, not just a cost

Kenya's Data Protection Act, 2019 requires businesses that handle personal data to keep it secure, collect only what they need and use it only for the purpose it was collected for. Customer lists, ID numbers and phone numbers sitting in spreadsheets that are emailed around and saved on personal laptops are hard to protect and hard to account for.

A proper system helps: access is controlled by role, data stays on a secured server, and you can see who viewed or changed a record. Some businesses must also register with the Office of the Data Protection Commissioner (ODPC). Software does not make you compliant on its own, but it makes compliance much easier to show.

What custom software costs in Kenya

At Edgecom, custom web applications and systems start from KES 100,000 before 16% VAT, and typically take four to eight weeks for a first version, longer for larger systems. The final price depends on the number of modules, user roles, integrations such as M-Pesa, and how much existing data needs to be moved across. Our website and software cost guide sets out our prices in full.

When comparing costs, include the hidden cost of the current way of working. If two staff spend a day a week each re-typing and reconciling, that is a real cost every month, even though no invoice arrives for it.

How to switch without disrupting the business

The biggest risk in replacing spreadsheets is trying to change everything at once. A staged approach works better.

1. Map the process. Write down how work actually flows today, step by step, including the workarounds. This often reveals problems that have nothing to do with software.
2. Pick the most painful part first. Usually it is payments, stock or customer records. Build that first, and get it working well.
3. Clean the data. Before importing, remove duplicates, fix formats and decide which version of each record is correct. Rubbish in a new system is still rubbish.
4. Run in parallel briefly. Use the new system alongside the old for a short, fixed period, compare the results, then switch off the old one. Do not let the parallel period drag on.
5. Train the team. Short sessions focused on each person's daily tasks work better than one long demonstration.
6. Add the next module. Once the first part is stable, move on to the next. Each stage pays back before the next one starts.

Questions to ask any software developer

• Will I own the data, and can I export all of it at any time?
• Where will the system be hosted, and who is responsible for backups?
• Who can see what, and how are permissions managed?
• How will M-Pesa payments be matched, and what happens to payments that cannot be matched?
• What does support cost after launch, and what response time is promised?
• Can you show me systems you have built that are running today?

Which businesses benefit most

We see the strongest case for moving off spreadsheets in businesses with many transactions or many people touching the same data: SACCOs and microfinance lenders, property managers collecting rent, logistics and transport companies, schools, distributors and wholesalers, and service firms that invoice many clients each month.

Talk to us about your system

We are a Nairobi team that builds and runs its own software products, and we build custom systems for businesses across Kenya. Read about our system development service, or our web development service if you need the website side too. Tell us what you are running on spreadsheets today and we will suggest the simplest way forward, whether that is one of our products or something built for you. Contact us and we will reply within one business day.