It is not the spreadsheet's fault
Every operation we have looked at in Tanzania and East Africa runs on spreadsheets somewhere, and that is fine. A spreadsheet is a good tool for a person to think with. The trouble starts when it stops being a tool and becomes the operation's memory: the only place that holds what was ordered, what was paid, what was promised, and how the three connect.
A tool does not care who uses it. A memory only works if the person who built it is in the room. That is the line between a business with good spreadsheets and a business with a memory problem, and it has nothing to do with how neat the columns are.
Five signs you have crossed it
Two files, two truths. The finance sheet says one stock number, the store sheet says another, and reconciling them means someone walking to the store to count by hand.
One person is the API. A formula or a filing habit only one employee understands sits between a question and its answer. When they are on leave, the question waits for them.
Payroll takes a day. Hours, advances, and deductions get copied by hand from three places into one, once a month, by someone who dreads the date.
You cannot answer "how much do we actually have" without a phone call. Cash, stock, and receivables live in different files kept by different people.
You are afraid to let someone go on leave. Not because they are irreplaceable as a person, but because the operation would not survive two weeks without their particular spreadsheet habits. That fear is the clearest symptom there is.
Why it gets worse with growth
A small operation can carry a memory problem for a long time, because the founder or one trusted employee holds more of the picture in their head. Growth removes that cushion. More transactions mean more chances for two files to disagree. More staff mean more people who need an answer the spreadsheet cannot give without a translator. More funders and banks mean more people asking for numbers that have to be defensible, not just plausible.
So the problem does not announce itself early. It sits quietly under a small operation and breaks loudly under a growing one, usually the same month you landed the bigger contract that was supposed to be the reward.
What to fix first
You do not fix a memory problem by buying software. You fix it by finding out exactly where the memory currently lives, one process at a time, before you touch a tool. Steady the foundations that are actively breaking, build the systems that replace the fragile handoffs, then let the operation run without you re-checking it every week.
Our free operations check runs the twelve questions we ask on every audit. Most people who answer them honestly already know which of the five signs is theirs. From there, an operations audit gives you a prioritized map of what to fix.