This is not the right way to build a growth system. It is what to do when you need pipeline this month and do not have time to build one properly — with the explicit understanding that you will go back and do it properly afterwards.
We have run this enough times to know both that it works and where it hurts.
Week 1 — Mine what you already have
Do not buy a list. The fastest pipeline in any company is sitting in systems it already pays for.
- Closed-lost from 6–18 months ago. The single highest-yield segment in this playbook. Circumstances change, champions move, budgets reopen. "We spoke last year — has anything changed on X?" converts unreasonably well.
- Opportunities that went dark at proposal. Not lost, just stalled. Often one email from restarting.
- Champions who changed jobs. Someone who liked you at their last company is a warm intro at a new one, and this is trivially detectable from enrichment.
- Engaged but never contacted. Repeat site visitors, content downloads, webinar attendees nobody followed up.
Expect a few hundred accounts. Expect them to convert several times better than anything cold you could build in the same week.
Week 2 — One tight cold segment
Pick the narrowest segment where you have real proof — ideally a segment where you can name three customers and a result. Not "B2B SaaS". Something like "Series B fintechs who bought us after outgrowing an in-house process".
Narrow beats broad here for a reason that matters under time pressure: you can write genuinely specific copy once and have it be true for every account on the list. Broad segments force generic copy, which is what fails.
Two hundred to four hundred accounts is the right size. Resist making it bigger.
Narrow beats broad. You can write specific copy once and have it be true for everyone on the list.
Week 2 — Turn on retargeting the same day
Push both lists into ad audiences immediately. It costs very little at this volume and it means that by the time touch three lands, the sender is not a stranger. This is the highest-leverage hour in the whole sprint.
Week 3 — Multi-channel, compressed
Standard sequencing timelines are built for programmes that will run for a year. On a sprint, compress: touch one and a LinkedIn view on day one, touch two on day three, a call attempt on day five, touch three on day eight, breakup on day twelve.
This is more aggressive than we would run steady-state, and it has a cost in domain health. Which is why the next point is not optional.
The honest risks
Three, and you should decide about them consciously rather than discover them:
- Domain damage. Compressed cadence on freshly warmed mailboxes is how programmes get burned. Use dedicated domains, watch reply rate per domain daily, and throttle the moment it moves.
- You are spending the reactivation list. Closed-lost can be worked roughly once a year. Using it in a sprint means it is not available next quarter.
- Nothing accumulates. A sprint produces meetings, not a system. If you stop after the meetings, you will run the same sprint next quarter with a thinner list.
Week 4 — Convert, then build
Book everything, respond within minutes rather than hours, and be ruthless about routing. Then, in the same week, start the real build: audience as a query, continuous enrichment, permanent retargeting loop, instrumentation.
The sprint buys you the quarter. The system is what stops you needing another sprint.