Sales Stage Commitment Validator
Check whether a deal's CRM stage matches the customer's demonstrated commitment.
Customise & copy
Add the context you have. The prompt updates as you work.
Select the stage currently recorded in the CRM.
List each known stakeholder and their role or influence.
Include observable actions, decisions, dates, approvals, or customer statements.
Select Yes only when the customer has made a clear commitment.
Live prompt
4 fieldsValidate whether the reported sales stage reflects the customer's actual commitment level. Use only the information provided; do not invent facts, quotes, testimonials, stakeholders, or evidence. Reported deal stage: Proposal/Negotiation Identified stakeholders: VP of Operations, Director of Procurement, and IT Security Manager Concrete evidence: The prospect completed a technical evaluation, approved the security review, requested a final pricing proposal, and scheduled a procurement meeting. Commitment status: No Return exactly these four sections: Assessment: Accurate, Too advanced, Too early, or Insufficient evidence Rationale: Explain the assessment using the reported stage, stakeholder coverage, evidence, and commitment status. Gaps: List the specific missing, weak, or contradictory signals. Correction or next action: State the CRM stage correction or the single most important action needed next. Be direct and conservative. Treat unsupported claims as unverified. Do not ask follow-up questions.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"reported_stage": "Proposal/Negotiation",
"commitment_status": "No",
"concrete_evidence": "The prospect completed a technical evaluation, approved the security review, requested a final pricing proposal, and scheduled a procurement meeting.",
"identified_stakeholders": "VP of Operations, Director of Procurement, and IT Security Manager"
}A small ritual that works
How to use it
- 01Select the reported deal stage.
- 02List identified stakeholders and their roles or influence.
- 03Add concrete evidence of customer actions, decisions, approvals, or statements.
- 04Select whether the customer has made a clear commitment.
Why it works
The prompt defines a narrow decision task: compare a reported sales stage with stakeholder coverage, concrete evidence, and commitment status. Its allowed assessment labels create a controlled classification set, while the rationale, gaps, and next-action fields require the reasoning to remain tied to the supplied deal information. The instruction to use only provided facts and treat unsupported claims as unverified establishes a conservative evidence boundary. The fixed four-section format also makes each response address the decision, supporting explanation, missing signals, and practical follow-up.
Where it fails
The prompt cannot resolve ambiguity that is not represented in the supplied fields. A stakeholder list does not establish decision authority, concrete evidence may be incomplete or contradictory, and the Yes/No commitment field provides less nuance than stages such as conditional approval, verbal intent, or pending procurement. The prompt also depends on the reported stage using the defined stage vocabulary; it does not provide rules for mapping custom CRM stages to those categories.
Customisation tips
Add explicit definitions for each stage, including the minimum evidence required to enter or leave it. If the workflow distinguishes economic approval, legal approval, procurement approval, and technical approval, give each its own input rather than relying on a general evidence field. Replace the binary commitment field with a controlled set of commitment states if partial or conditional commitments matter. You can also add a decision date, budget status, authority level, and next customer action so the assessment can separate stakeholder presence from verified decision control.
Watch-outs
- The prompt asks for a single most important next action, so several equally important gaps must be prioritized rather than listed as separate actions.
- The phrase "actual commitment level" may be interpreted broadly unless commitment criteria are defined for the relevant sales process.
- Evidence quality depends on the user entering observable actions, decisions, dates, approvals, or customer statements rather than general descriptions.
- The stage list combines commercial stages and terminal outcomes, so the instructions should clarify when a deal may be classified as Closed Won or Closed Lost.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.