Why good dashboards go unread
Plenty of Kenyan businesses have paid for a reporting dashboard that is genuinely good - fast, clear, everything a click away - and is opened on Monday morning and then not again until something goes wrong.
The reason is not quality. It is that opening it is a decision, and decisions cost attention. Running a shop already spends that budget on suppliers, staff, customers and cash. A report competing for the same attention loses, every time, no matter how well built it is.
So the question worth asking is not how to build a better dashboard. It is where your attention already goes.
The channel that is already open
In Kenya, for the overwhelming majority of business owners, the answer is WhatsApp. It is open all day. Suppliers are in it, customers are in it, staff are in it. Checking it is not a decision - it is a reflex.
Which means a business summary that arrives in that thread does not have to win anybody's attention. It is already there, between a supplier's message and a customer's order.
Questions get asked there too, in the gaps a working day is made of: waiting for a delivery, standing at the counter between customers, at nine in the evening about something that has been bothering you since lunchtime. Every one of those moments has a phone in it, and the phone is already on WhatsApp.
Summaries build the habit, alerts prevent the loss
Two different things travel over that channel and they do different jobs. It is worth designing them separately.
- The scheduled summary: short, same time each day, what moved and what is at risk.
- Two or three concrete actions, not a list of everything that could be done.
- Threshold alerts that fire the moment something breaks, independent of the schedule.
- A fast-moving item about to run out, before you lose the sales.
- A supplier price increase, on the day it appears rather than at month end.
- A till or cash position that does not reconcile, while people still remember the shift.
The language question, which is not cosmetic
Here is something visible in almost every Kenyan business we work with. An owner entirely comfortable in English will still, given the option, ask about their own money in Swahili or Sheng.
It is not a competence issue. It is that formal language makes an informal activity feel like a task. Asking "how much did we do yesterday" in the register you actually think in costs nothing. Asking it in a language you associate with paperwork costs a small amount of effort, and small amounts of effort are exactly what stop things becoming habits.
Technically this is one of the cheaper things to build - current systems handle Swahili and Sheng well. The payoff is out of all proportion to the cost, because usage is the only thing that eventually changes how a business is run.
What must not be relaxed
"Business AI on WhatsApp" covers a lot of poor products, so it is worth being clear about what a casual channel does not license.
The figures sent over WhatsApp should be the same figures, computed the same verified way, as the ones in your system. There should be no simplified chat mode that guesses more freely because the format is informal.
The safety rules should not relax either. Nothing that changes your records should happen through a chat reply. If something has been drafted for you, the message should tell you it is ready and take you somewhere it can be approved properly and recorded against your name.
And where coverage is unreliable, SMS fallback matters. A summary that only arrives when the data connection is good is a summary you cannot build a routine on.
Practical setup for a Kenyan business
If you want this working, the sequence is straightforward and the order matters.
- Make sure your sales, stock and purchases are actually being recorded in one system - reporting cannot fix incomplete records.
- Decide the three to five numbers that genuinely deserve a daily interruption.
- Set thresholds for the alerts, and expect to tune them for a month before they feel right.
- Connect WhatsApp through the official Business API rather than an unofficial workaround that can be cut off.
- Choose the language per recipient - the owner and the accountant may want different ones.
- Add SMS fallback for anyone working where coverage is patchy.
How Upeosoft sets this up
We build the systems that record the business - stock, sales, purchases, M-Pesa and eTIMS - and then connect them to the channel the owner actually uses. WhatsApp through the official API, SMS through the gateway we already run, and summaries written to be read in fifteen seconds.
The work we spend most time on is not the plumbing. It is deciding, with the owner, which handful of numbers earn the right to interrupt their morning, and setting alert thresholds that fire on real problems rather than on noise. Get that wrong and people mute the thread within a fortnight.
If your reports are technically excellent and nobody reads them, talk to us. The problem is usually the channel, not the report.
