Build This Now
Build This Now
speedy_devvkoen_salo
Blog/For Business/Nine Queries Tonight

Nine Queries Tonight

How much revenue are we losing to slow follow-up? Nine queries you can run tonight against your own records to produce a number your CFO will accept.

Quer o framework por trás destes projetos?

Obtenha o sistema Claude Code que usamos para planejar, construir, testar e lançar software em produção.

Veja o que construímos para empresas →
speedy_devvkoen_salo
speedy_devvWritten by speedy_devvPublished Jul 30, 20269 min readFor Business hub

Problem: You already know slow follow-up costs money. You have read the statistics. None of it has moved a euro of budget, because your CFO does not fund an industry average. They fund a number that came out of your own systems with a method attached.

Quick Win: Stop quoting research and produce your own figure tonight. Follow-up leakage means revenue lost not because you were outsold but because nobody replied, nobody followed up, or nobody was ever assigned. Nine queries against systems you already pay for turn it into a count and a euro figure. The ninth is the one nobody runs: reconcile how many inquiries arrived against how many were ever assigned to a named human. In LeanData's State of Lead Management survey of more than 500 B2B sales and marketing professionals, respondents said 25.5% of marketing-generated leads are assigned to the wrong account owner (LeanData). Wrong owner is bad. No owner is worse, and it does not show up in any report you currently read.

Why A Benchmark Will Not Get You Budget

The published research on follow-up is genuinely damning. In 2024, RevenueHero submitted demo requests to 1,000 B2B software companies and got a reply from only 365 of them: 63.5% never responded at all, and among those that did, the average reply took 1 day, 5 hours and 17 minutes (RevenueHero). That is worse than the 2011 Harvard Business Review audit of 2,241 companies, which found a 42-hour average and 23% never replying (HBR).

Now watch what happens when you put that in a board deck. Someone says "we are not like those companies." The conversation ends. You cannot win an argument about your own company using data about other companies.

Benchmarks also describe the wrong failure. Almost all published follow-up research measures response time, meaning how long the reply took. It says nothing about the inquiries that never entered anyone's queue, which is a different and larger category. Slow is a discipline problem. Absent is a plumbing problem. Different owners, different fixes, different price tags, and one benchmark cannot tell you which one you have.

So build your own. We have written elsewhere about why the cost of slow follow-up is a spend problem rather than a sales-effort problem; this post hands you the way to price it in your own currency.

Before You Start: The Three Fields You Need

You do not need a new system. You need three fields on every record, in whatever software you use to track customers and deals, plus your form submissions and shared inbox.

  1. A created timestamp. When did this inquiry or deal arrive? Without it there is no clock, and every query below is a clock.
  2. A named owner. Not a team, not a queue, not "sales". A specific person, with a start date for their ownership.
  3. A last two-way contact timestamp. The last time a message went out and something came back. Outbound-only activity is not contact, it is effort. Measuring effort gets you a report full of "just checking in" emails and no deals.

With all three, the nine queries take an evening. Missing the third, you hit a wall at query four, dealt with honestly further down. If your records are broadly untrustworthy, start with what to clean before you automate anything on top of it. You are in normal company: in Validity's 2025 survey of 602 CRM users and administrators, 76% said less than half of their organisation's customer data is accurate and complete, and 37% said they had lost revenue as a direct consequence (Validity).

Set the window at the last 90 days. Long enough to be more than a bad week, short enough that nobody can call the data stale.

The Nine Queries, In Order

Run them in this order. Query one is the denominator everything else is measured against, and query nine only means something once you have query one.

#The queryWhere it livesWhat a high count means
1Every inquiry received in the last 90 daysForm submissions, shared inbox, chat, phone logThis is your denominator, not a finding
2Of those, every one with no logged reply of any kind, everInbox and activity historyYou paid to generate it and never spoke to it
3Every inquiry where the first reply took longer than one hourFirst outbound timestamp minus created timestampThe window closed before you arrived
4Every open deal past the proposal stage with no two-way contact in 30 days and no recorded outcomeDeal stages, sent proposals, email historyNobody said no, so nothing was ever lost on purpose
5Every record with a written follow-up date that has passed with no activity sinceTasks, notes, call summariesA promise your team made and forgot
6Every record with exactly one outbound attempt and no replyActivity counts per recordOne touch and silence, treated as a decision
7Every deal sitting in one stage longer than twice your own median for that stageStage change historyA deal that is dead but still in the forecast
8Every open record whose named owner has left the company or changed roleOwner field checked against your staff listAn orphan nobody has noticed yet
9Query 1's count minus the count of inquiries ever assigned to a named humanOwner field, including its historyThe gap is not slow follow-up, it is no follow-up

Query nine is the one that changes meetings. Everyone assumes the answer is zero because the routing rules exist and nobody remembers turning them off. It is rarely zero. Inquiries arrive with a blank field the rule depends on, or from a source nobody wired up, or from a country with no assigned owner, and they sit in a default bucket no human reads. LeanData's respondents estimated a quarter of leads land with the wrong owner; the population with no owner at all sits underneath that and gets counted by nobody.

