How long does it take to go from idea to a designed MVP?

The timeline can range from just a few days to as long as six months. This isn’t a vague non-answer; it reflects the reality, and understanding what drives this variation is far more valuable than any average.

It depends on what kind of MVP you’re building.

Not all MVPs are created equal. Before asking about timelines, it’s crucial to answer a more fundamental question: what is this MVP actually for?

A prototype MVP, something to show stakeholders, test with users, or validate a concept, can come together in days. This isn’t a fully built product. Instead, it’s a designed artifact that behaves like one. In Figma or Framer, a skilled designer can produce something realistic enough to generate meaningful feedback in a week or less. Fast, cheap, and deliberately disposable.

A go-to-market MVP, a real product in the hands of real users, is a different proposition entirely. Here, you’re designing and building, so design decisions must be robust enough for engineers to execute and the product must be coherent enough for real-world use. This is where six-month timelines come in.

Between these two extremes lies a wide spectrum. The right timeline depends on your stage, available resources, and how much you already understand about the problem you’re solving.

What actually takes the time

Founders often assume design is the bottleneck. In reality, it rarely is.

The true time sinks in an MVP process are decisions and alignment: getting the founding team to agree on what the product actually is, resolving conflicting assumptions about users, and making tough calls about scope when everything feels essential.

A designer can prototype a feature in a day. Getting three founders to agree on whether that feature should exist at all can take a week.

That’s why early-stage design work that surfaces decisions quickly through sketching, rapid prototyping, and structured workshops often speeds up the entire process. You aren’t simply adding a step. Rather, you’re replacing weeks of circular discussion with a tangible artifact everyone can react to.

Two real examples

In 2017, I joined Cluey Learning, an ed-tech startup in Sydney, as part of a small team responsible for designing and building their go-to-market product. We weren’t prototyping. We were building the real thing: a platform that needed to work for students, tutors, and parents simultaneously, with real sessions, real payments, and real accountability.

From early design through to launch took six months. That included significant time spent not just designing screens but figuring out the product: what the experience should feel like, how the three user types would interact, and where the friction points were before they became support tickets. Six months felt like a short time for what we were building.

At the other end of the spectrum, I worked on a new product at Zendesk that went from idea to working MVP in just 77 days. We didn’t cut corners on design. The real accelerators were a hard launch deadline, a tightly constrained scope, and focused tiger teams made up of experienced people empowered to make fast decisions. It was an all-hands-on-deck push in which urgency, alignment, and decisive execution set the pace.

What speeds things up (and it’s probably not what you think)

Adding more designers doesn’t make the process faster; increasing the number of decisions does.

The single biggest accelerant in any MVP process is a founder or product lead who can make quick decisions on scope, user priorities, and what’s in or out. A designer working with a decisive stakeholder will move much faster than a large team waiting for consensus.

A few things that genuinely compress timelines:

• Starting with a prototype, not a spec: reaction is faster than imagination.

• Defining the one user scenario that matters most: scope creep is the enemy of speed.

• Separating “must work at launch” from “nice to have eventually”: ruthlessly

• Treating the first version as a hypothesis, not a commitment, frees everyone to move.

The number to hold loosely

If you’re building a prototype to test an idea, think days to weeks.
If you’re building a go-to-market product, think three to six months, with design typically leading engineering by four to six weeks.

Before asking “how long?”, first ask: what do we need to learn, and what’s the fastest way to learn it? The answer to that question will reveal more about your true timeline than any estimate ever could.