Eight questions
What to ask, and what a good answer sounds like
There's rarely one right answer. What you're listening for is a clear, specific reply that you understand, without having to take anything on faith.
01
"What do you need to know about our business before you suggest anything?"
The most expensive software is the kind that solves the wrong problem well. A developer who asks why before how is more likely to build something that matters.
Why it matters
Features are easy to list. Understanding what's actually costing you time or money takes a conversation.
A good answer sounds like
Questions about how the work gets done today, who's involved, what's frustrating, and what a good result would look like. You shouldn't need a technical spec to get started.
02
"Would you improve what we have, connect it, or replace it? Why?"
The systems you already use carry years of decisions about how your business works. Replacing them is sometimes right, but it shouldn't be the automatic answer.
Why it matters
A rebuild is the biggest, riskiest, most disruptive option. Often a smaller change gets most of the benefit.
A good answer sounds like
"It depends. Here's what we'd want to look at first." A developer who respects your current systems, and the people who built them, and explains the trade-offs of each path.
03
"Who will I actually work with day to day?"
The person in the first meeting isn't always the person writing the code. That can work fine, but you should know up front.
Why it matters
Every handoff between the person who understood your business and the person building the software is a place for details to get lost.
A good answer sounds like
Names and roles: who you'll talk to, who does the design and the building, and who answers when something breaks.
04
"Who owns the code, and could another developer take it over?"
Whatever arrangement you choose, you should understand it before you sign, along with what happens if you ever part ways.
Why it matters
Software usually outlives the original project. If only one person can work on it, your business depends on that person being available.
A good answer sounds like
A clear statement of who owns the code, in writing. Code built to consistent standards that another developer could read and maintain, and a straight answer about what switching later would involve.
05
"Where will it run, and where will our data live?"
Someone has to host the software, keep it secure, and back up the data. It's worth knowing who, and how you'd get your information out if you needed it.
Why it matters
Your records are part of the business. Losing access to them, or not knowing where they are, is a real risk.
A good answer sounds like
Where it's hosted and why, who's responsible for security updates and backups, and how you can get a copy of your data.
06
"What happens after launch, and what will it cost to keep running?"
The build price is only part of the cost. Hosting, updates, fixes, and changes as the business grows all continue after launch.
Why it matters
Software that nobody maintains slowly gets harder to change and riskier to run. Surprise costs later are worse than honest ones now.
A good answer sounds like
A plain explanation of what's included after launch, what isn't, and the options for ongoing support, so you can weigh the full cost before you start.
07
"What would you talk us out of?"
There's always more technology that could be added. A good partner will tell you when an idea isn't worth what it would cost to build and look after.
Why it matters
Every feature brings some ongoing upkeep. A developer who says yes to everything isn't necessarily looking out for you.
A good answer sounds like
A real example of advising a client to keep things simpler, and an acknowledgment that the decision is yours.
08
"How will we know it's working?"
Success should be described in your terms, not theirs: fewer things typed twice, invoices out on time, jobs that stop getting lost.
Why it matters
"The software launched" isn't the goal. The goal is the change in how your business runs.
A good answer sounds like
A conversation about what a good result looks like for you, agreed on before the work starts, and checked after.
A good developer should be glad to answer all of these. If an answer isn't clear, ask again; it's a reasonable thing to expect.