How to validate product-market fit before scaling growth

Executive overview

Most companies attempt growth hacking before confirming whether their product is worth growing. Without product-market fit, acquiring users just means replacing those who churn — growth flatlines regardless of spend.

Activation is the most powerful lever: a great first experience drives retention more than any re-engagement tactic.

The framework: confirm PMF quantitatively, then run a high-velocity test cycle — analyse, ideate, prioritise, test, repeat.

Measuring product-market fit

• Ask active users: "How would you feel if you could no longer use this product?"
• Threshold: if fewer than 40% say "very disappointed," do not scale growth efforts
• Only survey users who have used the product more than once, recently
• Track retention cohorts: plot the percentage of users still active over time
• A cohort that plateaus — even at 5–10% — signals PMF; one that trends to zero does not
• Where the cohort plateaus depends on the business model (free vs. paid, habit vs. utility)

Understanding why you have PMF

• Knowing you have PMF is not enough — understand which specific benefit drives must-have status
• If messaging promotes the wrong benefit, acquired users will not stay
• Qualitative analysis of what "must-have" users love comes before any growth experiment
• Misaligned messaging is a common reason companies with good products still fail to retain

Why growth hacking fails in most companies

• Growth is cross-functional: product, marketing, engineering, design, and data must collaborate
• As companies specialise, teams separate — coordination breaks down
• Marketers blocked from running in-product experiments retreat to paid channels only
• External channel optimisation (Facebook, Google) is just marketing — not growth hacking
• Bidding-based platforms drive up costs whenever any advertiser improves; sustainable advantage requires the full customer journey
• Perception problem: product teams fear growth experiments will degrade UX; the best experiments remove confusion, not add tricks

The growth hacking process

• Analyse first: qualitative diagnosis of who loves the product and why
• Generate ideas to improve the weakest points in the customer journey
• Prioritise which ideas to test based on potential impact
• Run tests; measure results; feed learnings back into the next cycle
• Focus spans acquisition, activation, retention, referral, and monetisation — in that order of priority

High-velocity testing

• Volume of experiments is the primary predictor of growth outcomes
• Run three to five tests per week, depending on company size
• No one consistently predicts which test will be the breakout — only volume reveals it
• Obsessing over one "perfect" test is a common mistake; breadth beats perfection
• Every test is a shot on goal; more shots mean more chances to find the high-impact change

Activation and retention

• Activation — the quality of the first experience — is the biggest driver of long-term retention
• Users who invest in a product (customisation, data entry) develop ownership and return more
• Re-engagement tactics matter, but only after activation is optimised
• Usability testing and surveys diagnose where users get confused; fixes compound over time

Culture shift from testing

• Consistent testing reveals that expert intuition is wrong a large fraction of the time
• Teams become less argumentative and more curious when data repeatedly overrides opinion
• Cross-functional humility — "how do we find the truth?" — replaces "my opinion vs. yours"