Funnel economics

Model what a buyer-path problem means for your funnel.

Use your own requests, conversion, ACV, and win rate. Then model a conversion drop on part of the funnel.

Your numbers, your scenario. Estimates, never claimed lost revenue.

Start with numbers your team already has.

Eight inputs. Every figure on this page is derived from them.

Editable examples, not industry averages.
Your funnel

Demo, contact-sales, quote, or trial requests.

How many of those requests usually become opportunities.

Average closed-won value for this segment.

Share of opportunities that close.

Used only to match coverage scope. It does not multiply the funnel.

Degradation scenario

One region, device, form, scheduler, or follow-up layer.

Set 0 for a complete loss on the affected requests.

How long the problem runs before someone localizes it.

Your high-intent funnel

This is what those Paths carry in a year.

$17.5M annual pipeline
$3.5M expected won revenue
High-intent requests
1,560 / year
Expected opportunities
624 / year

Your own funnel, calculated from your inputs. BookedDemo does not create this revenue and does not claim it.

Degradation scenario

Now model a conversion drop.

Conversion drops from 40% to 30% for 20% of requests, over 2 weeks.

  1. Requests through the affected funnel 12
  2. Expected opportunities, healthy 4.8
  3. Expected opportunities, degraded 3.6
  4. Difference 1.2
$33,600 modeled pipeline impact
$6,720 modeled expected revenue impact

One scenario, from your inputs. Not claimed lost revenue, and not a prediction of how often this happens.

Failures like this are real. In our Study, 14 of 1,000 public buyer Paths led to a dead, invalid, or unpublished destination. See the observed failures →

Annual coverage in context

Put annual coverage in context.

Compared with the annual funnel above, not with one modeled scenario.

Based on Path count

Coverage

$15,000 / year

  • 0.43% of modeled expected won revenue
  • About half your entered ACV.

Matched on 4 Paths.

Final scope also depends on scenarios and proof depth.

Annual coverage keeps these Paths under recurring external proof, with history, change detection, and fix verification.

A scale comparison, not a return.

Compare coverage

The longer a problem stays hidden, the more pipeline passes through it.

A drop in one region or on one device barely moves a weekly total, so it can run for weeks.

Catch it sooner

Recurring verification finds the break closer to when it starts.

See where it broke

Which region, device, buyer profile, form, or follow-up layer.

Keep the evidence

What an outside buyer reached, and what arrived after submit.

Verify the fix

Rerun the same Path and context to prove recovery.

Dashboards, manual checks, in-house scripts: compare the alternatives →

No hidden coefficients.

Multiplication only. Nothing weighted behind the scenes.

Annual funnel

annual requests = requests per week × 52

annual opportunities = annual requests × healthy conversion

annual pipeline = annual opportunities × average deal size

expected won revenue = annual pipeline × win rate

Degradation scenario

affected requests = requests per week × share affected × weeks

opportunity difference = affected requests × (healthy conversion − degraded conversion)

modeled pipeline impact = opportunity difference × average deal size

modeled expected revenue impact = modeled pipeline impact × win rate

Annual coverage context

share of expected won revenue = annual plan price ÷ expected won revenue

average deals = annual plan price ÷ average deal size

Paths covered appears in no formula. It only picks the closest standard plan. 1 to 2 Paths is Critical Paths, 3 to 6 is Coverage, 7 or more is Custom Coverage.

Where the defaults come from

The presets are editable examples, not research findings. Weekly volume and detection time are not credibly benchmarked anywhere, so replace them with your own.

Context, not coefficients: HBR on lead-response delay and our Study of 1,000 public buyer Paths. Neither sets a number in this model.

Modeled from your inputs. This page does not claim lost revenue, saved revenue, recovered pipeline, or a return on BookedDemo. It does not estimate how often a Path fails per year.

Now prove it on your real Paths.

A Proof Sweep shows what actually happens before you decide on annual coverage.

Prefer to talk first? Discuss your Paths. The fit and scoping conversation is free.