How do I choose an agency to build an MVP?

Ask about code ownership from day one, a price cap, whose account the product runs on, when you will see the first working part and who leads the project. Get the answers in writing and compare several vendors side by side.

Is it bad if an agency wants a specification first?

No. A short one-page brief helps both sides. The problem is a specification that takes months while nothing works and nothing gets tested with customers.

What if I have already signed one of these?

Ask now and agree an amendment: moving the repository and hosting to your account, a price cap or weekly demos of finished work. Discuss any contract change with a lawyer. This is not legal advice.

Checklist for founders

7 sentences that should make you walk away from an agency

When choosing an agency for the first version of your product, watch for seven sentences: code only at the end, a price with no cap, hosting on their account, months of specification, testing only at the end, their own platform and a team with no names. For each sentence below: why it is a problem and what to ask instead. One sentence does not make a bad vendor.

What you fill in and tick stays in this browser window only. Nothing is sent unless you ask for your result by email. It is gone when you close the page, so print your result.

For founders choosing an agency or a freelancer for the first version of a product. Tick the sentences you have already heard from a vendor.

Since 2023 we have shipped 15+ production projects. We ask ourselves these questions too, and we can answer each of them in writing.

1. The sentences

"We will hand over the code once the project is finished." Why it is a problem: until the project is done, you own nothing and cannot leave. Ask: "Can the repository be on our account from day one?" A good answer: "Yes, or on ours with access for you from day one."
"We will tell you the exact price once we see how it goes." Why it is a problem: without a cap and milestones, you pay for the vendor's uncertainty. Ask: "What is the cap and what happens when we reach it?" A good answer: a fixed price for the scope, or a monthly amount you can stop at any time.
"We will host it and handle the domains, you don't need to worry about it." Why it is a problem: whoever holds the account holds the product. Ask: "Can it run on our account, billed to us?" A good answer: "Yes, the hosting invoices will go to you."
"First we will write a detailed specification over a few months." Why it is a problem: months of documents while nothing works and nothing gets tested with customers. Ask: "When will we see the first working part?" A good answer: a specific date in weeks, not months.
"We will test everything at the end." Why it is a problem: bugs and misunderstandings show up when the budget is spent. Ask: "What will we see finished every week?" A good answer: changes you can try yourself in a test version.
"We will build it on our own platform." Why it is a problem: code that only one vendor can maintain ties you to that vendor. Ask: "Which common technologies are underneath, and who else can maintain it?" A good answer: technologies you can hire developers for without them.
"Our team will work on the project, we don't know the names yet." Why it is a problem: you cannot see who makes the decisions about your product. Ask: "Who will lead the project, and can we talk to them before we sign?" A good answer: a specific person you meet before signing.

2. What to do next

Send the questions in writing and compare the answers of several vendors side by side.
A good vendor welcomes the questions. They answer specifically and put the answer in the proposal.
Ask us the same questions. We answer them in writing.
Before you sign, also use 10 questions to ask a software vendor.

More tools for you

One-page brief for your first version: what to build first and what to cut

Six readiness questions, a template to fill in and a made-up example. What to build first and what to cut.

How far are you from a first paid version? 10 questions

10 questions on your first paying customer, scope, money and timing. See what to settle before the build.

Frequently asked questions

How do I choose an agency to build an MVP?: Ask about code ownership from day one, a price cap, whose account the product runs on, when you will see the first working part and who leads the project. Get the answers in writing and compare several vendors side by side.
Is it bad if an agency wants a specification first?: No. A short one-page brief helps both sides. The problem is a specification that takes months while nothing works and nothing gets tested with customers.
What if I have already signed one of these?: Ask now and agree an amendment: moving the repository and hosting to your account, a price cap or weekly demos of finished work. Discuss any contract change with a lawyer. This is not legal advice.

Where to next

MVP and product

A working product in weeks, not months

First version plan

Together we decide what goes into the first version, what does not, and when you will see it. We get back to you within two business days with a few questions about your work. Then we agree on what we do first.

Tell us what has to ship first Or a 15-minute intro call

Who we help

Services

Resources

What is an AI agent? Plain answer, business examples

When is Excel no longer enough for a business?