Questions To Ask Before Hiring A Product Development Agency

Judgment (the ones that matter most)

1. What would you cut from my scope?
The single best filter. Anyone who has genuinely thought about your product can answer instantly. 

2. What’s a project you’d turn down?
“None” means you are a wallet. 

3. Tell me about a product you built that failed. Why?
Fifteen years in, everyone has these. Vendors who cannot name one are hiding or new. 

4. What will be the hardest part of my build?
Vague answer, vague understanding. 

5. If my budget got cut in half tomorrow, what would you build instead?
Tests whether they think in outcomes or in feature lists.

The actual team

6. Who exactly will work on my product, and can I meet them before signing?
The A-team sells; ask who delivers. 

7. How many projects does that team run in parallel?
More than two or three and you know your real priority level. 

8. Senior-to-junior ratio on my project?
Fine either way — but the price should match the answer. 

9. What happens if my lead developer leaves mid-project?
 

10. Where is the team located and what overlap will I get with my hours?

Process and communication

11. How often do I see working software?
Weekly demos or walk away. Slides are not software. 

12. What do you need from me, weekly, for this to succeed?
“Nothing, we handle everything” is the worst possible answer — good builds need founder decisions. 

13. How do you tell me things I don’t want to hear?
Every project has a week where this matters more than any technical skill. 

14. What’s your definition of done for a feature?
Coded ≠ tested ≠ deployed ≠ documented. 

15. Show me a scope change from a past project — what happened to the price and timeline?
You are not asking if scope changes. It will. You are asking whether their machinery for it is fair.

AI (new in 2026, and revealing)

16. How does your team use AI, and how does that show up in my price?
AI-assisted teams genuinely ship faster. If their process is AI-native and their prices are 2022 prices, the savings are going somewhere that isn’t you. 

17. Will AI-generated code go into my product, and who reviews it?
The right answer involves the words “yes” and “senior engineers review everything.” 

18. Can my product’s data be used for training or shared with model providers?
Watch how precisely they answer. Imprecision here is disqualifying.

Money and ownership

19. Do I own all code, designs, and accounts from day one — and is that in the contract?
IP assignment should be unconditional and unambiguous. This question alone eliminates a shocking number of vendors. 

20. What’s in the quote — and what’s explicitly not?
Post-launch fixes, deployment, third-party costs, app store submission. 

21. What are my monthly run-costs after launch?
Hosting, AI inference, services. A vendor without this number hasn’t finished thinking. 

22. Payment terms — and what do I hold if things go wrong?
Milestone-based, with something meaningful tied to delivery.

After launch

23. What happens in the 60 days after launch — and what does it cost?
Launch week is when real users find real problems. No plan here means the quote is understated by 25–40%. 

24. If we part ways, what does handover include?
Repos, docs, credentials, a transition call with the new team. 

25. Can I talk to a client from two years ago?
Not last month — two years. Long-term references reveal how the code aged, which is the truest measure of build quality.

How to read the answers

You are not looking for perfect answers; you are looking for fast, specific, unrehearsedones. Vendors who have done this well for years answer instantly, with examples and the occasional confession. Vendors who improvise well in sales calls give beautiful answers with no proper nouns in them.

We publish our own process so you can check our answers against it. And if you’d like to run all twenty-five on us live, book the call -question 1 is our favorite.