Hiring a software agency is a big commitment, and the sales conversation is designed to look good. The right questions cut through that and reveal how they actually work. Here are the ones worth asking, and what good answers sound like.
The short answer
Ask about process, ownership, communication, team, and failure, the things that predict outcomes. Good answers are specific and plain-spoken; vague, defensive, or jargon-heavy answers are warnings. You do not need to be technical to judge any of these.
Questions worth asking
About the work
- "What do you need from me to make this succeed?" (Good agencies expect a partnership.)
- "How do you handle scope changes and overruns?" (Listen for a clear process.)
- "What will I own at the end, and how is it documented?" (Should be: everything, documented. See own your code and accounts.)
About the team
- "Who specifically will work on this, and what is their experience?" (Watch for bait-and-switch: senior in the pitch, juniors on the work.)
- "How do you communicate and how often?"
About the track record
- "Can I see relevant work and talk to those clients?"
- "Walk me through a project that went sideways and what you learned." (The most revealing question there is.)
About money and terms
- "Is this a fixed price for a defined scope, or hourly?" (See fixed-fee vs hourly.)
- "What happens if we want to part ways mid-project?"
What good answers sound like
Specific examples, plain explanations, comfort discussing failure, clarity on ownership and scope, and real references. Bad answers: vagueness, defensiveness, pressure to start building before the product is defined, or reluctance to give you ownership.
Negotiate from clarity
You get better answers, and better terms, when you come in with a defined scope rather than a fuzzy idea (see how to read a proposal). A product simulation gives you a runnable, documented foundation to bring to these conversations, so agencies quote precisely and you can tell who actually understands the work.
Want to hire from a position of strength? Start a project.
Frequently asked
What's the most revealing question to ask?
Ask them to walk you through a project that went wrong and what they changed afterward. Honest, specific answers show maturity; defensiveness or 'nothing ever goes wrong' is a red flag.
Should I ask technical questions I won't understand?
Focus on questions you can evaluate, process, ownership, communication, references. You will learn more from how clearly they explain things than from technical answers you can't judge.