The same survey found fewer than 34% of respondents said sales always follows up on marketing-generated leads (LeanData). Two thirds of companies already suspect the leak. Almost none have counted it.

Turning Nine Counts Into One Euro Figure

Nine counts do not get budget either. One euro figure does. Here is the arithmetic, using only numbers you own.

You need two of your own inputs:

  • V, your average value of a won deal.
  • W, the share of qualified inquiries you normally convert into a won deal.

Then, for any query's count C:

Exposure = C × W × V

That is the headline. Now discount it twice, in public, before anyone else does it for you.

The quality discount. Inquiries nobody contacted are not a random sample. They skew worse than the ones a salesperson chose to work, because some were obviously students, job seekers, or competitors. Halve W as a conservative floor and say so in writing. Better: hand-check 50 untouched records, classify them, and use the real ratio.

The recovery discount. You will not win back everything you surface. Use 0.15 unless you have evidence for better.

Defensible recoverable revenue = C × (W × 0.5) × V × 0.15

Here is the shape of it. Every number below is an illustrative format, not our data and not a benchmark. Substitute yours.

InputIllustrative value
Query 2 count (never replied to, 90 days)420
V, average won deal value€18,000
W, win rate from a qualified inquiry12%
Exposure (420 × 0.12 × €18,000)€907,200 per quarter
After quality discount (W halved to 6%)€453,600 per quarter
After recovery discount (×0.15)€68,040 per quarter

Two things about that last row. It is roughly €272,000 a year from one query, which is a real budget conversation. And it is defensible, because every assumption is visible and every one was chosen to be pessimistic. A number that survives hostile questioning at €68,000 beats a number that collapses at €900,000.

Repeat for queries 4, 5, 6 and 9. Do not add query 2 and query 9 together: they overlap heavily, because an inquiry with no owner is usually also an inquiry with no reply. Report them as two views of the same population and take the larger, not the sum. Double counting is the fastest way to lose the room.

Reading The Result: Detection Problem Or Discipline Problem

The mix matters more than the total, because it tells you what you are actually buying.

What the counts look likeWhat you haveWhat fixes it
Query 9 gap is large, queries 3 and 6 are smallA detection problem. Inquiries never reached a humanRouting and ownership plumbing. Days to weeks, no behaviour change required
Query 9 gap is near zero, queries 3, 5 and 6 are largeA discipline or capacity problem. Humans got them and did not work themManagement, workload, and something that watches for silence
Queries 4 and 7 dominateA pipeline hygiene problem. Deals are dying without anyone deciding they diedForce a recorded outcome, then re-engage the ones that never got a no
Query 8 is largeAn ownership problem. Departures orphaned live relationshipsA reassignment rule triggered by staff changes

That first row is the good news case. A detection problem is cheap and fast to fix, needs nobody to change how they work, and is exactly what follow-up and relationship recovery is built to close. A discipline problem is slower and more political, because it means volume exceeds what your team can service and someone has to say that out loud.

Queries 4 and 7 deserve a note. Matthew Dixon and Ted McKenna analysed 2.5 million recorded sales conversations and attributed 40% to 60% of lost deals to buyer indecision rather than to a competitor (Challenger). A deal that goes quiet after a proposal is usually not a loss you were outsold on. Nobody chose against you, which means nothing has to be reversed to bring it back.

What A Healthy Set Of Answers Looks Like

There is no published benchmark for most of these, and inventing one would defeat the purpose. But three of the nine have a correct answer that does not depend on your industry.

  • Query 2 should be zero. Not low. Zero. Every inquiry gets a reply, even a bad-fit rejection. Any number above zero is money you spent to generate a hand-raise and then ignored.
  • Query 9 should be zero. Every inquiry gets a named human within a defined window. There is no legitimate reason for an inquiry to exist with no owner.
  • Query 8 should be zero within a week of any departure. Reassignment is an offboarding step, not a discovery.

The other six are a policy choice you set in writing: how fast the first reply goes out, how long a deal may sit without two-way contact, how many attempts count as a real attempt. Then the queries become a standing report instead of a one-off, which is the difference between an interesting evening and one source of truth that notices silence on its own.

Where This Breaks: When Your Data Cannot Answer Query Four

Query four needs a last two-way contact timestamp, and this is where most audits stall. Four common reasons, and what to do about each.

Email is not synced. If replies land in individual inboxes and never touch the central record, your system knows what you sent and nothing about what came back. Fallback: run query four against the shared inbox and sent folders for a sample of 30 deals, extrapolate, and label it an estimate.

Activity is logged as tasks, not messages. "Called client" as a task tells you effort happened, not that contact happened. Fallback: count only calendar events with an accepted external attendee as proof of two-way contact. It undercounts, which is the right direction to be wrong in.

