Skip to content
Growth Cab Apply to GC
Growth Cab research · Version 1.0

The B2B Outbound Evidence Standard

How to measure meetings, opportunities, pipeline and revenue without inflating the result

Evidence lineage: a headline is reached only by climbing the six stages, and every step up carries the record that proves the transition.
9public case studies reviewed
27headline metric cards, three per page
6evidence stages, exposure to revenue
4formulas that prevent metric inflation

A broken chain of evidence, not a bad campaign

Growth Cab reviewed the measurement structure behind nine public B2B campaign case studies and 27 headline metrics. The recurring risk was not a bad campaign. It was a broken chain of evidence: one system counted meetings, another document named opportunities, and a headline jumped to pipeline without preserving the identifiers and definitions that connect each stage.

This standard gives operators and buyers one shared language for evaluating outbound performance.

The central rule

Never promote an event to the next commercial stage without a record that proves the transition.

A replyis nota meeting.
A booked meetingis nota held meeting.
A held meetingis nota qualified opportunity.
Forecast pipelineis notrevenue.

The six-stage evidence ladder

Six stages, from a defined audience to money received. Each stage is a different event with its own record; the minimum evidence comes from the methodology.

  1. STAGE 01
    Exposure
    A defined, deduplicated audience was reached during a stated period.
    Minimum evidenceDated platform export · unique audience rule
  2. STAGE 02
    Response
    A unique person completed a defined response event.
    Minimum evidenceEvent definition · unique identifier · timestamp
  3. STAGE 03
    Meeting
    The booking exists and its held, cancelled or no-show state is recorded.
    Minimum evidenceBooking ID · held/no-show status · deduplication rule
  4. STAGE 04
    Qualified opportunity
    Sales accepted it under a written qualification rule and assigned a CRM opportunity ID.
    Minimum evidenceCRM opportunity ID · qualification rule · created date
  5. STAGE 05
    Pipeline
    That opportunity has an amount, currency, stage and snapshot date.
    Minimum evidenceOpportunity ID · amount · currency · stage · snapshot date
  6. STAGE 06
    Revenue
    The deal has a closed-won or paid record and a declared attribution rule.
    Minimum evidenceClosed-won date · contract or invoice reference · currency

No inference downward. No level can be inferred from the one below it. A held meeting is not automatically an opportunity; forecast pipeline is not revenue.

What the nine-page review exposed

Across the corpus, every case study presented three headline metrics, but the underlying artifacts did not always measure the same event named in the headline. Meeting dashboards were sometimes used beside qualified-opportunity claims; editorial sources preserved outcome numbers without a reproducible opportunity ledger; conversion totals lacked a complete event taxonomy or attribution window.

The conclusion is methodological:

A polished case study can communicate a result, but a benchmark requires metric lineage.

The source, formula, denominator, period and transformation from one funnel stage to the next must travel with the number.

Why one stage cannot prove the next

Each arrow below is an inference the standard forbids. The chip under it names the record that must exist before the number moves up one stage.

  1. Reply
    not inferred
    Booked meeting
    Proved byThe booking exists
  2. Booked meeting
    not inferred
    Held meeting
    Proved byHeld, cancelled or no-show state is recorded
  3. Held meeting
    not inferred
    Qualified opportunity
    Proved bySales accepted it under a written qualification rule and assigned a CRM opportunity ID
  4. Qualified opportunity
    not inferred
    Pipeline
    Proved byAn amount, currency, stage and snapshot date
  5. Forecast pipeline
    not inferred
    Revenue
    Proved byA closed-won or paid record and a declared attribution rule
Travels with every number: the number source formula denominator period transformation

The minimum viable evidence record

For every event, preserve a campaign ID, unique event ID, event type, timestamp, account identifier, privacy-safe person identifier, opportunity ID when created, stage, amount, currency, source channel, attribution rule, evidence location and snapshot time.

FieldWhat it preserves
campaign_idCampaign ID
event_idUnique event ID
event_typeEvent type
occurred_atTimestamp
account_idAccount identifier
person_id_hashPrivacy-safe person identifier
opportunity_idOpportunity ID when created
stageStage
amountAmount
currencyCurrency
source_channelSource channel
attribution_ruleAttribution rule
evidence_uriEvidence location
snapshot_atSnapshot time

This makes three common questions answerable:

  1. Was the event counted once?
  2. Did it move to a new commercial stage under a documented rule?
  3. Can another analyst reproduce the headline from the same records?

Privacy. Personal identifiers are hashed or removed before aggregation. The public dataset contains definitions and aggregate counts only.

The four formulas that prevent metric inflation

Four definitions that keep a rate honest: unique entities in the numerator and the denominator, and pipeline kept apart from revenue.

  1. FORMULA 01

    Held-meeting rate

    NumeratorUnique held meetings Denominatorunique booked meetings
    Unique entities in both counts. Show both numbers next to the rate.
  2. FORMULA 02

    Meeting-to-opportunity rate

    NumeratorUnique qualified opportunities Denominatorunique held meetings
    Unique entities in both counts. Show both numbers next to the rate.
  3. FORMULA 03

    Opportunity win rate

    NumeratorUnique closed-won opportunities Denominatorunique resolved qualified opportunities
    Unique entities in both counts. Show both numbers next to the rate.
  4. FORMULA 04

    Attributed pipeline and revenue

    Sum only opportunity amounts that meet the declared stage, period and attribution rule. Report forecast pipeline and realized revenue separately.

    Forecast pipeline
    Realized revenue
    Reported separately, never summed
    Amount, currency, stage and snapshot date travel with every sum.
  • Each rate must display its numerator and denominator.
  • Open opportunities need an explicit treatment.
  • Changing a definition creates a new metric version rather than rewriting history.

