13/13 Gate✓ IQ Certified10/10?

The Pipeline Generation Block — 60-Min Training

📖 2,728 words🗓️ Published Jul 19, 2026

Direct Answer

The Pipeline Generation Block is a 60-minute, manager-led session that installs a repeatable habit: every AE and SDR commits to two or three defended 90-minute prospecting blocks per week, pre-staged in the sequencer and measured by outputs — touches, connects, and meetings booked — not by hours logged or attendance.

Why scattered prospecting fails and the block fixes it

The core problem this session names out loud is not skill — it is fragmentation. Reps rarely lose pipeline because they cannot write a good cold email; they lose it because prospecting is the first activity crowded out by deal-cycle calls, internal syncs, Slack pings, and reactive calendar drift. When outbound happens in scattered ten-to-fifteen-minute fragments between meetings, the rep spends most of that time re-orienting — reopening the list, remembering who they were calling, re-reading the last touch — and almost none of it actually prospecting.

Context-switching is the hidden tax. Each interruption during a focused hour costs real refocus time, so a rep who checks email, answers two Slack threads, and glances at their phone inside a single prospecting hour can end up with effectively zero deep-focus minutes despite "spending an hour on outbound." The block attacks this directly by converting prospecting from a background task into a foreground appointment. Ninety uninterrupted minutes against a pre-loaded list produces more real output than three fragmented hours, because momentum compounds inside a single sitting: the fifth dial is easier than the first, the tenth email reuses the rhythm of the ninth, and the rep never pays the re-orientation tax twice.

The founding claim of the session — written on the whiteboard and left up for the full hour — is deliberately simple: pipeline is built in blocks, not in the moments between meetings. Everything that follows is mechanics in service of that one sentence. The session does not try to make reps better writers or sharper on objection handling; it assumes the craft is adequate and that the missing ingredient is protected, concentrated time. That framing matters because it changes what "trying harder" means. A rep who feels behind will instinctively squeeze prospecting into more gaps, which multiplies the switching tax instead of reducing it. The block reframes the fix as fewer, larger, defended sittings — the opposite of the intuitive response — and the manager's job is to keep insisting on that counterintuitive shape until the results validate it.

Designing the block: time, list size, and sequence discipline

A block is not a generic "prospecting hour." It is engineered around three variables, and the training walks every rep through designing their own using one shared brief. First, time of day. The block should start within the first four hours of the rep's workday, before deal-cycle calls dominate and before decision-maker inboxes fill up. Reply and connect rates are generally stronger in the morning window, and — just as important — the rep still has the willpower to defend the block before the day's chaos accumulates. A block scheduled for 4 p.m. is a block that gets sacrificed to whatever caught fire at 2 p.m.

Second, list size. AEs pre-stage 25–40 named accounts; SDRs pre-stage 40–60 because outbound is their primary motion. The number is tuned deliberately: too few accounts and the rep runs out of list mid-block and loses momentum; too many and they slide into research drift, over-investigating each account instead of touching it. The list is named accounts the rep chose, not a generic segment — the point is that the rep has already decided these are worth pursuing, so the block is pure execution, not selection.

Third, sequence discipline. Each account is pre-loaded into the team's sequencer — Outreach, Salesloft, or Apollo — with its cadence step already known, so the rep spends the block executing touches (a Step 1 cold call, a Step 4 LinkedIn touch, a Step 7 break-up) rather than deciding what to do next. The single most important coaching point: the brief gets filled out the day before, never at the start of the block. Reps who walk in cold and "figure out who to call" burn the first twenty-five minutes on research and never recover. Cap research at roughly three to four minutes per account, pulled from intent signals and notes on adjacent deals, and set a concrete output target — 35-plus multi-channel touches and one to two booked meetings per block. The bad pattern to call out by name is "I'll just open my sequencer and work through the queue." That is reactive queue-clearing: the cadence engine hands the rep whoever it surfaces next, not their highest-intent named accounts.

Defending the block: the rep's rules of engagement