Proposals live in a separate tool. If quotes go out from finance software or a document tool, the record showing the proposal was sent is not the record you are querying. Fallback: pull the proposal log separately and match on company name by hand. Painful once, and it usually produces the single largest count of the nine.

Nobody records why a deal died. Then query seven returns stale deals with no reason attached and you cannot tell a dead one from a slow one. Fallback: report the count anyway. Deals with no recorded outcome are themselves the finding, and it is the same input problem that limits mining your own records for buying signals.

One more failure mode: a snapshot gets argued away. Someone will say the quarter was unusual. Run the same nine queries on the previous 90-day window before you present, so you arrive with a trend rather than an anecdote.

What To Do With The Number Once You Have It

Do not open with the total. Open with query nine.

The sequence that works: show how many inquiries arrived, show how many were ever assigned to a human, let the gap sit for a second, then show the euro figure with every discount visible. You are not asking anyone to believe a claim about the industry. You are showing them a subtraction they can verify themselves in ten minutes.

Then split the ask. The detection half is plumbing and should be fixed immediately, because it costs almost nothing and needs nobody to change their habits. The discipline half is a capacity conversation for a different meeting with a different owner. Bundling them is how these findings die: the plumbing fix gets held hostage to a debate about whether the sales team works hard enough.

Finally, put the nine queries on a schedule. Monthly for two through six, quarterly for the rest. A one-time audit produces a good week. A standing report produces a number that goes down and stays down, and a number that went down is the only proof anyone accepts.

Related Reading

  • The real cost of slow follow-up, the research behind why this leak exists
  • One source of truth and a watchdog for leads, turning these nine queries into standing rules
  • Clean your customer records before you automate, what to fix if query four returns nothing usable
  • Signals already inside your own records, five more queries against the same data, aimed at new revenue instead of recovered revenue

Frequently Asked Questions

How long does this actually take?

An evening with reasonable records, two or three days if proposals and inquiries live in separate tools and you have to match by hand. The arithmetic takes ten minutes once the counts exist. The hard part is never the maths, it is finding the last two-way contact timestamp for query four.

What if the number comes back small?

Then you learned something worth knowing for the price of one evening. Say so publicly and move your attention elsewhere. An audit that can only produce a large number is not an audit, and a defensible finding that follow-up is not your constraint stops the company buying tools for a problem it does not have.

Should we use a benchmark win rate if we do not know ours?

No. If you cannot calculate the share of qualified inquiries you convert into won deals, that is more urgent than anything in this audit, because it also means you cannot measure whether any fix worked. Work it out first, roughly, from won deals divided by qualified inquiries over the last four quarters.


Most companies read one more article about follow-up, agree it is a problem, and change nothing, because agreement is not a business case. Nine queries and one defensible euro figure is. If the audit says your problem is detection rather than discipline, that is the half we install: one source of truth for every lead, an owner on every record within minutes rather than never, and automatic flags on the follow-ups quietly dying. See what we build for companies →

More in For Business

  • The 30-Day AI Pilot That Ships
    95% of AI pilots deliver no profit. The fix isn't a better model. It's a 30-day pilot scoped to one bottleneck with an output you can test the next morning.
  • Automate Accounts Receivable
    A controlled plan for accounts receivable AI automation: invoice checks, collection priorities, disputes, cash application, and human approval.
  • AI Agents vs Employees
    The honest 2026 cost of AI agents vs employees: the real all-in cost of a hire, where AI cuts costs by 85%, where AI agents end up costing more than staff, and why 95% of pilots fail.
  • AI Change Management Plan
    Build an AI change management plan with workflow owners, role-based training, human controls, adoption metrics, and a six-week rollout cycle.
  • Safe AI Contract Review
    Build a safe AI contract review workflow that extracts terms, checks an approved playbook, routes exceptions, and keeps final approval with counsel.
  • AI for the CFO
    The four finance numbers a CFO should automate first, ranked by payback: month-end close, collections and DSO, forecast prep, and board reporting.

Quer o framework por trás destes projetos?

Obtenha o sistema Claude Code que usamos para planejar, construir, testar e lançar software em produção.

Veja o que construímos para empresas →
speedy_devvkoen_salo

On this page

Why A Benchmark Will Not Get You Budget
Before You Start: The Three Fields You Need
The Nine Queries, In Order
Turning Nine Counts Into One Euro Figure
Reading The Result: Detection Problem Or Discipline Problem
What A Healthy Set Of Answers Looks Like
Where This Breaks: When Your Data Cannot Answer Query Four
What To Do With The Number Once You Have It
Related Reading
Frequently Asked Questions
How long does this actually take?
What if the number comes back small?
Should we use a benchmark win rate if we do not know ours?

Quer o framework por trás destes projetos?

Obtenha o sistema Claude Code que usamos para planejar, construir, testar e lançar software em produção.

Veja o que construímos para empresas →