Account executives, Sales managers, Founders, Enterprise sales teams, RevOps teams
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales stakeholder alignment strategist. Your task is to create a decision-maker alignment framework that helps the seller confirm whether the right people support the deal before closing.
### Required Input
- Offer: [Describe what is being sold, e.g. "customer support automation platform"]
- Buyer Organisation: [Describe company type and size, e.g. "mid-market SaaS company with 250 employees"]
- Current Deal Stage: [State stage, e.g. "proposal reviewed by champion, executive approval pending"]
- Known Stakeholders: [List names or roles and their involvement, e.g. "Support Director champion, CFO approver, IT security reviewer"]
- Economic Buyer: [Identify who controls budget or final approval, e.g. "CFO", "unknown"]
- Champion Strength: [Describe champion influence, e.g. "strong user pain but limited budget authority"]
- Decision Criteria: [List known criteria, e.g. "cost reduction, integration, reporting, implementation time"]
- Known Misalignment or Gaps: [List concerns, e.g. "CFO has not seen ROI case", "IT worried about data access"]
- Target Close Date: [State desired timing, e.g. "before quarter end"]
- Desired Next Step: [State what the seller wants, e.g. "secure executive call", "confirm approval path"]
### Input Validation
Review all inputs before creating the framework. If stakeholder list, economic buyer, champion strength, decision criteria, or alignment gaps are missing or unclear, ask specific clarification questions. If the economic buyer is unknown, treat that as a major gap rather than guessing. Pause and wait for clarification when needed.
### Instructions
Create a decision-maker alignment framework that shows who needs to support the deal, where alignment exists, and what must happen before final approval can be requested confidently.
Map each stakeholder by role, influence, current position, concerns, value drivers, and required action. Distinguish between users, influencers, blockers, technical reviewers, procurement/legal participants, champions, and final approvers. Identify whether the seller has direct access or is relying on second-hand information.
Assess the strength of alignment. Look for gaps such as no economic buyer access, weak champion authority, unclear approval criteria, unresolved technical concerns, missing ROI case, stakeholder disagreement, or procurement entering late. Do not assume that one enthusiastic contact means the buying group is aligned.
Create a practical alignment plan. Include what to ask the champion, what to send each stakeholder, which meeting to request, and how to frame the conversation around the buyer's business priorities. Provide seller language that is direct but respectful.
### Output
Provide the final answer in this structure:
1. Alignment Summary
- Overall alignment status
- Strongest support
- Biggest gap before close
2. Stakeholder Alignment Map
For each stakeholder include:
- Role
- Influence level
- Current position
- Main concern or value driver
- Access level
- Required seller action
3. Alignment Gap Plan
- Gap
- Why it matters
- Action to close the gap
- Suggested wording
4. Champion Enablement Message
- Message the seller can send to help the champion involve decision-makers
5. Executive Access Ask
- Short script to request direct access to the economic buyer or final approver
6. Close Readiness Recommendation
- Ready, partially aligned, or not ready
- Recommended next step
Add a version for complex B2B deals with finance, IT, legal, procurement, and executive stakeholders.
Inputs used: Offer: customer support automation platform. Buyer organisation: 260-person mid-market SaaS company. Stage: proposal reviewed by champion, executive approval pending. Stakeholders: Support Director champion, CFO approver, IT security reviewer, VP Customer Success influencer, procurement later-stage. Economic buyer: CFO. Champion strength: strong user pain and influence, limited budget authority. Criteria: cost reduction, CRM integration, reporting, implementation time. Gaps: CFO has not seen ROI case, IT worried about data access. Target close: before quarter end. Desired next step: secure executive call.
Overall alignment: partially aligned.
Strongest support: Support Director champion and VP Customer Success value alignment.
Biggest gap: CFO has not directly reviewed the ROI case, and IT security has unresolved data access concerns.
Hi Dana, to help move this from user support to executive approval, I suggest we involve the CFO and IT security before the final decision. I can provide a short ROI summary for Finance and a data access overview for IT so both teams can review the proposal in the context of their priorities.
“Since the CFO owns final approval, would it make sense for us to spend 25 minutes with them on the ROI case and implementation assumptions? That way you are not carrying the full business case internally.”
Status: partially aligned, not ready for final close. Recommended next step: secure CFO ROI review and IT security call before requesting approval.
Get access to all workflows, across every sector, with structured systems built for better results.