Single feature MVP

Tomáš Veselý - podpořen AI
1 day ago
4 min read

We're building a comprehensive knowledge library about product development as part of our mission. The library is for anyone looking to make better decisions — primarily decisions about product development. Whether you're an inventor, a product manager, or a Chief Product Officer, using the right research methods and experiments increases your chances of building the right things for the right audience. Today we'll introduce the Single Feature Product validation method.

When to Use This Experiment?

A Single Feature Product is the right choice when you need to validate demand for a more complex product before investing time and money in it. Instead of building the whole platform, you build a single feature that solves one specific problem for a narrow target group — and you test it.

There's a hypothesis about one key feature that the value of the entire intended product rests on.
You need a market signal fast and at minimal cost.
You're targeting a narrow segment with one sharply defined problem.
A broad experiment risks damaging an established brand, so it's better kept separate.
You need clean data, free from the influence of surrounding features.

Basic Experiment Principles

The essence of the experiment is to narrow the product down to a single feature, deliver it to real users as a standalone feature, and see whether they want it.

Define the key feature. From the entire product concept, pick the one feature that solves a specific problem on its own and carries the largest share of the value.
Define the target niche. Identify the narrow group of users whose problem this feature solves better than anything else.
Build the feature. Build it as a standalone product with minimal scope — with no ties to the other intended features, and possibly no tie to the main brand either.
Deliver to users and collect data. Make the feature available to the target niche as a standalone offering and measure how the market responds to that single feature. The key metrics match the scope of the experiment: acquisition and email sign-ups (does the feature draw interest on its own?), activation (how many users actually use it), and direct feedback from early users that reveals their behavior, preferences, and pain points. Because the feature is isolated, the data isn't skewed by surrounding features and provides cleaner evidence. The signal to scale up gradually — adding more features — is when the single feature gains traction: users return, spread it further, and demand grows.
Identify the risks. The main risk is that too narrow a feature scope may not be compelling enough to draw users in at all. A single feature says nothing about whether the entire platform will work. It only confirms partial demand. On top of that, a positive signal from a small market niche may not generalize to the broader market. And you have to be ready to pivot based on the data rather than clinging to the original vision.

Real-World Experiment Example

Link to research:

Brothers Patrick and John Collison started working on Stripe in early 2010. The trigger was Patrick's frustration with how hard it was at the time to accept card payments on the web. Instead of building a complete payment infrastructure, they built just one narrow feature accepting card payments, which could be dropped into a website with a few lines of code (the famous "seven lines") — and they processed their first transaction within two weeks.

Demand was validated by the narrow tool itself, not by marketing. The Collisons deliberately held marketing back, and yet before its public launch Stripe had a waitlist of over a thousand developers, acquired almost entirely through word of mouth. That organic demand for a single feature was proof that the market need existed; only on this validated foundation did the tool grow into a full-fledged payment platform.

What Can Be Tested With This Experiment?

A Single-Feature Product is strongest at validating market demand: it isolates one feature, so the results aren't skewed by their surroundings. Specifically, you can test:

Market demand: whether one isolated feature attracts users on its own — the signal is organic sign-ups and repeat use without further incentive.
Willingness to pay: whether the narrow tool is valuable enough for users to pay for it, the signal is conversions to a paid version.
Choice of entry feature: which single feature is the must-have a platform can be built on, the signal is the feature people use on its own, without the rest of the product.
Technical feasibility: whether the key feature works reliably in live operation — the signal is completed real-world actions (transactions, tasks) with no manual intervention.
Activation and onboarding: whether a user reaches value quickly with minimal scope, the signal is a high share of activated users and a short time to first value.
Niche targeting: whether a narrow segment adopts the product faster than a broad audience, the signal is concentrated adoption within one niche.