The discovery call with a software agency is not a formality; it is the best opportunity you will have to understand whether this company can actually deliver what you need. Most people do not use it well. These are the questions that separate agencies that will deliver from those that will disappoint.
In this article
- Why most clients ask the wrong questions
- Questions about the team
- Questions about the process
- Questions about the project
- Questions about what happens after launch
- Questions about the contract
Most people interviewing a software agency focus on portfolio, price, and availability. These matter but they tell you relatively little about whether the agency will manage your project well, communicate honestly when things get difficult, and deliver something that actually solves your problem. The questions below are designed to surface the things that portfolios and proposals do not show.
1. Why most clients ask the wrong questions
The questions most clients ask in the first meeting are “what’s your hourly rate?”, “How long will it take?”, “Can you show me your portfolio?” Produce answers that are easy to give well regardless of actual capability. A well-rehearsed sales team can answer all of them convincingly without revealing anything substantive about how the agency actually works.
The questions that reveal genuine capability are the ones that require specific, experience-based answers, questions about failures, about tradeoffs, about what happens when things go wrong. These are harder to answer well without real experience and harder to fake with polished sales language.
The underlying principle
You are not evaluating what the agency says they can do. You are evaluating whether the evidence of what they have done justifies trusting them with your project. Every question below is designed to produce evidence, not assurances.
2. Questions about the team
Q1“Who specifically will work on our project and can I meet them today, not after we sign?”
Why this matters
The people who run the sales process are not always the people who run the delivery. Meeting the actual delivery team before committing tells you whether the seniority and communication style you experienced in the pitch will be present throughout the project.
Good sign: they bring the lead engineer and project manager to the call without hesitation.
Red flag: “We’ll assign a team once we’ve signed the contract.”
Q2“What happens if a key person on our project leaves mid-engagement?”
Why this matters
Staff turnover happens at every agency. The question is whether the agency has a process for managing it knowledge transfer protocols, documentation standards, backup staffing or whether your project simply stalls when someone moves on.
Good sign: a specific process with named backup roles and documented handover procedures.
Red flag: “That hasn’t happened to us” or a vague reassurance with no process behind it.
Q3“How many other projects will your team be working on alongside ours?”
Why this matters
A team split across many concurrent projects will give each one fragmented attention. Knowing the actual workload of the people assigned to your project tells you whether they have the capacity to deliver what they are promising on the timeline they are quoting.
Good sign: a specific, honest answer with clear capacity allocation.
Red flag: evasiveness or “our team is highly experienced at managing multiple projects.”
3. Questions about the process
Q4“Walk me through what the first four weeks of working together actually look like.”
Why this matters
A specific, detailed answer reveals whether the agency has a real delivery process or improvises project by project. You want to understand exactly when discovery happens, when you will see the first designs, when development starts, and what decisions you will be asked to make and when.
Good sign: a week-by-week breakdown with specific deliverables and decision points.
Red flag: generic agile methodology language with no specifics about your project.
Q5“How do you handle scope changes after development has started?”
Why this matters
Scope changes are inevitable. The question is whether the agency has a clear, fair process for assessing and pricing them or whether changes become a source of conflict and unexpected invoices. A good change management process protects both sides.
Good sign: a documented change request process with defined impact assessment and sign-off before work proceeds.
Red flag: “We’re flexible, we’ll figure it out as we go.”
Q6“Tell me about a project that did not go as planned. What happened and what did you do?”
Why this matters
Every agency has had a difficult project. How they talk about it reveals more about their character than any success story, whether they take accountability, how they communicated with the client under pressure, and what they learned from it.
Good sign: a specific story with honest acknowledgment of what went wrong and what changed as a result.
Red flag: “All our projects have gone smoothly” or a story where the client was entirely at fault.
4. Questions about the project
Q7“What assumptions is this estimate based on and what would cause it to change?”
Why this matters
Every estimate rests on assumptions. Agencies that cannot articulate them have not thought carefully enough about your project. Knowing the assumptions lets you validate them and understand which risks you are accepting when you sign.
Good sign: a written list of assumptions with specific conditions that would trigger a change order.
Red flag: “The estimate is solid, we’ve done projects like this before.”
Q8“Is there anything about our project brief that concerns you or that you would approach differently?”
Why this matters
An agency that agrees with everything in your brief is either not thinking independently or not willing to push back. A real partner will have questions, concerns, or alternative suggestions and their willingness to raise them before you sign is a strong signal of how they will behave throughout the project.
Good sign: specific, constructive pushback on elements of the brief with reasoning.
Red flag: “Your brief looks great we can build exactly what you’ve described.”
Q9“Can you show me a project similar to ours and can I speak with the client directly?”
Why this matters
Case studies are curated. Direct client references are not. A reference from someone who ran a similar project and who will answer honestly about the experience, not just the outcome, is the most reliable signal of what working with this agency is actually like.
Good sign: immediate offer of specific references matched to your project type.
Red flag: references offered only after significant delay, or only from very different project types.
5. Questions about what happens after launch
Q10“What does your support and maintenance process look like after go-live?”
Why this matters
Software always needs maintenance after launch bug fixes, dependency updates, security patches, performance tuning. Agencies that treat launch as the end of the engagement leave clients with systems that degrade over time and no clear owner when something breaks.
Good sign: a specific retainer or support package with defined response times and scope.
Red flag: “We’ll handle any issues as they come up” with no defined process or cost structure.
Q11“What documentation will we receive at the end of the project?”
Why this matters
If you ever need to bring the system in-house, switch agencies, or onboard a new developer, documentation is what makes that possible without starting from scratch. Agencies with strong documentation practices signal confidence in their work they are not creating lock-in through opacity.
Good sign: architecture decision records, API documentation, deployment runbooks, and codebase README as standard deliverables.
Red flag: “The code is self-documenting” or vague reference to “standard documentation.”
6. Questions about the contract
Q12“Who owns the intellectual property of everything you build for us?”
Why this matters
The answer should be unambiguous: you do, upon full payment. Some agencies retain IP until final payment is received, which is standard. Others include clauses that retain rights to components or frameworks — which needs to be understood and negotiated before signing.
Good sign: clear statement that full IP transfers to the client upon payment, with any exceptions explicitly listed.
Red flag: vague language about “shared IP” or reluctance to discuss it before contract stage.
Q13“What are the termination conditions and what happens to the work if we part ways mid-project?”
Why this matters
You hope never to need this, but understanding it upfront is essential. What notice period is required? What do you receive and own if the engagement ends early? Is there a handover process defined in the contract? These protections matter most when the relationship is under stress.
Good sign: clear termination clause with defined notice period, handover obligations, and IP transfer on work completed to date.
Red flag: vague or one-sided termination terms that leave the client exposed.
The bottom line
The right questions do two things: they give you the information you need to make a good decision, and they signal to the agency that you are an informed, engaged client who will hold them to what they promise. Agencies that are uncomfortable with detailed pre-contract questions are telling you something important about how they will handle difficult conversations during the project.
The agencies worth working with will welcome these questions because they have good answers, and because the clients who ask them tend to make better partners throughout the engagement.
If you want to put any of these questions directly to the SmartWayLabs team before deciding whether we are the right fit for your project, we would be glad to answer them. That is exactly the kind of conversation we think every client should have before signing anything.
Want to ask us these questions directly?
SmartWayLabs welcomes the hard questions we think clients who ask them make the best partners.Talk to the team ↗