Buyer Path Research

What makes a B2B Book a demo Path fragile?

We walked 1,000 public high-intent B2B buyer Paths from the outside. How they are built, how much sits behind the visible CTA, where they fail, and how fast a correct definition goes stale.

Public observation only. Nothing was submitted, booked, or created on any site.

1,000 frozen buyer Paths, 14 dead destinations A field of 1,000 small squares, one per measured buyer Path, with fourteen highlighted where the Path led to a dead, invalid or unpublished destination.

14 of the 1,000 Paths led to a dead, invalid, or unpublished booking or intake destination.

One square per measured Path. See the failure evidence.

What we found

Four things that make a buyer Path fragile.

  1. 44.1% Qualification runs deeper than the CTA shows 569 of 1,000 Paths reached a form. 251 of those 569 grew after the buyer started typing. Form complexity
  2. 22.8% A Path is a system, not a page 190 of 832 observed destinations sat on a host outside the company's own domain. 16.1% opened a popup before the buyer could type. Path topology
  3. 14 of 1,000 Some Paths led nowhere 14 frozen Paths led to a dead, invalid, or unpublished destination. Not an optimization suggestion: the destination itself was unavailable. Failure evidence
  4. 12 of 1,000 A correct Path definition goes stale 12 frozen Paths no longer matched their definition three days later. Whatever you verified has a shelf life. Change evidence

A generalizing execution system produced this dataset, not a hand-built corpus: 364 of 451 unseen Paths were credibly evaluated with no site-specific setup. Execution evidence.

Finding one

The form you first see is often not the form you complete.

569 of 1,000 Paths reached a form. In the sales-led comparison set, 179 of 218 did, and those forms ran longer.

Observed form controls, by set

Broad sample n = 569 forms reached · Comparison set n = 179 forms reached

Distribution of observed form controls in the broad B2B software sample (569 forms) and the comparison set (179 forms)
Controls Distribution Broad sample Comparison
1 to 5 controls 34.3%195 of 569 30.7%55 of 179
6 to 10 controls 33.9%193 of 569 29.1%52 of 179
11 to 14 controls 14.1%80 of 569 14.5%26 of 179
15 or more controls 17.8%101 of 569 25.7%46 of 179

Broad sample, n = 569 Comparison set, n = 179 Bars scaled to a 0 to 40% axis

Shape of the two form distributions
Form shape Broad samplen = 569 Comparisonn = 179
Median controls78
75th percentile1215
90th percentile1718
Revealed fields progressively44.1%251 of 56958.7%105 of 179

96 of 101

forms with 15 or more observed controls revealed fields progressively. That is 95.0%.

Controls are counted across reveal passes, so this is partly definitional. Safe reading: long forms were rarely visible all at once.

Implication

A visible CTA often fronts a deeper qualification interaction that only appears once execution begins. Static inspection understates it.

Not claimed

Nothing here says long forms convert worse or that progressive reveal is a defect. The Study measured structure, not outcomes.

Finding two

A buyer Path is a system, not a page.

High-intent Paths routinely cross page, popup, embed, and vendor boundaries before a buyer can say anything.

Where all 1,000 Paths in the broad sample ended up

The furthest buyer-visible intake surface reached.

  • First-party form 524
  • Vendor scheduler 272
  • Vendor-hosted form 41
  • First-party scheduler 5
  • No intake reached 158

The five most common shapes, over the 842 Paths that reached an intake surface

  1. Entry pageFirst-party formProgressive reveal
    236 of 842 · 28.0%

    The form grows while the buyer fills it in.

  2. Entry pageFirst-party form
    224 of 842 · 26.6%

    The only shape a single page check covers.

  3. Entry pageEmbedded frameVendor scheduler
    132 of 842 · 15.7%

    Renders inside the page, served cross-origin by a booking vendor.

  4. Entry pagePopup windowVendor scheduler
    107 of 842 · 12.7%

    The buyer leaves the tab. Nothing on the original page records what happens next.

  5. Entry pageEmbedded frameVendor form
    73 of 842 · 8.7%

    The intake form belongs to a third party, inside the company page.

The remaining 70 of 842 split across hosted vendor booking pages and popups to a form. Shapes are mutually exclusive and cover all 842.

How third-party dependency is defined here

