A founder told me they knew they had product-market fit when the support tickets changed. "Early on, every ticket was 'how do I do X?' or 'this doesn't work.' One day, the tickets shifted to 'can I do more of X?' and 'I need this for my whole team.' The questions went from confusion to expansion. That's when I knew."

Your support queue is a real-time indicator of product-market fit. Not a survey. Not a metric. The actual words your customers use when they talk to you.

Pre-PMF: The Confusion Tickets

Before product-market fit, support tickets are dominated by confusion and frustration.

"What does this feature do?" means the product isn't self-explanatory. The user signed up but can't figure out the value proposition from the product itself.

"This doesn't work the way I expected" means the product's mental model doesn't match the user's mental model. They thought it did one thing. It does another. Or the same thing, but differently than expected.

"I think I found a bug" (that isn't a bug) means the product's behavior is surprising. The user encounters intended behavior that seems wrong to them because the design didn't communicate the intent.

"Can you help me set this up for [use case your product doesn't support]?" means you're attracting the wrong users, or your marketing promises something the product doesn't deliver.

Pre-PMF ticket composition: 40% confusion, 25% bugs, 20% "how do I...?", 15% feature requests for things that should already exist. The overall tone is confused and tentative.

At PMF: The Expansion Tickets

When you hit product-market fit, the ticket composition shifts.

"Can I get more seats?" means the user is sharing the product with their team. They've validated it individually and want to expand.

"Does this integrate with [tool]?" means the product is becoming part of their workflow. They're not evaluating it anymore. They're embedding it.

"I need to export/import more data" means they're going deep. They're building processes around your product. Volume is increasing.

"Is there an API?" means a developer wants to build on your product. This is peak integration intent.

At PMF, confusion tickets drop. Bug reports shift from "this doesn't work" to "this works but could work better." Feature requests shift from "basic stuff that should exist" to "advanced stuff that would make me a power user."

The overall tone changes too. Pre-PMF tickets sound uncertain. PMF tickets sound impatient. The user knows what they want and they want more of it.

Post-PMF: The Growth Pains

After PMF, if you're scaling, the tickets change again.

"Your product is slower than it used to be." Performance issues from growth. Your infrastructure needs to scale with your user base.

"I can't manage 50 team members in the current UI." Your product was designed for 5-person teams and now enterprises are using it. The UX doesn't scale.

"We need SSO/SAML/SCIM." Enterprise requirements that didn't matter at 100 customers but are blocking deals at 1,000.

"Your pricing doesn't make sense for our usage." You priced for early adopters and the pricing model doesn't scale linearly. Large customers are paying disproportionately.

These are good problems. They mean demand is outrunning your product's current capabilities. But if you don't address them, you lose the customers who grew with you.

The PMF Loss Signal

The scariest ticket pattern: the shift from expansion to confusion, in reverse.

"I used to know how to do this but now I can't find it." You redesigned something and broke existing workflows.

"Why did the price go up?" You changed pricing and didn't grandfather existing customers.

"This feature used to be included in my plan." You moved features between tiers and existing customers lost access.

"I'm not sure your product is the right fit anymore." The most dangerous ticket. This customer was at PMF with you and now they're not.

If your ticket composition shifts from expansion back to confusion, something changed. Maybe you over-complicated the product. Maybe you changed the pricing model. Maybe a competitor emerged that better serves the customer's evolved needs. Whatever it is, the support data will show you before churn data does (by 30 to 60 days).

How to Track This

Classify your tickets by intent (Supp does this across 315 categories) and group those intents into PMF stages:

Confusion: "what does this do?", "this doesn't work as expected", "I'm confused about..." Adoption: "how do I set up...", "can I do...", "where do I find..." Expansion: "can I add users?", "API access?", "enterprise features?", "integration with..." Growth pain: "it's slow", "pricing doesn't scale", "need admin controls" Risk: "thinking about cancelling", "found an alternative", "not the right fit"

Track the percentage of tickets in each group monthly. Plot the trend.

A healthy trajectory: confusion decreases, adoption stays steady, expansion increases. That's PMF approaching or strengthening.

A concerning trajectory: expansion decreasing, confusion increasing, risk appearing. That's PMF weakening.

The support data doesn't lie. Surveys can be gamed. NPS can be biased. But the words customers use when they're genuinely trying to use your product, that's the truth.