Article
Five questions to ask before you commission custom software
Custom software is a serious investment, and most of the risk is decided before a line of code is written. These are the questions we would want any client to have answered first.
Building software for your own business can be one of the best decisions you make, or an expensive lesson. Which one it turns out to be is usually settled early, in the conversations before the build starts. These five questions are the ones we find matter most.
1. What problem are we solving, in one sentence?
If the answer takes a paragraph, the project is not ready. "We need a platform" is not a problem. "Our agents spend half their day copying orders from messages into a spreadsheet" is.
A clear problem gives everyone a way to judge every later decision: does this feature help solve it or not?
2. Who will use it, and what is their day like?
Software is used by particular people in particular conditions. Are they at a desk or in the field? On a laptop or an entry-level phone? With a stable connection or an unreliable one? Comfortable with technology or wary of it?
A tool that suits the head office and frustrates the people who do the work will be quietly abandoned. It is worth meeting those users before designing anything for them.
3. Does something already do this well enough?
Sometimes the honest answer is that an existing product covers most of the need, and a small amount of connecting work covers the rest. That is cheaper and faster than building from nothing, and a good partner should tell you so.
Custom software makes sense when the way you work is the thing that sets you apart, or when nothing on the market fits the conditions you operate in.
4. What happens after launch?
Launch day is the beginning of a system's life. It will need fixes, updates and changes as the business changes. Before starting, be clear about who maintains it, who can change it, and who owns the code and the data.
A project with no plan for the months after delivery is only half planned.
5. How will we know it worked?
Decide in advance what success looks like, in terms the business cares about: time saved, errors avoided, customers served, orders processed. Agree how it will be measured.
Without that, a project can be finished on time and on budget and still leave nobody sure whether it was worth it.
Before you start
None of these questions needs a technical background to answer. They need honesty about how the business runs today and what you want it to do tomorrow. If the answers are clear, the build is far more likely to go well. If they are not, finding them is the most valuable first step.
We are happy to work through them with you. Book a call and bring the problem, even if it is still rough.