Published now
- AI Sales Lead Qualification & Routing
- Sales Pipeline Intelligence System
- B2B Outbound Capacity & Pipeline Calculator
- B2B Leads & Outbound Insights
D2 B2B Leads & Outbound Work
This page documents what D2 can currently prove publicly across B2B lead operations: implementation evidence for qualification and routing, a transparent outbound capacity model, and published operating methodology. It does not present an unmeasured campaign as a client success story.
Proof maturity
This distinction is intentional. The Work library should become more persuasive as evidence matures, not by relabeling methodology or prototypes as performance.
A source-backed B2B outbound client case with a defined period, denominator, deliverability state, replies, qualified meetings, pipeline progression and outcome boundary.
Published evidence assets
Revenue Operations · Implementation Evidence
A source-backed workflow architecture for capture, enrichment, CRM context, AI-assisted scoring, deterministic routing and measurement. It does not claim conversion lift or revenue impact.
Evidence
Source-backed workflow architecture
Status
Adjacent B2B implementation evidence — not a measured outbound client outcome
Revenue Operations · Pipeline Intelligence
A source-backed architecture for CRM normalization, historical context, pipeline risk, forecasting, corrective action and coaching signals.
Evidence
Source-backed architecture
Status
Selected intelligence system — not a measured pipeline-lift outcome
Outbound Capacity & Economics Model
A published decision-support model for secondary domains, mailbox capacity, reply/meeting assumptions, pipeline value and in-house versus managed-pilot cost comparison.
Evidence
Published calculator logic with explicit assumptions
Status
Decision-support model — not observed campaign performance
Methodology & Knowledge Evidence
Published technical guidance covering deliverability, secondary domains, signal-based prospecting, qualification, routing and outbound operating models.
Evidence
Published methodology, definitions and operating guidance
Status
Knowledge evidence — not a client outcome
Claim boundary
01
A lead-qualification workflow can prove architecture, controls and routing logic; it does not by itself prove better conversion or revenue.
02
A calculator can make assumptions and capacity math transparent; it is not observed campaign telemetry.
03
Published methodology can show operating discipline; it is not evidence that every mailbox, market or ICP will perform the same way.
04
Reply rate, meeting rate, pipeline and revenue should only be reported as outcomes when the underlying period, denominator and source records are available.
B2B Work FAQ
Not yet. The current public evidence covers implementation, models and methodology. D2 should publish a client outcome case only when the period, source records, denominators and claim boundary can be disclosed responsibly.
Because the implementation is directly relevant to B2B revenue operations, but its original evidence type remains Automation implementation evidence. Cross-linking does not change the proof type.
No. It is a scenario model. Inputs and assumptions help scope capacity and economics, but observed performance depends on deliverability, ICP quality, signals, messaging, market conditions and sales follow-up.
B2B evidence fit
D2 can scope the operating model against the evidence already published, define what needs to be instrumented, and establish the measurement boundary before an outbound pilot is treated as a performance case.
Discuss B2B outbound