Primary question
What should a buyer ask a SaaS seller before investing serious time in the deal?
Practical takeaway
The right seller questions are designed to test transferability, evidence quality, and story consistency, not to collect generic background information.
Key points
- Ask for examples and systems, not just opinions and summaries.
- Keep revenue, customer behavior, and transfer questions separate.
- Notice where the seller can explain the business clearly and where the story goes soft.
Framing
The first seller conversation is a screening tool, not a diligence replacement
A serious buyer should leave the first seller conversation with a clearer sense of what the business is, how it actually runs, and whether the transfer work looks legible. That is enough. The call does not need to exhaust every diligence question.
What matters is whether the seller can explain the business coherently without hiding behind dashboards or broad claims. A clean early call reduces the number of deals that graduate into expensive curiosity.
- Use the call to test whether the story and the operating reality match.
- Keep your questions grouped by revenue, operations, and transfer risk.
- Treat vagueness as information, not as something to smooth over with optimism.
What the first call should help you answer
- Is the business understandable enough to underwrite?
- Can the seller explain customer behavior without hand-waving?
- Does the handoff sound like a real workflow or a promise?
- Is there enough evidence quality to justify deeper diligence?
Questions
Ask for systems, exceptions, and examples instead of seller summaries
Founders usually know how to tell the upside story. Better questions force operating detail: how support works, where churn comes from, which customers are fragile, what breaks in the product, and which workflows still live only in the founder's head.
Questions that begin with 'walk me through the last time' are often stronger than questions that begin with 'would you say' because they pull the conversation toward evidence instead of posture.
- Ask how customers are acquired, retained, and lost.
- Ask what support, maintenance, and edge cases still depend on the founder.
- Ask which parts of the handoff will be hardest for a new owner to inherit.
High-value seller questions
| Area | Question | Why it matters |
|---|---|---|
| Revenue | Which customers would worry you most if they churned in the next 90 days? | Surfaces concentration and fragility faster than a top-line MRR number. |
| Customer behavior | What patterns do you see when customers churn or downgrade? | Tests whether retention is understood or merely observed. |
| Operations | What recurring tasks still require your judgment every week? | Exposes founder dependency and hidden workload. |
| Transfer | Which parts of the business would be hardest to hand over cleanly? | Clarifies where transition risk will show up after close. |
Interpretation
Judge how the seller answers, not only what they answer
A seller does not need to have a perfect business to be credible. But the seller should be able to describe weaknesses clearly, separate facts from assumptions, and make the transfer work legible enough that the buyer can price it.
This is where the call becomes useful. Strong sellers are rarely flawless; they are usually just clearer about the business they are actually selling.
- Clarity is more valuable than a polished narrative.
- Consistency across questions matters more than charisma.
- If the seller cannot explain the operational load, the buyer should assume it is higher than presented.
Note
A soft answer is still a real answer
If the seller gets vague exactly where transfer, retention, or support burden should become concrete, the buyer should treat that softness as part of the diligence file.
Related pages
Buy
· Guide
Apr 9, 2026 · ready
How to buy a micro-SaaS
A workflow-first foundation for sourcing, screening, diligencing, and taking over a small software business without confusing activity for conviction.
11 min read
5 sources · high
Read entry →Buy
· Guide
Apr 9, 2026 · ready
Micro-SaaS due diligence checklist
A practical checklist for deciding whether a small software business is understandable, transferable, and worth operating after close.
10 min read
6 sources · high
Read entry →Buy
· Guide
Apr 11, 2026 · ready
Red flags in micro-SaaS acquisitions
A practical guide to the signals that should lower conviction or kill a small software acquisition before the buyer confuses seller momentum with deal quality.
7 min read
4 sources · mixed
Read entry →