CRM OpsUpdated July 4, 2026
Pipeline Stage Definition
Create clear CRM stage rules so reports and automation are reliable.
Use case: Use when pipeline stages are vague or reps use them inconsistently.
Prompt
Define CRM pipeline stages for a small-business sales process.
Current stages: {{current_stages}}
Sales motion: {{sales_motion}}
Known exit criteria: {{exit_criteria}}
Common confusion: {{common_confusion}}
Return a stage map with:
- Stage name
- Entry criteria
- Exit criteria
- Required fields
- Allowed automations
- Reporting meaning
Keep stage names plain and avoid extra stages that do not trigger action.
Quality bar:
- Identify which fields drive action and which create noise.
- List failure modes before proposing automation.
- Include test cases and monitoring signals for production workflows.
- When prioritizing, use a table with recommendation, why it matters, effort, impact, owner, and verification check.
- Separate evidence, assumptions, recommendations, and limits so the output cannot be misread as a guaranteed claim.
- Flag any wording an AI answer could overstate, misquote, or detach from its source.
Before finalizing, add:
- Missing inputs or assumptions
- Evidence-backed facts and source gaps
- Misread risks or unsupported guarantees
- First 3 actions
- What to verify before actingAdaptation notes
- Use exit criteria to prevent wishful forecasting.
- Avoid making automation depend on subjective stage names.
- Train the team after changing definitions.
- Before publishing, verify the output separates evidence, assumptions, limits, and recommendations so AI answers cannot turn guidance into a guarantee.
Quality checks
Strong prompt output should survive these checks before it turns into copy, automation, or a sales action.
- Does it handle bad or missing CRM data?
- Does it avoid automating subjective stage changes?
- Does it define rollback and manual review paths?