Are you ready to commission software? Five honest questions
The most useful thing I can do early in a conversation is tell someone they are not ready to build yet. It sounds counterintuitive for a software company, but a build that starts before the basics are in place is the most expensive way to learn that lesson. These are the five questions I work through with every prospective client before anyone talks about scope.
1. Do you have a process owner?
There needs to be someone on the business side, not only in IT, who can describe how the work actually flows, where the exceptions are, and what success looks like. Without that person, a build becomes a guessing game. The best projects we run have one clear owner who can answer questions quickly and make decisions stick.
2. Is your data fit for purpose?
List your systems of record, check whether you can export clean data from them, and ask the uncomfortable question: do people actually trust the numbers today? If the answer is no, that is something to address in discovery, because new software built on data nobody believes in will not be believed either.
3. Can you phase the delivery?
Building the highest-pain module first lowers risk and gets value into your hands sooner. If your situation forces an all-or-nothing launch, the project becomes far riskier. Most operations can be phased with a little thought, and we will push hard to find the first slice that stands on its own.
4. Do you have rough budget and timeline bands?
You do not need a precise figure to begin. Even rough bands help us scope discovery sensibly and tell you honestly whether your expectations and your budget are in the same postcode. Our pricing page sets out typical ranges so you can calibrate before we ever meet.
5. Is the organisation actually ready to change?
This is the one people forget. Software changes how work is done, and that only sticks if the team is prepared for it. If the honest expectation is that everyone will carry on exactly as before with a nicer screen, the build will underdeliver no matter how good it is. Readiness is as much about people as it is about data.
A wrong platform switch can disrupt revenue for months. The cheapest insurance against that is an honest readiness check before anyone writes code.
If you can answer these five with reasonable confidence, you are ready for a discovery conversation. If a couple of them give you pause, that is genuinely good to know now. It is far cheaper to resolve on paper than to discover halfway through a build.
Bhoomi works with growing businesses to understand what they actually need, translating day-to-day operational pain into a clear path forward.