Ask how they scope and price, who owns the code and accounts, who exactly will work on your project, how often you will see working software, what happens after launch, and for references from founders like you. Good companies answer all of these directly and in writing. Evasive answers about ownership, team or process are the reason to keep looking.
Choosing a development partner is the biggest purchasing decision most founders make before they have revenue. The companies all have polished websites and confident case studies. The questions below are how you look behind them. Ask every company the same list, write the answers down, and compare.
Questions about scoping and price
- How do you arrive at a price? Good answer: a discovery phase that defines scope, then a fixed price for the first release. Worrying answer: a number quoted from your email before any questions.
- What is excluded from this price? Every quote excludes something. You want to hear it now, not in month three. Listen for design, testing, admin tools, hosting setup, app store submission and post-launch fixes.
- What happens if I want to change something during the build? Good answer: a clear change process with pricing agreed in advance. Worrying answer: "we are flexible", with no detail.
- What did your last three projects cost against their original quote? Nobody hits every estimate. A company that can talk honestly about overruns and what they learned is safer than one that claims a perfect record.
Questions about the team
- Who exactly will work on my project, and can I meet them? The people in the sales call are not always the people who build. Ask for names, roles and a conversation with the lead developer or project manager before signing.
- Are they employees or subcontractors, and where are they? Either can be fine. What you want is a straight answer and a stable team for the length of the project.
- How many projects does each person work on at once? Two or three is normal. Six means your project gets attention when it is loudest.
- Who is my single point of contact and how quickly do they respond? Get a name and a service level, even informally.
Questions about process
- How often will I see working software? Good answer: a demo every one or two weeks from the first month. Worrying answer: a big reveal at the end.
- How do you test? Listen for automated tests, testing on real devices, and someone whose job is quality rather than developers checking their own work.
- How do you handle security? Even for a simple app, you want to hear about secure authentication, encrypted data and safe handling of payments. Blank looks are disqualifying.
- What do you need from me, and when? A good team will tell you exactly which decisions and materials are on the critical path and by when. See our guide to what to expect from kickoff to launch.
Questions about ownership
- Who owns the code, and when does ownership transfer? The only good answer: you, in writing, with transfer on payment of each milestone or at the latest on final payment. Read who owns the code for why this matters.
- Whose name are the accounts in? Repositories, cloud hosting, domains, app store accounts, payment providers. They should be in your company's name from day one, with the agency given access.
- Could another team take over the code if we parted ways? A confident yes, with mention of documentation and standard technologies, is what you want.
Questions about after launch
- What happens in the first month after launch? Bugs will appear. Who fixes them, how fast, and is it included?
- What does ongoing support cost? A retainer, hourly, or a maintenance contract. Get the shape of it now so it is not a surprise.
- Will you help me hire an in-house team later? A partner says yes. A vendor who wants to keep you dependent hesitates.
Questions about track record
- Can I speak to two founders you have worked with, at my stage? Then actually call them. Ask what went wrong and how the company handled it.
- Show me a product you built that is still live and being used. Case studies are written by the agency. A live product with real reviews is evidence.
What the answers tell you
| If they... | It suggests |
|---|---|
| Answer everything directly and offer to put it in writing | A company used to accountable relationships |
| Ask you more questions than you ask them | They are scoping honestly, which is what you want |
| Hesitate on ownership or accounts | Lock-in is part of the business model |
| Cannot name the team | Your project will be staffed with whoever is free |
| Promise a date before understanding the scope | The date is a sales tool, not a plan |
| Push back on some of your ideas | They will tell you the truth later too |
Our answers
For the record: we scope through a paid discovery phase and then fix the price and timeline for the first release. You own the code and all accounts from day one. You meet the project manager and lead developer before signing. You see a demo every one or two weeks. After launch we support the product and, when the time comes, help you build your own team. If you want to run this list on us, we are happy to answer every question.
Frequently asked questions
How many companies should I talk to?
Three is enough to compare and few enough to do properly. Send each the same brief, ask each the same questions, and compare the answers, not only the totals.
Should I choose the cheapest quote?
Choose the quote you understand best, from the team you trust most, within your budget. The cheapest quote is often the one that excluded the most. Ask what is missing before comparing prices.
Is it a bad sign if a company says no to my project?
It is a good sign about the company. Teams that turn down work that does not fit are the ones that finish the work they take on. Ask them who they would recommend instead.
What if I do not understand the technical answers?
Say so and ask for the plain version. A good company can explain its choices to a non-technical founder. If it cannot, communication will be a problem for the whole project.
Should I ask about their technology stack?
Briefly. You want to hear that it is mainstream, well supported and easy to hire for. You do not need to evaluate the specific choices unless you have a technical advisor to do it with you.