The B2B Outbound Evidence Standard
How to measure meetings, opportunities, pipeline and revenue without inflating the result
- 9public case studies reviewed
- 27headline metric cards, three per page
- 6evidence stages, exposure to revenue
- 4formulas that prevent metric inflation
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 recurring risk was a broken chain of evidence
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 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.
Exposure
A defined, deduplicated audience was reached during a stated period.
- Dated platform export
- Unique audience rule
Response
A unique person completed a defined response event.
- Event definition
- Unique identifier
- Timestamp
Meeting
The booking exists and its held, cancelled or no-show state is recorded.
- Booking ID
- Held/no-show status
- Deduplication rule
Qualified opportunity
Sales accepted it under a written qualification rule and assigned a CRM opportunity ID.
- CRM opportunity ID
- Qualification rule
- Created date
Pipeline
That opportunity has an amount, currency, stage and snapshot date.
- Opportunity ID
- Amount
- Currency
- Stage
- Snapshot date
Revenue
The deal has a closed-won or paid record and a declared attribution rule.
- Closed-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.
Digital360 case study
Elevate case study
Jobtome case study
TendersTool case study
FlashLabs case study
Maildoso case study
Taplio case study
Prospeo case study
La Growth Machine case study
9public case studies reviewed27headline metric cards, three per page
-
Mismatch 01
Meeting dashboards were sometimes used beside qualified-opportunity claims.
-
Mismatch 02
Editorial sources preserved outcome numbers without a reproducible opportunity ledger.
-
Mismatch 03
Conversion totals lacked a complete event taxonomy or attribution window.
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.
Travels with every number:
- Reply Not inferred Booked meeting Proved byThe booking exists
- Booked meeting Not inferred Held meeting Proved byHeld, cancelled or no-show state is recorded
- Held meeting Not inferred Qualified opportunity Proved bySales accepted it under a written qualification rule and assigned a CRM opportunity ID
- Qualified opportunity Not inferred Pipeline Proved byAn amount, currency, stage and snapshot date
- Forecast pipeline Not inferred Revenue Proved byA closed-won or paid record and a declared attribution rule
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.
This makes three common questions answerable:
- Was the event counted once?
- Did it move to a new commercial stage under a documented rule?
- 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.
"campaign_id"- Campaign ID
"event_id"- Unique event ID
"event_type"- Event type
"occurred_at"- Timestamp
"account_id"- Account identifier
"person_id_hash"- Privacy-safe person identifier
"opportunity_id"- Opportunity ID when created
"stage"- Stage
"amount"- Amount
"currency"- Currency
"source_channel"- Source channel
"attribution_rule"- Attribution rule
"evidence_uri"- Evidence location
"snapshot_at"- Snapshot time
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.
-
Formula 01
Held-meeting rate
Unique entities in both counts. Show both numbers next to the rate.
-
Formula 02
Meeting-to-opportunity rate
Unique entities in both counts. Show both numbers next to the rate.
-
Formula 03
Opportunity win rate
Unique entities in both counts. Show both numbers next to the rate.
-
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.
Amount, currency, stage and snapshot date travel with every sum.
Forecast pipelineRealized revenueAlways reported separately
- 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:
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?
- How should an outbound close rate be calculated?
- What does “pipeline generated” need to include?
- Can a screenshot verify a case-study result?
- What should a B2B lead-generation provider report?
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.
The B2B Outbound Evidence Standard, version 1.0How 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.
The B2B Outbound Evidence Standard, version 1.0What 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.
The B2B Outbound Evidence Standard, version 1.0Can 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.
The B2B Outbound Evidence Standard, version 1.0What 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.
The B2B Outbound Evidence Standard, version 1.0Downloadable toolkit
Machine-readable files for the evidence record, the campaign worksheet and the claim review. CSV and JSON, no sign-up.
- Download Evidence dictionaryEvidence dictionary with the required fields and allowed event types.Opens in any spreadsheet · 2 KB
- Download Campaign measurement worksheetCampaign measurement worksheet for numerator, denominator and attribution rules.Opens in any spreadsheet · 1 KB
- Download Case-study claim checklistCase-study claim checklist for editorial and proof review.Opens in any spreadsheet · 1 KB
- Download Evidence record JSON schemaMachine-readable JSON schema for evidence records.Machine-readable · 2 KB
- Download The standard as JSONStages, minimum evidence, formulas and non-inference rules in one machine-readable file.Machine-readable · 3 KB
- Download ChangelogVersion history of the standard, starting with version 1.0 on 22 September 2026.Plain text · 1 KB
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.
Audit rule
A metric passes only when the evidence supports the same:
If one field is absent, the metric may remain a company claim but cannot be promoted to a comparable benchmark.
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:
Evidence ladder
| Stage | What it proves | Minimum evidence |
|---|---|---|
| 1Exposure | A message could have been seen | Dated platform export; unique audience rule |
| 2Response | A person responded or converted | Event definition; unique identifier; timestamp |
| 3Meeting | A meeting was booked or held | Booking ID; held/no-show status; deduplication rule |
| 4Qualified opportunity | Sales accepted the opportunity | CRM opportunity ID; qualification rule; created date |
| 5Pipeline | A qualified opportunity has value | Opportunity ID; amount; currency; stage; snapshot date |
| 6Revenue | Money was contracted or received | Closed-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.
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.