A Path counts as third-party dependent if any one of four things held. The observed destination was on a host outside the company's own domain. The intake form itself was vendor-hosted. The scheduler surface was a cross-origin embed. Or the scheduler was a hosted vendor booking page. A Path counts once even if several applied.

Of the 190 destinations that sat outside the company's own domain, 184 were on a recognizable scheduling or form vendor and 6 were on other non-brand hosts.

The denominator is the 842 Paths that reached a buyer-visible intake surface, not all 1,000. Paths that never reached an intake surface cannot be classified this way.

Implication

Every handoff adds a state a page check cannot verify. The Path is only correct if all of them are.

Not claimed

Nothing here says third-party tools are bad or reduce conversion. The finding is dependency, not quality.

Finding three

Some Paths led nowhere at all.

1,000 frozen buyer Paths, 14 dead destinations A field of 1,000 small squares, one per measured Path. Fourteen are highlighted: six that the frozen Study runner claimed automatically, and eight confirmed during Study adjudication.

Every square is one frozen buyer Path. Squares are placed in sample order.

  • 6 claimed by the frozen Study runner
  • 8 confirmed during Study adjudication

14of 1,000

At the observation point, 14 of 1,000 frozen buyer Paths led to a dead, invalid, or unpublished booking or intake destination.

The buyer followed the company's own CTA and arrived at a vendor error page, an unpublished calendar, or a missing route. Rare, and invisible from inside: nothing records a buyer who never reached a form.

These were not optimization suggestions. The destination itself was unavailable to the outside buyer.

The runner claimed 6 of the 14 on its own. The other 8 were confirmed from stored evidence during adjudication. A market observation, not a detection claim.

Broad sample, adjudicated
View failure evidence

What qualified: the CTA destination rendered a vendor error state, an unpublished or missing booking page, or a not-found document. Nothing bookable, and no intake form. Company names are withheld.

The 14 dead destinations, by surface, buyer-visible evidence, and how each was established
Destination surface What the buyer saw How it was established
Calendly, hosted booking page “This Calendly URL is not valid.” Claimed by the runner
Calendly, hosted booking page via popup “This Calendly URL is not valid.” Claimed by the runner
Calendly, hosted booking page via popup Invalid-URL error page, no calendar rendered Claimed by the runner
Calendly, hosted booking page “URL is invalid” Claimed by the runner
Calendly, hosted booking page “URL is not valid” Claimed by the runner
Calendly, hosted booking page via popup “URL is invalid” Claimed by the runner
Calendly, embedded frame on a live page “This Calendly URL is not valid.” inside the embed Confirmed in adjudication
Google Calendar appointment schedule “Appointment not found” Confirmed in adjudication
Google Calendar appointment schedule via popup “Appointment not found” Confirmed in adjudication
Cal.com team page via popup “No links set up”, no booking widget Confirmed in adjudication
Cal.com team page Unpublished-team status message, no scheduler Confirmed in adjudication
HubSpot Meetings on a brand-hosted domain Not-found page, no scheduler, no form Confirmed in adjudication
Vendor form destination via popup 404 not-found page Confirmed in adjudication
First-party booking route, redirected 404 error page, no form or scheduler Confirmed in adjudication
Evidence boundary

One measurement pass. It says what an outside buyer would have hit at that moment, not how long the destination had been dead.

Not claimed

No lead loss, revenue loss, routing or CRM failure. A buyer-visible dead destination at one point in time, nothing beyond that.

Finding four

Paths do not stay frozen.

We recorded each definition at screening, then walked it. Two separately aged sets, never pooled.

Broad sample

Frozen about 3 days before measurement

12 of 1,000 Paths, or 1.2%, no longer matched the definition we had frozen.

  • CTA no longer present under its frozen wording8
  • Destination replaced by a different surface2
  • CTA renamed1
  • CTA present, no observable response1
Comparison set

Frozen roughly two weeks to five months earlier

8 of 163 older Path definitions, or 4.9%, no longer matched.

  • CTA no longer present under its frozen wording6
  • Acquisition or rebrand redirect to another company1
  • Route gone, domain no longer serving the site1

Change classes were coded from the stored adjudication notes. The two tracks are never combined.

Implication

A correct Path definition is dated evidence. Its shelf life is shorter than most teams assume.

