How to Run a Buyer Discovery Call for a Sub-$100k Digital Business

Sub-$100k deals collapse on the discovery call more often than on price. Here's the script.

Most sub-$100k deals that fall apart do not fall apart on price. They fall apart on the first call, or rather they should have, and instead they limp on until the buyer discovers in diligence what a sharper call would have surfaced in twenty minutes. By then the buyer has spent a fortnight reading transaction logs and half-liking the deal, and walking away costs more emotionally than it should. The call is where you buy yourself the option to say no cheaply.

The problem is that the discovery call at this size is deceptively casual. There is no NDA, no letter of intent, no data room, no advisor sitting in. It is one busy seller and one hopeful buyer on a thirty-minute video call, and the seller has usually done fewer of these than the buyer. That informality is the trap. Without structure, the call drifts into rapport, the seller talks about the parts they enjoy, and the buyer leaves warm but no better informed than the listing already made them.

This is a reference piece. Keep it open before your next call.

Why the discovery call decides the deal

A good listing tells you what the seller chose to write down. The call tells you what they say out loud when asked a direct question they were not expecting. Those are different bodies of information, and the gap between them is where the risk lives.

Three things are almost impossible to get from a listing and reliably available on a call. The first is the honest why-now. A listing says "moving on to new projects." A call, if you ask well, tells you whether that means burnout, a new job that killed the time budget, a co-founder split, or a slow decline the seller has decided to stop nursing. The second is the operating rhythm – how many hours a week the thing actually takes, on which days, doing what. The third is the seller's private read on what stops working after they hand over the keys. Every founder knows one thing about their business that would not survive their departure. Most will tell you if you ask plainly. Almost none will write it in a listing.

You are not on the call to be liked. A buyer who treats discovery as a sales pitch, working to charm the seller into choosing them, gives away ground they will want back on the second call. Discovery is information collection. Warmth is fine. Performance is not.

The 30-minute structure

Thirty minutes is enough. If it is not, that is information too.

Spend the first five minutes on context – who you are, what you are looking for, and one sentence on why this listing. Keep it short. The seller does not need your life story, and every minute you spend talking is a minute you are not learning anything.

Give the middle fifteen minutes to the question block, which is the next section. Fixed questions, fixed order. You are running an agenda, not having a chat.

Reserve five minutes for the red-flag check – the specific inconsistencies you noticed in the listing and want to test against a live answer. Then five minutes to agree the next step: what you need to see, by when, before a second conversation.

If the seller wanders past their slot on a question they enjoy, that is not warmth to be indulged. It is a signal. A founder who cannot summarise their own business inside a time-boxed half hour is telling you something about how loosely it has been run. Note it and steer back. The discipline of the call is part of the diligence.

The ten questions, in order, with what each answer reveals

Ask them in this order. The order matters – you open with the fact-based questions that are hard to fudge, and you arrive at the softer, more revealing ones once the seller has warmed up and is answering on instinct rather than script.

1. Walk me through what the business does and who pays for it. You are checking whether the seller can describe their own customer. A good answer names a specific person or segment and the problem they pay to solve. Evasion sounds like the product spec read back to you – features, stack, roadmap – with no human at the centre of it. A founder who cannot describe the customer usually did not talk to them.

2. What does a normal week of running this actually involve? You want hours, tasks, and cadence. A good answer is concrete and slightly boring: "Two hours on Monday clearing support, an hour midweek on the newsletter, occasional deploys." Evasion is the phrase "it basically runs itself," which is almost never true and easy to test against the next questions.

3. Where do the customers come from? You are mapping the acquisition channel and its fragility. A good answer names channels and rough proportions, and admits concentration where it exists: "Mostly one SEO article that ranks, plus word of mouth." Evasion is vagueness – "organic, mostly" – which usually means the seller has not looked.

4. Walk me through the revenue over the last twelve months. You are testing the numbers against the listing and watching for a story that explains the shape. A good answer volunteers the dips and what caused them. Evasion is a flat "it's been steady" when the listing chart plainly is not, or a reluctance to go month by month.

5. When did you last log into the analytics, and what were you looking at? This is a behaviour question dressed as a data question. A good answer is recent and specific. A seller who has to think hard about the last time they checked the numbers has already half-left the business, and you are buying something that has been coasting.

6. What breaks or gets neglected when you are away for two weeks? You are asking for the failure point directly. A good answer is honest: "Support times slip, and I have to catch up on one manual billing job." Evasion is "nothing, it's all automated," which contradicts almost every real business at this size and is worth probing until it cracks.

7. What have you tried that did not work? You are checking whether growth is stalled because it is genuinely capped or because the seller stopped trying. A good answer shows a founder who experimented and learned. A blank on this question means either the business was never pushed, or the seller is not telling you why they stopped pushing.

8. What would you do next if you were keeping it? You want their honest read on the upside, separated from the sales pitch. A good answer is specific and slightly wistful – the thing they never got to. Evasion is a generic growth list ("ads, SEO, partnerships") that anyone could recite, which tells you they have not thought about this particular asset's next move.

