The Product-Market Fit Pyramid: A Founder's Guide

Dan Olsen's Product-Market Fit Pyramid stacks five layers, bottom to top: target customer, underserved needs, value proposition, feature set, and user experience. The bottom two layers define your market; the top three define your product. You reach product-market fit by building each layer to fit the one directly beneath it, in order.

Quick Answer: The Product-Market Fit Pyramid is a five-layer model from Dan Olsen's The Lean Product Playbook for pursuing fit on purpose instead of by luck. Build from the bottom up. Get the target customer right, and every layer above it has a foundation. Skip a layer, and everything stacked on top inherits the crack.

Most founders treat product-market fit as a mysterious event that either happens to you or doesn't. Olsen's argument is the opposite: fit is a structure you can build deliberately, layer by layer, and each layer either rests on solid ground or on a guess. The pyramid turns a vague aspiration ("we need product-market fit") into a diagnosable stack, so when growth stalls you can point to the exact layer that failed instead of blaming the whole idea.

This guide walks each of the five layers from the base upward, explains why the model splits the market from the product, and shows how the Lean Product Process builds the pyramid step by step. By the end you'll be able to locate where your own product is weak, and in what order to fix it.

Why the Product-Market Fit Pyramid separates market layers from product layers

The pyramid draws a hard line through the middle: the bottom two layers are your market, and the top three layers are your product. Product-market fit, in Olsen's definition, is the moment your product (the top three) genuinely satisfies the market (the bottom two). Everything else in the model exists to make that fit inspectable.

The market is the problem space. Your target customer and their underserved needs describe what people want and why — the problems that exist in the world whether or not you ever ship anything. You don't invent this layer; you discover it. That distinction sits at the heart of Olsen's method, and it's worth internalizing through the wider lens of problem space versus solution space thinking before you touch a single feature.

The product is the solution space. Your value proposition, feature set, and UX describe how you intend to serve those needs. This is the part you control and build. The critical mistake founders make is starting here — designing screens and shipping features — before the two market layers underneath are solid.

The order is not decorative. Each layer is a foundation for the one above it, so the pyramid must be built bottom-up:

• Your underserved needs only make sense relative to a specific target customer.
• Your value proposition is a promise about which of those needs you'll meet better than alternatives.
• Your feature set is the concrete delivery of that value proposition.
• Your UX is how the customer actually experiences those features.

Here is how the five layers map to market versus product and the question each one answers:

Read the table bottom-up and the logic becomes obvious: each higher layer is only answerable once the layer below it is settled. You cannot honestly define a value proposition until you know whose unmet needs you're addressing. This is why "we'll figure out the customer later" is such an expensive sentence.

Layer 1: Target Customer — deciding exactly who you build for

The base of the pyramid is a precise definition of the specific customer you are building for, because every layer above it is measured against that customer's reality. Get this wrong and the whole stack tilts, no matter how good your engineering is.

Specificity is the whole point. "Small businesses" is not a target customer; it's a category containing millions of contradictory needs. Olsen pushes founders toward a sharply defined segment — the kind of customer you could picture, name, and go find this week. The narrower and more concrete the definition, the sharper every decision above it becomes.

Personas make the abstraction usable. Olsen recommends building target-customer personas: a synthesized, semi-fictional profile that captures the segment's goals, context, behaviors, and constraints. A good persona is a decision tool, not a marketing artifact — you hold feature ideas up against it and ask, "does this matter to her?"

A common trap is choosing your target customer to match the product you already want to build. That reverses the pyramid. The customer comes first precisely because they are the fixed point everything else must fit. If you find your definition conveniently expanding to include everyone your features might appeal to, you've stopped defining a market and started rationalizing a product.

Layer 2: Underserved Needs — finding the problems worth solving

The second layer identifies the specific customer needs that are important yet poorly served by existing options, because unmet importance is exactly where opportunity lives. A need that's both highly important to your customer and badly served today is the gap your product can profitably fill.

Needs live in the problem space, not the feature space. A need is an outcome the customer wants — save time on invoicing, feel confident the numbers are right, avoid embarrassing errors. It is emphatically not "an invoicing dashboard." Features are your proposed solutions; needs are the underlying jobs those features are meant to accomplish. Keep them separate or you'll validate your solution instead of the problem.

The gap is importance minus satisfaction. Olsen frames opportunity as the space between how important a need is and how satisfied customers currently are with existing options. Two questions locate it:

• How important is this need to the target customer, on its own terms?
• How satisfied are they with the best solution available today?

High importance plus low satisfaction is an underserved need — the sweet spot. High importance plus high satisfaction is a crowded, defended market. Low importance is a distraction regardless of satisfaction. Mapping needs on these two axes tells you which problems are actually worth building for.

