Most bad MVP experiences were predictable. The warning signs were there in the first conversation, but the founder did not know which questions to ask.
These 12 questions surface them before you pay anything. For each one, here is what a good answer sounds like and the red flags that mean you should walk away.
About the people
- Who exactly will write the code? Good answer: a named person you can talk to directly.
- Can I see something you built that real people use today? Good answer: a live product, not only mockups.
- How many projects are you running at once? Good answer: a specific, small number.
About scope and price
- What exactly is included, and what is not? Good answer: a written list of both.
- Is the price fixed? What happens if I want changes? Good answer: changes are written down with their own estimate.
- How are payments split? Good answer: milestones tied to working software you can see.
Ask me all twelve. I will answer every one in writing before you pay anything.
Book a free scoping call →About the work
- How often will I see working software? Good answer: at least weekly, with a live link.
- What stack will you use, and why? Good answer: common tools another developer could pick up.
- How will you test the AI feature? Good answer: on your real inputs, with a way to measure accuracy.
About ownership and after launch
- Who owns the code, hosting and API accounts? Good answer: you do, from day one.
- What happens after launch? Good answer: a defined fix period and a handoff walkthrough.
- If you disappeared tomorrow, could someone else take over? Good answer: yes, because the code is documented and uses standard tools.
Red flags
- Reluctance to put scope in writing
- Code or accounts held in the builder's name
- No working software until the final week
- Big promises without a single live example
Frequently asked questions
How do I know if an MVP developer is any good?
Look at products they shipped that people use today, and check how clearly they answer questions about scope and ownership.
Should I ask for references?
Yes. A short call with a past client is one of the best signals you can get.
What should an MVP contract include?
The written scope, price and payment milestones, timeline, ownership of code and accounts, and what happens after launch.
Ask me these 12 questions
Book a free scoping call and put me through this list. You will get straight answers, a written scope and a fixed price, with no obligation to go further.
- Free 30-minute call
- Fixed price from $7,500
- Live in four weeks
- You own the code
I take on two to three builds at a time, so start dates fill up.