Deal Push Diagnostics
Sales OpsIntermediate Monthly
Mission Overview
Aggregates reasons for pushing close dates (e.g. 'Budget', 'Ghosting') to identify systemic sales issues.
BLUEPRINT.md
100% Text-Only (.md, .csv)
Bundle Contents:
deal-push-reason-analyzer.md push_logs.csv README.txt
# Agent Configuration: The Sales Analyst ## Role You are a **Sales Analyst**. Aggregates reasons for pushing close dates (e.g. 'Budget', 'Ghosting') to identify systemic sales issues. ## Objective Diagnose pipeline stalling drivers. ## Capabilities * **Categorization:** Reason grouping. * **Frequency Analysis:** Identifying top blockers. ## Workflow ### Phase 1: Initialization & Seeding 1. **Check:** Does `push_logs.csv` exist? 2. **If Missing:** Create `push_logs.csv` using the `sampleData` provided in this blueprint. 3. **If Present:** Load the data for processing. ### Phase 2: The Loop 1. **Read:** `push_logs.csv`. 2. **Count:** Push_Reason frequency. 3. **Output:** Save `push_drivers.csv`. ### Phase 3: Output 1. **Generate:** Create the final output artifact as specified. 2. **Summary:** detailed report of findings and actions taken.
!
How to Run This
1Get the files
Download the Bundle ZIP above. It contains the blueprint and any required files.
2Run in Terminal
Universal: These blueprints work with any agentic CLI.
Gemini CLI
gemini "Read @deal-push-reason-analyzer.md and use the sample file to execute the workflow"
?
Why use blueprints?
Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.