State the drill plainly: a block that is not defended is a block that does not exist. Most reps fail here not from lack of discipline but because their manager, their AE-SDR counterpart, and their customer-facing calendar all assume their time is interruptible by default. The session gives every rep a concrete, mechanical defense protocol so willpower is not the load-bearing element.

The protocol has five moves. Flip scheduling availability off for the block hours so booking links return no open slots — a one-click toggle that removes most of the inbound interruption surface. Set a specific status message, not a vague "heads down," but "Prospecting block until 11:30, will respond at 11:35"; specificity pre-empts the follow-up "are you really busy?" ping. Accept no internal meetings during block hours, which works only if the manager pre-blocks the same hours on their own calendar so cross-functional invites bounce. Put the phone in another room or in focus mode, because a single glance restarts the refocus clock. And run one browser window with only the sequencer tab and a prospecting-research tab open — no email tab, no chat tab, no CRM dashboard.

Email and CRM hygiene get their own separate block later in the day; folding them into prospecting time is how the block quietly dies. Name the one acceptable exception so reps do not treat the rule as absolute and then resent it: a live inbound from a target account in the current-quarter pipeline is worth breaking the block for. Everything else waits. Close by naming the trade-off honestly — defending the block will feel rude in week one, but by week three the rest of the organization routes around it without being asked, and the rep stops having to justify it. The discomfort is front-loaded and temporary; the reputation for being unreachable during a known window becomes a form of respect once the results show up in the pipeline review.

The manager's defense script

The manager's behavior is the highest-leverage variable in the entire program, so the session rehearses it verbatim. Set the scenario: a rep is mid-block, a peer pings them for a "quick two minutes" on a deal, the rep ignores it, and the peer escalates to the manager — "is Jordan around? Can't reach them." This is the exact moment the block lives or dies, and the manager must handle it the same way every time so the team internalizes the pattern.

A workable script: *"Jordan is in their pipeline-generation block until 11:30. I protect those blocks for the team because they're how we hit our pipeline coverage. If it's a deal blocker, send me the detail and I'll unblock it myself or get Jordan on it at 11:35. If it can wait, drop it in the deal channel and Jordan will pick it up. Want me to ping you when Jordan's back?"* The structure matters: name the block, own the reason, offer a real alternative, close the loop.

Just as important is what the manager must never do. Do not apologize ("sorry, Jordan's tied up") — that frames the block as a soft preference rather than a commitment. Do not pull the rep out to handle the question yourself — the rep instantly learns the block is overridable. And do not forward the ping into the rep's DMs with "FYI when you're free," because that forward *is* the interruption you just defended against. The failure mode that kills these programs after a quarter is almost always manager defense collapsing: the policy gets set, the calendars get blocked, and then in week three the manager schedules a one-on-one inside a rep's block. The team reads that as permission to skip, and the whole thing unwinds. The manager should treat their own calendar as the loudest signal in the room — one violation costs more credibility than ten reminders can rebuild.

Measuring block effectiveness: the math

Effectiveness is measured by outputs per block, not hours logged or aggregate activity counts. The team inspects the same short funnel every week. A focused 90-minute block against a pre-staged list of roughly 30 accounts typically produces something in the range of 35–42 multi-channel touches (calls, emails, social), 12–15 connects (answers, replies, responses), three to four real conversations, and one to two booked meetings for a mid-market AE. Those booked meetings then convert to qualified opportunities over the following two to three weeks. Run two blocks a week and the weekly pipeline contribution stacks; run them every week for a quarter and self-sourced coverage becomes a meaningful share of the number rather than a rounding error.

Handle the predictable objections directly, because they surface in every room. *"My deals are at stage 4, I don't have time for outbound"* — every stage-4 deal either closes or slips, and the block builds the pipeline that replaces it; reps who only work the current quarter run out of pipeline in the next one. *"I can't get 35 touches in 90 minutes"* — the sequencer auto-queues the next account the moment a touch is finished, so the real bottleneck is research drift, not capacity; reps hitting the target are spending three to four minutes per account, not ten. *"My list isn't ready, I'll start next week"* — that is precisely the failure to fix this week, not a reason to skip, so the manager pair-sits for fifteen minutes today to stage the first list. Close the section with the action: every rep publishes their Week 1 block schedule and target-list count in the team channel before leaving the room.

