Free Deal Risk Review Prompt
Short answer: Inspect an opportunity for evidence of a real, winnable deal before forecast time.
BEFORE YOU COPY
Bring the context. Skip the blank page.
Collect account context, stakeholders, buyer language, stage, decision process, evidence from calls or artifacts, risks, next-step constraints, and the exact sales moment the output must improve. The prompt separates facts from assumptions, compares viable paths, and produces the promised artifact instead of generic advice.
- Add contextProvide your company, buyer, motion, constraints, and decision.
- Run the workflowPaste the free prompt into ChatGPT, Claude, or Codex.
- Inspect the artifactReview assumptions, risks, actions, and the quality check.
FULL PROMPT · FREE FOREVER
Copy the full GTM workflow.
No account or email required. Copy it into ChatGPT, Claude, or Codex, add your context, and make the decision in front of you.
Copy the prompt
## StackSwap execution contract You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation. 1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success. 2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed. 3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof. 4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly. 5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer. 6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation. 7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy. ### Output contract Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary. ### Evidence and verification Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification. ### Follow-on behavior Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library. ### Cross-platform behavior This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context. --- --- name: deal-risk-review description: "Diagnose deal risk from buyer evidence, stage behavior, decision process, competition, and next-step quality." allowed-tools: Read Write WebSearch WebFetch metadata: author: Nick French / StackSwap version: '1.0' product: Operator Playbook --- # Deal Risk Review Deal risk is the gap between what the team hopes is true and what the buyer has demonstrated. ## When to use it Use in a deal review, forecast inspection, stage change, or before a major investment of time. Do not use it to create a pessimistic score without evidence or an action. ## Inputs to collect Collect stage and exit criteria, buyer evidence, stakeholders, champion strength, economic buyer access, decision process, competition, pain and impact, timeline, next step, blockers, and historical conversion patterns. ## Method 1. Score evidence across pain, urgency, value, access, decision, competition, implementation, and commercial fit. 2. Separate missing evidence from negative evidence and from internal execution risk. 3. Identify the single largest risk and the smallest action that can test it. 4. Reclassify forecast category and stage only from observable evidence. 5. Set owner, date, exit condition, and a kill or recycle rule. ## Output Produce a risk scorecard, evidence ledger, risk-ranked action plan, stakeholder and decision map, forecast recommendation, next-step script, and stop/recycle conditions. ## Verification and failure modes Compare the review to source moments and later outcomes. Guard against activity mistaken for intent, champion theater, seller optimism, stale dates, and risk lists with no owner or test. ## Quality gate The review is useful only if it changes a decision: invest, test, advance, hold, recycle, or exit.
Free forever. No email gate.
Was this prompt useful?
Thumbs up if it helped. Thumbs down if it needs work.
THE PROMPT IS THE START
Want an independent read on the real project?
Start the free discovery QA audit. Show StackSwap what your builder already knows, then get a focused next move.
QUESTIONS
About this free prompt
What does this deal risk review prompt help with?
Inspect an opportunity for evidence of a real, winnable deal before forecast time.
Who should use this deal risk review prompt?
This free GTM prompt is for B2B SaaS founders, GTM leaders, and RevOps operators who need a useful first draft without starting from a blank page.
What should I add before running this deal risk review prompt?
Add your company, buyer, GTM motion, constraints, and the decision you need to make. Better context produces a more specific artifact and makes weak assumptions easier to spot.
What output does this deal risk review prompt produce?
MEDDPICC-style risk review and close/no-close recommendation. The workflow is designed to produce that artifact instead of generic GTM advice.
Can I use this deal risk review prompt in ChatGPT, Claude, or Codex?
Yes. The workflow is designed for ordinary chat, Claude, and Codex, with platform-specific formats available to copy for free.
How do I get a better result from this deal risk review prompt?
Include real customer language, current numbers, and hard constraints, then inspect the assumptions and risks in the result. Treat the first output as a decision artifact to improve, not an unquestionable answer.