What happens after the signal fires.

Building a signal-based outbound engine from zero

Role

VP of Marketing & GTM (acting CMO)

Timeline

90-day pilot (2024)

Team size

Two BDRs repurposed from telesales, one manager, and sales ops support

Challenge

Zero proactive lead generation, a reactive inbound-only model, underutilized telesales capacity

The challenge

The company's growth had always been inbound: referrals, RFPs, and the brand recognition that comes with being an incumbent in a long-established category. The market was shifting underneath that.

• ·Competitors were building proactive outbound engines
• ·Website signals showed high-intent account activity with no structured follow-up
• ·Telesales reps were underutilized, spending time on low-value activities
• ·Sales team wanted more first meetings but had no systematic prospecting support

The CEO asked: "Can we build a lead generation capability without hiring externally?"

The stakes: miss the shift to proactive go-to-market and watch competitors capture the high-intent accounts already visiting our site.

The solution

Team building: repurpose before you hire

I identified two telesales reps with the right profile. Both were hungry, coachable, and tired of low-impact work. I proposed a 90-day pilot around them.

The first rep brought high energy and a competitive streak, and wanted to prove himself in sales. The second was detail-oriented, process-driven, and had the strongest phone presence on the floor.

I worked with their manager to carve out all of their time for the BDR pilot and secured sales ops support for the CRM configuration.

The operating model (what I built)

1. BDR operating model (complete 90-day plan)

The pod was a manager, the two BDRs, and sales ops support. The day ran on six fixed time blocks between morning and end of day:

• ·Signal review and prioritization
• ·Power hour: calls and emails
• ·Research and sequence building
• ·Lunch and admin
• ·Calls and follow-ups
• ·Planning and CRM hygiene

2. KPI framework (what gets measured)

3. Signal-to-meeting workflow

• ·Account-intent signals fed a daily signal report
• ·Tier-A accounts got the high-priority touch SLA
• ·Tier-B accounts (utilities, tolling) got a 24-hour touch SLA
• ·Tier-C accounts (all others) got a 48-hour touch SLA

4. Training and enablement (what I taught them)

Week 1: bootcamp

• ·Day 1: value props, ICP profiles, competitive landscape
• ·Day 2: signal-workflow training, CRM workflows, intent dashboard
• ·Day 3: call scripts, email templates, objection handling
• ·Day 4: live call listening, shadowing AEs
• ·Day 5: practice calls, sequence building, Q&A

Weeks 2 to 4: daily coaching

• ·Morning huddles (15 min): priorities, blockers, wins
• ·Live call listening (Tue/Thu): real-time feedback
• ·Email reviews (Wed): template customization guidance
• ·End-of-week debrief: metrics review, skill building

Ongoing

• ·Bi-weekly 1:1s with each BDR
• ·Monthly calibration sessions with sales leadership
• ·Quarterly playbook updates based on what's working

5. Outbound messaging kits (what they used)

Email templates

• ·The acquired SaaS platform into a collections cross-sell, kept short enough to read on a phone
• ·Healthcare revenue cycle denials automation, written around value
• ·Digital and AI collections for the enterprise, written around productivity

Call scripts

• ·A 30-second opener: hook, value prop, ask
• ·A brief voicemail built as a callback driver
• ·A five-touch sequence framework running over 10 business days

The framework (what they followed)

I documented everything in a book-length BDR playbook covering:

• ·ICP definitions by vertical
• ·Lead routing logic
• ·CRM field requirements (Intent Tier, Last Sequence Day)
• ·Discovery brief template for AE handoffs
• ·Compliance brief (call windows, DNC, opt-outs)

The outcome

Meeting generation

First meetings started landing on the calendar where there had been none, and both reps held the Tier-A response window through the pilot. SQLs came out of those meetings with conversion tracked directionally.

Team development

Both reps came through the program as lead generation specialists rather than telesales reps, both stayed, and both became the strongest performers in the pod. The playbook they worked from is what makes the next hire cheap.

Pipeline impact

The pod created real pipeline from BDR-sourced meetings and closed deals inside the pilot period, all of them cross-sells of the acquired SaaS platform. The point of the pilot was to prove the model before spending on headcount, and it did.

A standing weekly meeting rate per BDR from a standing start, built without external hires, using repurposed talent and systematic enablement.

Leadership angle: team building from scratch

This was team building from the ground up rather than management of an existing team.

Identifying potential

I hand-picked both reps on hunger for growth beyond doing the job, coachability, and the resilience to handle rejection without quitting.

Building the system

I gave them a system rather than an instruction to make calls. That meant daily schedules with time blocks, KPI dashboards with leading indicators, a training curriculum with skill progression, and quality assurance with live feedback.

Creating the culture

The pod was competitive and collaborative at the same time, and the reps traded wins and tactics openly. Scorecards were daily and visible, so there was nowhere to hide. The quality bar was the conversation, and dials were only the way to get one.

Attribution clarity

My work:

• ·Program design and operating model
• ·BDR selection and team structuring
• ·Training curriculum and coaching schedule
• ·Workflow documentation and playbooks
• ·Messaging templates and scripts
• ·CRM configuration specs
• ·KPI dashboards and reporting
• ·Compliance guardrails
• ·Implementation roadmap

The company's assets:

• ·Account-intent signal source
• ·The CRM
• ·The telesales reps who became the pod
• ·Proprietary collections and AI platform capabilities
• ·Compliance infrastructure
• ·Client references for social proof

What made this work

I proved the model with existing talent before asking for budget, which is a much easier conversation than asking for headcount on a forecast.

Enablement was structured, measured, and iterated rather than left to the reps to figure out.

Intent data meant the reps were calling accounts already researching the company, while the interest was still live.

The two-hour Tier-A window meant we reached prospects while they were still in research mode, when a cold call still reads as helpful.

Artifacts

• ·BDR operating model (90-day plan)
• ·Daily cadence schedule (six time blocks)
• ·KPI framework and dashboard specs
• ·ICP definitions by vertical
• ·Signal-to-meeting workflow
• ·ABM list strategy
• ·Email templates by vertical
• ·Call scripts (30-second opener, voicemail)
• ·Five-touch sequence framework
• ·Week-1 task list
• ·BDR playbook

Keywords BDR LeadGeneration TeamBuilding Outbound SignalBasedSelling Enablement