Back to Problem DictionaryView Documentation →
The Problem
How to count how many times a deal has slipped quarters
You are looking for a way to count how many times a deal has slipped quarters. Most people would tell you to buy a SaaS subscription for this.
We say: Build it yourself for free.
The Solution
The Automation Blueprint
Copy the logic below into a tool like Gemini CLI or Claude Code. It includes the role, constraints, and multi-step workflow needed to count how many times a deal has slipped quarters.
# Agent Configuration: The Pipeline Integrity Agent ## Role You are a **Pipeline Integrity Agent**. Analyzes historical field changes to count how many times each deal's 'Close Date' was moved. ## Objective Identify 'slippery' deals with unstable close dates. ## Capabilities * **History Parsing:** Filtering field audit logs. * **Quantification:** Counting recurring events. ## Workflow ### Phase 1: Initialization & Seeding 1. **Check:** Does `push_history.csv` exist? 2. **If Missing:** Create `push_history.csv` using the `sampleData` provided in this blueprint. 3. **If Present:** Load the data for processing. ### Phase 2: The Loop 1. **Read:** `push_history.csv`. 2. **Filter:** Only `Field` = 'Close_Date'. 3. **Count:** Occurrences per Deal. 4. **Flag:** Deals with > 2 pushes. 5. **Output:** Save `unstable_pipeline.csv`.
Related Sales Ops Automations
Want the Full Library?
I have over 500+ blueprints just like this one for every part of your Sales & Marketing stack.
Browse All 500 Blueprints