Weekly CRM Pipeline Health Summarizer
Transform raw CRM deal stage changes into a concise, analytical pipeline health report for sales leadership.
Customise & copy
Add the context you have. The prompt updates as you work.
Paste the raw list of deals with stage movements, timestamps, sizes, and owners.
Specify the team, region, or segment this report covers.
Define the threshold or flag criteria used for stalled deals.
Select the context where this summary will be presented.
Live prompt
4 fieldsAnalyze the provided weekly CRM deal stage changes to generate a concise pipeline health summary for sales leadership. Stick strictly to the data provided and avoid inventing metrics, revenue figures, or deal movements. Target Report Format: 1. Executive Overview: Total pipeline volume added, advanced, and lost based on Acme Corp: Discovery -> Demo, $50k ARR, FinTech, AE: John Doe, Stalled: 12 days Globex: Proposal -> Closed Lost, $120k ARR, Healthcare, AE: Jane Smith, Stalled: 45 days. 2. Stage Progression Velocity: Analysis of deals moving forward versus backward, segmented by Enterprise North America. 3. Bottleneck Identification: Highlight key bottlenecks where deals are stalling, referencing the Deals in current stage > 30 days. 4. Actionable Recommendations: Direct, analytical suggestions for pipeline acceleration to be discussed during the Weekly Executive Pipeline Sync. Tone and Constraints: - Maintain a professional, direct, and analytical tone with zero sales hype or motivational filler. - Focus strictly on overall pipeline health, not individual rep performance.
Proof before you use it
A real example
Tested on gemini-3.1-flash-lite on 2026-09-02
{
"deal_data": "Stark Industries: Demo -> Evaluation, $250k ARR, Manufacturing, AE: Tony S., Stalled: 5 days\nWayne Enterprises: Evaluation -> Negotiation, $500k ARR, Defense, AE: Bruce W., Stalled: 35 days\nLexCorp: Qualification -> Closed Lost, $100k ARR, Tech, AE: Lex L., Stalled: 10 days",
"meeting_type": "Weekly Executive Pipeline Sync",
"pipeline_segment": "Global Strategic Accounts",
"stalled_deals_context": "Deals exceeding 30 days in stage"
}A small ritual that works
How to use it
- 01Paste your raw CRM deal stage export into the 'Raw Deal Stage Data' field.
- 02Define your pipeline segment and the threshold for what constitutes a 'stalled' deal.
- 03Select the specific meeting type to tailor the tone and focus of the recommendations.
- 04Generate the report and copy the structured summary directly into your meeting brief.
Why it works
The prompt establishes a strict, professional reporting format and enforces constraints against sales hype and motivational filler. By tying sections directly to specific placeholder variables (like deal_data, pipeline_segment, and stalled_deals_context), it forces the model to ground its outputs in the supplied CRM inputs rather than generic sales advice.
Where it fails
The prompt lacks instructions regarding the treatment of closed-won or closed-lost deals in pipeline volume totals and segment definitions, which leads the models to hallucinate segment classifications (e.g., SMB vs. Mid-Market), mislabel closed-lost deals as active, and speculate on unprovided financial targets and causal factors.
Customisation tips
Explicitly define how 'closed-won' and 'closed-lost' deals should impact pipeline volume calculations (e.g., whether they add to total active pipeline or represent outflow) and restrict recommendations to purely logistical next steps instead of speculative root causes.
Watch-outs
- Models may invent external business standards, such as 'standard operational timeframes,' that do not exist in the raw CRM text.
- Models often extrapolate unprovided segment tiers (such as SMB or Enterprise) from simple industry tags.
- Models can mischaracterize terminal states (like Closed Lost) as requiring ongoing monitoring.
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.