The commitment and the close

The final five minutes convert intent into calendar entries, because a commitment that is not written down and accepted in the room evaporates by Monday. The manager makes three explicit asks. First, block the two blocks now — open the calendar in the room, create two 90-minute events titled something unambiguous like "Pipeline Generation Block — Do Not Schedule Over," set them as busy, and send them to the manager as an invite so the manager can defend them. Second, pre-stage the first list before leaving — load 25–40 named accounts into the sequencer for the first block, and if the list isn't ready, pair-sit with the manager for fifteen minutes until it is. Third, commit to the weekly review — block outputs get logged in the shared sheet before the team meeting, and that meeting opens with block adherence and block outputs, not deal-cycle updates.

The framing to leave the team with is the same one that opened the hour: the block is a meeting with future revenue. Defend it like a renewal call, run it like a deal you intend to win, and the pipeline compounds. Adherence rarely shows up in the numbers the first week — expect to defend the block for a full month before booked meetings mature into qualified opportunities and the coverage ratio visibly moves. The manager's job for those first thirty days is simply to make sure the block survives contact with a normal, busy week. Reps will test whether the policy is real by watching what happens the first time something urgent collides with a block; the answer they get in week one determines whether the habit takes root or quietly dissolves by the end of the month.

FAQ

How many blocks per week should a rep actually run? Two per week is the AE minimum and three is the SDR minimum. More than three tends to collide with deal-cycle obligations for AEs; fewer than two rarely produces enough compounding pipeline to move the coverage ratio. Start at the minimum and defend it before adding more.

What if a rep genuinely cannot hit 35 touches in 90 minutes? Diagnose before lowering the target. Almost always the cause is research drift — spending eight to ten minutes per account instead of three to four. The sequencer auto-advances to the next account, so raw capacity is rarely the constraint. Tighten the pre-block research cap and the touch count recovers.

Should email and CRM hygiene ever happen inside the block? No. Email, CRM updates, and internal admin get a separate dedicated block later in the day. Folding them into prospecting time is the most common way the block quietly erodes, because "just updating one record" reliably becomes twenty minutes of context-switching.

How does the manager keep the block alive during a busy quarter-end? By defending it out loud at least once a week and never violating it themselves. If the manager books a one-on-one inside a rep's block even once, the team treats it as permission to skip. Pre-blocking the manager's own calendar on the same hours removes the temptation.

What tools are required to run the block properly? Any modern sequencer that auto-queues the next account — Outreach, Salesloft, or Apollo — plus a research source for intent and account context and a calendar the whole team can see. The tooling is secondary to the discipline; the block works with whatever sequencer the team already owns.

How do you measure whether the program is working overall? Track outputs per block (touches, connects, meetings) weekly and self-sourced pipeline coverage monthly. Rising adherence with flat pipeline usually means list quality, not effort, is the issue; rising pipeline with strong adherence is the signal the program is compounding as designed.

Sources

flowchart TD A[Day Before: Fill Pre-Session Brief] --> B[Pre-Stage 25-40 Accounts in Sequencer] B --> C[Attach Intent Signals + Adjacent Deal Notes] C --> D[Block Starts in First 4 Hours of Day] D --> E[90 Minutes Locked, One Sitting] E --> F{35+ Touches Hit?} F -->|Yes| G[Log Outputs, Schedule Next Block] F -->|No| H[Diagnose: Research Drift or Tool Drag?] H --> I[Adjust Brief for Next Block] G --> J[Target: 1-2 Meetings Booked] I --> J

flowchart LR A[1 Block = 90 Min] --> B[35-42 Touches] B --> C[12-15 Connects] C --> D[3-4 Conversations] D --> E[1-2 Meetings Booked] E --> F[Qualified Opp in 14-21 Days] F --> G[2 Blocks/Week Compounds] G --> H[Quarterly Self-Sourced Coverage]

Related on PULSE

