11 different Types of MVPs to Kickstart Your Software Project

We’ve broken this list down by low-fidelity MVPs and high-fidelity MVPs, and we’ve added one wildcard at the end that could fall into either category depending on your strategy.

We’ll start our discussion with high-fidelity MVPs since they require the most time and effort to build and launch, then we’ll move on to low-fidelity MVP types.

Keep in mind that many startups use a low-fidelity MVP as the first step toward validating their idea. They then go on to create a high-fidelity MVP once they’re confident there’s a market for it.

Single-feature MVP

The single-feature MVP is what most people think of when they imagine an MVP, so we’ll start there. As the name implies, it delivers on one feature and one feature alone—that key differentiator that will hopefully allow your new product to stand out in the marketplace.

An example of a single-feature MVP was Spotify, which streamed music and nothing more. Prior to Spotify, people bought and downloaded songs from the Apple store for 99 cents, so Spotify needed to determine whether there was a market for streaming.

Use cases:

• Allows companies to validate a novel idea or a unique take on an existing service
• Gives perfect clarity surrounding that single feature and how to improve it

Piecemeal MVP

MVPs are designed to be as simple as they need to be, but no simpler! In other words, they must include all the necessary tools to deliver the product’s core functionality, and that may involve a number of processes behind the scenes.

A piecemeal MVP uses third-party tools and technologies to bring everything together, rather than having the software development team build each component.

For example, an MVP for a B2B app that allows it to generate coupons and discount codes might require PDF generation, email integration, file management, and search capabilities.

Launching a piecemeal MVP is much easier and far less expensive than building an MVP with all those backend technologies from scratch. It allows the product development team to validate their value proposition and start gathering user feedback relatively quickly.

Use cases:

• Complex products that rely on a number of established technologies
• Industries that are mature and developed

“Wizard of Oz” MVP

The Wizard of Oz MVP creates the appearance of a fully automated software solution. In reality, however, there’s a human being behind the scenes completing the actions that your fully functional product will someday perform.

Imagine an app that books “onward tickets” so that digital nomads with one-way tickets don’t experience any hassles when entering a new country.

It may appear as though, with the press of a button, the system books a new refundable ticket you can show to the airline before boarding. In reality, however, there’s someone booking the flight and canceling it 48 hours later.

Amazon’s original website is another example of a Wizard of Oz MVP, even though the term didn’t exist back in 1995. People would place orders for books, and someone would place the order manually on the backend.

Use cases:

• Excellent way to validate an idea while keeping MVP costs in check
• Ideal for new features or new products that the market hasn’t seen before

Concierge MVP

A Concierge MVP is a website or platform that connects customers with people who want to perform a given task. Instead of creating an automated solution, the Concierge MVP receives a command from potential customers, and a human being fulfills it.

Does that sound a lot like the Wizard of Oz MVP we just talked about? Of course it does, because it’s nearly the same thing with one key differentiator. The Wizard of Oz MVP creates the illusion of automation, just like the wizard did in Dorothy’s adventure.

By contrast, the concierge MVP is fully up-front about what it’s doing—there’s no “man behind the curtain” because there’s no curtain.

Use cases:

• Concierge MVPs help product teams assess the viability of their solution
• Teams will often form partnerships with other companies to run the manual processes

Crowdfunding MVP

The Crowdfunding MVP could be categorized as low-fidelity or high-fidelity, depending on whether you’ve got a working model of the product that people can download and explore during your campaign.

Crowdfunding is an excellent way to build buzz around an interesting, novel product idea. If people are willing to back your idea and you reach your funding goal, you’ve definitely validated demand for it. It’s also a great way to build an initial user base. And of course, the funding can help startups get off the ground with minimal investment.

Use cases:

• Startups with novel ideas that could catch on
• Entrepreneurs who need extra cash to get a project going

Landing page MVP

A landing page MVP is a low-fidelity MVP, as are all the MVP types that follow. As the most basic type of MVP available, it simply consists of a landing page that touts your upcoming product idea without requiring you to spend weeks or months in MVP development.

Rather than creating a functional product, the landing page MVP is used to garner interest and build an email list of potential users who may want to test your high-fidelity MVP when it’s available. It’s essentially the first step toward validating the product idea, and it’s a solid marketing strategy.

Use cases:

• Companies validate product ideas based on the interest the landing page MVP garners
• Landing page MVPs can help build that initial user base

“Fake door” MVP

The Fake Door MVP is similar to the landing page MVP, but it goes a step further by advertising a product or feature as though it actually exists. This provides solid data on whether someone would be willing to purchase the product, rather than evaluating hypothetical interest.

What happens when someone clicks to purchase it? That’s when you reveal that the product or feature set is still under development. That runs the risk of annoying customers, so use this approach sparingly.

Test just enough potential users to validate your idea. Once you do so, get to work building a product or feature set they’re willing to pay for.

Use cases:

• Teams testing a new product idea where they want to be sure people are willing to pay for it
• Established products that want to introduce new features or a new category of subscription plan

Marketing campaign MVP

A marketing campaign MVP makes full use of all the different marketing channels available to product development teams today, including:

• PPC advertising
• Social media marketing
• Forums (such as Reddit)
• New product platforms (such as Product Hunt)
• Any other popular advertising method

By garnering interest and getting potential users to sign up for your mailing list and receive updates, you’ll both build your user base and validate your product.

Use cases:

• Companies looking to validate a product idea and build a user base
• Teams hoping to identify key selling points of a new product idea

Email campaign MVP

An email campaign MVP, or email MVP, is similar to the marketing campaign MVP, except that it focuses exclusively on marketing your MVP through email. This can work great if you’ve got a solid email list or you can partner with someone who does.

Just avoid purchasing lists or spamming people who didn’t opt into your list because that can get you in all kinds of hot water. It can put your domain onto spam lists, and it can destroy your brand.

Use cases:

• Companies with an established email list can test a new product idea
• Teams that want to avoid spending money prematurely on MVP marketing campaigns

Pre-order MVP

A pre-order MVP offers customers the opportunity to pay upfront for a product you promise to deliver at a later date. This can work well for established companies that have already delivered products that users love, but it will be a hard sell for a startup with nothing to support its credibility.

The pre-order MVP is the ultimate form of validation for a low-fidelity MVP because people vote with their money. It also allows you to make money upfront, which you can allocate toward building a better product.

That said, it does lock you into those promises. If you don’t deliver the features you said you would deliver, or you miss your delivery dates, people may be upset. In fact, you could be legally liable if you fail to meet those deadlines since people have already paid for the product.

Use cases:

• Companies that have already sold successful products and have a reputation for excellence
• Teams that want a strong degree of product validation

Explainer video MVP

An explainer video MVP uses, as the name implies, a short video to explain a hypothetical product—just like those that companies use to explain existing products. The difference is that an explainer video MVP’s call-to-action is usually to sign up for the mailing list and get updates when the product is available.

Explainer videos are effective at helping people understand how unique products work. Dropbox’s MVP was an explainer video, which was helpful at the time because off-site storage was something enterprises used (not regular people or small businesses).

Use cases:

• Companies seeking to explain a product that many people aren’t familiar with
• Organizations looking to validate a complex idea