The spreadsheet-and-email setup that worked perfectly well when your organization had twenty staff and one office starts creaking somewhere around two hundred staff and three locations. Nobody decided this on purpose. It happened gradually, one extra spreadsheet, one extra email thread, one extra person copying numbers from one place to another, until one day the whole thing is held together by a handful of people who happen to remember where everything lives.
Here is how to tell the difference between an organization having a bad week and one that has genuinely outgrown what it is running on.
The Gap Nobody Talks About: Size, Not Industry
Most advice about business software is written as if the industry is what matters: retail software, clinic software, school software. In practice, the more important variable is size and structure, not sector. A single-branch clinic and a five-branch hospital group have almost nothing in common in terms of what they actually need, even though both are technically healthcare. A SACCO with one office and a SACCO with tens of thousands of members across several branches are, in every practical sense, running two entirely different kinds of operation.
Signs Worth Taking Seriously
A few patterns show up again and again in organizations that have quietly outgrown their setup. Different departments keep their own separate version of what is supposed to be the same information, and nobody is fully sure which version is correct anymore. Decisions wait on one specific person, because they are the only one who understands how a particular spreadsheet or process actually works, and everything stalls the day they are on leave. Producing a simple report for leadership or a board meeting takes days of manually pulling numbers together rather than minutes. And every time the organization opens a new branch, campus, or programme, someone has to rebuild the same record-keeping approach again from scratch, because nothing about the current setup was built to be repeated.
This Is a Real, Documented Pattern in Kenya
This is not a hypothetical problem. Kenyatta National Hospital, one of the country's oldest and largest hospitals, reportedly relied largely on manual records to manage patient care and operations for over 125 years before rolling out a proper system covering clinical care, administration, and billing together. More broadly, a majority of hospitals in Kenya are reported to still have no electronic records system at all. Kenya's largest SACCOs hold tens of billions of shillings in member assets while still relying heavily on paper-based record-keeping for contributions and loans in parts of their operation. These are not small, disorganized outfits. They are large, established institutions that simply grew faster than their internal systems did, which is exactly the pattern worth recognising early rather than late.
What This Does Not Mean
Recognising this does not mean you need to rip out everything and replace it in one large, risky project. Most organizations in this position do not need a complete overhaul, they need the specific point of failure identified and addressed, whether that is one shared system replacing five separate spreadsheets, or a proper reporting layer sitting on top of what already exists. If you are trying to work out whether the version of this problem showing up in your own organization is Excel and email finally reaching their limit, we go into exactly that in why bigger Kenyan organizations still run on Excel and email, and what breaks first.
If any of the signs above sound familiar, the next step is a conversation, not a formal procurement process. Our business systems and automation service starts with exactly that, and we cover what a proper scoping conversation looks like, without the tender-style process many assume this requires, in how to scope a systems project without a Big 4-style RFP process.