Pipeline Playbook banner

GM!

A rep has a strong-looking opportunity list. The forecast review is orderly. Yet proposal revisions wait three days, champion follow-ups are generic, and a buyer's implementation question sits unanswered.

The operating question isn't how many deals are open. Which buyer commitments can this team actually service before the next decision point?

Pipeline coverage tells you what's in play. It doesn't tell you whether the people needed to move those deals have room to do the work. When workload is hidden, managers often respond to slippage by asking for more activity—the same people, with less time per buyer decision.

Measure work due, not just opportunities open

An active deal creates specific work: prepare a commercial revision, get a technical answer, convene two stakeholders, or confirm the buyer's decision. The effort isn't equal across deals or stages.

A quiet evaluation with no buyer action due this week should not consume the same attention as a procurement deadline with open redlines. But a large deal with a vague “check in” task is not automatically urgent either.

An opportunity is a container. The next buyer commitment is the unit of work.

Keep CRM stage and forecast category as they are. Add a short execution queue beside the opportunity list. This is a capacity control, not another qualification score.

Build a five-field execution queue

For each deal with work due in the coming week, record:

  1. Buyer decision or milestone: What will the buyer do next, and when? A named security review or internal demo beats “follow up.”

  2. Seller deliverable: What must your team supply before that milestone? Make it a concrete output, not “support buyer.”

  3. Owner and dependency: Who produces it? Note whether legal, solutions, finance, or a manager must contribute.

  4. Due date and effort band: When must it be ready? Mark effort as small, medium, or substantial using your team's own definitions—not invented hours.

  5. Consequence if missed: Does the buyer's decision move, does the team lose access, or is the work genuinely deferrable?

You don't need a new tool to start. A filtered CRM view and a shared queue work if the owner updates the due date and dependency during the deal review.

Don't turn effort bands into precision theater. Their purpose is to expose conflicting commitments, not to pretend every legal review takes the same amount of time.

Triage the collision in public

Illustrative scenario: an AE promises a revised order form for Tuesday, a security response for Wednesday, and an executive business case for Thursday. Legal owns the redlines. A solutions engineer owns the security response. Both are already committed elsewhere.

The AE's calendar looks open. The team's delivery queue is not.

At the weekly review, the manager asks which buyer milestone is fixed, which work needs specialist capacity, and which promise can be renegotiated before it is missed. Legal gets an explicit slot; the security owner confirms when evidence will be ready; the buyer receives a revised date for the business case if necessary.

That is a better outcome than marking all three deals “on track” and discovering the collision on Wednesday.

A buyer deadline without a staffed deliverable is a forecast assumption.

Separate four queue states

Use these labels during review:

  • Staffed: An owner accepted the work and the date fits available capacity.

  • At risk: An owner exists, but another commitment or dependency threatens the due date.

  • Unstaffed: No one has accepted the required output. Assign or renegotiate before treating the buyer milestone as secure.

  • Waiting on buyer: Your team has delivered its part and the next action belongs to the customer. Name the buyer action and agreed date; don't use this label to hide unfinished seller work.

These are delivery states, not forecast categories. A deal can remain a credible opportunity while its next deliverable is at risk. The manager's job is to decide what that means for timing rather than silently changing the CRM close date.

If a buyer milestone has moved, record the buyer-confirmed new date. If the buyer has not confirmed one, avoid presenting a seller-estimated date as a buyer commitment.

Stop feeding the queue blindly

When new opportunities arrive, ask who will handle the next meaningful buyer request. If the team cannot staff it, choose deliberately: move capacity from lower-consequence work, set a realistic delivery date with the buyer, or hold the opportunity in a research/nurture state until a buyer milestone is real.

Do not solve this by telling reps to manufacture activity or by closing valid opportunities to make the workload chart look clean. The point is to protect the work that converts interest into a buyer decision.

Review recurring collisions by owner and work type. If every technical answer waits for the same specialist, the constraint may be in support capacity or handoff design, not rep discipline. If the queue is full of seller-created tasks with no buyer milestone, cut those tasks before asking for more headcount.

Weekly action

Take one rep's active deals and list every seller deliverable due before the next buyer milestone. Add owner, dependency, due date, effort band, and consequence if missed.

Mark each item staffed, at risk, unstaffed, or waiting on buyer. Resolve one collision in the next pipeline review: assign capacity, renegotiate the buyer promise, or revise the timing assumption in the forecast.

Check the decision against the buyer's actual deadline—not the CRM task due date alone.

— Pipeline Playbook