🔍 Product-Market Fit

Introduction

You have demos that people like. Users tell you the idea is interesting. Investors nod. The team works well. Yet the same thing always happens: few users come back regularly, trials don't turn into paying customers, calls end with "let's touch base in a few months".

This is the point where many founders tell themselves a comfortable story: "we need more marketing", "we need more budget", "we need one more feature". Often that's not true. Often the problem is upstream: the market isn't pulling the product yet.

The Product-Market Fit framework serves exactly for this: understanding if you're building something a specific segment really wants, enough to use it, pay for it, recommend it and keep using it. Steve Blank synthesized it well years ago: many startups fail not because they can't develop a product, but because they don't find real customers. Eric Ries then transformed this intuition into a rapid learning process based on testing, feedback and iteration.

When you have this clarity, everything changes: roadmap, pricing, sales, fundraising, hiring. When you don't have it, you risk "scaling noise": you spend more to amplify a product the market tolerates, but doesn't want.

What is Product-Market Fit and why it matters

Product-Market Fit isn't "having a good product". It's the alignment between a product and a specific market segment that really wants it. Marc Andreessen made the idea famous by defining it as being in a good market with a product capable of satisfying it. Bill Aulet formulates it equally practically: there is PMF when your product matches what customers in a specific market are interested in buying. (pmarchive.com)

It matters because before PMF you're still gathering evidence. After PMF you can start optimizing growth, channels, pricing and organization. This is why the framework became universal: it prevents confusion between weak signals—compliments, successful demos, vanity metrics—and the only evidence that really counts, which is repeated use, retention, organic demand and willingness to pay. (pmarchive.com)

How to use it: step by step

1. Define a small market, not "anyone could use it"
PMF is not sought across an entire continent or generic sector. It's sought in a precise beachhead market. You need to be able to say: "we're building for HR managers at 50-200 person SMBs in Germany who've outgrown Excel but can't justify enterprise stack". If the market is too broad, every feedback will be contradictory and you'll never know if the problem is the product or the segment. This approach aligns with Disciplined Entrepreneurship's beachhead market and customer profile logic.

2. Formulate a painful and frequent problem
The product doesn't need to be "useful". It needs to remove concrete, costly or frustrating pain. Interview real users and get them to tell you what they do today, how much time they waste, what workarounds they use, what slows them down and what makes them angry. The right questions aren't "would you like this solution?", but "how do you solve it today?", "what does it cost you?", "when did you last live this problem?". The principle is simple: stop selling, start listening; the facts are outside your building.

3. Build the minimum offering that solves that problem
Here many founders get it wrong: they think PMF requires a complete product. No. It requires a product focused enough to be tested on real users. MVP doesn't mean a poor product; it means a focused product. One key feature used often beats ten features ignored. The goal isn't to impress the market. It's to learn fast if the core value really exists.

4. Measure qualitative and quantitative traction signals
To understand if you're approaching PMF look at four signal families: retention, frequency of use, willingness to pay and advocacy. In B2B SaaS also observe activation time, trial-to-paid conversion, expansion into additional modules or seats, sales cycle length and referrals. If you use the Sean Ellis test, the key question is: "How disappointed would you be if the product disappeared?"; exceeding 40% "very disappointed" is a strong signal, though not enough on its own. (pmfsurvey.com)

5. Iterate on segment before iterating on feature
If the data doesn't work, don't immediately add features. First ask yourself: are you talking to the right customer? A classic mistake is keeping the wrong target fixed and changing the product infinitely. Sometimes PMF comes not when you improve the software, but when you narrow the segment, change positioning or shift the dominant use case. The right cycle is build, measure, learn, then decide whether to persevere or pivot.

5 Best Practices

Start with customers in most pain, not the largest market
Founders finding PMF fastest don't immediately chase maximum TAM. They seek a small group with intense, frequent and urgent pain. If the problem is truly felt, they more easily accept clear feedback and you get legible signals.

Measure behavior, not enthusiasm
"Beautiful product" means nothing. "I've used it three times this week" means a lot. PMF shows in action: repeated use, renewal, introduction to colleagues, request for expansion.

Keep direct contact with users
Until you have PMF, the founder can't fully delegate customer discovery to sales, marketing or research. You need to listen directly to calls, demos, objections and use cases. That's where you understand if value is real or just presented well.

Cut without mercy what doesn't move retention
Many early-stage roadmaps are full of cosmetic features. Keep only what increases activation, frequency of use, conversion or renewal. Everything else is technical noise or product ego.

