PMF

Product-Market Fit is famously hard to define and famously easy to recognise. Marc Andreessen’s heuristic still holds: you know you have it when the product is being pulled by users, the press, and the cap table all at once, and your problem is no longer how to find customers but how to keep up with them.

Pre-PMF, almost everything you do is a bet. The right org chart, the right tech stack, the right hiring plan all depend on which segment of customers actually pulls. Post-PMF, the questions become operational: scale the team, harden the stack, control the burn.

Worked example of the most expensive pre-PMF mistake: a team raises a seed round, hires four engineers, and spends nine months building a Kubernetes-backed, multi-region, microservices platform “so we can scale”. They scale to forty users, run out of runway, and the architecture they built for millions never gets tested by hundreds. The opposite failure is rarer but real: a team finds the pull, gets featured, and the single overloaded server falls over during the one week the whole market was watching. The engineering call is entirely a function of which side of the PMF line you are on, which is why naming the line honestly matters more than any stack decision.

The honest trade-off founders dodge: admitting you are pre-PMF feels like admitting failure, so decks describe a slog of one-customer-at-a-time selling as “early traction”. If acquisition is still a grind and churn is high enough that word of mouth cannot carry growth, you are pre-PMF regardless of the deck, and the right move is to keep shipping the cheapest MVP that resolves the next uncertainty rather than build for a scale you have not earned. A discovery-phase helps you name the riskiest assumption; a fractional operator can prevent expensive technical mistakes during the search, but cannot substitute for the founder’s relentless customer obsession that actually produces the pull. Past PMF, you typically need a CTO, not a co-founder. See Fractional CTO Austria.