History is the product, not the reassurance: what changed, when the Path last worked, and whether the fix restored it.

Limitation

This is not an annual mutation rate. These are cross-sectional observations of differently aged definitions. A real rate needs repeated observation of the same Paths.

Execution

Most unfamiliar Paths needed no site-specific setup.

~4 in 5

364 of 451 · 80.7%

Paths the frozen runner had never executed before. Credibly evaluated from the entry page and the CTA alone, with no per-site scripting.

A fresh holdout of 50 unseen companies on the current runner agrees: 40 of 50 evaluable, 46 of 50 trustworthy with no false claim.

What “evaluable” means here

Evaluability is the share of Paths that produced a credible evaluation. It is not accuracy, not a pass rate, and not a coverage ceiling for customer Paths. It does not mean one Path in five is unsupported.

The cold Study contract

  • Entry page supplied.
  • CTA to follow supplied.
  • No site-specific setup.
  • Nothing submitted.

Your Path contract

  • Intended Path concierge-confirmed.
  • Approved buyer context agreed.
  • Expected follow-through declared.
  • The retained definition is the baseline for every later run.

Give BookedDemo any public high-intent B2B sales Path. We verify it from the outside and show how far the buyer got, and where proof stops.

In scope: demo request, contact sales, request a quote, and trial entry.

Supporting a Path is not the same as proving every downstream outcome.

Some evidence cannot be captured from outside. The run returns the deepest honest result and names the boundary.

  • CAPTCHA or bot challenge
  • Inaccessible third-party surface
  • SMS, phone, or private-channel continuation
  • Internal CRM or routing state
  • Action requiring your approval

None of these is a site BookedDemo cannot handle.

Path Market Context · research preview

Where does your Path sit?

One observation gets more useful placed against patterns seen across other public buyer Paths.

Where one Path sits in the observed distribution

All 569 forms reached in the broad sample. The marker is a worked example, not a customer.

Distribution of observed form controls across the 569 forms reached in the broad sample A column chart from 1 to 25 or more controls. The median is 7, the 75th percentile is 12, and the 90th percentile is 17. An illustrative Path at 18 controls sits above the 90th percentile. 1 controls: 18 of 569 forms 2 controls: 22 of 569 forms 3 controls: 36 of 569 forms 4 controls: 62 of 569 forms 5 controls: 57 of 569 forms 6 controls: 56 of 569 forms 7 controls: 44 of 569 forms 8 controls: 39 of 569 forms 9 controls: 24 of 569 forms 10 controls: 30 of 569 forms 11 controls: 15 of 569 forms 12 controls: 33 of 569 forms 13 controls: 17 of 569 forms 14 controls: 15 of 569 forms 15 controls: 10 of 569 forms 16 controls: 25 of 569 forms 17 controls: 10 of 569 forms 18 controls: 10 of 569 forms 19 controls: 9 of 569 forms 20 controls: 8 of 569 forms 21 controls: 2 of 569 forms 22 controls: 10 of 569 forms 23 controls: 4 of 569 forms 24 controls: 3 of 569 forms 25 or more controls: 10 of 569 forms
p50 · 7 p75 · 12 p90 · 17
18 observed controls
  • Median, all observed forms7 controls
  • 75th percentile12 controls
  • 90th percentile17 controls
  • Comparison set, contact-sales median12 controls · n = 47
  • Illustrative Path18 controls

Context produces a better question, not a verdict.

An 18-control contact-sales form sits above the 90th percentile: 523 of the 569 observed forms asked for 18 or fewer.

Unusual does not mean wrong. It tells you where to investigate.

Every Path BookedDemo executes adds to that frame. A one-off audit cannot provide it.

  • Is the extra qualification deliberate?
  • Does it apply in every region and device?
  • Was it always this long?

A research preview, not a product feature. No grade, no score, no best-practice claim. BookedDemo does not ship interactive benchmarking today.

Why this matters

Three mechanisms decide whether a buyer reaches you.

We use published work to explain why the structure above matters, never to estimate anything about our own sample.

  1. Interaction effort Every added field and validation error is another place a high-intent buyer stops. Baymard, Checkout Flow Average Form Fields Baymard, Cart Abandonment Rate Statistics
  2. Errors and latency Slowing a page moves business metrics. A destination that fails outright removes the interaction entirely. Kohavi, Tang & Xu, “Speed Matters”
  3. Follow-up delay Response time to an inbound web lead is strongly related to the odds of qualifying it. After-submit is part of the Path. HBR, The Short Life of Online Sales Leads

