Define the ICP before you touch a tool
A B2B workflow that skips the ideal-customer definition produces a big, unusable list. Write one sentence that names the industry, company size band, the buyer role, and the single public signal that proves fit - a hiring post, a service page, a tech badge, a recent funding note. Everything downstream inherits the quality of that sentence.
- Industry and sub-niche, not just "B2B".
- Company size band (e.g. 2-50 staff).
- The economic buyer's likely title.
- One visible, verifiable fit signal.
The five-stage pipeline that actually converts
A repeatable B2B pipeline moves each prospect through five checkpoints, and a lead only advances when it clears the one before it. Skipping a stage is what fills a CRM with contacts nobody can use. It also mirrors how buyers actually move: McKinsey finds B2B buyers now use an average of ten channels across a single purchase, so a one-touch, one-channel blast misses most of the journey.
- 1. Source - find companies matching the ICP from public data.
- 2. Verify - confirm a working public email or phone.
- 3. Qualify - open the source and confirm the fit signal is real.
- 4. Personalize - one true, specific reason for the message.
- 5. Track - log sends, replies, and objections to tune the next batch.
Batch small, learn, then scale
Run the first cycle at five to ten leads, not five hundred. A small batch tells you within a day whether the niche has enough public contact data and whether your angle lands. Scale only the exact niche-and-offer combination that produced replies - broad scaling before validation is the most expensive mistake in outbound.
Instrument the workflow so it compounds
The difference between a workflow and a one-off blast is memory. Record contactable rate, reply rate, and the top objection for every batch. When contactable rate drops, your niche or geography is too tight; when replies drop, the offer or opener is the problem. Fix one variable per cycle.
- Contactable rate = kept leads / candidates found.
- Reply rate = replies / messages sent.
- Watch the trend across batches, not a single run.