The moment "we need to fix how we do this" turns into "we need to digitize our operations," a lot of organizations quietly assume the next step has to involve hiring a big consulting firm and running a long, formal bidding process with multiple companies submitting competing proposals. For a government office or a large corporate, that is genuinely how it works. For an established SACCO, NGO, hospital group, or school network with a real but specific problem, it almost never needs to.
You Are Not the Government, and You Do Not Need to Act Like It
Formal bidding processes exist because large public and corporate spending has to be justified to auditors, regulators, and boards well beyond the people actually going to use the system. That is a real requirement at that scale, and it is also the reason those projects take months to even reach a signed agreement. An organization where an executive director, operations manager, or finance director can simply decide to hire someone does not need to recreate all of that machinery to do this properly. Treating a normal internal systems project like a government contract usually just adds months of delay without adding any real protection you did not already have.
What Actually Happens Instead
In practice, a properly planned project starts with a conversation, not a stack of paperwork. That conversation covers how the relevant process actually works today, who is involved in it, where the delays and repeated effort actually show up, and what a genuinely better version would let your team do that it cannot do now. From there, a capable team can put together a clear, plain-language proposal describing what would be built, roughly how long it would take, and what it would cost, without needing a formal bidding process to get there.
Questions Worth Thinking Through Beforehand
The conversation goes faster, and the resulting proposal is more accurate, if you already have a rough answer to a few things. How many people or departments actually touch this process day to day. What your current record-keeping method actually is, whether that is one spreadsheet, several, or a mix of spreadsheets and paper. And which specific report or decision tends to get delayed the most, since that is usually the clearest sign of where the real cost is sitting.
What You Get at the End
The result of this process is a proposal you can actually read and understand on your own, not a lengthy document written for a review committee. It should tell you plainly what gets built, in what order, and what it costs, in language a non-technical decision-maker can evaluate without needing someone else to translate it first.
If you recognise your organization in any of the patterns covered across this series, starting in signs your organization has outgrown its current system, the next step really is just that conversation. Get in touch and describe how things currently work, and our business systems and automation service will take it from there.