CRM OpsUpdated July 4, 2026
Weekly Revenue Ops Summary
Summarize pipeline and follow-up issues into a useful weekly note.
Use case: Use when exporting weekly CRM metrics or sales activity notes.
Prompt
Create a weekly revenue operations summary.
New leads: {{new_leads}}
Won deals: {{won_deals}}
Lost deals: {{lost_deals}}
Stalled deals: {{stalled_deals}}
Follow-up misses: {{follow_up_misses}}
Return:
- 5-bullet executive summary.
- Biggest risk this week.
- Biggest opportunity this week.
- Follow-up actions by priority.
- Data quality issues that affect confidence.
Write for a founder or operator, not a data analyst.
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 counts and examples, not huge exports.
- Separate data quality issues from business performance.
- Keep the summary actionable.
- 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?