Stay in the problem space while you gather needs. The moment a customer says "you should add a button that does X," it's tempting to write it down as a requirement. Resist. Translate it back into the underlying need — what were they trying to accomplish, and why does the current option fall short? Solutions are cheap and plentiful; a clearly articulated, important, unmet need is rare and valuable. Keeping the distinction between the problem space and the solution space sharp at this layer is what stops you from validating your own assumptions back to yourself.

This is the layer where founders benefit most from disciplined evidence-gathering rather than intuition. Customer interviews, need mapping, and structured capture of what you hear turn a hunch into a ranked list. A validation platform like Edmired exists to make that capture and ranking a repeatable habit, so the needs feeding your value proposition are the ones customers actually voiced, not the ones you assumed.

Layer 3: Value Proposition — how your product wins the needs it targets

The value proposition is your deliberate decision about which underserved needs your product will meet and how it will beat the alternatives at meeting them. It's the first layer of the product and the hinge where the problem space finally becomes a solution. Every feature you later build should trace directly back to a promise made here.

A value proposition is a set of choices, not a slogan. It commits you: these needs, not those; this dimension of superiority, not that one. Olsen frames it as the intersection of the needs you'll serve and where you'll be better than competitors. Trying to serve every need equally well produces a product that's better at nothing — the definition of no value proposition at all.

Differentiation must be against the real alternative. The competition is not just rival apps; it's whatever the customer does today, including spreadsheets, workarounds, and doing nothing. Your value proposition has to win against that baseline, on the needs your target customer actually cares most about.

Deciding what to leave out is part of the work. A strong value proposition names the needs you will deliberately underserve so you can dominate the ones that matter most. Founders resist this because saying no feels like losing ground. In practice, a focused promise on three needs beats a diluted promise on ten, because the customer feels the difference on the axes they weigh most heavily.

Layer 4: Feature Set — the MVP that delivers your value proposition

The feature set is the specific functionality you build to deliver on your value proposition, and Olsen's guidance is to ship the minimum viable version of it first. The MVP feature set is the smallest bundle of features that delivers enough value to let real customers validate the promise you made one layer down.

Features are hypotheses, not commitments. Each feature is a bet that it will deliver some slice of your value proposition to the target customer. Because it's a bet, it should be prioritized by expected benefit — how much this feature moves the needle on an important, underserved need — rather than by how easy or fun it is to build.

"Minimum" and "viable" are in tension on purpose. Cut too much and the MVP doesn't deliver enough value to test anything meaningful; the customer can't tell whether your value proposition is true. Include too much and you've spent months building before learning anything, which defeats the point. The MVP feature set is the smallest thing that still delivers a genuine, testable dose of your value proposition.

Prioritization is the core discipline of this layer. Olsen recommends ranking candidate features by their expected benefit to the target customer, then drawing the line at the smallest set that clears the bar for a real test:

• Must-have features deliver the core of the value proposition; without them there's no product to test.
• Nice-to-have features add value but can wait for a later iteration.
• Low-priority features address minor needs or serve customers outside your target segment.

The point isn't to build a small product forever. It's to build the smallest product that produces real learning, so the features you invest in next are the ones evidence tells you to build.

Layer 5: User Experience (UX) — how customers actually perceive your features

The top layer is the user experience: the design and interaction that make your features tangible to the customer, because features only exist to a user through the UX that surfaces them. Your customer never touches your feature set directly — they touch the interface, the flow, the words, and the feel. That experience is the product to them.

UX is where invisible value becomes felt value. A feature can perfectly serve an underserved need and still fail if the customer can't find it, understand it, or trust it. Great UX reveals the value your features contain; poor UX buries it. The layer sits at the top of the pyramid precisely because it's the surface everything below it has to reach the customer through.

But UX cannot rescue a broken lower layer. This is the most important thing to understand about the top of the pyramid. A beautiful, frictionless experience wrapped around features that don't serve a real underserved need is a polished answer to a question nobody asked. Design excellence is necessary but never sufficient — it amplifies whatever is beneath it, for better or worse.

That direction of dependency runs the whole pyramid. UX amplifies the feature set; the feature set delivers the value proposition; the value proposition targets underserved needs; and those needs belong to a specific customer. Strength at the top cannot compensate for weakness at the bottom.

How the Lean Product Process builds the pyramid from the bottom up

Olsen pairs the pyramid with the Lean Product Process, a six-step method that constructs the five layers in order and then tests them with real customers. The pyramid is the what; the process is the how — a repeatable loop for building each layer on evidence rather than assumption.

The six steps map almost one-to-one onto the layers, then add the two build-and-test steps that turn the model into an experiment:

Steps one through four build the pyramid bottom-up. You settle each layer before starting the next, so your value proposition rests on real needs and your feature set rests on a real value proposition.