[The Pipeline Generation Sprint Reboot — 60-Min Training](/knowledge/st223)
[The Referral Generation Reboot — 60-Min Training](/knowledge/st161)
[Pipeline Review to Revenue: Template for a Data-Driven Sales Sprint Session](/knowledge/st0784)
[AI Video Generation Selling to the Video Production Lead — 60-Min Training](/knowledge/st423)
[AI Image Generation Selling to the Creative Director — 60-Min Training](/knowledge/st422)

Download:

## Direct Answer

The Pipeline Generation Block is a 60-minute, manager-led session that installs a repeatable habit: every AE and SDR commits to two or three defended 90-minute prospecting blocks per week, pre-staged in the sequencer and measured by outputs — touches, connects, and meetings booked — not by hours logged or attendance.

## Why scattered prospecting fails and the block fixes it

The core problem this session names out loud is not skill — it is fragmentation. Reps rarely lose pipeline because they cannot write a good cold email; they lose it because prospecting is the first activity crowded out by deal-cycle calls, internal syncs, Slack pings, and reactive calendar drift. When outbound happens in scattered ten-to-fifteen-minute fragments between meetings, the rep spends most of that time re-orienting — reopening the list, remembering who they were calling, re-reading the last touch — and almost none of it actually prospecting.

Context-switching is the hidden tax. Each interruption during a focused hour costs real refocus time, so a rep who checks email, answers two Slack threads, and glances at their phone inside a single prospecting hour can end up with effectively zero deep-focus minutes despite "spending an hour on outbound." The block attacks this directly by converting prospecting from a background task into a foreground appointment. Ninety uninterrupted minutes against a pre-loaded list produces more real output than three fragmented hours, because momentum compounds inside a single sitting: the fifth dial is easier than the first, the tenth email reuses the rhythm of the ninth, and the rep never pays the re-orientation tax twice.

The founding claim of the session — written on the whiteboard and left up for the full hour — is deliberately simple: pipeline is built in blocks, not in the moments between meetings. Everything that follows is mechanics in service of that one sentence. The session does not try to make reps better writers or sharper on objection handling; it assumes the craft is adequate and that the missing ingredient is protected, concentrated time. That framing matters because it changes what "trying harder" means. A rep who feels behind will instinctively squeeze prospecting into more gaps, which multiplies the switching tax instead of reducing it. The block reframes the fix as fewer, larger, defended sittings — the opposite of the intuitive response — and the manager's job is to keep insisting on that counterintuitive shape until the results validate it.

## Designing the block: time, list size, and sequence discipline

A block is not a generic "prospecting hour." It is engineered around three variables, and the training walks every rep through designing their own using one shared brief. First, **time of day.** The block should start within the first four hours of the rep's workday, before deal-cycle calls dominate and before decision-maker inboxes fill up. Reply and connect rates are generally stronger in the morning window, and — just as important — the rep still has the willpower to defend the block before the day's chaos accumulates. A block scheduled for 4 p.m. is a block that gets sacrificed to whatever caught fire at 2 p.m.

Second, **list size.** AEs pre-stage 25–40 named accounts; SDRs pre-stage 40–60 because outbound is their primary motion. The number is tuned deliberately: too few accounts and the rep runs out of list mid-block and loses momentum; too many and they slide into research drift, over-investigating each account instead of touching it. The list is named accounts the rep chose, not a generic segment — the point is that the rep has already decided these are worth pursuing, so the block is pure execution, not selection.

Third, **sequence discipline.** Each account is pre-loaded into the team's sequencer — Outreach, Salesloft, or Apollo — with its cadence step already known, so the rep spends the block executing touches (a Step 1 cold call, a Step 4 LinkedIn touch, a Step 7 break-up) rather than deciding what to do next. The single most important coaching point: the brief gets filled out the day before, never at the start of the block. Reps who walk in cold and "figure out who to call" burn the first twenty-five minutes on research and never recover. Cap research at roughly three to four minutes per account, pulled from intent signals and notes on adjacent deals, and set a concrete output target — 35-plus multi-channel touches and one to two booked meetings per block. The bad pattern to call out by name is "I'll just open my sequencer and work through the queue." That is reactive queue-clearing: the cadence engine hands the rep whoever it surfaces next, not their highest-intent named accounts.

