Support tickets are the unfiltered heartbeat of a SaaS company. Learn how to analyze volume and sentiment to uncover hidden technical debt and churn risks during acquisition due diligence.
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 most buyers approach a SaaS acquisition, they immediately dive into the spreadsheet. They look at Monthly Recurring Revenue (MRR), churn rates, and EBITDA margins. These are certainly critical metrics, but they are also the easiest metrics to manipulate or obscure. A seller can adjust recognition timing, bundle services, or classify one-time fees in ways that flatter the headline number. However, support data tells a different story. It is raw, time-stamped user interaction that is much harder to fake convincingly over a long period.
I have seen too many deals fall apart because the buyer waited until the final week to ask for raw data. By then, the seller has already sanitized the most important insights. Support tickets represent the single most honest metric in your due diligence package. When a user complains, they are not trying to close a sale; they are expressing a genuine pain point. This qualitative feedback, when aggregated, provides a granular view of product health, scalability issues, and customer satisfaction that no survey can fully capture.
At Deal Alert AI, we treat support data as a first-class citizen in our evaluation framework. It is not just an operational annoyance to be audited; it is a leading indicator of revenue retention. If support tickets are spiking in specific categories, you are often looking at a future churn event before it appears in the P&L. By the time a customer cancels their subscription, the damage is done. But the ticket often comes weeks or months prior. Reading these signals correctly can save you from buying a leaky bucket.
We scan Empire Flippers, Flippa, Acquire.com and Quiet Light daily — scoring every listing. Start free.
Volume is only useful when viewed in the context of time. A static number tells you nothing; a trend tells you everything. You need to analyze ticket volume on a weekly and monthly basis, correlating it with your user growth curve. Ideally, support ticket volume should grow slowly as your user base expands, but it should not grow linearly with new signups. If your user base grows by 10%, but your ticket volume grows by 50%, you have a serious problem. This indicates that the new users are not sticking, or that the onboarding experience is broken and creating friction for every new cohort.
We also look for seasonality. Some SaaS products have predictable peaks. For example, e-commerce SaaS tools often see a spike in tickets from merchants right before Black Friday or the holidays. If the timeline shows these natural peaks, that is a normal operating rhythm. However, if you see a sudden, unexplained spike in the middle of a normal quarter, that is a red flag. It could indicate a buggy software release, a pricing change that confused customers, or a competitor launching a superior feature that caused confusion among your existing base.
Trend analysis also helps you calculate your true Headcount Efficiency Ratio (HER). This is the number of support tickets one agent can handle per day. As volume increases, this number usually stabilizes. If you see this ratio declining over time, it means your support team is becoming less efficient. This could be due to outdated ticketing software, lack of proper documentation, or the increasing complexity of the product. Scaling support costs faster than revenue is a sign that your operational model is fragile. It suggests that as you acquire more customers, your gross margins will compress significantly, making the business less profitable than the proforma statements suggest.
Key Insight: Look for the "Churn-Support Lag." On average, high-churn segments in SaaS generate 2x more support tickets in the 30 days prior to cancellation compared to retained users. If your support team is overwhelmed with "how do I do X" questions from premium customers, you are likely experiencing onboarding friction that will lead to high early-stage churn.
Not all tickets are created equal. In due diligence, we categorize tickets into three distinct buckets: Bugs/Breaks, Friction/Confusion, and Feature Requests. This classification is crucial because it tells you where the value is leaking and where the product roadmap is lagging. "Bugs" are the immediate threats to product stability. If a significant percentage of tickets are related to login failures, data corruption, or critical crash bugs, you are buying a ticking time bomb. The cost of fixing deep-seated technical debt is rarely reflected in the asking price, but it will consume your first year of ownership.
"Friction" tickets are often the most insidious. These are questions like "How do I export this data?" or "Why can't I see my invoices?" If a significant portion of your support volume is based on basic usability, your product is not intuitive. In the modern SaaS landscape, users expect self-service. If they have to pay for your product and then pay your support team to tell them how to use it, your value proposition is weak. This type of friction often correlates with higher churn, especially among self-serve tiers. It suggests that the buyer is relying on hand-holding to retain customers, a strategy that does not scale.
Finally, "Feature Requests" are promising, but dangerous if mismanaged. A healthy SaaS company sees feature requests as market research. However, if the support team is spending 40% of their time writing copy-pasted "This is on our roadmap" responses, it means the product is not meeting core needs. You must distinguish between nice-to-have features and must-have blockers. If top-tier enterprise customers are blocked on specific integrations, and those requests are flooding the support queue, you are missing out on revenue expansion opportunities. The ticket volume here represents lost deal size, not just saved customers.
While support tickets are customer-facing, technical error logs are developer-facing. Both need to be cross-referenced. A common tactic in SaaS acquisitions is to hide technical debt by ensuring that no tickets are filed for non-blocking errors. However, if you look at the backend logs, you might find that the system is throwing exceptions every few hours. These errors might not stop the user from using the app, but they slow it down or cause data inconsistencies that eventually lead to support tickets later. This is "slow bleed" technical debt.
During due diligence, I request access to the analytics dashboard for error rates. I am looking for a ratio of errors per active user. If this ratio is higher than the industry standard (which varies by complexity, but generally should be low for mature products), it signals that the codebase is buckling under load. This is critical for scaling. If the platform can’t handle 10% more traffic without spiking error rates, your growth plan is capped. The seller may have been able to keep churn low by capping sales, but once you remove those caps, the platform will collapse.
We also analyze the "Mean Time to Resolution" (MTTR) for critical bugs. If a critical bug takes two weeks to fix, and it generates five tickets per day for two weeks, you have a massive operational inefficiency. Moreover, the impact on brand reputation is significant in the SaaS world. Word travels fast in niche communities. If your product is perceived as unstable, sales teams will struggle to close new deals, even if the existing customer base remains quiet. This hidden cost of instability is rarely quantified in a valuation model, leading to an overpayment for a fragile asset.
Red Flag Alert: If the seller states they have "low" support volume because they use a chatbot to deflect users, ask for the "Chatbot Resolution Rate." If users are being deflected into a chatbot but then abandoning the session or subsequently emailing support, the volume has not decreased; it has just been hidden. The underlying problem remains, and the user experience is often worse because they feel ignored. Always audit the "escalation rate" from bot to human agent.
Support data must be viewed through the lens of LTV (Lifetime Value). A customer who generates high ticket volume but stays for eight years is a different animal than a customer who generates high ticket volume and churns in month three. The former is a "high-touch" requirement; the latter is a "bad fit" problem. In your due diligence, you should sample support tickets and map them to specific customer accounts (to the extent allowed by privacy policies and data structures). Identify the cohorts with the highest ticket-to-MRR ratio. These are your most expensive customers to serve.
If your highest-value customers (your top 10% by revenue) are your most support-intensive users, you need to reassess your service model. Often, this is acceptable in enterprise SaaS where relationships matter. But if this is true for mid-market or self-serve segments, your unit economics are broken. You are acquiring customers whose acquisition cost (CAC) might be high, but whose service cost (SCAC) is even higher, eating into your gross margin. The support ticket data reveals this hidden cost of goods sold (COGS). It allows you to build a more accurate Pro Forma that accounts for the true cost of serving your customer base.
Furthermore, look at the correlation between support contact and renewal. Do users who contact support renew at higher or lower rates? In some industries, proactive support can actually increase renewal rates because it builds trust. In others, especially in complex technical platforms, frequent contact is a sign of frustration. You must analyze this specific correlation for the target business. If the data shows that every ticket lowers the probability of renewal by 5%, you can quantify the revenue at risk. This allows you to negotiate a price adjustment or request a specific escrow holdback to cover the cost of fixing the underlying usability issues that are driving these tickets.
Support is a people business. The software is just a conduit. During due diligence, you must evaluate the health of the support team itself. High ticket volume combined with high agent turnover is a classic sign of operational distress. If the average tenure of support agents is less than six months, you are buying a business that is constantly training new staff. This leads to inconsistent quality, longer resolution times, and further customer frustration. It creates a vicious cycle that is very difficult to break, especially for a new owner who may not have the cultural footprint yet.
I always ask to speak with the Head of Support and a frontline agent. I observe the tone of the team. Are they drowning? Do they have the tools to succeed? If the agents are using manual spreadsheets to track their own performance, or if they are lacking a centralized knowledge base, the scalability is limited. The "human element" dictates the speed of response. As the business grows, will this team keep up? If the answer is no, the operational cost will skyrocket. You need to factor in the cost of recruiting a better leader or implementing new ticketing infrastructure into your post-acquisition model.
Burnout also impacts the accuracy of the data. Stressed agents may misclassify tickets, assign lower priorities to valid complaints, or use canned responses too aggressively. This pollutes the data you are using for due diligence. You need to verify that the categorization of tickets is consistent and logical. If the data is messy, the insights are unreliable. A clean, well-managed support operation is an asset because it provides accurate, actionable intelligence. A chaotic support team is a liability because it hides problems until they become crises. Your job is to distinguish between a team that is busy and a team that is struggling.
To systematize your review, you need a rigorous checklist. This ensures you do not miss the subtle signals that financial statements miss. I use the following numbered checklist when evaluating SaaS targets. This list is designed to be executed by both the financial analyst and the product expert on your deal team. It combines quantitative volume analysis with qualitative sentiment review. By following this sequence, you can build a composite score of the operational health of the user support function.
Each item below is a mandatory stop. You cannot proceed to the next valuation step until these data points are collected and analyzed. This discipline prevents emotional bias from clouding your judgment. The numbers will tell you if the support engine is a strength or a weakness, and you must have the courage to adjust the offer price accordingly. Do not let a charismatic seller convince you that "it’s under control" without the data to back it up.
Here is the specific checklist we utilize at Deal Alert AI for our private clients and partners:
Once you have this data, how do you use it? It is a powerful negotiation lever. If you find that 40% of tickets are related to a specific broken feature, you can argue that the product roadmap is not just a future cost, but a current leakage of revenue. You can demand a price reduction equal to the estimated LTV of the customers at risk of churning due to this specific issue. This shifts the risk from you to the seller.
Alternatively, you can negotiate an escrow holdback. For example, you might agree to the asking price but hold back 10-15% of the purchase price in escrow for 12 months. You release this money only if the specific support metrics improve to a certain baseline. This aligns the seller’s incentives with the actual operational health of the business. It forces them to clean up the mess before you fully own it. This structure is common in platforms like Empire Flippers, where operational metrics are a key part of the deal structure.
Many buyers underestimate the cost of "fixing" a support machine. It is not just about hiring a new tool; it is about rebuilding the processes. If you are buying a business with a chaotic support operation, you are buying a management headache. Factor in 6-12 months of revenue disruption while you stabilize the team and the processes. Adjust your discounted cash flow (DCF) model accordingly. The present value of your future cash flows is lower if the first year is spent putting out fires.
Strategic Lever: Use "Support Efficiency" as a valuation metric. Present the offer based on a "normalized" EBITDA that reflects the cost of fixing the support issues, not the current EBITDA. If the current EBITDA is $200k, but fixing the top 3 ticket drivers requires $50k/year in development and support staffing, your valuation should be based on $150k of sustainable earnings.
Where you source this data matters. While large marketplaces like Flippa list thousands of opportunities, data quality varies wildly. Some sellers provide curated dashboards that hide the ugly truth. Others provide raw SQL access, which is gold. Always request access to the actual support tool (Intercom, Zendesk, Help Scout, etc.) as a read-only user during the data room phase.
Do not rely solely on the exportable CSVs. Sometimes, the export filters out certain metadata or tags that are crucial for categorization. Logging into the platform allows you to see the actual tags, the priority levels assigned by agents, and the status history of the tickets. You can see if tickets are sitting stagnant for weeks. You can see if agents are deleting tickets (which is a major red flag, though usually logged in system audit trails). The interface often reveals workflow bottlenecks that a spreadsheet cannot.
Additionally, verify the data integrity by doing a spot check. Pick a random week and manually verify a sample of 20 tickets against the logs. Does the "Closed" status match the actual resolution? Are tickets being auto-closed after 24 hours regardless of user satisfaction? These subtle data hygiene issues can distort your volume and trend analysis. If the data is unreliable, you cannot make a confident decision. If a seller resists providing backend access, assume the worst. Transparency is the hallmark of a healthy business; opacity is the hallmark of a problem.
Acquiring a SaaS business is not just buying a piece of code; it is acquiring an engine of customer relationships. Support is the interface where that relationship is tested daily. By rigorously analyzing support ticket volume, trends, and types, you gain a profound advantage over other bidders. You see the business as it truly is, not as the marketing materials claim it to be.
Use this knowledge to build a safer investment. A business with "messy" support data is not automatically a bad buy, but it is a specific type of buy that requires specific post-acquisition action. Maybe the solution is just a new onboarding flow that deflects 50% of tickets. Maybe it requires a senior engineer to rewrite a core module. Understanding the specific pain points allows you to value the business correctly and plan your first 90 days with precision.
At Deal Alert AI, we believe that data-driven diligence is the only way to mitigate risk in the SaaS market. The gap between a successful acquisition and a failed one is often in the details. Support tickets are those details. They are the voice of the customer, captured in black and white. Listen to them. They will tell you if the foundation is solid enough to build your next empire upon. Don't skip this step. It is the cheapest insurance policy you can buy in the entire diligence process.
We scan Empire Flippers, Acquire, Flippa, and Quiet Light daily. The best sub-$500K businesses are gone within 48 hours.