9. Why sell, and why now? This question carries the most weight, which is why it sits late, after the seller has stopped guarding. Burnout, a new job, a distraction, "we just had a baby" – all valid, all human, all fine. "I just felt like it" is not an answer; it is a wall. If the why-now does not hold together, nothing else you heard is safe.

10. Is there anything I have not asked that I should have? You are handing the seller room to disclose. Honest sellers use it – a lapsed integration, a key customer wobbling, a dependency they forgot to mention. A fast "no, I think you've covered it" is not damning, but a long pause followed by a small confession is the most useful thirty seconds of the call.

Take written notes throughout, not a recording. The point is not to have a transcript. The point is that translating what the seller said into your own words, in the moment, is itself the first pass of diligence. A recording lets you skip the thinking. Notes force it.

Red flags that surface in the first call

Some problems only show up when a live answer contradicts the written one. The seller who cannot describe their customer, from question one. The founder who has not opened the analytics in a month, from question five. The project that "basically runs itself" whose support inbox, on inspection, answers in forty-eight hours. Revenue described as steady over a chart that visibly is not – the kind of gap that is exactly why the dashboard is the least reliable number in the pack.

None of these is automatically fatal. A neglected business at a fair price can be a genuine opportunity for an operator who plans to actually run it – that is the buy-and-grow case, and it is a good one. The flag is not the neglect. The flag is neglect the seller will not name, priced as if it were not there. What you are testing on the call is not whether the business is perfect. It is whether the seller's account of it survives contact with a direct question.

What the structure actually buys you

Take one fictional listing: a small content site in the personal-finance niche, around $2,400 a month, listed at roughly $70k, "runs itself, moving on to new projects."

Run the unstructured version and it goes forty-five minutes. The buyer opens with enthusiasm, the seller warms to it, and the conversation settles into the parts the seller likes – the writing, the early wins, the plan they never got to. Rapport is high. Forty-five minutes in, the buyer knows the seller is friendly, the niche is one they find interesting, and the traffic "comes from Google." They end on "this looks really promising, let's talk again," and hang up warm and no wiser. The concentration risk, the why-now, and the state of the analytics were never touched, because there was no slot forcing them onto the table.

Run the structured version on the same listing and it takes thirty. By question three the buyer learns that eighty per cent of traffic comes from four articles, one of which has been sliding since a search update in March. By question five the seller admits the last real analytics session was "a couple of months ago." At question nine the why-now turns out to be a full-time job started in spring, which explains the neglect and the slide together. Same seller, same asset, same friendliness – but now the buyer walks away knowing this is a conditions case at best, priced as if the traffic were stable when it is quietly not. The warm call flattered the deal. The structured call described it.

The decision template

Here is the discipline that separates a discovery call from a nice chat. Do not decide on the call.

The pull to soften the decision in real-time is strong. You have spent thirty minutes with a real person who was candid and likeable, and the human instinct is to reward that with encouragement – to say "this looks great" while you are still on the line. Resist it. You are not obliged to render a verdict in the moment, and doing so trades your leverage for a moment of comfort. Thank them, agree the next step, and decide later, alone, against your notes.

When you sit with the notes, the call resolves into one of three outcomes. Proceed to diligence: the numbers, the why-now, and the operating rhythm all held together, and you want to see the books. Proceed with conditions: it holds together if one specific thing checks out – a channel that is less concentrated than it looked, a dependency that is documented, a metric confirmed against the raw data. Walk away: something did not add up and the seller could not steady it when pressed.

Two questions close the file. Would I be comfortable running this next Monday if the seller vanished tonight? And do I believe the why-now? If either answer is no, it is a walk-away or a conditions case, regardless of how warm the call felt. Listings like these appear on platforms such as Indiemaker every week, and the buyer who can decline cleanly is the one who eventually acquires something good, because they were never bidding from a place of relief.

The call is not where you buy the business. It is where you earn the right to keep looking at it. Most buyers get that backwards, and treat the first friendly conversation as a reason to stop being careful. The structured call does the opposite. It is designed to give you an early, cheap, honest reason to say no – and the buyers who make peace with saying no often are the ones who, over a few years, quietly build a portfolio worth having. When a call clears this bar, what follows is the deeper work: the proportionate due diligence a small deal actually deserves, before you wire anything to anyone.

Quick reference: the ten questions

Keep this on screen during the call. Ask in order – the hard-to-fudge facts first, the softer questions once they're answering on instinct.

1. Walk me through what the business does and who pays for it.
2. What does a normal week of running this actually involve?
3. Where do the customers come from?
4. Walk me through the revenue over the last twelve months.
5. When did you last log into the analytics, and what were you looking at?
6. What breaks or gets neglected when you're away for two weeks?
7. What have you tried that didn't work?
8. What would you do next if you were keeping it?
9. Why sell, and why now?
10. Is there anything I haven't asked that I should have?

Then close, don't decide: thank them, agree the next step, and score it later against your notes – proceed, proceed with conditions, or walk away.