10 Red Flags Buyers Miss When Evaluating a SaaS Business

A SaaS listing leads with MRR and a growth curve. Whether the revenue recurs by contract or by hope, what the churn looks like cohort by cohort, and whether the code can survive its author, all of that sits underneath the curve, and it is where SaaS acquisitions succeed or fail.

The red flags below are the patterns that most consistently appear across SaaS acquisition listings. They function as a general screening framework, a starting point for the questions a buyer should be asking. They are not a substitute for deal-specific analysis. The findings in a Dealytix report are tailored to the asset in question: its actual numbers, its specific niche, the seller's responses to inquiry. A general checklist tells you where to look. A targeted report tells you what is there.

What "red flag" actually means in this context

A red flag is a signal that the data shows something the listing has not explained, e.g., a deviation, an absence, or a pattern that warrants further inquiry before pricing the deal. Whether it justifies walking away, renegotiating, or proceeding with conditions depends on what the seller's response to the question reveals. The cost of catching a red flag is a few hours of analysis. The cost of missing one, that is, discovering it three months into ownership can erode a significant portion of the purchase value.

The 10 red flags

1. Top-line growth is shown; cohort behavior is not. Growing MRR can hide a leaky bucket that empties the moment acquisition slows. How each month's customers retain over time is the single most predictive dataset in a SaaS deal, and its absence from a listing is a choice.

2. Revenue figures come from a dashboard, not the billing system. The payment processor's records are the ground truth; a metrics dashboard is a presentation layer. Material divergence between the two reprices the deal or ends it.

3. Annual prepayments are presented as monthly recurring revenue. A year of cash booked upfront inflates the monthly figure and pulls a wall of renewal risk into the buyer's first year. How the recurring number is actually calculated decides what multiple it deserves.

4. A handful of accounts, or a single plan, carry the revenue. Customer concentration turns churn from statistics into events: one cancellation is a bad quarter. Concentrated revenue belongs in an earnout or a discounted multiple.

5. Lifetime-deal history sits inside the recurring figure. Lifetime deals are one-time cash wearing a subscription costume, with a perpetual service obligation attached and no future income to match. The honest recurring figure excludes them.

6. The code was written by contractors and the ownership paperwork is thin. Without written intellectual-property assignment from everyone who wrote it, what is being sold may not be fully the seller's to sell. The gap surfaces at the worst moments: closing, or your own exit.

7. The product cannot live without one developer, or one API. A single irreplaceable engineer is key-person risk; a single critical third-party API is platform risk with someone else's pricing power attached. Both transfer with the deal, and neither appears in the P&L.

8. Net revenue retention sits below the waterline. When expansion and retention together fall meaningfully short of replacing what churns, new sales are refilling a draining tank. Growth spend in that condition is treading water, priced as progress.

9. Growth required the founder's face, network, and discounts. Sales driven by the founder's audience and personally negotiated discounts do not transfer with the domain. Which acquisition channels are structural, and which are personal, is the durability question.

10. There is no convincing answer to why it couldn't be rebuilt quickly. If the core value can be reproduced fast with current tooling, increasingly including AI tooling, the durability of the revenue depends on proprietary data, integrations, and switching costs. A feature is a head start, not a moat.

How to respond when you find one

A red flag is an opportunity to raise a question to the seller. Ideally, in writing, and observe how it gets answered. A seller who acknowledges the issue, explains what is behind it, and proposes a structural response is communicating that the data is real and the deal is genuine. A seller who reframes, redirects, or supplies a different number is communicating something else.

Three productive ways to handle a red flag:

1. Make it a price adjustment. Quantify the financial impact and adjust the offer accordingly. A declining trend or a concentration risk may warrant discounts.

2. Make it an earnout. Convert the contested portion of value into deferred consideration, paid only if the channel sustains the metric the seller is asserting. This shifts the risk to the side of the table where the information lives.

3. Make it a condition precedent. Decline to close until a specific deliverable is provided, e.g., source records, a cost itemization, key contracts. Attempts to negotiate around the condition reveal whether the original assertion was accurate.

Common questions

A clearer picture before you commit

Send us the listing URL. Independent analysis delivered within 48 hours, before you bid, before you offer, before you sign.

Independent · Evidence-graded · 48-hour delivery · Not financial advice