When software projects go wrong, the cause is rarely the technology itself. Far more often, the client and the development company had different expectations from the start, and nobody noticed until money and time had already been spent. The good news is that most of those misunderstandings can be uncovered before you sign anything, simply by asking the right questions and paying attention to how they are answered.
Here are ten questions worth putting to any agency or development firm, whether it is down the road or several time zones away.
Ownership and scope
1. Who will own the code, the data and the accounts?
The only acceptable answer is that you will. That includes the source code repository, cloud hosting accounts, domain names, app store listings and any third-party subscriptions the product depends on. The development company should receive access, not ownership. Make sure the contract says so explicitly.
2. What exactly is included in the price?
Ask for a written breakdown: discovery, design, development, testing, deployment, documentation, training. Equally important is what is not included. Hosting, store submission, analytics, content entry and post-launch support are common gaps.
3. How will changes be handled and priced?
Requirements will evolve once you see the product taking shape. That is normal. What matters is a clear, agreed mechanism for estimating, approving and billing changes, so that neither side is surprised.
People and process
4. When will I see something that works?
A strong partner puts working software in front of you early and regularly, typically within the first few weeks. If the plan involves months of silence followed by a grand reveal, your risk is high.
5. Who will actually do the work?
The senior people in the sales meeting are not always the ones writing the code. Ask who is on the team, whether any work is subcontracted, and who will be your day-to-day contact for the duration of the project.
6. How do you use AI in development?
This is a relatively new question, and an important one. Teams that use AI coding tools well can work faster and keep costs down. But you should also hear how code is reviewed by experienced developers, how security is checked and what rules govern the data shared with AI services. “We do not use AI” and “AI does everything” are both answers worth probing.
After launch and beyond
7. What happens once the product is live?
Software needs maintenance: bug fixes, security updates, compatibility with new browsers and operating systems. Ask how support is organised, what response times you can expect and how it is billed.
8. May I speak with previous clients?
A portfolio shows what was built. A conversation with a former client tells you what the collaboration was like: communication, deadlines, problem-solving and honesty when things went wrong.
9. What if we decide to work with someone else later?
Ask whether the code is documented, whether it relies on proprietary frameworks owned by the vendor and how a handover would work. A confident partner will not be offended by this question. A partner who makes leaving difficult should worry you.
10. What do you see as the biggest risk in this project?
This may be the most revealing question of all. An experienced team will name real risks, such as unclear requirements, a fragile integration or a tight deadline, and explain how they would manage them. If the answer is that there are no risks, that in itself is the risk.
Red flags to watch for during selection
- A quote produced within hours, without any questions about your business.
- A price dramatically lower than every other offer.
- Reluctance to put ownership, scope or support terms in writing.
- Vague answers about who will be on the team.
- Pressure to sign quickly before you have compared options.
How to compare offers fairly
Quotes are only comparable if they describe the same product. Before approaching several firms, prepare a short brief covering your goals, users, must-have features and constraints. Send the same document to every candidate and ask each one to state their assumptions. Then compare not only the totals but also the approach, the team, the timeline and the answers to the ten questions above. The cheapest offer and the best value are rarely the same thing.
Pay attention to how they listen
Beyond the answers themselves, notice how each candidate behaves during the conversation. Do they ask about your customers, your margins and your constraints, or do they jump straight to technology? Do they challenge parts of your plan that seem unnecessary, even if that means a smaller project for them? Do they explain technical choices in language you understand? A partner who is curious about your business in the first meeting is far more likely to build something that actually serves it. One who only talks about frameworks and features may deliver exactly what was written down and still miss the point.
Consider independent guidance
If no one in your organisation has a technical background, consider bringing in an independent technology consultant to help define requirements, review proposals and sit in on key meetings. The cost is modest compared with the cost of choosing the wrong partner and having to start again.
About to select a development partner? Our technology consulting services can help you define the brief and evaluate proposals objectively, even if you end up choosing someone else.
