How to Run User Interviews During SaaS Due Diligence to Avoid Costly Mistakes

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.

Buying a SaaS business is not just about looking at revenue multiples. It is about understanding the engine that drives that revenue. The most expensive mistake buyers make is relying solely on back-office data like MRR, ARPU, and churn rates from Salesforce or Stripe dashboards. Those numbers can be manipulated, smoothed, or temporarily inflated by one-off large contracts. The only way to truly understand the health of a subscription business is to talk to the people paying for it.

I have seen due diligence processes fail because the buyer assumed the founder’s narrated growth story was true, only to find out during the first 30 days of ownership that 40% of the "active" users were actually dormant or using free trials that never converted. User interviews are your primary tool for mitigating this risk. They allow you to triangulate what the seller tells you against what the customer actually feels, thinks, and experiences. It is a qualitative overlay that adds critical context to the quantitative data.

In this guide, we break down the exact process for running effective user interviews during SaaS due diligence. This is not about being friendly; it is about being forensic. You are looking for red flags, you are validating retention drivers, and you are assessing how resistant the product is to competitive threats. If you are looking for high-quality, vetted SaaS opportunities in this space, platforms like Deal Alert AI aggregate data that can help you pre-qualify assets before you even reach out to the seller for interview schedules.

Why User Interviews Are the Ultimate Risk Mitigation Tool

Financial due diligence tells you what happened. For example, it tells you that MRR was $50,000 in Q1 and $60,000 in Q2. But it does not tell you why. Did revenue grow because the product feature set improved? Did it grow because the sales team worked harder? Or, worryingly, did it grow because the seller lowered prices to close deals, creating a fragile revenue base that will crumble if you raise prices back to market rate? User interviews answer the "why" questions that spreadsheets cannot.

The primary risk in SaaS acquisition is churn. If you buy a business with 3% monthly churn, the math works out to a very specific lifetime value (LTV). However, if 3% churn looks stable on a dashboard, it might be masking a deeper issue: customers are churning because support is slow, or because the core value proposition is being eroded by a new competitor. By speaking directly to recent churned customers and long-term loyalists, you can categorize the reasons for departure and retention. This allows you to build a more accurate LTV model, which directly impacts your offer price.

Furthermore, interviews help you assess the "stickiness" of the community around the product. In SaaS, a strong user community can be a massive competitive moat. If customers are referring their peers, participating in forums, and advocating for the product on Twitter or LinkedIn, that is valuable intellectual capital that is not captured in the P&L. Conversely, if the user base is passive, the business is likely dependent entirely on paid acquisition costs (CAC), which is a much more volatile and expensive way to sustain growth. Understanding this dynamic is crucial for projecting future marketing budgets.

Preparation: Building the Interview Shortlist

You cannot interview every single user. Nor should you. Your goal is to achieve "narrative saturation," a point where new interviews start yielding the same insights as previous ones. For a SaaS business with 500+ customers, I typically recommend a sample size of 10 to 15 interviews. This usually covers three distinct cohorts: loyal customers (1+ year tenure), recent churners (last 90 days), and recently acquired users (last 30 days). This mix gives you a 360-degree view of the lifecycle.

The selection process must be meticulous. Ask the seller for a list of these users, but verify their engagement independently before the call. Check their login activity, support ticket history, and even their social media footprints. You do not want to interview a user who has not logged in for three months but still appears as "active" in your CRM. This is a common point of failure where sellers present "inactive" users as "dormant," when in reality, they are mentally checked out.

Once you have your list, you need to handle the outreach carefully. The seller should ideally make the introduction, framing you not as a "buyout investigator," but as a "product improvement specialist." Your goal for the outreach email is to secure a 20-minute call. If the seller cannot secure interviews, or if users refuse to talk to a third party, this is a massive red flag. It suggests that the relationship with the customers is purely transactional and lacks the loyalty that protects a SaaS business from attrition. If you are struggling to find assets where the seller is transparent and willing to facilitate these introductions, browsing curated listings on Flippa can help you identify sellers with a history of high engagement and responsive communication.

The Interview Framework: Questions That Reveal Truth

Most buyers make the mistake of asking leading questions like, "Do you like our product?" or "Would you renew your subscription?" The answer will almost always be "yes," because humans are polite. Your questions must be behavioral and specific. You want to ask about their past actions, not their future hypothetics. For instance, instead of asking if they would recommend the product, ask them about the last time they tried to share it with a colleague. What specifically made that interaction easy or difficult? What did that colleague say about the product?