```mermaid
flowchart TD
    A[Day Before: Fill Pre-Session Brief] --> B[Pre-Stage 25-40 Accounts in Sequencer]
    B --> C[Attach Intent Signals + Adjacent Deal Notes]
    C --> D[Block Starts in First 4 Hours of Day]
    D --> E[90 Minutes Locked, One Sitting]
    E --> F{35+ Touches Hit?}
    F -->|Yes| G[Log Outputs, Schedule Next Block]
    F -->|No| H[Diagnose: Research Drift or Tool Drag?]
    H --> I[Adjust Brief for Next Block]
    G --> J[Target: 1-2 Meetings Booked]
    I --> J
```

## Defending the block: the rep's rules of engagement

State the drill plainly: a block that is not defended is a block that does not exist. Most reps fail here not from lack of discipline but because their manager, their AE-SDR counterpart, and their customer-facing calendar all assume their time is interruptible by default. The session gives every rep a concrete, mechanical defense protocol so willpower is not the load-bearing element.

The protocol has five moves. **Flip scheduling availability off** for the block hours so booking links return no open slots — a one-click toggle that removes most of the inbound interruption surface. **Set a specific status message**, not a vague "heads down," but "Prospecting block until 11:30, will respond at 11:35"; specificity pre-empts the follow-up "are you really busy?" ping. **Accept no internal meetings** during block hours, which works only if the manager pre-blocks the same hours on their own calendar so cross-functional invites bounce. **Put the phone in another room or in focus mode**, because a single glance restarts the refocus clock. And **run one browser window** with only the sequencer tab and a prospecting-research tab open — no email tab, no chat tab, no CRM dashboard.

Email and CRM hygiene get their own separate block later in the day; folding them into prospecting time is how the block quietly dies. Name the one acceptable exception so reps do not treat the rule as absolute and then resent it: a live inbound from a target account in the current-quarter pipeline is worth breaking the block for. Everything else waits. Close by naming the trade-off honestly — defending the block will feel rude in week one, but by week three the rest of the organization routes around it without being asked, and the rep stops having to justify it. The discomfort is front-loaded and temporary; the reputation for being unreachable during a known window becomes a form of respect once the results show up in the pipeline review.

## The manager's defense script

The manager's behavior is the highest-leverage variable in the entire program, so the session rehearses it verbatim. Set the scenario: a rep is mid-block, a peer pings them for a "quick two minutes" on a deal, the rep ignores it, and the peer escalates to the manager — "is Jordan around? Can't reach them." This is the exact moment the block lives or dies, and the manager must handle it the same way every time so the team internalizes the pattern.

A workable script: *"Jordan is in their pipeline-generation block until 11:30. I protect those blocks for the team because they're how we hit our pipeline coverage. If it's a deal blocker, send me the detail and I'll unblock it myself or get Jordan on it at 11:35. If it can wait, drop it in the deal channel and Jordan will pick it up. Want me to ping you when Jordan's back?"* The structure matters: name the block, own the reason, offer a real alternative, close the loop.

Just as important is what the manager must never do. **Do not apologize** ("sorry, Jordan's tied up") — that frames the block as a soft preference rather than a commitment. **Do not pull the rep out** to handle the question yourself — the rep instantly learns the block is overridable. And **do not forward the ping into the rep's DMs** with "FYI when you're free," because that forward *is* the interruption you just defended against. The failure mode that kills these programs after a quarter is almost always manager defense collapsing: the policy gets set, the calendars get blocked, and then in week three the manager schedules a one-on-one inside a rep's block. The team reads that as permission to skip, and the whole thing unwinds. The manager should treat their own calendar as the loudest signal in the room — one violation costs more credibility than ten reminders can rebuild.

## Measuring block effectiveness: the math

Effectiveness is measured by outputs per block, not hours logged or aggregate activity counts. The team inspects the same short funnel every week. A focused 90-minute block against a pre-staged list of roughly 30 accounts typically produces something in the range of 35–42 multi-channel touches (calls, emails, social), 12–15 connects (answers, replies, responses), three to four real conversations, and one to two booked meetings for a mid-market AE. Those booked meetings then convert to qualified opportunities over the following two to three weeks. Run two blocks a week and the weekly pipeline contribution stacks; run them every week for a quarter and self-sourced coverage becomes a meaningful share of the number rather than a rounding error.

