What are the most important questions to ask a software development agency?

The five most important questions are: How long does your scoping process take and what does it produce? How is your PM and engineering structured? Can you commit to a fixed price? What happens when requirements change mid-project? Can you provide two references from comparable projects?

Should I ask a software agency about their technology stack?

Yes, but it's not the most important question. Ask whether their stack is portable — whether your future in-house team or another agency can work in it. Proprietary frameworks and unusual technology choices create long-term lock-in that's expensive to exit.

How do I know if an agency is being honest with me?

An honest agency will tell you when they can't deliver something, proactively list what's not included in their scope, give you references that aren't on their website, and walk you through past project challenges as readily as past project successes.

Questions to Ask a Software Agency Before You Hire Them

The questions that reveal an agency’s actual delivery capability are not the questions you’ll naturally ask. Most founders ask about the portfolio, the team size, the technology stack, and the timeline. These are all reasonable questions — and none of them are the most predictive.

The most predictive questions are about process, incentives, and references. Here are the 15 you should ask before signing anything.

Questions About the Scoping Process

1. “How long does your scoping process take, and what does it produce?”

What you’re looking for: A named deliverable (specification document, user story map, technical architecture review) produced over 2–4 weeks.

Red flag: “We can usually scope in a call or two and send you a quote within a few days.” This means the quote is a guess.

2. “Can I see an example of a past specification document (anonymised)?”

What you’re looking for: A structured document with user stories, technical approach, assumptions, exclusions, and pricing breakdown.

Red flag: “We don’t really do formal specification documents — we work iteratively.” Iterative doesn’t mean unscoped.

3. “What happens when your estimates turn out to be wrong?”

What you’re looking for: A clear explanation of how low-confidence items are handled (flagged in the proposal, priced as ranges, recommended for discovery sprint).

Red flag: “We’re experienced enough that our estimates are usually accurate.” This is the answer of someone who hasn’t thought carefully about estimation uncertainty.

Questions About Team Structure

4. “Who will be working on my project day to day?”

What you’re looking for: Named people (or at least named roles) with seniority described.

Red flag: “Our team will be assigned based on availability at project start.” This means the people who pitched are not the people who build.

5. “Does your PM have an engineering background?”

What you’re looking for: A PM who can participate in technical discussions, review code, and understand architecture decisions.

Red flag: “Our PMs focus on stakeholder management and delivery coordination.” These are necessary PM skills — but not sufficient for software delivery.

6. “Who makes technical architecture decisions on my project?”

What you’re looking for: A named senior engineer who will be involved throughout, not a solutions architect who scopes and then hands off.

Red flag: Vague answers about “the team” making decisions collectively, without a named technical lead.

Questions About the Commercial Model

7. “Will you commit to a fixed price for this project?”

What you’re looking for: A yes, subject to a scoping phase to define requirements.

Red flag: “We’d prefer to work time and materials for projects with any uncertainty.” All projects have uncertainty — the question is whether the agency is capable of estimating and managing it.

8. “What is your payment schedule?”

What you’re looking for: Milestone-based payments with 10–20% deferred to final delivery.

Red flag: Requesting 100% upfront or more than 50% before any working software is demonstrated.

9. “How do you handle change requests?”

What you’re looking for: A written process: change submitted in writing, impact assessed, change order signed before work starts.

Red flag: “We’re flexible about changes — we’ll figure it out as we go.” Flexibility without process means scope creep charged at the agency’s discretion.

Questions About Past Delivery

10. “Did your last three projects come in on budget and on time?”

What you’re looking for: Honest answers — “two of three, the third had a change request that extended the timeline by two weeks because of [specific reason].”

Red flag: “Yes, always.” No agency delivers 100% on time and budget across all projects. If they claim this, they’re either redefining what counts or they’re not being honest.

11. “Tell me about a project that went wrong and how you handled it.”

What you’re looking for: A specific example with a root cause analysis and what changed in their process afterward.

Red flag: “We don’t really have projects that go wrong.” Or deflection to a version where the client was at fault.

12. “Can you provide two or three client references from comparable projects?”

What you’re looking for: Actual clients you can call, not testimonials on a website.

Red flag: “We prefer to let our portfolio speak for itself.” Portfolios are curated; references are honest.

Questions About Post-Delivery

13. “What happens after the project launches?”

What you’re looking for: A clear answer about handover, documentation, and post-launch support options with defined costs.

Red flag: “We’ll cross that bridge when we come to it.” Or silence.

14. “Who owns the code and IP when the project is complete?”

What you’re looking for: “You do.” Clean IP assignment to the client on final payment.

Red flag: Any ambiguity. Software IP ownership should be explicit in the contract.

15. “Can I take this project to another agency if our relationship doesn’t work out?”

What you’re looking for: “Yes — we use standard technology and produce documented code. Any competent agency can take over.”

Red flag: Any lock-in — proprietary frameworks, undocumented code, or conditions on handover.

What PostMVP’s Answers Look Like

We answer all 15 of these questions in our first conversation. Our scoping phase is 2–4 weeks and produces a specification document that becomes the contract. Our PM writes code. We commit to fixed prices. Our payment schedule is milestone-based with 15% deferred to final acceptance. Our change process is written. We provide references — and we tell you upfront when we’re not the right fit for a project.

In Summary

The questions that predict agency delivery quality are about process, incentives, and honesty — not portfolio, technology, or team size. PostMVP asks these questions of ourselves before any client does, because the answers are the same criteria we use to evaluate our own work.