Pre-PMF

For years, companies answered the question "the product is finished, so why isn't it selling?" the same way every time: not enough people have heard about it. So they bought ads, hired salespeople, and shipped more features.

The trouble was that two different situations had no separate names. Early weakness comes in two forms with opposite treatments. In one, there are people who want the product and they simply don't know it exists. In the other, they will still not want it after they hear about it. Money spent on the first form works. Money spent on the second disappears at the rate you spend it. The two look identical on a dashboard for the first few weeks, which is why the wrong treatment was so easy to pick.

The meetings went like this. A founder asks why revenue is flat when 800 people signed up this month, a marketer answers that reach is too low, and next month's ad budget doubles. Signups reach 1,600, and a month later the number of people still around is the same thirty-something it always was. The door got wider, but nobody stays in the room.

Pre-PMF is the name for that second situation. It says the product has not yet reached product-market fit, the state where what you built lines up with real demand in a specific market. What the stage asks of you is not more reach. It's finding out why the few people who stayed, stayed.

Numbers go up without accumulating. Signups happen, visits happen, and a few weeks later almost nobody is left. Three symptoms show it.

1. The retention curve falls to the floor. Group everyone who signed up in the same week and chart how many come back each week after. Forty of 100 in week one, 18 in week two, 6 in week four, still dropping — that shape means nothing is holding anyone. A curve like that also caps the company: total users stall at some level no matter how much traffic you add on top.
2. The team can't explain the few who remain. Ask what those six people in week four have in common and you get six different answers. Retention you can't explain doesn't repeat next month.
3. The product keeps changing. You ship an MVP, the smallest version that can test a hypothesis, get no reaction, ship something else, and redraw that smallest version every quarter.

Spending works differently here too. Ten customer interviews — conversations where you sit with a customer and hear what they were trying to do and where it broke — are worth more than $6,000 of advertising, because the question this stage needs answered is who and why rather than how many. For the same reason, staffing a sales team early leaves you with fixed costs and little else. When the product changes, the pitch that team memorized gets thrown out with it.

What moves you is the share of people who stay, not the revenue total. Four signals together mark the line.

1. Curve flattening — the falling curve stops dropping at some level and lies flat. Flat at 24 percent means one in four arrivals settles in, and the same share can be expected from the people you bring in next.
2. A Sean Ellis test above 40 percent — a survey that asks how you would feel if you could no longer use the product and counts the share who answer "very disappointed." It runs in days, but only people who are still around answer it. If week-four retention is 6 percent and the survey says 52 percent, you measured the enthusiasm of a dozen fans.
3. The people who stay fit one description. Once it reads as a sentence — operations leads at 20-to-50-person teams who write documents daily — you can go looking for more companies matching it.
4. The share holds when you add channels. If 500 people from paid ads also retain at 22 percent in week four, the earlier 24 percent didn't come from friends and early fans. Retention that only holds for the first hundred people you recruited by hand is not something you can plan against.

When those four hold, you are in post-PMF, where the question shifts from what to build to how to acquire faster and cheaper. No single threshold separates the two, though. It's usually a stretch of several quarters, and crossing it once doesn't make it permanent. Move from selling to twenty-person teams to selling to 300-person companies and permissions, access logs, and security review show up before the contract does. Without those three, deals stop regardless of the retention you built earlier. The gap there is what people call the chasm.

"We're still pre-PMF. Let's revisit sales hiring next quarter."

Adding people now means the cost stays behind when the product changes.

"Signups doubled and week-four retention is still 6 percent. Before we pour in more traffic, let's find out why people leave."

The cause sits in the product rather than in acquisition, so stop the spend.

"This request came from one customer. Let's build it when ten of them ask for the same thing."

Saying yes to every individual request makes it impossible to tell what's actually right.

Pagedeck had a flat curve among teams of about twenty, then moved toward 300-person enterprise customers and landed back in this stage. Four contracts closed in three months, and all four closed for different reasons. When Grace proposed hiring three more salespeople, Mia pushed back: four different reasons means nobody knows yet how to produce the fifth contract, and hiring into that leaves payroll as the only result. Four contracts in a quarter reads like traction on a slide, and this one isn't.

The most common misreading treats pre-PMF as a product that isn't finished. When something is missing, the missing thing feels like features. But what separates this stage is whether anyone gets held, not how many features exist. Products with twenty features cross the line while products with eighty don't. Features are countable and holding power is not, which is what makes the substitution feel reasonable. Read it as a feature gap and the team keeps building whatever gets requested — a year later there are forty more features and week-four retention is still 6 percent.

Reading it as a time period causes the same damage. People hear it as roughly the first year of a company, but the phrase describes a state and not a calendar. A four-year-old company can still be here, and a company that crossed over lands back here when it changes markets. Reasoning from the calendar produces "we're in year three, time to scale," and six months later what's left is higher fixed costs and a curve that still hasn't flattened.