```mermaid
flowchart LR
    A[1 Block = 90 Min] --> B[35-42 Touches]
    B --> C[12-15 Connects]
    C --> D[3-4 Conversations]
    D --> E[1-2 Meetings Booked]
    E --> F[Qualified Opp in 14-21 Days]
    F --> G[2 Blocks/Week Compounds]
    G --> H[Quarterly Self-Sourced Coverage]
```

Handle the predictable objections directly, because they surface in every room. *"My deals are at stage 4, I don't have time for outbound"* — every stage-4 deal either closes or slips, and the block builds the pipeline that replaces it; reps who only work the current quarter run out of pipeline in the next one. *"I can't get 35 touches in 90 minutes"* — the sequencer auto-queues the next account the moment a touch is finished, so the real bottleneck is research drift, not capacity; reps hitting the target are spending three to four minutes per account, not ten. *"My list isn't ready, I'll start next week"* — that is precisely the failure to fix this week, not a reason to skip, so the manager pair-sits for fifteen minutes today to stage the first list. Close the section with the action: every rep publishes their Week 1 block schedule and target-list count in the team channel before leaving the room.

## The commitment and the close

The final five minutes convert intent into calendar entries, because a commitment that is not written down and accepted in the room evaporates by Monday. The manager makes three explicit asks. First, **block the two blocks now** — open the calendar in the room, create two 90-minute events titled something unambiguous like "Pipeline Generation Block — Do Not Schedule Over," set them as busy, and send them to the manager as an invite so the manager can defend them. Second, **pre-stage the first list before leaving** — load 25–40 named accounts into the sequencer for the first block, and if the list isn't ready, pair-sit with the manager for fifteen minutes until it is. Third, **commit to the weekly review** — block outputs get logged in the shared sheet before the team meeting, and that meeting opens with block adherence and block outputs, not deal-cycle updates.

The framing to leave the team with is the same one that opened the hour: the block is a meeting with future revenue. Defend it like a renewal call, run it like a deal you intend to win, and the pipeline compounds. Adherence rarely shows up in the numbers the first week — expect to defend the block for a full month before booked meetings mature into qualified opportunities and the coverage ratio visibly moves. The manager's job for those first thirty days is simply to make sure the block survives contact with a normal, busy week. Reps will test whether the policy is real by watching what happens the first time something urgent collides with a block; the answer they get in week one determines whether the habit takes root or quietly dissolves by the end of the month.

## Related questions

### How is a Pipeline Generation Block different for SDRs versus AEs?
SDRs run three blocks a week minimum with larger lists (40–60 accounts) because outbound is their primary motion. AEs run two blocks minimum with smaller lists (25–40) because they balance deal-cycle work. Both groups use the same brief, defense protocol, and output measurement.

### What should a rep do if a customer call lands inside a planned block?
Customer calls always win. The rep reschedules the block to the next open 90-minute window the same day and notifies the manager. The block is shifted, never skipped — skipped blocks compound and the rep never catches up.

### Can sequence follow-ups count toward the block, or must every touch be net-new?
Follow-up cadence steps (Step 4, Step 7, break-ups) count toward the block's touch total. The only constraint is that the rep works their named target list, not whatever the sequencer surfaces from across their entire book of business.

### How long before block adherence shows up in pipeline numbers?
Roughly 14–21 days for booked meetings to convert to qualified opportunities, and 30–45 days for the team's overall coverage ratio to move. Managers should plan to defend the block for a full month before anyone stops asking whether it works.

### What is the single biggest reason teams abandon the block after a quarter?
Manager defense fails. The policy is set and calendars are blocked, but the manager schedules something inside a rep's block, and the team reads that as permission to skip. The fix is the manager pre-blocking their own calendar on the same hours.

## FAQ

**How many blocks per week should a rep actually run?**
Two per week is the AE minimum and three is the SDR minimum. More than three tends to collide with deal-cycle obligations for AEs; fewer than two rarely produces enough compounding pipeline to move the coverage ratio. Start at the minimum and defend it before adding more.

