This is the claim that most changes what you are buying, and the one least visible in financial statements. It is more testable than it looks: founder dependency leaves fingerprints in the subscription data, in the acquisition mix, and in the shape of the largest accounts.
TL;DR: The five-hours-a-week claim is testable against the subscription data. Here is where founder dependency shows up in a billing export, and what to ask for when it does.
Sellers are usually describing their current steady state honestly. Five hours a week can be genuinely true for a mature product with a settled customer base, and it can also be true only because the founder has absorbed a decade of context that makes each decision fast. The distinction is not about hours; it is about which of those hours are transferable. Nothing in a P&L captures that, so the test has to come from elsewhere.
Four mechanisms account for most of the gap between this claim and what the raw rows show. They are not mutually exclusive and they compound.
If new customers arrive from the founder's audience, community presence, podcast appearances or personal network, the channel does not convey with the asset. Ask for acquisition source by month and check what share is attributable to a person rather than a system.
Low support hours with high customer satisfaction often means one person answers everything with total product knowledge. Ask for ticket volume, median response time, and whether any documented process or macro library exists.
The top accounts in a founder-led business are frequently retained by a relationship rather than by the product. Cross-check the concentration analysis against tenure: long-tenured large accounts with no formal contract are relationship-held.
Five hours a week is sometimes achieved by not doing things. Ask about dependency versions, unpatched libraries, the last significant infrastructure change and any single-person deployment process. Deferred work becomes your work in month one.
Every step below runs on a subscription-level export in a spreadsheet. None of it needs access to the seller's live billing account, which matters, because as a buyer you will not get one.
These are the thresholds we use in our own reports. They are working thresholds rather than industry standards, and the right line for a given deal depends on contract length, tenure and how transferable the customer relationships are.
| What you find | Verdict | What to do about it |
|---|---|---|
| Documented processes, non-founder support, systematised acquisition | Green | The claim is about the system rather than the person. This is what transferable looks like. |
| Under 20% of new customers from founder-attributable channels | Green | Acquisition will survive the transition. Verify the support story separately. |
| More than 40% of new customers from founder-attributable channels | Price it in | You are buying a product and not its distribution. Budget for replacement acquisition from day one. |
| Top accounts long-tenured, large and uncontracted | Investigate | Relationship-held revenue. Meet those customers before close and consider a hold-back tied to their retention. |
| No documentation, no second person, no deployment process | Price it in | The five hours are absorbed context. Price a transition period and a real handover, or budget to rebuild the knowledge. |
Ask for these before the LOI. After the LOI you are renegotiating rather than negotiating, and a seller who will not produce subscription-level rows has told you something useful either way.
Illustrative. A $18,000 monthly SaaS, five hours a week, no employees. Acquisition source data shows 54% of new customers over twelve months arriving from one founder's community presence, with clear spikes after each public appearance. Six of the top ten accounts have been customers for over four years with no written contract. Support is 40 tickets a month answered personally, median response under two hours, with no documentation. Nothing here is misrepresented: the founder really does spend five hours a week. But roughly half the acquisition channel and a meaningful share of the retention leave with them, and the five hours become twenty for a new owner without the context. The correct response is not to walk away, it is to price the transition and to structure the deal so the handover actually happens.
Founder dependency is the risk most likely to change the outcome of a small SaaS acquisition and the one least represented in the financials. It is also the most addressable through structure rather than price: a transition services agreement with defined deliverables, an earn-out tied to retained revenue, direct introductions to the largest accounts before close, and a documentation requirement as a condition of closing. Diagnose it from the data, then solve it in the contract.
The relevant tool on this site is the buyer risk assessment, which runs the arithmetic above on a file you paste in. The full method is documented in the 5-risk buyer-side method and the due-diligence checklist.
Every check on this page can be run by hand in a spreadsheet, and if you have the time you should. If you would rather not: send us the target's subscription export and we run the full human-reviewed analysis — logo churn, revenue churn, customer concentration, annual-plan decay, zombie MRR and an A–F revenue-quality grade. The free Starter tier covers one CSV per month, which is enough to check a single deal.
See a sample report → · Get the free 23-point checklist →
Look for the founder in the data rather than in the hours. Acquisition source by month shows whether new customers arrive through a system or a person. Tenure and contract status on the largest accounts show whether revenue is held by the product or by a relationship. Support volume against documented process shows whether low hours mean systematised or absorbed.
The share of the business's performance that relies on one person's audience, relationships or accumulated context rather than on transferable systems. It rarely appears in financial statements, and it is usually the largest single gap between the business the seller runs and the business the buyer receives.
Often, yes, and structure is usually the better tool. A transition services agreement with specific deliverables, an earn-out tied to retained revenue, introductions to the top accounts before close and a documentation requirement as a closing condition all address the risk directly. Price is a blunt instrument for a problem that is really about handover.