Product-Market Fit Engineering Signals

Retention as the Primary Signal

Marc Andreessen defined product-market fit as being in a good market with a product that can satisfy that market. The most reliable quantitative signal is user retention. Sean Ellis, who coined the term 'growth hacking,' proposed a specific threshold: if 40% or more of surveyed users would be 'very disappointed' if the product went away, the product has achieved PMF. But survey responses can be gamed; retention data cannot.

Cohort retention curves tell the story. A product with PMF shows a retention curve that flattens -- the curve drops in the first few weeks as casual users leave, then stabilizes as the core user base continues using the product. A product without PMF shows a curve that trends toward zero. Analyze weekly or monthly retention by cohort: what percentage of users who signed up in week 1 are still active in week 4, week 8, week 12? A flattening curve above 20-30% for a B2C product or above 60-70% for a B2B product is a strong positive signal.

Look at usage frequency within retained users. A social product where retained users log in daily has stronger PMF than one where they log in monthly. A B2B tool where teams use it multiple times per day has stronger PMF than one that gets checked weekly. The ratio of daily active users to monthly active users -- the DAU/MAU ratio -- captures this intensity. Facebook's benchmark of 50%+ DAU/MAU for strong consumer products remains a useful reference point.

Organic Growth and Word-of-Mouth Signals

Products with PMF grow organically because satisfied users tell others. Track the percentage of new users who arrive through organic channels -- direct traffic, referrals, and word of mouth -- versus paid acquisition. If organic growth accounts for less than 30% of new users, the product may be acquiring users through marketing force rather than product satisfaction. Dropbox achieved viral growth through its referral program, but the referrals worked because users genuinely valued the product enough to recommend it.

Monitor the sources of inbound customer support and sales inquiries. Products with PMF attract inbound interest -- prospects reaching out without prompting, users requesting features for additional use cases, and partners suggesting integrations. This pull from the market contrasts with the push required when the product lacks fit. Slack's early growth was almost entirely inbound, with teams discovering and adopting the product without a sales team.

Track viral coefficient -- the number of new users each existing user brings in -- and the time it takes for that sharing to occur. A viral coefficient above 1.0 means the product grows exponentially without paid acquisition. Most B2B products will not achieve this, but even a coefficient of 0.3-0.5 significantly reduces customer acquisition cost and indicates that users find enough value to recommend the product.

Infrastructure Stress as a PMF Indicator

Engineering teams have a unique vantage point on PMF: system behavior under organic load. When the infrastructure starts straining -- response times increasing, database queries slowing, queues backing up, support tickets rising -- without a corresponding increase in marketing spend, that is a signal of genuine demand. Products without PMF never stress-test their infrastructure through organic growth because the growth is not there.

Monitor API usage patterns for signals of deep integration. When customers build automations, custom integrations, or workflows on top of the API, they are investing effort that signals strong value perception. Track the number of API consumers, the diversity of endpoints used, and the frequency of API calls. Twilio's internal PMF analysis tracked the number of customers who integrated more than three API endpoints as a proxy for product depth.

Watch for usage patterns the team did not anticipate. When users bend the product to serve use cases the team did not design for, that indicates strong underlying value. Slack was designed for team communication but users created channels for cross-company collaboration, customer support, and community building. These emergent use cases signal that the core product provides enough value to attract creative adaptation.

Revenue and Willingness-to-Pay Signals

For products with a monetization model, revenue retention is a more reliable PMF signal than user retention. Net revenue retention -- which accounts for expansion, contraction, and churn -- above 100% means existing customers are spending more over time. Bessemer Venture Partners publishes benchmark data showing that best-in-class SaaS companies maintain net revenue retention above 120%, indicating strong PMF within their customer base.

Willingness to pay before the product exists is a particularly strong signal. When potential customers offer to pay for a prototype, sign letters of intent for a product in development, or commit to annual contracts based on a demo, the market is pulling the product forward. Stripe's early customers were willing to integrate a payment API from a two-person startup because the existing alternatives were painful enough to justify the risk.

Pricing power is another indicator. A product with strong PMF can raise prices without significant churn because the value delivered exceeds the price charged. A product without PMF faces immediate pushback on any price increase because users are not deeply invested. Track the response to price changes: if a 20% price increase results in less than 5% churn, the product has pricing power that reflects genuine PMF.

When Engineering Should Signal a PMF Problem

Engineering teams often sense PMF problems before anyone else because they see the gap between what is built and what is used. If the team consistently ships features that see low adoption -- less than 10% of active users engaging with a new feature within the first month -- the product may be solving problems users do not have. Track feature adoption rates and surface this data in product reviews.

High churn in specific user segments reveals PMF gaps. If enterprise customers retain at 95% but SMB customers churn at 50%, the product has PMF for enterprises but not for small businesses. Segment retention data by company size, industry, use case, and acquisition channel. This granular view reveals where PMF exists and where it does not, which is more actionable than a single blended retention number.

The most honest PMF assessment comes from combining quantitative signals with qualitative user feedback. When users describe the product as 'nice to have' rather than 'essential,' PMF has not been achieved regardless of current usage metrics. Run the Sean Ellis survey quarterly, track retention curves by cohort, monitor organic growth trends, and present this data alongside feature usage to create a complete picture of product-market alignment.