DEMAND GEN
BDR Pod: Signal-to-Meeting
Signal-driven BDR pod with a hard ≤2-hour signal-to-touch SLA.
Project Details
Outcome
40–60 meetings + 12–20 SQLs (first 90 days); ≤2-hour signal-to-touch.
Scope
Signal capture → enrichment → ICP score → contact append → 2-hour outreach SLA.
Stack
ZoomInfo WebSights • Enrichment • CRM • Outbound
Governance
Documented workflow • enforced SLA • weekly operating review
What I Shipped
- Outcome — 40–60 meetings + 12–20 SQLs targeted in 90 days under a hard ≤2-hour SLA.
- Constraint — no new headcount: repurposed existing telesales into a 2-person BDR pod.
- System — WebSights signal ingest → company match → ICP score → contact append before human touch.
- Governance — SLA with teeth: every signal timestamped; misses reviewed weekly and fixed at the process layer.
- Artifacts — process map, SLA doc, weekly review template.
Interview Line
No new headcount. I repurposed telesales into a signal-driven BDR pod with a hard 2-hour SLA—first 90 days targeted 40–60 meetings and 12–20 SQLs.
Longform Draft
Longform draft available (markdown).
Deep Dive
In a live walkthrough I can share redacted artifacts (process maps, KPI dictionaries, example reporting packs, and automation logs).
DEEP DIVE
HOVER TO REVEAL
Example artifacts: routing decision tree; KPI dictionary excerpt; QA checklist; a "what changed?" weekly narrative page.