Most buyers look at MRR. Smart buyers look at the inbox. Support ticket volume is one of the most reliable leading indicators of customer health. Here’s how to use it.
Deal Alert AI is reader-supported. We earn commissions from affiliate links at no cost to you.
This post is based on a video from our Deal Alert AI YouTube channel. Watch the original or read the full breakdown below.
When you are evaluating a SaaS acquisition, the spreadsheet presented by the seller usually looks clean. Monthly Recurring Revenue is flat or growing. Churn is under the industry average. Net revenue retention is solid. On paper, the numbers look good. But spreadsheets can be curated, manipulated, or simply incomplete. In the world of SaaS due diligence, you need to look beyond the top-line metrics to see what is actually happening on the ground. This is where support ticket volume becomes your most valuable diagnostic tool.
Support tickets are the raw, unfiltered feedback from your customers. They represent the moment where friction exists. Whether it is a billing issue, a feature request, a bug, or a confusion point in the user interface, the ticket is a signal. By analyzing the volume, frequency, and nature of these tickets, you can build a psychological profile of the product and its user base. It tells you if customers are delighting, struggling, or merely going through the motions before they eventually churn.
I have seen too many deals fall apart because buyers focused exclusively on LTV and CAC while ignoring the underlying operational instability. A business might have high retention, but if support costs are ballooning because every user needs hand-holding to use the product, that "retention" is an illusion. It is retention through dependency, not satisfaction. Understanding how to interpret support data is not optional for sophisticated buyers; it is the foundation of a robust valuation model. It separates the investors from the tourists.
We scan Empire Flippers, Flippa, Acquire.com and Quiet Light daily — scoring every listing. Start free.
To make sense of raw ticket numbers, you must normalize them. A company with 1,000 users and 500 tickets a month is fundamentally different from a company with 10,000 users and 500 tickets. The metric you need to calculate is "Tickets Per Active User" (TPAU). This ratio gives you a standardized view of friction. For a self-serve SaaS product, a healthy TPAU often hovers between 0.05 and 0.15, meaning one in every ten to twenty users generates a ticket in a given month. However, this varies heavily by niche and complexity.
Consider the difference between a simple expense tracking app and an enterprise-level ERP system. The expense tracker should have very low ticket volume because the interface is intuitive. If TPAU is high, the product is likely confusing. The enterprise ERP, on the other hand, might have a higher baseline TPAU simply because the functionality is complex and users require configuration assistance. The key is not just to look at the absolute number, but to compare it against historical trends and industry benchmarks. Is the TPAU increasing or decreasing over time? If it is increasing while user growth is steady, you have a problem.
I recommend you ask the seller for a 24-month export of support data, ideally from their helpdesk software like Intercom, Zendesk, or Freshdesk. Do not rely on a summary. You need the individual tickets, stamped with dates, categories, and resolution times. From this data, you can calculate the month-over-month change in TPAU. A sudden 20% increase in TPAU in the last quarter is a massive red flag. It suggests that a recent update, a change in onboarding flow, or a bug has severely degraded the user experience. This kind of structural decay is expensive to fix and difficult to reverse quickly after closing.
Not all tickets are created equal. In your due diligence, you must segment the ticket volume into distinct categories. I typically break them down into four buckets: Technical Bugs, Usability/UX Issues, Billing/Payment, and Feature Requests. The ratio between these categories tells you the health of the engineering team and the direction of the product roadmap. If 80% of your tickets are technical bugs, you are buying a ticking time bomb. It means the codebase is unstable, and the engineering team is in fire-fighting mode rather than building new features.
Usability and UX tickets are interesting. High volume here suggests that the product is functional but difficult to navigate. This is often a sign that the onboarding process is weak or that the documentation is poor. While frustrating, UX issues are often cheaper to fix than backend bugs. It usually requires design work and content creation, which can be done without major code rewrites. However, if UX tickets are high and persistent, it indicates a mismatch between what the customer expects and what the product delivers. This mismatch is a primary driver of voluntary churn.
Billing and payment tickets are a specific concern for SaaS businesses. If a significant portion of support volume is related to credit card chargebacks, invoicing errors, or plan confusion, your revenue stack is fragile. These are not just support issues; they are governance issues. A business with high billing friction has a high risk of revenue leakage. I have seen businesses lose significant MRR because their billing cycles were misaligned with customer expectations, leading to angry emails and cancellations. You must audit the billing category specifically to ensure that revenue recognition is clean and that the payment processor is integrated smoothly.
One of the most powerful uses of support data in due diligence is correlating ticket history with churn dates. You need to identify users who churned in the last 12 months and look at their support activity in the 30, 60, and 90 days prior to their departure. Did they file tickets? If they did, what were they about? Often, you will find a pattern. For example, users who filed a ticket about a specific feature failure were 40% more likely to churn within the next month. This kind of data allows you to predict future churn cohorts with a degree of accuracy that traditional regression models cannot match.
Let’s look at a real-world example. I was reviewing a B2B SaaS company with seemingly low monthly churn of 2%. The seller assured me the retention was strong. However, when I analyzed the ticket data for the last six months, I found that users who submitted tickets regarding "integrated reporting" had a churn rate of 15% in the following month. The company had a hidden feature gap. Their core users, the ones actually doing heavy analysis, were struggling with the reporting module. The low overall churn was masking a high churn among the most valuable segment of customers. Had I not looked at the tickets, I would have overvalued the business based on surface-level retention metrics.
This analysis allows you to adjust your multiple. If you identify that a specific segment of your user base is at high risk of churning due to consistent support friction, you should value that portion of the MRR at a lower multiple. This is the essence of sophisticated SaaS valuation: it is not a single number, but a weighted average of risk-adjusted segments. By using support ticket volume to identify these vulnerable segments, you can negotiate a price that reflects the true economic reality of the business, rather than the marketing narrative of the founder.
SaaS businesses are often touted as having high margins, but support is one of the biggest hidden costs that scales poorly. As your user base grows, does your support cost grow linearly, or does it scale sub-linearly? Ideally, as you improve documentation and self-service, support costs should decrease relative to revenue. If support costs are growing faster than revenue, the business is not scaling efficiently. You need to calculate the "Cost Per Ticket" and the "Support Cost as a Percentage of MRR." For a standard SaaS, support should ideally be between 3% and 7% of MRR. If it is above 15%, you are looking at a service business disguised as software.
You must also assess the capacity of the current support team. How many engineers or support staff are currently handling the volume? Are they burning out? Burnout in the support team leads to slow resolution times, which leads to angry customers, which leads to churn. During due diligence, I speak to the support leads. I ask them about their longest shift, their biggest frustration, and what they would change if they had a magic wand. Their answers tell you more about the operational culture than any HR handbook can. If the support team is overwhelmed, they need immediate hiring or automation investment post-closing, which will eat into your initial cash flow.
Furthermore, consider the tooling. Is the business using a modern helpdesk with AI-enabled triage, or are they using email inboxes and spreadsheets? The infrastructure you are acquiring matters. A modern stack allows for better data capture and faster response times. An outdated stack is a liability that will require immediate upgrade capital. Factor this into your purchase price. I have seen buyers close on a business only to spend the next three months rebuilding the support infrastructure because the legacy system could not handle the ticket volume. This is a non-revenue-generating expense that should be negotiated down from the sale price.
Now that you have the data, how do you use it? Do not just note it in a memo. It needs to be baked into your financial model. First, use the historical churn correlation to adjust your projected LTV. If data shows that 10% of your current users are "high-friction" users (those who file frequent bugs), apply a lower retention rate to this segment in your forward projections. Second, adjust your COGS for support. If current support costs are unsustainable at the current growth rate, model in the cost of scaling the support team or investing in better documentation. This often increases your break-even point and extends your time to positive cash flow.
Third, use the ticket categories to prioritize your post-acquisition roadmap. If 50% of tickets are about a specific feature, your Product-Manager-in-Residence (and you will need one) knows exactly where to focus the first 90 days. This de-risks the integration phase. You are not guessing what to build; you are solving known pain points. This clarity allows the product team to deliver quick wins, which can improve early post-close retention and morale. It turns the support data from a diagnostic tool into a strategic asset.
Finally, use the data to protect yourself in the earn-out structure. If you agree to an earn-out based on continued growth, ensure the earn-out conditions account for support-driven churn. For example, if the seller promises that churn will stay below 3%, but your analysis shows that the current ticket volume suggests a 5% churn risk, the earn-out should be structured to reflect this higher risk. This protects you from paying for growth that is not sticky. It ensures that the seller remains aligned with your goal of *retaining* customers, not just acquiring them.
There are certain patterns in support ticket data that should act as immediate deal-killers. First, a sudden, unexplained drop in ticket volume. Sellers often try to hide bad metrics. If ticket volume drops by 30% in the last month of data provided, it may not be because the product got better. It could be because customers stopped caring enough to complain before leaving. Or, it could be that the seller disabled ticket collection temporarily. Always verify the data source. Check the API logs of the helpdesk platform to ensure the data was not manipulated.
Second, a high percentage of "billing" tickets. If more than 10% of all tickets are related to payment failures or invoice confusion, the revenue engine is broken. Fixing this is not a product problem; it is an infrastructure problem. It requires enterprise-level integration work that is costly and slow. I have walked away from deals because the billing system was a custom-built mess that would require six months of full-time engineering attention just to stabilize. That is not a SaaS business; that is a tech support project.
Third, a lack of categorization. If the seller’s support team does not tag tickets, you are blind. You cannot analyze what you cannot categorize. If they refuse to implement basic tagging now, they will not do it later. It indicates a lack of operational discipline. A business without disciplined support operations is hard to scale. It relies on heroics rather than processes. In investing, you need processes. Without them, you are betting on the character of the founder, who will no longer be running the company when you take over. This is too high a risk for most institutional or pragmatic buyers.
To ensure you never miss these critical insights again, I have compiled a specific checklist for your next SaaS due diligence process. This is not a general IT checklist; it is a support-specific audit. Use this to guide your request for information (RFI) and your data room review. Following this list will give you the confidence to negotiate from a position of strength, knowing exactly what is hidden in the inbox.
To bring this theory to life, let’s look at two hypothetical deals that illustrate the power of this analysis. In Deal A, a buyer was interested in a HR-tech SaaS with $50k MRR. The financials were clean. Churn was 1.5%. However, the support ticket analysis revealed that 60% of tickets were related to a specific payroll integration with a local bank. The bank had changed its API, and the product team had been patching it manually for months. The churn rate for users on that specific payroll setup was 8%. The buyer adjusted the valuation down by 20% and required the seller to fix the integration pre-close. When they analyzed the market, they found that the local bank was losing market share, meaning the pain point would become irrelevant anyway, but the fix was cheap. The deal closed at a lower price, and the product stabilized.
In Deal B, the story was different. A buyer looked at a project management tool with $80k MRR. The overall churn was 3%, which looked okay. The ticket volume was low. But the tagging was poor. The buyer pulled the raw text and ran a simple keyword frequency analysis on the top 100 tickets from the last month. The phrase "export data" appeared 40 times. The phrase "can't delete" appeared 25 times. The product had no good export function and a broken delete feature for inactive users. The support team was manually doing these tasks in SQL. The buyer realized that the support team was acting as a database administrator, not a support team. This indicated a codebase that was too rigid to scale. The buyer chose to walk away, saving themselves from inheriting a technical debt nightmare that would have required a complete rewrite.
These examples highlight that support data is not just about counting items. It is about reading the narrative of the product. It tells you if the engineering team is building correctly, if the product matches the market need, and if the financials are sustainable. It is the difference between buying a machine that makes money and buying a money pit that requires constant manual intervention to keep running. Always dig deep. The inbox never lies; it just waits for you to read the fine print.
In the SaaS acquisition space, information asymmetry is your enemy. The seller knows everything. They know which users are angry, which features are broken, and why the churn rate looks stable when it isn’t. As a buyer, your job is to erase that asymmetry. Support ticket volume and content are the single most accessible sources of truthful operational data. They are generated daily, they are recent, and they are hard to fake without significant effort.
If you are serious about buying durable, profitable online businesses, you must adopt a disciplinary approach to due diligence. Stop accepting high-level dashboards. Demand the raw data. Run the correlations. Look for the hidden risks. By doing so, you position yourself to make offers that are competitive yet safe. You become the buyer who understands the product, not just the P&L. This expertise is what allows you to find undervalued assets that others are too lazy to investigate. For more resources on data-driven acquisition strategies, visit Deal Alert AI to see how we are democratizing access to this level of insight for independent buyers.
As you move forward, keep this mindset: every ticket is a dialogue with the market. It is a chance to improve the product or to identify a risk. When you evaluate a business, you are not just buying its revenue; you are buying its problems. Make sure you know what those problems are before you sign the wire transfer instructions. The cost of due diligence is a fraction of the cost of a bad acquisition. Invest in the analysis. Your portfolio will thank you. And if you are looking for vetted SaaS opportunities that come with this level of pre-vetted data, check out Empire Flippers or Flippa, but apply this same scrutiny to every deal that crosses your desk. Stay sharp, stay data-driven, and always protect your downside first. That is how you build a lasting digital asset empire. Deal Alert AI is here to help you navigate this complex landscape with clarity and confidence.
We scan Empire Flippers, Acquire, Flippa, and Quiet Light daily. The best sub-$500K businesses are gone within 48 hours.