When we tell a business owner in Nairobi that a custom dashboard is an option, the reaction is usually the same: a polite nod and a mental note that this is for banks and telcos. That assumption is a decade out of date, and it costs Kenyan SMEs real money every month.
So let's do something the industry avoids and talk about actual numbers.
The honest range
For a single-purpose internal dashboard — one that pulls your operational data into one screen, with login, roles, and a few reports — you're looking at roughly the same order of magnitude as a decent second-hand van, not a building. Our own entry tier starts around $450 for a tightly scoped tool, and a full multi-module system starts around $1,750 during our current launch pricing.
Why such a wide range? Because "dashboard" means five different things. Price is driven almost entirely by these factors:
- How many things it tracks — one workflow, or five departments
- Whether it only displays data or also records it (forms, approvals, edits)
- Integrations: M-Pesa, accounting software, WhatsApp, email, existing spreadsheets
- How many kinds of user need different permissions
- Whether reporting is fixed (five known reports) or exploratory (build your own view)
What makes projects expensive is rarely the code
The biggest cost driver we see isn't technical complexity. It's undecided requirements. A client who knows exactly which five numbers they need on screen every Monday gets a system built quickly and cheaply. A client who wants "everything, so we're future-proof" pays for months of work, most of which nobody will use.
This is the single best cost-control lever available to you, and it's free: decide what the first version must do, and be ruthless about what it doesn't.
Compare against what you already pay
Here's the comparison almost nobody runs. Tally your current monthly software spend: a project tool, a CRM, an invoicing subscription, maybe a reporting add-on, each billed per user in dollars. Call it $80 a month for a small team — modest by most standards.
That's $960 a year. Nearly $3,000 over three years, rising every time you add a staff member or the vendor changes its pricing. And at the end of it you own nothing, your data lives in someone else's product, and none of the workflows quite match how you actually operate.
A custom tool is built once. There's no per-seat charge when you hire your fourth or fourteenth employee. That's the arithmetic that surprises people: over a three-year horizon, purpose-built software is often the cheaper option, not the extravagant one.
Where SaaS still wins
We'd rather be useful than salesy, so: don't build custom when a mature product already does the job properly. Accounting and payroll are good examples — they're heavily regulated, well served, and there's no advantage in reinventing them. Email, calendars, storage: use the big tools.
Custom makes sense when your process is your advantage, or when no product fits the Kenyan reality you operate in. Rent collection tied to M-Pesa, field teams reporting by WhatsApp, distribution routes across counties — these are the cases where off-the-shelf tools force you to work the American way and you spend your life in workarounds. We unpack that trade-off in full in Custom Software vs SaaS.
What "built once, no SaaS bloat" means in practice
Our model is deliberately simple. You pay for the build, in two halves — 50% to start, 50% on delivery, by M-Pesa, bank transfer, or cash. You own your data completely and can export it any time. We keep the codebase and maintain it, which is what lets us keep prices at this level and fix things quickly instead of handing you a repository you'd need to hire a developer to touch.
Aftercare is bundled into the plan rather than sold as a surprise line item. No per-user pricing, no feature tiers that lock the report you need behind an upgrade.
How to price your own project in ten minutes
- Write down the five numbers you wish you could see every Monday morning
- Write down where each one lives today (a spreadsheet, M-Pesa messages, someone's head)
- Note which of those you also need to update, not just view
- List every system it must talk to
- Count the distinct types of user who need access
That page is a scope. Bring it to any developer and you'll get a real quote instead of a vague one — and you'll have eliminated the main reason software projects overrun. For property portfolios specifically, this piece on ditching spreadsheets shows what a first version usually covers.
If you'd like a straight answer on what your specific dashboard would cost, the pricing quiz at aiscope.online takes about two minutes and points you to a realistic range before you talk to anyone.