These are e-commerce and general web studies. The mechanisms transfer. The numbers do not.

Method

How we studied the Paths.

One frozen runner build walked all 1,218 Paths. Raw evidence was checksummed before interpretation, every Path was adjudicated from that frozen record, and the two sets are never pooled.

How we measured it: samples, execution, and adjudication

What we observed on every Path

  • The route from the public entry surface to the buyer intake surface.
  • Path classes: demo request, contact sales, request a quote, sales-assisted trial.
  • Form structure, including fields that appear only once the buyer starts typing.
  • Scheduler surfaces, popups, embeds, and handoffs to third-party vendors.
  • Whether the destination was reachable and usable.

Why the measurement holds up

  • One runner build, frozen for all 1,218 Paths.
  • Raw evidence checksummed before anyone interpreted it.
  • Every Path adjudicated from that frozen evidence, including those that produced no result.
  • Paths the evidence could not settle were re-checked by hand.
  • The two sets are never pooled into one prevalence number.
The two sets of Paths and how they differ
Property Broad sample Comparison set
Companies 1,000 218
Where they came from A deterministic walk over a broad B2B software frame, then screened for a live public high-intent Path. Carried forward from earlier BookedDemo research and product-validation work, then measured the same way.
Reached a buyer intake form 569 of 1,000 · 56.9% 179 of 218 · 82.1%
Showed a scheduler surface 277 of 1,000 · 27.7% 4 of 218 · 1.8%
Read it as Skewed toward young, YC-adjacent companies. It describes the B2B software frame we walked. It is not a census of B2B SaaS and not a representative estimate of the whole market. Selected rather than sampled, so it supports comparison only. It is not a representative sample of any segment, and prevalence is never quoted from it.

All 1,218 Paths were walked by the same frozen runner build in one observation regime. Nothing was submitted, booked, or created: zero submit clicks were recorded.

Raw evidence was checksummed before interpretation. Every row was adjudicated into one of three buckets: a credible evaluation, an honest boundary or inconclusive result, or a gap. Rows the stored trail could not decide were re-checked by a human operator.

Evaluable means the run produced a credible evaluation. Trustworthy means it produced no false claim, including runs that correctly stopped at a boundary. Neither is accuracy.

Observation window. Every number describes one measurement pass. It is dated evidence about a public surface, not a permanent property of a company. Full boundaries.

Boundaries

Where the evidence stops.

What we could not observe, we do not claim.

CAPTCHA is a proof boundary, not a break
37 of 1,000 Paths hit a CAPTCHA or bot-protection boundary. Recorded as proof boundaries, never as Broken. Searles et al., An Empirical Study and Evaluation of Modern CAPTCHAs, USENIX Security 2023
No submit, so no response claim
Nothing was submitted. The Study says nothing about how often a response arrives after a form is sent.
No internal access, so no internal truth
No CRM, routing, ownership, or attribution. Only what an outside buyer could see.
One context, so no context prevalence
One region, one device, one buyer profile. The Study cannot say how often a Path behaves differently by context.
A frame, not a census
A deterministic walk over a B2B software frame, skewed toward young companies. Not a representative estimate of every B2B SaaS company.
No conversion or revenue effect
We measured structure and reachability, not conversion, pipeline, or revenue.
One Path per company
One frozen high-intent Path per company. Companies run more, and we did not measure the rest.

What this means

The hard part is that the Path keeps moving.

A buyer Path is a changing chain of externally observable states across pages, popups, embeds, and vendors. Any link can go quiet without anyone inside noticing.

A one-time audit

What was true once, on one day, in one context.

Retained verification

  • What changed since the last trustworthy run.
  • When the Path last worked.
  • Which Path and which context is affected.
  • What an outside buyer actually reached.
  • Whether a fix restored the expected behavior.

Not reassurance that everything is fine. A maintained proof record for the Paths that carry your highest-intent buyers.

See the same method applied to your Paths.

A Proof Sweep does the same work on up to three of your own high-intent Paths, with kept evidence and a shareable Run Report.

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