{"id":"revops-stage-definitions-entry-exit-template","audience":"revops","category":"sales-work","technique":"format","track":"sales","level":"intermediate","title":"Write stage definitions with entry and exit criteria","free":false,"task":"You're publishing the new opportunity stages for reps. For each of the four current stages, fill this template: \"Stage:\", \"Entry:\" and \"Exit:\", one line each, with a blank line between stages. Use the current stage names, not the old ones. Every Exit line must be something a manager can check in the CRM. Plain text, under 170 words.","materialLabel":"Stage redesign notes (attached to your prompt automatically)","material":"STAGE REDESIGN - working notes, Oct 28 - Nov 6, 2026\n\nOld stages: Qualified > Demo > Proposal > Negotiation > Closed\n\nDecision (Nov 6 sales leadership): 4 open stages, renamed:\n1. Discovery (replaces Qualified)\n2. Solution Fit (replaces Demo)\n3. Proposal\n4. Commit (replaces Negotiation)\n\nWhat has to be true, from the workshop:\n- Discovery starts when a meeting with a prospect is held and pain is logged. Leaves when budget range and decision process fields are filled in.\n- Solution Fit starts once the prospect agrees to a demo with their team. Leaves when a technical contact confirms fit in writing (email attached to the opp).\n- Proposal starts when pricing is sent. Leaves when the deal desk approves pricing (approval box checked).\n- Commit starts when the economic buyer says yes. Leaves when the order form is signed (closed won) or the deal is lost.\n\nWorkshop wish list (not agreed): \"rep feels good about it\" as a Commit gate; a 5th stage called Legal.","rules":[{"type":"plainText"},{"type":"maxWords","max":170}],"mistakes":[{"title":"Using the old names","why":"The AI mixes old and new stage names because both appear in the notes.","fix":"Add: \"Use the Nov 6 names: Discovery, Solution Fit, Proposal, Commit.\"","checks":["r0"]},{"title":"No template","why":"The AI writes a paragraph per stage, so reps can't scan it.","fix":"Show the shape: \"Stage: / Entry: / Exit:, one line each, blank line between stages.\"","checks":["r1"]},{"title":"Pulling in the wish list","why":"The AI includes ideas from the workshop that were never agreed.","fix":"Add: \"Only agreed criteria. Every Exit must be checkable in the CRM.\"","checks":["r2","r0"]},{"title":"Getting markdown","why":"The AI bolds the field labels and adds a heading.","fix":"Add: \"Plain text, no bold, no heading.\"","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and adds explanation per stage.","fix":"Cap it: \"each line under 15 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Uses current names","patterns":["discovery","solution fit","new names","current names"]},{"label":"Shows the template","patterns":["stage:","entry:","exit:"]},{"label":"Checkable exits","patterns":["check(able)? in (the )?crm","visible","field"]},{"label":"Leaves out the wish list","patterns":["wish list","not agreed","only agreed"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown"]}],"hint":"Give the AI the exact field labels, the current stage names, and the rule that every exit must be visible in the CRM.","rubricLabels":["Uses the stage names Discovery, Solution Fit, Proposal and Commit, with no stage called Qualified, Demo, Negotiation or Legal","Every stage has exactly one Stage, Entry and Exit line, and the Proposal Exit line says the deal desk approves pricing","No Exit line uses a feeling (such as the rep feeling good about it); each one names something visible in the CRM"]}