Best for
- Enterprise sales teams that lose momentum during security or procurement review
- AEs managing deals with legal, IT, finance, or compliance stakeholders
- Sales engineering teams repeatedly answering the same diligence questions
Spot enterprise deal blockers from calls and CRM notes, then assemble the security, procurement, ROI, and implementation answers buyers need to move forward.
A deal-specific review packet with security answers, procurement proof, implementation details, ROI support, and stakeholder-specific notes.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
5 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Many deals do not stall because the buyer lacks interest. They stall because new stakeholders enter with unanswered questions about security, procurement, risk, implementation, or ROI. This workflow turns deal signals into a prepared review packet before the buyer has to chase every answer internally.
Expected results
Packet creation time
2-4 hours per deal
Once approved answers and assets are organized, the workflow reduces repeated manual searching and rewriting for each enterprise review.
Stakeholders covered
4-6 internal audiences
Enterprise review commonly involves security, IT, procurement, finance, executives, and the champion, each with different questions.
Deal friction reduced
Fewer repeated diligence loops
A complete packet gives the champion approved answers and proof before questions turn into delays.
Sales risk control
Approved answers only
Security and compliance claims come from official trust content instead of improvised rep responses.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45 min
45 min
Start in Salesforce and find opportunities where security, legal, procurement, IT, finance, or executive approval has been mentioned. Work in salesforce and capture the concrete operating details: record ID, source evidence, issue type, severity, owner, decision, next action, and follow-up date. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A shortlist of active opportunities that may stall because of review, diligence, or procurement friction.
A shortlist of active opportunities that may stall because of review, diligence, or procurement friction.
The best time to build this packet is before procurement formally asks for it. Once the deal is already stalled, you are reacting instead of guiding.
45-60 min
45-60 min
Use Gong and Salesforce notes to identify every blocker, open question, stakeholder concern, and implied risk. Work in gong, salesforce, and claude and capture the concrete operating details: source material, decision criteria, working notes, owner, output link, review status, and open questions. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A deal blocker map organized by stakeholder, risk type, and urgency.
A deal blocker map organized by stakeholder, risk type, and urgency.
Implied blockers matter. 'Our IT team will need to look at this' is often not a logistics comment. It is a trust, risk, or workload concern waiting to surface.
Pro workflow preview
Previewing 2 of 7 steps
Get the remaining 5 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Analyze this opportunity data and extract possible deal blockers.
Opportunity notes:
{{opportunity_notes}}
Call transcript excerpts:
{{call_transcripts}}
Stakeholders:
{{stakeholders}}
For this deal, output:
1. Explicit blockers
2. Implied blockers
3. Stakeholder associated with each blocker
4. Risk category: security, legal, procurement, finance, IT, implementation, ROI, executive approval, or other
5. Buyer language that signals the blocker
6. What proof or answer is needed
7. Urgency level
8. Recommended packet section
Do not invent blockers. Use the notes and transcript evidence.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A buyer-facing deal room and mutual action plan that keeps next steps, stakeholders, proof, and decision criteria visible between meetings.
A post-call coaching system with objection clusters, rep feedback, follow-up drafts, and reusable response plays from real buyer conversations.
A CRM-ready pre-call intelligence pack with account context, participant notes, discovery hypotheses, questions, risks, and a post-call capture template.