Most founders describe product market fit as a feeling. The product "clicks" with users, growth becomes easier, and support tickets shift from complaints to feature requests. That intuition is real, but it is also unreliable. We have worked with founders who thought they had product market fit because growth was strong, only to discover that their retention numbers told a completely different story. We have also seen the opposite: founders who doubted their traction while sitting on analytics data that clearly showed fit.
Product market fit is not a binary switch. It is a spectrum, and your analytics contain specific signals that tell you where you are on that spectrum. You do not need expensive analytics platforms to find them. You need to know what to look for and how to interpret what you find.
Retention Is the Only Metric That Cannot Lie
Revenue can grow while retention declines, which means you are filling a leaky bucket with paid acquisition. User signups can spike from a press mention without indicating any lasting interest. But retention, specifically cohort retention, tells you whether people who try your product keep using it.
Pull your retention data by weekly or monthly cohorts. Plot each cohort as a line showing what percentage of users are still active over time. If the lines flatten, meaning they stop declining and stabilize at some percentage, you have a retention floor. That floor is your strongest product market fit signal.
The specific numbers depend on your product category. For a B2B SaaS tool, month 3 retention above 40% is a strong signal. For a consumer app, week 4 retention above 20% suggests fit. For a daily use product like a communication tool, day 7 retention below 50% is a warning sign regardless of how fast you are growing.
If your retention curves never flatten and instead decline steadily toward zero, you do not have product market fit yet, no matter what your other metrics say. This is the most important data point in your entire analytics stack, and we always look at it first when assessing a product during consulting engagements.
Feature Usage Concentration
Most products have dozens of features, but product market fit usually comes from 2 or 3 of them. Your analytics can tell you which ones matter by examining feature usage concentration.
Look at which features your retained users, the ones who stay past month 3, use most frequently. Then compare that to the features your churned users interacted with. The gap between these two groups reveals your core value loop, the specific workflow that makes retained users stay.
On projects we have shipped, we have seen this analysis produce surprising results. A project management tool we worked on found that the users who retained were not using the Kanban board (the marquee feature) but were heavily using the recurring task automation. The team had been investing engineering resources into the Kanban experience while the actual retention driver was under invested.
You can run this analysis with event tracking data from any analytics platform. Group users into retained and churned segments, then compare their feature usage in the first 7 days. The features that show the biggest usage gap between these segments are your product market fit features.
The Sean Ellis Survey, Quantified
The classic Sean Ellis test asks users "How would you feel if you could no longer use this product?" with options ranging from "very disappointed" to "not disappointed." A score above 40% "very disappointed" is the widely cited threshold for product market fit.
But most founders never run this survey. The good news is that behavioral data can approximate it. Look at these signals as behavioral proxies for the "very disappointed" response:
Daily active users / monthly active users ratio. A DAU/MAU ratio above 30% means roughly a third of your monthly users come back every day. For most B2B products, this ratio between 15 and 25% indicates healthy engagement. Above 30% suggests the product is deeply embedded in daily workflows.
Session frequency per retained user. How many times per week does an active user open the product? If retained users average 4+ sessions per week for a productivity tool, they are relying on it. If they average once per week, the product is useful but not essential.
Time to first value. How quickly do new users perform the core action that retained users do most? If your retained users all created a report within 2 days of signing up, but the median time to first report across all users is 8 days, you have a product market fit problem disguised as an onboarding problem. Fixing the onboarding to get users to the core value faster often moves the retention curve more than building new features.
Organic Growth Signals
Paid acquisition can mask a lack of product market fit. Organic growth signals cannot be faked, and they are visible in your analytics.
Direct traffic growth. If the percentage of your traffic coming from direct navigation (people typing your URL or using bookmarks) is increasing over time, users are coming back without being prompted. This is a strong fit signal because it represents habitual usage.
Organic search for your brand name. If branded search volume is increasing, people are hearing about your product through word of mouth and searching for it. Google Search Console shows this data for free. A 10% month over month increase in branded searches is a meaningful organic growth signal.
Referral and invite behavior. If your product has any sharing or invite mechanism, track the viral coefficient, meaning the average number of new users each existing user generates. A coefficient above 0.5 means organic growth is meaningfully supplementing your acquisition efforts. Above 1.0 and growth becomes self sustaining. We have seen these patterns clearly in case studies like Traderly where organic engagement drove growth.
Expansion revenue. For SaaS products, existing customers upgrading to higher tiers or buying additional seats is one of the purest product market fit signals. It means the product is valuable enough that users want more of it. Net revenue retention above 110% (meaning existing customers generate 10% more revenue this year than last year, even accounting for churn) is the gold standard.
Where Most Founders Get Stuck
The most common mistake is looking at aggregate metrics instead of segmented data. Your overall retention rate might be 25%, which looks mediocre. But when you segment by acquisition channel, you might find that users from organic search retain at 55% while users from paid ads retain at 8%. That is not a product problem, that is a targeting problem. The product has fit with a specific audience, and your paid acquisition is reaching the wrong people.
Similarly, segment by use case. A project management tool might have poor overall retention but excellent retention among teams that use it for client work specifically. That segment is where your product market fit lives, and the product roadmap should serve that segment first.
We wrote about validating startup ideas before writing code, but validation does not stop at launch. Post launch validation through analytics is an ongoing process that should inform every sprint.
Turning Signals Into Action
Finding product market fit signals is only useful if it changes what you build. Here is how to translate analytics insights into engineering priorities:
1. Double down on retention drivers. Whatever features your retained users love, make them better, faster, and easier to discover. Do not spread engineering resources across 10 features when 2 of them drive all the retention.
2. Fix the onboarding path to core value. If your analytics show that users who perform a specific action in the first 48 hours retain at 3x the rate, redesign onboarding to guide every new user to that action immediately.
3. Stop investing in low retention segments. If a feature or user segment shows consistently poor retention, stop building for it. That sounds harsh, but engineering time is finite, and spending it on segments without fit comes at the cost of segments with fit.
4. Instrument what you cannot measure. If reading this post made you realize you are missing critical event tracking, fix that first. You cannot optimize what you cannot measure. Setting up proper analytics is one of the first things we do when building web and mobile applications.
Product market fit is not a mystery. It is a measurable state that your analytics can reveal if you ask the right questions. If you are building a product and want help interpreting what your data is telling you, or if you need to build the analytics infrastructure to capture these signals in the first place, let us know what you are working on.