**What if a rep genuinely cannot hit 35 touches in 90 minutes?**
Diagnose before lowering the target. Almost always the cause is research drift — spending eight to ten minutes per account instead of three to four. The sequencer auto-advances to the next account, so raw capacity is rarely the constraint. Tighten the pre-block research cap and the touch count recovers.

**Should email and CRM hygiene ever happen inside the block?**
No. Email, CRM updates, and internal admin get a separate dedicated block later in the day. Folding them into prospecting time is the most common way the block quietly erodes, because "just updating one record" reliably becomes twenty minutes of context-switching.

**How does the manager keep the block alive during a busy quarter-end?**
By defending it out loud at least once a week and never violating it themselves. If the manager books a one-on-one inside a rep's block even once, the team treats it as permission to skip. Pre-blocking the manager's own calendar on the same hours removes the temptation.

**What tools are required to run the block properly?**
Any modern sequencer that auto-queues the next account — Outreach, Salesloft, or Apollo — plus a research source for intent and account context and a calendar the whole team can see. The tooling is secondary to the discipline; the block works with whatever sequencer the team already owns.

**How do you measure whether the program is working overall?**
Track outputs per block (touches, connects, meetings) weekly and self-sourced pipeline coverage monthly. Rising adherence with flat pipeline usually means list quality, not effort, is the issue; rising pipeline with strong adherence is the signal the program is compounding as designed.

## Sources

- https://www.outreach.io/resources
- https://salesloft.com/resources/
- https://www.apollo.io/resources
- https://www.gong.io/resources/
- https://calnewport.com/deep-work-rules-for-focused-success-in-a-distracted-world/
- https://hbr.org/2016/03/collaborative-overload
- https://www.gartner.com/en/sales
- https://blog.hubspot.com/sales

## Related on PULSE

- [The Pipeline Generation Sprint Reboot — 60-Min Training](/knowledge/st223)
- [The Referral Generation Reboot — 60-Min Training](/knowledge/st161)
- [Pipeline Review to Revenue: Template for a Data-Driven Sales Sprint Session](/knowledge/st0784)
- [AI Video Generation Selling to the Video Production Lead — 60-Min Training](/knowledge/st423)
- [AI Image Generation Selling to the Creative Director — 60-Min Training](/knowledge/st422)

Was this helpful?

Deep dive · related in the library

tl · pulse-toolsHow Many Sales Reps Do I Need to Hire for My SaaS Company to Hit Next Year''s Goal?tl · pulse-toolsHow Many Sales Reps Do I Need to Hire for My Landscaping Company This Year?tl · pulse-toolsHow Many Membership Sales Reps Do I Need to Hire for My Gym?tl · pulse-toolsHow Many Sales Consultants Do I Need to Hire for My Medical Spa?pulse-tools · toolsHow Many Salespeople Do I Need to Hire for My Car Dealership?pulse-tools · toolsHow Many Salespeople Should I Schedule on My Auto Dealership Floor Each Day?pulse-tools · toolsHow Many Sales Reps Do I Need to Hire for My Painting Company to Grow Next Year?pulse-tools · toolsHow Many Sales Reps Do I Need to Hire for My HVAC Company to Hit Its Growth Target?pulse-tools · toolsHow Many Salespeople Should I Schedule Each Day at My Jewelry Store?pulse-tools · toolsHow Many Employees Should I Schedule Each Shift at My Bowling Alley?

Kory White

The Pipeline Generation Block — 60-Min Training

Why scattered prospecting fails and the block fixes it

Designing the block: time, list size, and sequence discipline

Defending the block: the rep's rules of engagement

The manager's defense script

Measuring block effectiveness: the math

The commitment and the close

Related questions

How is a Pipeline Generation Block different for SDRs versus AEs?

What should a rep do if a customer call lands inside a planned block?

Can sequence follow-ups count toward the block, or must every touch be net-new?

How long before block adherence shows up in pipeline numbers?

What is the single biggest reason teams abandon the block after a quarter?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