Partners Running an agency? Partner with us
The Graylemon Journal Build logs, teardowns and method, by email. Subscribe All resources
Follow the studio LinkedIn Instagram
Partner with usBook a call (opens in a new tab)
Journal · Build log

PMF: why paying customers aren't product-market fit, and what we measure instead

At the PMF stage, the question is whether the right people want the product badly enough to keep using it. Payment proves willingness to pay; it doesn't prove fit. Fit shows up in retention: the people you built it for coming back without being asked, for the reason you built it. This is how we read the stage on our own ventures, why otlo's label says "paying customers" and not "fit", and what we do when retention isn't there.

The Stuck-to-Scale steps on a blueprint grid: six blocks rising on one base, with the fourth step, PMF, drawn solid.
Mihir PatelFounder, Graylemon
On this page

In short

  • PMF asks one question: do the right people want it badly enough to keep using it?
  • Paying customers are necessary, not sufficient. We claim fit only once retention data supports it.
  • The most common false positive is a handful of friendly design partners. They stay out of goodwill, not need.
  • When retention isn't there, we cut and narrow before we add. More features rarely rescue a product people don't come back to.

The most flattering sentence in product is "we have customers". It's true, it's hard-won, and it answers a different question from the one this stage asks. PMF isn't whether someone paid once. It's whether the people you built it for keep coming back, and whether you could tell a stranger exactly why.

01What is the PMF stage for?

PMF, product-market fit, is the fourth stage of Stuck-to-Scale. Its question is: do the right people want it badly enough to keep using it? Three phrases in it do the work.

  • "The right people" means the buyer you defined at Define, not whoever happened to turn up.
  • "Badly enough" means they'd be genuinely put out to lose it, not mildly pleased to have it.
  • "Keep using" means retention: coming back over time, without being chased.

PMF sits after Build because you can't measure retention on a product that doesn't work yet. It sits before Market because reach multiplies whatever you already have. Pour reach onto a product people don't keep, and you're paying to meet people who will leave.

02Why aren't paying customers enough?

Payment proves a buyer believed the promise enough to try it. Retention proves the product kept the promise. They're different events, and only the second one compounds.

otlo, our community intelligence product, is in market with customers paying real money. Its label on our site says exactly that: "In market, paying customers". It doesn't say fit, and that's a decision, not an oversight.

Decision · otlo's label stops at paying customers

  • What we chose: "In market, paying customers", on our site and wherever we describe otlo.
  • What we gave up: a stronger word, and the story it would tell anyone weighing the venture.
  • Why: paying customers prove willingness to pay. They don't yet prove fit, and a stage label is the first thing a careful reader checks.
  • What happens next: we'll claim fit once retention data supports it, and we'll show the evidence when we do.

We explain why stage labels matter so much to anyone judging a studio's portfolio in How to evaluate a venture studio before you back one.

03What does being stuck at PMF look like?

The false positive we see most is a handful of friendly design partners. They stay because they like the team, want to help, or aren't paying yet. Their retention is real, and it tells you almost nothing about a market. The other signals are quieter.

Signs a team is stuck at PMF, and what each usually means
SignalWhat it looks likeWhat it usually means
Growth only comes from pushingEvery new user needs a call from the founderThe product isn't pulling people back on its own
Features added to fight churnA new release for every customer lostA fit problem being treated as a feature problem
The loudest customer sets the roadmapOne account's requests fill the backlogFit with one customer, mistaken for fit with a market
Fit is always nearly thereEvery review ends with "a few more tweaks"Nobody wrote down what fit would look like
The wrong people stayThe users who retain aren't the buyer you definedThere may be fit, but with a different market than the plan

The last row isn't bad news. It's often the most useful finding of the stage. It just means going back to Define with better evidence than you had the first time.

04What do we measure at the PMF stage?

We decide what counts before we look, the same way we set kill criteria before a test, and we build the tracking into the product before launch rather than bolting it on afterwards.

  • Activation. The first moment a new user gets the value the product promises, defined in advance as a single event.
  • Retention, by the group people started in. Do users who began together come back, and does the curve level off instead of falling towards nothing?
  • Who retains. The buyer from Define, or someone else?
  • The repeated action. What do retained users do again and again? Whatever it is, that's the product, whatever the roadmap says.
  • Why people leave. Asked, not guessed.

Then we review those numbers every week with the person who decides, because a metric nobody acts on is decoration.

Insight

Retention is the one metric a user can't be persuaded into. Almost everything else can be bought.

05What do we do when retention isn't there?

Our first operating principle is cut, don't expand, and this is the stage where it matters most.

  1. Cut what retained users don't use. The product gets simpler, and the signal gets clearer.
  2. Narrow the buyer to the people who do retain, and re-run Define for them if the gap is large.
  3. Fix activation before acquisition. If new users never reach the first moment of value, more new users won't help.
  4. Decide against the stop line. The kill criteria were set before the test, so the result can't be argued away.

apprn is being judged exactly this way. It's in a live test with real salons, and its go or no-go decision will be made against kill criteria set before the test began. We'll publish the criteria before we publish the result, so the call can't be rewritten afterwards.

More features rarely rescue a product people don't come back to.

When the right people keep coming back, the question moves on: can we reach them repeatably, and will they pay? That's Market.

06Questions founders ask about PMF

How do we know when we've found product-market fit?

When the people you built it for keep using it without being chased, retention levels off instead of falling, and you can say why in one sentence. If you need persuading, you're not there yet.

Can a small number of customers show fit?

Yes, if they're the right customers and they keep using the product for the reason you built it. A few customers who stay out of goodwill show nothing.

Should we spend on marketing before PMF?

Carefully. Reach multiplies what you have. Before fit, spend on learning who stays and why, not on getting in front of more people.

What does Graylemon do at the PMF stage?

We build activation and retention tracking into the product, review it weekly with the person who decides, cut what retained users don't use, and hold the product to its stop line. We don't promise fit. We measure it.

Where this fits

AI Product Build designs activation and retention tracking into the product before launch, so you can tell fit from goodwill and see what the people who stay actually use.

  • Stage: PMF
  • Strategy
  • Launching a product
  • Source: method, own ventures

Search Graylemon

↑↓ Move↵ OpenEsc Close