Pipedrive Lost Reason Trend Analyzer

Step 1 — The Fetcher

Code-only

Retrieves lost deal data from Pipedrive API for the current and prior months — lost reason, deal value, pipeline stage at loss, segment tags, source attribution, owner, and close dates. Pulls historical lost deal records for trend and pattern analysis.

Step 2 — The Assembler

Code-only

What does The Assembler actually decide? Computes 5 loss pattern dimensions: top reasons by value (lost reasons ranked by total deal value impact), trending reasons (reasons with growing frequency MoM), stage of loss (which pipeline stages see most losses), segment patterns (loss reasons by deal segment/vertical), and actionable interventions (specific process changes mapped to each loss reason).

Step 3 — The Analyst

Tier 2 Classification

This step exists because raw data alone is not enough. Analyzes loss patterns for actionable insights: which reasons are growing fastest, where in the funnel deals die most, which segments have unique loss patterns, and what specific interventions could address each top reason. Generates prioritized intervention recommendations with estimated impact.

Step 4 — The Formatter

Tier 3 Creative

Without this step, upstream analysis sits idle. Generates a Notion monthly lost reason intelligence report with reason rankings, trend analysis, stage-of-loss breakdown, segment patterns, and intervention recommendations, plus a Slack digest with top 3 loss prevention actions.When 3 of 10 leads scored below threshold, the fix was the pipeline, not the criteria. Acceptance criteria is locked — no post-hoc relaxation.