Skip to content
All guides

Guide · 4 steps

The MVP guide: from idea to launch

A minimum viable product (MVP) is the smallest version of your product that real users can use and pay for. Building one well comes down to a handful of decisions, made in the right order.

This guide puts our posts in that order. Start at step 1 if you only have an idea, or jump to the step you are on.

Step 1

Decide what to build

Pick the first user and the one job the product does for them, then decide what is left for version two. These posts cover scope, platform and the tools to build with.

  1. 5 min readHow to scope an MVP: what to build first, what to cutHow to scope an MVP in one week: pick one user and one job, list every screen, cut what does not test the idea, and agree a fixed price before design starts.
  2. 7 min readPoC vs prototype vs MVP: which should you build first?PoC vs prototype vs MVP: what each one proves, who it is for, what it costs in time, and a simple way to decide which one your startup should build first.
  3. 6 min readWeb app or mobile app first: how founders decideWeb app or mobile app first? How to decide from where your users are, what the phone must do, how people find you, and when a PWA is enough to start.

Step 2

Choose who builds it

Write a brief, compare teams and agree how you pay and what you own. A clear brief and a fixed quote protect both the budget and the date.

  1. 8 min readMVP development for non-technical founders: a plain guideMVP development for non-technical founders: what you decide, what to leave to the team, how to check progress without reading code, and what to own from day 1.
  2. 6 min readHow to write a software project brief: a templateHow to write a software project brief an agency can quote from: what to include, what to leave out, and a copyable template you can fill in in an afternoon.
  3. 7 min readAgency, freelancer or in-house team: who should build your MVP?Agency vs freelancer vs in-house for your MVP: cost, speed, risk and who manages the work, with a side-by-side table and a simple way to decide.
  4. 8 min readHow to hire MVP developers: where to look and what to askHow to hire MVP developers for a startup: the skills a first version needs, where to find developers, what to ask, a paid trial task and what to put in writing.
  5. 6 min readHow to choose an MVP development agency: 9 questionsHow to choose an MVP development agency: nine questions on price, code ownership, weekly demos, references, team and support, plus the red flags to watch.
  6. 7 min readFixed price vs hourly: how to pay for a software buildFixed price vs hourly software development: when each model fits, how scope changes are handled, and what a fixed quote should include before you sign.

Step 3

Plan the build

Most first versions take 8–12 weeks. These posts cover the week-by-week plan and the technical choices that change it.

  1. 7 min readHow long does it take to build an MVP? A weekly planHow long does it take to build an MVP? Usually 8–12 weeks. See the week-by-week plan, what fits in 4, 6 or 8 weeks, and what makes a build slower or faster.
  2. 6 min readReact Native vs Flutter: which should your startup pick?React Native vs Flutter for a startup's first app: hiring, performance, UI, packages, web reuse and when to go native, with real projects built on each.

Step 4

Launch and the first month

Both app stores review an app before it goes live, and the weeks after launch decide what you build next.

  1. 11 min readApp store launch checklist: Apple and Google PlayAn app store launch checklist for Apple and Google Play: accounts, listing assets, privacy forms, review times and update release dates, with a PDF to print.

Rather have it built for you?

We scope a first version in a week and launch it in 8–12, for a fixed price agreed before design starts.