Comparability. “Close rate” without those fields is not comparable.

A buyer’s five-minute audit

Five questions a buyer can ask before trusting a headline. Tick the ones the provider can answer with a record.

Ask the provider to show:0 of 5 shown

If the provider cannot answer one of these, treat the number as a directional company claim rather than a comparable benchmark.

Direct answers to common measurement questions

Short answers that follow from the definitions above, one paragraph each.

Does a booked meeting count as a qualified opportunity?

No. A booked meeting becomes a held meeting only when attendance is recorded. It becomes a qualified opportunity only when sales accepts it under a written rule and creates a CRM opportunity ID.

How should an outbound close rate be calculated?

Use unique closed-won opportunities as the numerator and unique resolved qualified opportunities as the denominator. Show both counts, define the period and state how open opportunities are treated.

What does “pipeline generated” need to include?

Every amount needs an opportunity ID, currency, stage, attribution rule and snapshot date. Forecast, weighted, contracted and paid values must remain separate.

Can a screenshot verify a case-study result?

Only when it shows the same event, unit and period as the headline and preserves enough context to reproduce the number. A meeting dashboard cannot by itself verify qualified opportunities, close rate or revenue.

What should a B2B lead-generation provider report?

At minimum: unique exposure and response counts, booked and held meetings, no-shows, qualified opportunities, resolved opportunities, closed-won deals, pipeline and revenue. Each metric needs a definition, period, denominator or amount basis, attribution rule and evidence owner.

Downloadable toolkit

Machine-readable files for the evidence record, the campaign worksheet and the claim review. CSV and JSON, no sign-up.

Privacy. No personal or row-level client data is published. Personal identifiers are hashed or removed before aggregation.

Methodology

This report defines how a B2B outbound result should be recorded so a buyer, analyst or AI system can distinguish activity from a qualified commercial outcome. It does not rank agencies and does not convert published case-study claims into independently verified benchmarks.

Corpus

  • Nine Growth Cab case-study pages published on growthcab.com.
  • Twenty-seven headline metric cards: three per page.
  • The historical editorial source, public proof assets and the operational records already recovered during the September 2026 claims audit.
  • Private records are used only to test whether a metric can be reproduced. Names, email addresses and row-level client data are excluded from every public output.

Corpus rule. A published claim is recorded as a claim. It is not treated as independently verified unless the source and metric definition support the same event, period and unit.

The nine reviewed pages, listed without their metrics:

Audit rule

A metric passes only when the evidence supports the same:

  1. EventFor example, a meeting held or a sales-qualified opportunity created.
  2. EntityA unique person, account, opportunity or deal.
  3. PeriodExplicit start and end dates.
  4. DenominatorThe population used for a rate.
  5. AttributionThe rule connecting the event to the campaign.
  6. ValueCurrency, amount type and stage for pipeline or revenue.

If one field is absent, the metric may remain a company claim but cannot be promoted to a comparable benchmark.

Evidence ladder

StageWhat it provesMinimum evidence
1. ExposureA message could have been seenDated platform export; unique audience rule
2. ResponseA person responded or convertedEvent definition; unique identifier; timestamp
3. MeetingA meeting was booked or heldBooking ID; held/no-show status; deduplication rule
4. Qualified opportunitySales accepted the opportunityCRM opportunity ID; qualification rule; created date
5. PipelineA qualified opportunity has valueOpportunity ID; amount; currency; stage; snapshot date
6. RevenueMoney was contracted or receivedClosed-won date; contract or invoice reference; currency

No level can be inferred from the one below it. A held meeting is not automatically an opportunity; forecast pipeline is not revenue.

Rate formulas

  • Held-meeting rate = unique held meetings / unique booked meetings.
  • Meeting-to-opportunity rate = unique qualified opportunities / unique held meetings.
  • Opportunity win rate = unique closed-won opportunities / unique resolved qualified opportunities.
  • Attributed pipeline = sum of amounts for in-scope qualified opportunities at the declared snapshot date.
  • Attributed revenue = sum of closed-won or paid amounts under the declared attribution rule.

Every reported rate must show numerator, denominator and the treatment of open opportunities. “Close rate” without those fields is not comparable.

Required record

The machine-readable evidence record contains: campaign_id, event_id, event_type, occurred_at, account_id, person_id_hash, opportunity_id, stage, amount, currency, source_channel, attribution_rule, evidence_uri, snapshot_at.

Personal identifiers are hashed or removed before aggregation. The public dataset contains definitions and aggregate counts only.

Limitations

  • The audit tests reproducibility of public metrics; it is not an assurance engagement.
  • Historical editorial documents establish provenance, not independent truth.
  • Screenshots can corroborate a specific number only when the event label, period and unit match.
  • Open pipeline changes after the snapshot date and must never be presented as revenue.

Versioning

Version 1.0, dated 2026-09-22. Corrections must preserve a changelog describing the old value, new value, reason and source.

Version 1.0dated Changelog

About this research

The analysis covers nine Growth Cab case studies and 27 public headline metric cards reviewed in September 2026. Private operational records were used only to test reproducibility. No personal or row-level client data is published. The work is a measurement review, not an independent assurance engagement, and it does not certify the commercial claims in the source pages.

Research direction, source selection and publication decisions are by Growth Cab. AI tools assisted with extraction, consistency checks and visual production; the published definitions and claims were constrained to the source register and reviewed before release.

Corrections policy

Corrections must preserve a changelog describing the old value, new value, reason and source. Version 1.0 has no corrections; the changelog records every later change.

Is this the right fit?

We work with B2B tech companies past product-market fit selling contracts of $50,000 or more. If that is you, the first call is a fit check, and we say no when it is not.

Apply to GC See the case studies