Learn How to Launch An MVP In One Minute

Key Takeaways

A Minimum Viable Product centers upon the idea that you should release a new product ASAP. Don’t spend nine months building all the features. Instead, build the most important features — just enough to learn whether or not people even want the thing you’re making.

Repeat after me: an MVP means getting the most learning for the lowest amount of effort. Ask yourself, “How can I get this product in front of people as quickly as possible?”

Example of Minimum Viable Product in action

  • Dropbox started as an MVP
  • Here at One Month, we use Launchrock to build a landing pages, and to collect email addresses for classes that aren’t yet in development. This helps us learn which classes are most in demand.

How to Learn to Build an MVP Today

  1. Steve Blank, and Eric Reis: Read about the experts and follow them on Twitter (5 minutes).
  2. Data Drive Products Now! (slideshow): Check out this cool case study from on Etsy developer Dan McKinley (12 minutes).

Additional Resources

No One Cares (About Your MVP)

In this Founder Friday, I answer your questions about MVPs. Questions like:

“How early should I release my MVP?”

(It was basically just iterations of the same question haha)

Look, there are three parts to an MVP.

Product, that’s the obvious part.

Minimum, it should only have the features that it needs. Here you should tend towards less rather than more. It’s your baby and you’re afraid people are going to make fun of it, so you want to give it as much of a chance of success when you release it as possible so you keep adding all these features and polishing it up so it looks good.

But what you don’t realize is that by doing all that adding of features, you’re likely killing its chance of success in the real world — first, because you risk someone else coming in and building it before you, and second, because more features and more polish doesn’t necessarily mean better.

Many products that are successful are actually simplified products of things that already exist. Twitter is just Facebook without all of the other features, and a 140 character limit.

But what counts as minimum? Well that depends on the second word, Viable.

You will only have a GUESS as to what minimum features constitutes a viable product, and you have to actually release it to see if your guess is right. If your product is too minimal to be viable when you release it, then it won’t get usage. So what? No big deal. At least you didn’t waste any time building additional stuff that no one needed.

Then you can go back to the drawing board and think about how your product needs to change in order to be viable. But at least you got really useful information.

That’s one thing that a lot of people don’t realize. If you release your product and it’s not viable — aka no one uses it — then no one will care. It’s not like everyone will know your product is lame and will boycott it and never use it again. No — repeat after me: NO ONE CARES (about your MVP). And that’s a good thing. Now go learn something.

What is a Minimum Viable Product?

It’s a tool for finding product market-fit (AKA when people love your product and/or want to pay you for it) Wikipedia some great info on when you’ve achieved product market fit.

It’s something you can change quickly.

According to Steve Blank “An MVP allows you to gain maximum amount of learning in the shortest amount of time”.

It’s a tool that helps you discover your early adopters, get early revenue, and gather data on the viability of your business. Whether you’re building a business to business application or a consumer facing app, an MVP is a critical tool for helping ensure you nail your startup’s business model before you invest in scaling.

Here are important aspects for discovering and building a useful Minimum Viable Product.

The prototyping team.

If you’re in a startup, chances are you’re burning through cash and that you need to move quickly from idea to revenue. Perhaps the most important aspect of any startup is it’s team. In the earliest stages, this team should consist of three types of people, the hacker, hustler, and designer. I won’t go too deep into each of these roles but it’s important to note that skills in sales and rapid prototyping are key to being able to move quickly and iterate on the design of your product during MVP development.

Build things that don’t scale.

Paul Graham, founder of Y Combinator, wrote an excellent article about the idea of building things that don’t scale. A common mistake entrepreneurs make is writing code too early and trying to build out a fully functional product. Depending on the market you’re attacking, you may be able to build a high-fidelity MVP that is really just a bunch of interconnected and clickable mockups. This could be enough of you to pre-sell early adopters without actually writing a single line of code.

Another option is to leverage existing services like WordPress and Google forms and create a version of your service that looks automated on the front end while in reality, you’re behind the curtain manually making the service run. The point here is to try and test whether someone will pay you to actually execute your value proposition.

Know what you’re measuring.

When I’m testing a B2B Saas business, I often use a version of the High-fidelity MVP to try and get early adopters to either sign a letter of intent or pre pay me to build the service. In this case, I’m measuring the number of customers I talk to who are actually willing to pay. However, when building say the next Twitter, you might be testing ways to drive traffic to a landing page where you’re asking people to give you their e-mail to get on a waiting list. In this case you’re measuring conversion rates and you have a pass/fail metric that will help you determine whether the MVP is a success or not.

If you aren’t measuring and capturing data with you’re MVP, you’re going to have a tough time demonstrating the evidence for why your business will be viable.


It’s important to remember that the MVP is not a final version of your product. Whether your MVP is actual code or clickable mockups, you’re not intending to keep any of the work you’re doing. You need to have mentality that the MVP is just a prototype that can be changed at anytime. This is why the prototyping team is so important at the earliest stages. You need people who move quickly and don’t get stuck in building something that’s perfect but rather something that gets you maximum learning in the shortest amount of time. When the evidence dictates you need to pivot, they’ll be ready to pull an all nighter and pump out the updated version.

But wait, How do I even decide where to start? and Can I start now with just a one person team?

In my work with startups, schools, and corporations, these are a questions I get all the time.

Start by talking to customers. If you’ve got an idea for a specific market, reach out to target users and ask them to tell you about the challenges they face. Try and focus on their pain points and then sketch out your first MVP on the back of a napkin. Then get feedback from the user. Repeat this ten times until you have a good understanding of the pain you’re trying to solve. This will help you have a much better understanding of what MVP you should try to build first.

A huge part of being an entrepreneur is being able to recruit talented people to join you. You’re constantly selling your vision and mission to potential partners and employees and asking them to give up cash and opportunity to follow you into your startup. That said, it is possible to start building your startup with just a one man team. In our One Month MVP course, I’ll dive deep into the steps you need to take to help sell, design, and build your first MVP without writing a single line of code. If you’re working alone or with the ideal prototyping team you’ll be able to use the evidence you gathered and the prototypes you build to help sell your vision to investors, partners, and you’re first customers.