When interviewing long-term customers, focus on the "aha" moment. Ask them, "When you first signed up, what was the specific problem you were trying to solve? And what specific feature or workflow in our product actually solved that problem?" If they cannot articulate a clear, singular value proposition, the business is at risk. Users who cannot clearly explain why they pay you are the first to churn when a competitor launches a cheaper alternative or when the economic climate tightens. You want to hear language that maps directly to the core mission of the product.

For recent churners, the approach must be empathetic but unyielding. Their objection is the data point. Ask, "What was the specific trigger that made you cancel?" Was it a pricing change? A feature gap? A support issue? Or did a competitor offer them something better? You are looking for patterns. If five out of six churners mention the same missing integration or the same slow support response time, you now have a clear roadmap for your first 90 days. If you fix this, you can likely reverse the churn trend, adding direct value to your acquisition. Conversely, if the reasons are disparate (one hates price, one wants a feature, one is just moving jobs), the churn may be natural market volatility rather than a product defect.

Identifying Red Flags and Signal Decay

One of the most common red flags in user interviews is "feature creep" complaints. If users mention that the product feels bloated, confusing, or that they only use 10% of the features, this indicates technical debt and user experience decay. In SaaS, simplicity is a currency. If your users find it hard to find the value they paid for, they will churn. This is particularly dangerous in businesses that have been scaling rapidly without iterating on the user experience. The codebase may be a monster, and the cost to fix the UX issues might exceed the value of the asset if not accounted for in your due diligence.

Another subtle red flag is reliance on "founder knowledge." If users say they rely heavily on the founder or a specific team member for guidance, troubleshooting, or strategic advice, this is an operational dependency that does not scale. A robust SaaS product should be self-sufficient. If the founder steps away (which they will after the sale), and the users are already complaining that "support is slow" or "we don’t understand how to get X to work," you are buying a business that has a broken onboarding or knowledge base. This translates to higher future CAC because new users won’t activate without manual hand-holding.

Pay close attention to the language used when discussing price. If users express dissatisfaction with the price but continue to pay, they might be locked in due to switching costs or lack of alternatives. This is a precarious position. It means your churn is artificially suppressed by inertia, not loyalty. The moment a new, easier-to-use competitor enters the market, that inertia shatters, and you face a cliff-edge churn event. Interviews allow you to measure this "shock tolerance." You are essentially calculating the margin of error in your pricing strategy. If the feedback is lukewarm on value-to-price ratio, you need to discount your offer to reflect the risk of a price war or a demand shock.

Quantifying Qualitative Data for Valuation Adjustments

How do you turn a conversation into a number in your Excel model? You don't just take a qualitative note and ignore it. You create a "Risk Adjustment Score" based on the interview outcomes. For example, if you identify a systematic onboarding bug that affects 20% of new users, and you estimate the cost to fix the engineering ticket is $15,000, you deduct that from the enterprise value. If you find that 30% of churn is due to a lack of feature X, and building Feature X costs $50,000, you must decide if the ROI of building it post-acquisition is viable or if you should lower your price to account for the inevitable churn that will occur until it is built.

I recommend maintaining a structured spreadsheet during the interview phase. Columns should include: User Cohort, Tenure, Main Pain Point, Feature Request, Price Sensitivity (1-5 scale), and NPS Sentiment. After 10 interviews, a pattern emerges. If 7 out of 10 rate price sensitivity high, you know your LTV ceiling is lower than the seller’s projection. You must run the numbers with a lower ARPU (Average Revenue Per User) to see if the business remains profitable at that lower price point. This is the core of value negotiation. You are not just negotiating for a discount; you are negotiating for the business to be valued at its real risk-adjusted performance level.

This quantification also helps in structuring your earn-outs. If you find during interviews that the user base is enthusiastic about a new flagship feature that is currently in beta, you can tie a portion of your purchase price to the successful adoption of that feature. For example, 20% of the purchase price is an earn-out payable in 12 months, contingent on that feature generating $10,000 in MRR. This aligns the seller’s incentives with the user’s satisfaction. If the feature wasn’t as good as the seller claims, the earn-out doesn’t trigger, protecting your capital. Findings like these are critical, which is why we encourage buyers to use tools like Deal Alert AI to cross-reference advertised feature sets with actual user sentiment data available in public reviews and forums.

Negotiation Leverage: Using Insights to Close

User interviews give you psychological and tactical leverage in the final negotiation. When you have data that contradicts the seller’s optimistic growth narrative, you can present it calmly on a whiteboard. For instance, if the seller claims churn is low because their "enterprise customers" stay forever, but your interviews with mid-market customers reveal a struggle with retention, you present the mid-market data. You show that the "enterprise" claim is a vanity metric masking a broken mid-market engine. This shifts the power dynamic. The seller realizes you understand the business deeper than they expected, which often leads them to offer a better price to close the deal quickly rather than risk losing a savvy buyer.

