No one loses money because they use Excel. They lose money because of what Excel cannot do: chase, alert, or reconcile on its own. The cost is invisible on the P&L because it never appears as a line item — it appears as slower cash, forgotten customers, and decisions made three weeks late.
The economics of a spreadsheet
A spreadsheet is a passive record. It changes only when a person opens it. Every business process built on one therefore inherits three properties:
- It has no clock. Nothing happens because time passed. A due date sitting in a cell triggers nothing.
- It has no memory of who did what. The last-modified stamp names a file, not a decision.
- It cannot be two places at once. The moment a second copy exists, you have two competing versions of the truth and no arbiter.
These three properties produce three predictable leaks. Below is how each one drains money, and what a targeted fix looks like.
Leak 1 — Cash: money you have already earned, arriving late
The mechanism. The invoice is raised. It enters a debtors sheet. Nothing chases it. It is chased when someone remembers, when cash gets tight, or when the customer calls about something else. Average days-sales-outstanding (DSO) drifts from a contractual 30 to an actual 55–70.
What it costs. Take annual revenue of KSh 120M and a 25-day DSO gap. That is roughly KSh 8.2M of cash permanently parked outside the business — financed either by your overdraft, at 14–18%, or by your own delayed supplier payments and the goodwill they consume. The annual cost sits between KSh 1.1M and KSh 1.5M, and it never appears as a cost.
The fix, without changing your accounting system.
- Define the ladder. Write the escalation once: reminder at −3 days, notice on day 0, follow-up at +7, phone call at +14, hold on new orders at +30. Agree it with sales before you automate it.
- Export daily, not monthly. Most accounting packages will export an aged-debtors CSV on a schedule. That file, not the spreadsheet, becomes the source.
- Automate the send. A scheduled job reads the file and sends the correct rung of the ladder from the finance mailbox. Personalised, but not manual.
- Log every touch. Each message writes a row: invoice, date, rung, response. This is the record you never had.
- Escalate by exception. Humans handle only what the ladder could not resolve. That is a 10-minute daily job instead of a two-day monthly one.
Typical result: 12–20 days off DSO within one quarter, with no new accounting software and no change to how invoices are raised.
Leak 2 — Follow-up: revenue that was never lost, only forgotten
The mechanism. A quote goes out. It sits in a sheet with a status column. The status is updated when someone thinks about it. Sales staff work the deals they remember, which are the recent ones and the loud ones. Everything else quietly expires.
What it costs. In firms without a follow-up system, 30–45% of issued quotes receive no second contact. Industry win rates on second contact typically run 15–25%. If you issue KSh 40M of quotes a year and 35% are never followed up, you are leaving roughly KSh 2.1–3.5M of winnable revenue on the table annually — at zero additional acquisition cost, because you already paid to generate the enquiry.
The fix.
- Make the quote an event, not a file. Every quote issued creates a dated record with an owner and a next-action date. A shared database, a form, or even a properly structured shared sheet with enforced columns will do.
- Set the cadence by value. High-value quotes: contact at day 2, 7, 14, 30. Low-value: day 3 and day 10, then archive. Do not apply one rhythm to everything.
- Automate the prompt, keep the human. The system reminds the owner and drafts the message; the salesperson decides and sends. Full automation of sales follow-up reads as spam and damages the relationship.
- Make ageing visible. One weekly list: quotes with no contact in 14 days, sorted by value. Reviewed in the sales meeting. Visibility alone recovers a surprising share.
- Record the reason for loss. Five options, no free text. Within two quarters this tells you whether you are losing on price, lead time, or specification — which is a pricing decision, not a sales one.
Leak 3 — Reporting: numbers that arrive after the decision
The mechanism. Management accounts are assembled monthly by one person consolidating several workbooks. They are ready on the 15th, describing a month that ended two weeks earlier. Every decision made in between is made blind.
What it costs. Rarely a single dramatic loss; instead a persistent drift — margin erosion noticed a quarter late, an unprofitable product line carried for two quarters, overtime authorised against a budget that was already exhausted. The cost is the compounding of small, late corrections, and it typically exceeds both other leaks combined.
The fix.
- Choose five numbers, not fifty. Cash position, debtors over 30 days, order book value, gross margin on completed jobs, and one operational metric that predicts the others (on-time delivery, utilisation, scrap rate).
- Refresh them weekly, in a fixed format. Same layout, same day, same time. Consistency matters more than sophistication — the value is in the trend line, which only exists if the definition never moves.
- Automate the assembly, not the interpretation. A scheduled export plus a simple transformation removes the assembly labour. A human still writes two sentences of commentary — that is the part that carries judgement.
- Publish, do not present. The pack lands in the same channel every Monday whether or not there is a meeting. Reports that require a meeting to exist stop existing when the meeting is cancelled.
- Define every metric in writing. One page, agreed by finance and operations. "Gross margin" quietly means three different things in most firms, and the argument about the definition is what kills the report.
What "without replacing your systems" actually means
Every fix above works alongside QuickBooks, Sage, Tally, Excel and Outlook exactly as they are today. The principle is read, don't rebuild:
- Systems keep their role as the record. You extract from them on a schedule.
- A thin layer holds the events they do not: chases sent, contacts made, reasons for loss.
- Automation sends, reminds and assembles. It does not replace the ledger, and it does not touch the general ledger's integrity.
- Nobody learns new software. The outputs arrive in email and the tools already in daily use.
This is deliberately unambitious architecture, and that is the reason it survives. Full replacements fail on change management, not technology.
A 60-day sequence
- Days 1–10: Measure. Current DSO, percentage of quotes with no second contact, and the date management accounts were actually available for the last three months. Three numbers, on one page.
- Days 11–25: Fix cash. Ladder defined, daily export scheduled, automated reminders live. Fastest payback of the three, which funds the rest politically.
- Days 26–40: Fix follow-up. Quote register with owners and next-action dates; weekly ageing list in the sales meeting.
- Days 41–60: Fix reporting. Five metrics, weekly, automated assembly, fixed publication slot.
- Day 61: Re-measure the same three numbers. Publish the delta.
The honest caveat
None of this fixes a pricing problem, a quality problem, or a demand problem. Spreadsheets do not cause those. What these three fixes do is stop the business losing money it has already earned — and they buy back the management attention currently spent on assembly, chasing and reconciliation. That attention is the scarcest resource in the firm, and it is being spent on work that a schedule could do.