Steps five and six turn the pyramid into a test. You build a prototype that expresses your MVP feature set through actual UX, then put it in front of target customers to see whether the value proposition holds. Their reaction is data about every layer at once.

Then you iterate. The process is a loop, not a line. Test results send you back down the pyramid to revise whichever layer the evidence indicts — sometimes a feature, sometimes the value proposition, occasionally the target customer itself. For the full step-by-step mechanics of each stage, see our guide to the six steps of the Lean Product Process, which unpacks how to run the loop in practice.

The reason this beats "build it and see" is that it localizes failure. When customers don't respond, the process tells you which layer to interrogate instead of leaving you to rebuild everything.

Why building the pyramid out of order breaks product-market fit

Building the layers out of order is the most common way founders fail at product-market fit, because a layer built on an unverified layer beneath it is a guess dressed as progress. The pyramid's whole value is the discipline of sequence — and skipping it produces predictable failure modes.

Starting at the top: features and design first. The classic startup death is building a polished product before confirming anyone needs it. You end up with excellent UX over a feature set that delivers a value proposition nobody wanted, aimed at a customer you never defined. Every layer is competent and the pyramid still collapses, because the base was never there.

A vague target customer poisons everything above it. If layer one is "everyone," your needs list is unfocused, your value proposition can't differentiate, and your feature set sprawls to cover contradictory demands. Diagnosing this after the fact feels like a hundred small problems; it's really one problem at the base.

An undifferentiated value proposition breeds a me-too feature set. Skip the hard choices at layer three and your features drift toward copying competitors, giving customers no reason to switch from what they already use. The failure looks like weak features; the cause is a missing decision one layer down.

Out-of-order building also hides which experiment you're running. When you ship a fully built, well-designed product and it lands flat, you've conflated five questions into one launch and can't tell which layer failed. Did customers not want it, not understand it, or not find it better than their spreadsheet? Building bottom-up and testing with an MVP keeps the layers separable, so each round of feedback implicates a specific layer instead of condemning the entire idea. Cheaper experiments produce clearer verdicts.

Here's the diagnostic power of the model: when something isn't working, you walk down the pyramid until you hit the lowest weak layer, then rebuild upward from there. Weak UX might be a design problem — or it might be a symptom of features that never mattered. The pyramid tells you where to look. This diagnostic discipline is exactly why the model pairs so well with a rigorous definition of product-market fit and how to measure it: the pyramid locates the broken layer, and a fit metric tells you whether your fixes are working.

Key Takeaways

• The pyramid has five layers, built bottom to top: target customer, underserved needs, value proposition, feature set, and user experience — and each one is the foundation for the layer above it.
• The bottom two layers are your market, the top three are your product. Product-market fit is the moment the top three genuinely satisfy the bottom two.
• The market is the problem space and the product is the solution space. You discover the bottom two layers and you build the top three — confusing the two is the root of most misfires.
• A target customer must be specific enough to name and find. "Everyone" at the base guarantees an unfocused product all the way up the stack.
• Underserved needs are where importance is high and current satisfaction is low. That gap, not your feature ideas, defines the real opportunity.
• The MVP feature set is the smallest bundle that still delivers a testable dose of your value proposition — small enough to learn fast, viable enough to prove the promise.
• When product-market fit fails, walk down the pyramid to the lowest weak layer and rebuild upward. Strength at the top can never compensate for weakness at the base.

Frequently Asked Questions

What are the five layers of the Product-Market Fit Pyramid?

From bottom to top: target customer, underserved needs, value proposition, feature set, and user experience (UX). The bottom two layers make up your market; the top three make up your product. You build them in order, because each layer depends on the one directly beneath it being solid.

Who created the Product-Market Fit Pyramid?

Dan Olsen created the Product-Market Fit Pyramid and introduced it in his 2015 book The Lean Product Playbook. He pairs the pyramid with the six-step Lean Product Process, a repeatable method for building and testing each layer with real customers rather than treating product-market fit as luck.

Which layers of the pyramid are the market and which are the product?

The bottom two layers — target customer and underserved needs — are your market, or problem space. The top three layers — value proposition, feature set, and UX — are your product, or solution space. Product-market fit is achieved when your product layers genuinely satisfy your market layers.

How is the pyramid different from the Lean Product Process?

The pyramid is the model of what product-market fit is made of; the Lean Product Process is the how — a six-step loop for building each layer and testing it. Steps one through four construct the pyramid bottom-up, and steps five and six build a prototype and test it with customers, then you iterate.

Where should a founder start when building the pyramid?

Start at the base: define a specific target customer, then identify their underserved needs before designing anything. Building top-down — features and UX first — is the most common failure mode, because it stacks a polished product on a market you never verified. The base is the fixed point everything else must fit.