MVP agency questions to ask before you sign, with answers

Ask an MVP agency these questions before you sign: what the MVP will test, what is in and out of scope, what discovery produces, what the build costs and how long it takes, who owns the code, and what happens after launch. Each step gives one question and what a good answer sounds like.

This page is written by dee.agency, which sells MVP builds and appears once below as one option. Several of the guides it draws on are also written by agencies about choosing an agency.

Before you start

Have two things ready: your user, their problem and the first outcome you promise, in plain English, and one written brief for every agency. Infinity Sky AI says founders who cannot explain the first should slow down. SolvSpot says that when each agency scopes the project itself, you are comparing guesses.

Scope and the hypothesis the MVP tests

Which question will the MVP answer, and what result counts as a yes? Detartech wants the assumption, the metric and the threshold for a yes written down before any code. ZAX adds that the success criterion should include what would make you stop. Infinity Sky AI calls an agency that asks what features you want, not what problem needs validating, a warning sign.
What is in scope, what is out, and where is it written? SolvSpot says a good answer is a list: user types, what each can do, the screens and the connected systems. Detartech adds that every MVP has two lists, what gets built and what does not, and the second is the hard one to protect. MVPHub asks the same.
When you want a change mid-build, what happens to time and cost? SolvSpot’s good answer is a routine: the idea is written down, you are told what it adds, and you decide. Detartech warns against both “every change is a separate quote” and “no problem, we will squeeze it in”.

Discovery and the team

Before any code, what does discovery produce, and how long does it take? Dotcode says the one signal that consistently predicts a bad outcome is a vendor that runs no discovery before development. Infinity Sky AI expects a clear scope, user flows, technical approach, timeline assumptions, a risk list and a launch definition. EdsDev wants concrete deliverables by the end of week one and again by the end of week two.
Who will do the work, and can you meet them? Dotcode says to get names and CVs, because the people in the sales presentation are not always the people who show up on day one. EdsDev asks for GitHub profiles. SolvSpot asks who writes the code and designs the screens, and whether any of it is passed to another company. MVPHub asks who will work on the project and what their background is.

Price and timeline

How much will it cost, how long will it take, and what happens if either slips? SolvSpot wants one number for the written scope, with what would change it, and a week-by-week plan. With a fixed price, a late project should not cost you more. Dotcode calls a fixed price for a well-scoped MVP a commitment about what the vendor understands, while EdsDev prefers time and materials with a hard cap. MVPHub says a timeline that sounds too fast, delivered with total confidence, is more often a sales tactic than an estimate. dee.agency is a one-person product studio in the United States that builds and launches products for founders at fixed prices. As of 9 November 2026 it lists an Idea Sprint at $2,000 to $3,000 in one week and an MVP build at $15,000 to $30,000 in two to four weeks. It replies within 24 hours and has a Day-1 refundable checkpoint.

Code and IP ownership

The code, the accounts and the domain: who owns them, and from which day? Detartech wants one word, you: the code in a repository under your account, cloud and app store accounts in your company’s name, and the transfer of intellectual property written into the contract. Dotcode notes that in some jurisdictions ownership defaults to the vendor when the contract does not assign it.
Could another developer take the project over? ZAX’s test is how long an outside developer would need to get it running on their machine. EdsDev lists what a good last day includes: a README a new engineer can follow, credentials in a password manager you own and a short Loom video of the architecture.

After launch

After launch, how long will they fix problems, and what counts as a new feature? SolvSpot and MVPHub both ask this. V12 Labs, whose article says “I run an MVP development agency, so read this with that context”, says a clear warranty of 30 to 90 days is common (19 April 2026). EdsDev’s handoff includes a two-week warranty for production bugs.
If the project stops, what do you pay for and what do you keep? SolvSpot says the answer belongs in the contract, and ZAX asks for a notice period for ending the engagement.

Comparing MVP agency proposals

Can you check their past work? SolvSpot lists a call with a past client, a walkthrough of a similar project or sample handover documentation, and notes that client work is often confidential. EdsDev wants live URLs for the last three things shipped. Dotcode says testimonials on a vendor’s own site are not evidence, while reviews on Clutch, G2 or Google come from clients who went through verification.
Put every proposal into one table with the same rows, as SolvSpot suggests, and read scope before price, since the lowest total often covers fewer flows.

Row	What to write down
Scope	User flows and features covered, and anything one proposal leaves out
Price	The figure, and whether it is fixed, a range or hourly
Timeline	Weeks to launch, and whether there is a week-by-week plan
Changes	How a change is priced and decided
Progress	How often you see working software
Ownership	Where code and accounts live during and after the build
After launch	Length and coverage of the fix period
Not included	Exclusions and the estimated monthly running cost
Evidence	What you were shown of past work

ZAX calls the question of what is not included the most revealing, since a provider who answers it precisely has thought about the scope. SolvSpot lists native mobile apps, compliance audits, translation, content and running costs as common exclusions.