From Idea to MVP in 12 Weeks: A Founder’s Roadmap

A minimum viable product is the smallest thing that proves people want what you are building. This week-by-week roadmap shows how to get from idea to launch in twelve weeks without cutting the wrong corners.

Developer working on a laptop at a hackathon
Building an MVP — Sebastiaan ter Burg (CC BY 2.0)

A minimum viable product (MVP) is the smallest version of a product that lets you learn whether real people want it — and will use it, recommend it or pay for it. It is not a prototype that only works in a demo, and it is not version 1.0 with every feature on the wish list. It is a real, working product focused on one core job, built well enough that early users trust it.

Twelve weeks is a realistic timeframe for many software MVPs when scope is disciplined. This roadmap shows how to use those weeks, what to decide when, and which corners you must never cut.

Key takeaways

  • Define the one core problem and the one core user before writing any code.
  • Scope ruthlessly: every feature must support the main user journey or the learning goal.
  • Do not cut corners on security, data protection, backups or basic accessibility.
  • Build in two-week sprints with real user feedback, and decide on launch metrics up front.
  • Launch is the start of learning, not the finish line.

Before week 1: validate the problem

The most expensive MVP is one that solves a problem nobody has. Before committing budget, talk to at least 10–15 potential users. Ask about their current behaviour, not your idea: how do they solve the problem today, what does it cost them, what have they tried? Look for evidence of pain — workarounds, spending, frustration. If you can, test demand with a landing page, a waiting list or a manual “concierge” version of the service.

Weeks 1–2: discovery and scope

The goal of the first two weeks is a shared, written understanding of what will be built and why.

  • Problem statement: one sentence describing who has which problem and why it matters.
  • Primary user and core journey: the single path from sign-up to “aha moment” that the MVP must nail.
  • Success metrics: for example activation rate, weekly active users, conversion to paid, or task completion time.
  • Feature list with MoSCoW prioritisation: Must have, Should have, Could have, Won’t have (this time).
  • Technical approach: platform (web, iOS, Android), stack, integrations and hosting — see how to choose a tech stack.
  • Risks and assumptions: what must be true for the product to succeed, and how the MVP will test it.

A useful test for every feature: “If we leave this out, can the user still complete the core journey, and can we still learn what we need to learn?” If yes, it waits.

Weeks 2–3: design

Design starts with user flows and low-fidelity wireframes, then moves to a clickable prototype of the core journey. Put the prototype in front of five or so target users and watch them try it. Small usability tests at this stage catch problems that would cost far more to fix in code. Establish a simple design system — colours, typography, components — so development is consistent and fast.

Weeks 3–10: build in four sprints

Development runs in two-week sprints, each ending with a demo of working software on a staging environment.

SprintWeeksTypical focus
13–4Foundations: project setup, CI/CD, authentication, data model, design system, first screens
25–6Core journey part one: the main objects and actions users work with
37–8Core journey part two: notifications, payments or integrations if they are must-haves
49–10Admin panel, analytics events, polishing, performance and accessibility fixes

Review priorities at the end of every sprint. New ideas will appear — add them to the backlog, not to the current sprint, unless something more important is removed.

Weeks 11–12: test and launch

  • Quality assurance: functional testing of every must-have, cross-browser and device testing, and automated tests for critical flows.
  • Security review: authentication, authorisation (users can only see their own data), input validation, secrets management, dependency scanning.
  • Legal basics: privacy policy, terms of service, cookie consent where needed, and data processing agreements with your providers.
  • Operations: production hosting, backups, error tracking, uptime monitoring and alerts.
  • App stores: developer accounts, listings, screenshots and review submission for mobile apps — allow time for review.
  • Launch plan: who gets access first (often a closed beta), how you will onboard them and how they can give feedback.

Corners you can cut — and ones you must not

Fine to cut in an MVP

  • Advanced settings and customisation
  • Secondary user roles
  • Automation of rare admin tasks (do them manually)
  • Pixel-perfect animations
  • Support for every edge-case platform
  • Self-service for things you can handle by email

Never cut

  • Security of accounts and data
  • Backups and the ability to restore
  • Privacy compliance and consent
  • Basic accessibility and mobile usability
  • Error tracking and monitoring
  • Clean, documented, version-controlled code

After launch: measure, learn, iterate

Launch is the beginning of the learning loop. In the first weeks:

  1. Watch your success metrics daily and look at where users drop off in the core journey.
  2. Talk to users — especially those who stopped using the product.
  3. Fix friction in the core journey before adding new features.
  4. Plan the next sprints based on evidence, not opinions.

Decide in advance what result would make you pivot, persevere or stop. That decision is much easier to make before the launch emotions kick in.

What an MVP costs

Costs vary with complexity, platforms and integrations. A focused web or cross-platform mobile MVP built by a small experienced team typically sits in the range of a few months of a senior developer’s cost — far less than a full product, and far more than a no-code prototype. Running costs at MVP scale (hosting, email, monitoring) are usually modest. Use our project cost estimator for a ballpark figure.

No-code or code?

No-code and low-code tools are excellent for validating ideas quickly, internal tools and landing pages. They can become limiting when you need complex logic, scale, specific integrations or full ownership of your intellectual property. A common path: validate with no-code or a concierge service, then build the MVP in code once demand is proven.

Frequently asked questions

Can an MVP really be built in 12 weeks?

Yes, for a focused product with a clear core journey and a decisive product owner. Complex integrations, regulated data or many user roles extend the timeline.

Web app or mobile app first?

Choose where your users are and what the core journey needs. A responsive web app is fastest to iterate; cross-platform frameworks such as Flutter make iOS and Android feasible within an MVP budget.

Who should own the code?

You should, from day one, in a repository under your account. This protects your investment and makes it easy to grow the team later.

What happens after the MVP?

You iterate based on user data: improve the core journey, add the most-requested features and scale infrastructure as usage grows.

Ready to build?

Our fixed-price MVP Launch Package follows exactly this roadmap: discovery, design, four build sprints, QA and launch, with 30 days of support afterwards. Not sure whether your idea is ready? Start with a Discovery & Blueprint or book a free call.

Sisusoft Team

Practical guides from the engineers and IT specialists at Sisusoft Technologies. We write about the problems we solve every day for small and growing businesses.

Keep reading

Related articles

Have a problem that technology should solve?

Tell us about it. We reply within one business day with honest next steps.