What changes the moment you launch
Before launch, your job was to build the thing. After launch, your job is to learn what the thing should become. The skills barely overlap. The founders who struggle keep optimising for shipping features when they should be optimising for learning.
The first 90 days
- Weeks 1–2: Watch, don't ship. Resist adding features. Talk to every early user. Find where people get stuck and where they light up.
- Weeks 3–6: Fix the leak before filling the bucket. If users drop off at onboarding, no new feature helps. Remove the single biggest point of friction.
- Weeks 7–12: Double down on the one thing that works. A pattern emerges — one use case, one segment, one moment of real value. Build around that, ruthlessly.
Instrument everything
You can't find product-market fit blind. Before you chase PMF you need to see behaviour: activation rate, time to first value, retention curves by cohort, and where people drop. If you launched without analytics, fixing that is week-one work.
The iteration loop
Tighten the cycle to its smallest honest form:
Observe a real behaviour → form one hypothesis → ship the smallest change to test it → measure → keep or kill.
The teams that find fit fastest aren't shipping the most — they're running this loop the most times per month with the most intellectual honesty about results.
Signs you're getting close
- Retention curves flatten instead of decaying to zero — people stick.
- Users get upset when the product is down. They'd miss it.
- Growth starts coming from word of mouth, not just your own pushing.
- You can describe, in one sentence, exactly who it's for and why they love it.
None of this requires building more. It requires building the right things, proven by real behaviour — exactly where a partner who's done it before earns their keep, whether that's a React Native product or one with AI features at its core.
How to measure product-market fit
Product-market fit isn't a feeling — it's a measurable threshold, and chasing it blind is why so many post-launch teams spin. Three lenses, used together, tell you where you really stand.
1. The 40% test
Sean Ellis's question: "How would you feel if you could no longer use this product?" If 40% or more of your activated users answer "very disappointed," you're in product-market-fit territory. Below 25%, keep iterating — the market is telling you the value isn't landing yet.
2. Retention cohorts
The most honest signal there is. Plot retention by signup cohort — day-over-day for consumer, week-over-week for B2B. Fit shows up as a curve that flattens: a stable group that keeps coming back. A curve that decays to zero means no fit yet, no matter how good your acquisition numbers look.
3. Organic pull
When word of mouth, referrals and unprompted inbound start outpacing your own outbound effort, the market is pulling the product out of you. That pull shows up in the pipeline before it shows up in a dashboard.
The metrics that matter — and the vanity ones that don't
Most post-launch dashboards measure motion, not progress. Track the few numbers that actually predict retention:
- Activation rate — the share of new users who reach first real value, not just those who sign up.
- Time to first value (TTFV) — how long until the "aha" moment. Shortening it is some of the highest-leverage work you can do.
- Cohort retention — D1/D7/D30 for consumer, W1/W4/W12 for B2B.
- Referral / k-factor — are users bringing other users?
Downloads, signups, pageviews and total registered users are vanity metrics: they keep rising even while the product fails. A simple test — if a number can't go down when you're doing badly, it isn't telling you anything.
Five ways founders stall after launch
- Premature scaling. Pouring money into ads before retention is fixed just buys churn faster. Fix the leaky bucket first.
- The feature factory. Shipping features to feel productive instead of removing friction from the one path that already works.
- Listening to the loudest user. One vocal customer's wishlist isn't a roadmap. The pattern across the users who quietly churned is.
- Vanity metrics. Celebrating signups while D30 retention sits near zero.
- Pivoting on noise. Abandoning a direction after one bad week — or clinging to it for a year. Decide on cohorts, not moods.
Product-market fit looks different by product type
The signal you chase depends on what you're building:
- Consumer apps live or die on early retention and habit — day-1 and day-7 retention and session frequency are the story, the model behind a ride-booking loop like Station.
- B2B SaaS fits when a team adopts it into a workflow and renews; watch weekly active accounts, seat expansion and logo retention — the shape of an operations tool like POPProbe or an HR & payroll platform like Attled.
- Marketplaces need both sides to work. Liquidity — fill rate, time-to-match and repeat transactions — is the fit signal, as in a creator-to-venue platform like Claris.
What a strong iteration system looks like
Finding fit faster is mostly operational discipline. The teams that get there run a weekly rhythm:
- An analytics stack wired before launch — events, funnels and cohort retention — so every change is measurable.
- Five user conversations a week, every week. Qualitative interviews explain why the numbers move.
- One weekly review of the latest cohort's retention, ending in a single decision: the most important change to make.
- Ship the smallest test of one hypothesis at a time, so you can actually attribute the result.
Quantitative data tells you what is happening; qualitative tells you why. You need both, on a cadence — otherwise you're guessing with extra steps.
Frequently asked questions
How long does it take to reach product-market fit?
There's no fixed timeline, but most teams that find it do so within 6–18 months of launch by iterating tightly. If you've been live for two years with flat retention and no organic pull, the honest read is that you haven't found it yet — and more features won't change that.
What is the 40% product-market fit test?
Survey your activated users with "How would you feel if you could no longer use this product?" If at least 40% answer "very disappointed," you likely have product-market fit. It's a directional gut-check, best paired with retention data.
Should I add features or improve retention first?
Retention, almost always. New features rarely rescue a product users don't return to — they just add surface area to maintain. Fix the drop-off in your core loop before broadening scope.
What metrics prove product-market fit?
Flattening cohort-retention curves, a 40%+ "very disappointed" score, and growth increasingly driven by word of mouth. Downloads and signups don't count.
Can an agency help us find product-market fit?
A good product partner won't hand you fit, but it will get you there faster — instrumenting analytics properly, running a disciplined iteration loop and shipping the right small tests instead of a bloated roadmap. Book a call if you'd like a second set of eyes on your numbers.