Use a small but serious dashboard
Few KPIs, updated often: retention, conversion, time to first value, referrals, expansion. If every week you change metrics or only look at vanity numbers like impressions, visitors or raw sign-ups, you're telling yourself a story.

3 Common Mistakes to Avoid

1. Mistaking paid growth for PMF
It happens when a startup buys traffic, does aggressive outbound or forces repeated demos and interprets leads as proof of value. They're not. If when you stop pushing the demand evaporates, you don't have PMF: you just have temporary distribution.

2. Adding functionality instead of solving the core problem
It's the typical reflex of good building teams. Every piece of feedback becomes a new feature. The result is a more complex product, not a more desirable one. If the user doesn't perceive clear value in early interactions, more features rarely save it.

3. Running interviews that collect politeness, not truth
"Would you use it?" is a terrible question. "Would you pay?" said in the abstract too. People want to be kind. To avoid this, ask about present and past: how they solve it today, how much they spend, how much time they lose, who decides, what they've already tried. Behavior beats declared opinions every time.

Real Example: Personio

Personio is a very useful case because it didn't try to "do HR for everyone". It chose a very specific market gap: SMBs grown too large for Excel but too small to justify heavy, expensive enterprise stacks. Founded in Munich in 2015, today Personio presents itself as an HR platform for companies of 10 to 5,000 employees; its official story shows founding in 2015 and passing 10,000 customers in 2023. (Personio)

In the case you provided, PMF signals are almost from a textbook. The first is very low churn. If customers stay, the product isn't just interesting: it enters processes. The second is NPS above 60. To provide context, Bain explains that for many companies the average NPS range for relationship/episode sits around 30–40; staying consistently above 60 means being in a very strong loyalty band. (Bain)

The third signal is even more important: spontaneous referrals above 40% of new customers. When word-of-mouth starts to really matter, it means you're not just selling with your commercial team anymore. The market starts working for you. The fourth is the Sean Ellis test: over 40% of customers would say "very disappointed" if Personio disappeared. It's not a vanity metric; it's a direct measure of perceived dependence on the product. (pmfsurvey.com)

Then there are two signals many founders undervalue. One: sales cycles shorten. This shows the market understands the category better and better grasps the product's value. Two: expansion revenue happens even without strong commercial push, because customers add modules. When those who already bought you expand spontaneously, PMF isn't just at entry: it's consolidating over time.

The key point, though, is this: Personio doesn't seem to have found PMF by doing "more stuff". It found it by choosing an underserved segment, speaking its operational language and building a markedly better solution than the status quo. Not "more innovative" in the abstract. More useful, more buyable, more adoptable.

When you don't have it yet

For an early-stage founder, this is the most useful part. You probably don't have Product-Market Fit yet if:

• each new sale requires heavy educational effort and the customer doesn't immediately see why your product is necessary;
• users activate, but don't return regularly;
• your sales team only closes with discounts, customizations or roadmap promises;
• pilots start, but few become real contracts;
• the product appeals to one champion inside, but doesn't generate team-wide adoption;
• customers don't spontaneously recommend you;
• the moment you stop pushing, the pipeline empties;
• every call changes your direction, because no dominant use case emerges yet.

In summary: when you have PMF you feel pull. When you don't, you're pushing everything the time.

Recommended Resources

• The Lean Startup — the most useful book to understand validated learning, MVP and build-measure-learn cycle — https://theleanstartup.com/ (theleanstartup.com)
• The Mom Test — practical guide to run serious customer interviews and stop collecting useless compliments — https://www.momtestbook.com/ (The Mom Test)
• The only thing that matters — the classic text by Marc Andreessen on the operational meaning of Product-Market Fit — https://pmarchive.com/guide_to_startups_part4.html (pmarchive.com)
• PMFsurvey — free tool to run the Sean Ellis test and track the "very disappointed" signal — https://pmfsurvey.com/ (pmfsurvey.com)
• Strategyzer Test Card — free template to transform assumptions on customer, problem and solution into concrete tests — https://strategyzr.s3.amazonaws.com/assets/vpd/resources/the-test-card.pdf (strategyzr.s3.amazonaws.com)

Next Step with IdeaLedger

If you want to use this framework on your idea, on IdeaLedger you'll find the interactive tool—coming soon—to transform assumptions, interviews, traction signals and market tests into a guided path. Not to "inspire" you, but to quickly understand if the market is really saying yes to you.