You can also use interview insights to propose specific "post-closing" plans that the seller has never considered. If users are complaining about mobile usability, and you have a roadmap to fix that, you can demonstrate to the seller that you are not just a cash buyer, but a strategic partner who will grow the asset. Often, motivated sellers will pick up the slack on price if they believe you have a credible plan to increase the value of the business. Your due diligence becomes your sales pitch to the seller. It shows preparation, knowledge, and intent. It separates you from the bandwagon of buyers who just want to look at a multiple and write a check.

Furthermore, these insights help you structure the transition period. If you know that the user base is anxious about vendor changes, you can plan a communication campaign before closing. You can hire the right CPO or Head of Customer Success specifically to address the pain points you discovered. If users said support was slow, you know to budget for an additional support engineer in the first 90 days. This specificity builds confidence in your internal team and your advisors. It proves that you are ready to operate the business immediately, not just to collect royalties. This readiness is a key differentiator in competitive auctions. For more examples of how to structure these complex negotiations, check out the deep-dive case studies on Empire Flippers, which often detail the post-acquisition integration strategies alongside the deal metrics.

Building a Repeatable Due Diligence Process

To turn this from a one-off task into a scalable skill, you need a standardized checklist. Every SaaS is different, but the fundamental questions remain the same. Consistency ensures that you are not missing critical data points due to fatigue or bias. It also allows you to compare assets against each other. If you run 5 due diligence processes in a year, a standardized scoring system lets you rank the "quality of users" across all 5 deals, helping you make the final executive decision on which asset to pursue. The process below is the exact framework I use and teach to my acquisition team.

1. Define the Cohorts: Select 10-15 users: 5 loyal (1+ year), 5 recent churners (90 days), 5 new (30 days). Ensure tenure diversity.
2. Verify Engagement: Cross-check user activity logs. Exclude anyone with no login activity in the last 60 days to avoid "ghost" users.
3. The "Aha" Question: Ask each user to identify the single feature that stopped them from leaving. Record the exact feature name.
4. The "Churn Trigger": For churners, identify the specific moment or event that triggered the cancellation. Is it price, product, or support?
5. Price Sensitivity Audit: Ask users if they would still pay if the price increased by 10%. A "no" from more than 3 users indicates high price sensitivity.
6. Support Friction Check: Ask users to describe their last support interaction. If it was negative or unresponsive, flag the support operational debt.
7. Competitor Benchmarking: Ask what they considered before buying and why they chose this product. This reveals your actual market positioning vs. your perceived positioning.
8. Feature Request Aggregation: List every feature request. If 4+ users request the same thing, it is a product gap, not a niche need.
9. Community Sentiment Scan: Ask if they would recommend the product to a peer without prompting. If the answer is hesitant, the NPS is likely lower than reported.
10. Operational Dependency Flag: Ask if they rely on specific staff members. If yes, flag the key-person risk for the integration plan.

Executing this checklist rigorously transforms you from a passive observer to an active analyst. It ensures that no stone is left unturned. It also creates a paper trail that you can reference in your term sheet negotiations. When you sit down with the seller, you can point to specific quotes from their customers. This makes it extremely difficult for them to dismiss your concerns as "buyer's remorse" or unnecessary nitpicking. The data is undeniable. The users have spoken, and you have the transcript.

Conclusion: The Cost of Skipping the Conversation

The difference between a great acquisition and a bad one is rarely the multiple. It is the visibility into the underlying health of the asset. Financials are historical; they tell you where the car has been. User interviews tell you if the engine is making a weird noise, if the tires are bald, or if the GPS is stuck. You can buy a car with a clean title, but if the engine is failing, the title does not matter. In SaaS, the "engine" is the customer relationship. If that relationship is fragile, disengaged, or driven by reasons other than product value, the business is structurally unsound.

I have seen buyers lose six figures because they skipped this step. They looked at the 4x SDE multiple, they loved the niche, and they closed. Then, in month two, churn spiked because the new CMO tried to raise prices based on the seller's historical data, unaware that users were already complaining about affordability in interviews that were never conducted. They bought a business that looked good from the outside but was rotting from the inside. You cannot afford to make that mistake.

Start treating user interviews as a mandatory component of your due diligence, not an optional extra. Build the relationships, ask the hard questions, and let the customers decide if the business is worth the price tag. If you want to streamline the initial sourcing phase so you can focus more of your energy on these critical qualitative checks, leverage platforms like Deal Alert AI to filter for high-engagement assets with documented user sentiment. Due diligence is the most important part of buying a business. Do not rush it. Do not skip it. The truth is in the conversation.