Your Deal Has a Coordination Problem
A prompt workflow for building the consensus path that turns committee interest into a signed deal
This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.
Get the PMM’s Prompt Playbook and Modern B2B Marketing today!
Need help with product marketing or prompts? Let me know.
Workflow Name: Consensus Path Planning and Deal Acceleration
Created by insights.tinytechguides.com
What this workflow does
I’ve watched deals die where every single stakeholder privately supported the purchase. No one objected. No one said no. The deal just stalled because nobody created a mechanism to turn all that private support into a collective decision.
When a deal goes quiet, sales teams usually blame a lack of motivation. The champion went dark. The economic buyer stopped responding. The technical team wants more data. These look like engagement problems. They’re structural failures. The committee never reached a specific consensus milestone, and nobody noticed because the pipeline report tracks stages, not alignment.
This workflow maps the path from first engagement to signed deal. It identifies the sequence of stakeholder engagements, the milestones the committee must reach, the mechanisms that build collective commitment, and the recovery protocols for when deals stall. The output is a deal architecture document that gives sales a stage-by-stage engagement plan and gives marketing visibility into where their content supports committee alignment.
This workflow does not create messaging, map the committee, or surface hidden objections. That’s what the first three workflows in this series do.
It answers one question: what is the specific path from fragmented interest to collective commitment, and what do you do when that path breaks?
Workflow steps summary
Step 0: Define inputs
Step 1: Define the consensus milestones
Step 2: Map the stakeholder engagement sequence
Step 3: Identify consensus-building mechanisms
Step 4: Design the stall recovery playbook
Step 5: Build the deal architecture timeline
Step 6: Assemble the consensus path plan
This is the fourth and final workflow in the buying committee series. It builds on the outputs from the first three:
The workflow was created by insights.tinytechguides.com and connects to these existing workflows:
Step 0: Define inputs
Before running the workflow, gather these inputs:
{account_type} = target account profile or segment
{deal_examples} = recent won, lost, and stalled deals
{sales_inputs} = call notes, objections, deal commentary
{customer_inputs} = outputs from Voice of Customer workflow
{competitive_context} = outputs from Competitive Landscape Mapping
{committee_map} = output from Buying Committee Decision Mapping Workflow
{risk_analysis} = output from Hidden Objection and Risk Surface Analysis Workflow
{messaging_map} = output from Committee-Aware Messaging and Content Mapping Workflow
{avg_sales_cycle} = average sales cycle length for this deal size
{sales_process} = current sales stages or methodology (e.g., MEDDPICC, Sandler, custom stages)
Step 1: Define the consensus milestones
A signed deal is the final milestone, but it is the result of many smaller consensus events that happen inside the buying organization. Before a committee can approve a purchase, they must collectively agree on a series of intermediate decisions. That the problem is worth solving. That the category of solution is right. That this vendor is the best fit. That the timing is right. That the terms are acceptable. Missing any of these intermediate consensus points creates a stall, and most sales teams cannot tell you which milestone their deal has actually reached versus which one they have assumed.
Prompt:
Role
You are a senior B2B sales strategist who designs deal architectures for complex enterprise sales involving multi-stakeholder buying committees.
Context
A signed deal requires the committee to reach consensus on five intermediate decisions: problem significance, solution category, vendor preference, timing, and terms. Missing any of these creates a stall that shows up as a “stuck” deal in the pipeline.
Task
Using {committee_map}, {risk_analysis}, {sales_inputs}, and {deal_examples}, define the internal consensus milestones for a purchase in {account_type}.
Format
For each of the five milestones (problem consensus, category consensus, vendor consensus, timing consensus, terms consensus):
Description of what agreement looks like at this stage
Key stakeholders who must be aligned
Evidence they need to reach alignment
The gatekeeper for this milestone
The most common reason this milestone stalls
The event or evidence that unlocks it
Deliver as a table. After the table, provide a narrative summary (3-5 sentences) describing the typical sequence and where the buying process most often breaks down.
Tone
Strategic and grounded in real-world sales dynamics. Write as someone who knows the difference between a milestone that has been genuinely reached and one that has been assumed.
Your pipeline isn’t stuck. It just skipped a milestone nobody noticed.
Step 2: Map the stakeholder engagement sequence
The order in which you engage stakeholders matters as much as the message. Engaging the economic buyer too early, before the technical team has validated feasibility, undermines credibility. Engaging procurement too late, after expectations are set without their input, creates adversarial dynamics. The right sequence builds momentum by creating a chain of internal endorsements where each stakeholder’s support makes the next engagement easier.
Prompt:
Role
You are a senior enterprise sales architect who designs multi-threaded engagement strategies for complex B2B deals with large buying committees.
Context
Buying committees do not engage in a linear sequence. Some stakeholders can be engaged in parallel. Others must be sequential. The wrong order creates friction that compounds across the deal cycle.
Task
Using the consensus milestones from Step 1, {committee_map}, and {sales_inputs}, design the optimal stakeholder engagement sequence for {account_type}.
Format
1- Engagement timeline table with columns: Stakeholder, First Engagement Timing, Engaged By, Goal of First Engagement, Prerequisites
2- Multi-threading strategy describing which stakeholders can be engaged simultaneously, which must be sequential, and where the champion should make introductions versus where sales should request meetings directly
3- Escalation triggers table with columns: Stall Signal, Escalation Action, Who to Involve, Anti-Pattern to Avoid
4- A text-based engagement sequence showing the flow across deal stages
Tone
Tactical and specific. Build this for a sales team executing on real deals, not a training manual.
Step 3: Identify consensus-building mechanisms
Individual stakeholder buy-in does not automatically become committee consensus. A committee where every member privately supports the purchase can still fail to act because no one created the mechanism for converting private support into collective commitment. Consensus requires structure. Shared evaluation criteria, visible commitment signals, and events where alignment is tested and confirmed rather than assumed.
Prompt:
Role
You are a senior organizational psychologist and B2B sales strategist who specializes in the dynamics of group decision-making within enterprise buying committees.
Context
The gap between individual interest and collective commitment is where most deals die. Consensus requires shared frameworks, commitment events, and coalition management, not just good meetings with individual stakeholders.
Task
Using the outputs from Steps 1-2, {committee_map}, and {risk_analysis}, identify the mechanisms that build consensus within this buying committee for {account_type}.
Format
1- Shared evaluation framework with 5-8 weighted criteria the committee can use to evaluate together rather than in isolation
2- Commitment escalation events table with columns: Event, Purpose, Success Signal, Facilitation Notes
3- Coalition-building tactics as a numbered list, each with a 2-3 sentence description covering alliance strengthening, friction neutralization, swing vote conversion, and blocker isolation
4- Commitment artifacts table with columns: Artifact, Associated Milestone, Owner, Why It Matters
Tone
Practical and psychologically informed. Write as someone who understands both the organizational dynamics and the tactical moves that convert understanding into action.
Step 4: Design the stall recovery playbook
Every complex B2B deal stalls at some point. The question is not whether stalls happen but whether the team can diagnose the cause and execute a recovery before the deal slips to “no decision.” Most sales teams treat stalls as a motivation problem when they are actually a structural problem. A specific consensus milestone was not reached, or a specific stakeholder’s concern was not addressed, and no one noticed until the deal went quiet.
