On this page
Choosing a development partner is one of the biggest decisions a founder makes. The right team ships a product your customers love; the wrong one burns months of runway. These twelve questions help you tell them apart before you sign anything.
Start with a short brief#
Before you contact anyone, write one page: the problem you're solving, who the users are, the three to five things the product must do at launch, your deadline and your budget range. Send the same brief to every company you talk to, so their answers can be compared.
The 12 questions#
Experience#
- Can you show me two or three products like mine that are live today? Ask for links and app store pages, not just screenshots.
- What went wrong on a past project, and what did you change? Good teams answer honestly and specifically.
- Can I speak to a past client? A short reference call tells you more than any case study.
Team#
- Who exactly will work on my project? Names, roles and seniority, and whether they are employees or freelancers.
- Can I talk to the developer or designer, not just sales?
- What happens when someone is ill or leaves? You want a team, not a single point of failure.
Process#
- How will I see progress? Look for weekly demos on a live staging link, not status reports.
- How do you handle scope changes? There should be a clear, written way to agree on changes and their cost.
- How do you test before release? Code review, automated tests and a staging environment are signs of a mature team.
Ownership, price and support#
- Will the code and accounts be mine from day one? Code in your GitHub, hosting and domains in your name, and an IP assignment in the contract.
- Is the price fixed per milestone, or hourly? Fixed milestones protect your budget; hourly needs close tracking.
- What support do I get after launch? Ask what's included, for how long, and what ongoing help costs.
Red flags#
- They quote a price without asking questions about your users or goals
- Every answer is "yes, we can do that"
- You can't speak to anyone who will actually build the product
- Code or credentials are only handed over after the final payment
- No written proposal with scope, milestones and timeline
How to compare quotes#
Lay the proposals side by side and compare the same things: the features included at launch, the milestone plan, who is on the team, how progress is shown, what support follows launch and who owns the code. The cheapest quote often leaves something out; the most expensive isn't automatically the best.
Frequently asked questions#
Should I choose a local or an offshore company?#
Both can work. An offshore team usually costs less; what matters is overlap with your working hours, clear communication and ownership terms. Our guide to hiring an offshore development team covers how to do it safely.
Freelancer or agency?#
A freelancer suits small, well-defined tasks. An agency suits products that need design, development, testing and support working together.
How many companies should I talk to?#
Three is usually enough to see the real range of approaches and prices without losing weeks.
Want to put us to the test? Book a free call and ask us all twelve, or read how we work.






