Pipedrive Lost Reason Trend Analyzer

AI-powered monthly loss reason trend analysis — top reasons by deal value, trending patterns, stage-of-loss concentration, segment divergence, and actionable interventions.

Analyzes Pipedrive lost deals monthly to identify why you are losing and whether it is getting better or worse. Ranks loss reasons by deal value impact, tracks MoM trends, maps reasons to deal stages, compares enterprise vs SMB patterns, and generates specific process/training/product interventions per top reason. Notion loss analysis report + Slack executive summary. 24-node n8n workflow with monthly scheduler. BQS 12/12 certified.

triggerSchedule01FetcherPipedrive API02Assembler5 Dimensions03AnalystLoss Patterns04FormatterBrief + DigestNotionLoss BriefSlackAction Digest

Four Agents. Monthly Loss Pattern Intelligence. Actionable Interventions.

The Fetcher

Step 1The 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.

The Assembler

Step 2The Assembler

Code-only

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).

The Analyst

Step 3The Analyst

Tier 2 Classification

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.

The Formatter

Step 4The Formatter

Tier 3 Creative

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.

What It Does NOT Do

×

Does not modify deals in Pipedrive — read-only analysis of lost deal records

×

Does not predict which active deals will be lost — it analyzes historical loss patterns

×

Does not replace win/loss review meetings — it provides data-driven loss intelligence for those discussions

×

Does not auto-implement interventions — it recommends process changes for human decision-making

×

Does not analyze won deals — use Win Rate Trend Analyzer (#87) for win rate intelligence

The Complete Customer Success Bundle

6 files. Main workflow + scheduler + prompts + docs.

pipedrive_lost_reason_trend_analyzer_v1_0_0.jsonMain workflow (24 nodes)
pipedrive_lost_reason_trend_analyzer_scheduler_v1_0_0.jsonScheduler workflow (3 nodes)
README.md10-minute setup guide
docs/TDD.mdTechnical Design Document
system_prompts/analyst_system_prompt.mdAnalyst prompt (loss pattern analysis)
system_prompts/formatter_system_prompt.mdFormatter prompt (Notion + Slack)

Tested. Measured. Documented.

Monthly lost deal reason analysis with reason rankings, trending reason detection, stage-of-loss breakdown, segment patterns, and actionable interventions delivered via Notion and Slack.

Pipedrive Lost Reason Trend Analyzer v1.0.0──────────────────────────────────────────Nodes:        24 main + 3 scheduler (27 total)Agents:       4 (Fetcher, Assembler, Analyst, Formatter)LLM Calls:    2 per run (Analyst + Formatter)Model:        Sonnet 4.6 (SINGLE-MODEL)Trigger:      Schedule (monthly 1st 9:00 UTC) + WebhookPattern:      BATCH (monthly loss pattern analysis)Tool A:       Pipedrive (pipedriveApi) — lost deals, reasons, stages, segmentsTool B:       Notion (httpHeaderAuth) — monthly lost reason intelligence reportTool C:       Slack (httpHeaderAuth) — digest with top 3 loss prevention actionsITP:          8/8 records, 14/14 milestonesBQS:          12/12 PASSCost:         $0.03–$0.10 per run

What You'll Need

Platform

n8n 2.7.5+

Est. Monthly API Cost

Monthly cost ~$0.03-0.10/run

Credentials Required

  • Anthropic API
  • Pipedrive (API token, pipedriveApi)
  • Slack (Bot Token, httpHeaderAuth Bearer)
  • Notion (httpHeaderAuth Bearer)

Services

  • Pipedrive CRM with lost reason tracking enabled
  • Anthropic API key
  • Notion workspace
  • Slack workspace (Bot Token with chat:write)

Setup Track

Quick Start

~15 min

All credentials live, n8n running

Full Setup

1–2 hrs

Needs API config + tables

From Scratch

2–4 hrs

No n8n, no credentials

Pipedrive Lost Reason Trend Analyzer v1.0.0

$199

one-time purchase

What you get:

  • Production-ready n8n workflow (24 nodes + 3-node scheduler)
  • 5-dimension loss pattern analysis (top reasons by value, trending reasons, stage of loss, segment patterns, actionable interventions)
  • Lost reason ranking by total deal value impact with MoM trend
  • Trending reason detection showing which loss reasons are growing fastest
  • Stage-of-loss breakdown identifying where in the funnel deals die
  • Segment-specific loss patterns revealing vertical or segment vulnerabilities
  • Actionable intervention recommendations mapped to each top loss reason
  • Notion monthly lost reason intelligence report with full analysis
  • Slack digest with top 3 loss prevention actions
  • Configurable: pipeline selection, reason mapping, segment fields, lookback period
  • Full technical documentation and system prompts

Frequently Asked Questions

What are the 5 loss pattern dimensions?+

Top reasons by value ranks lost reasons by total deal value impact. Trending reasons identifies reasons growing in frequency month-over-month. Stage of loss shows which pipeline stages see the most losses. Segment patterns reveals loss reasons specific to deal segments or verticals. Actionable interventions maps specific process changes to each top reason.

Does it require Pipedrive lost reason tracking?+

Yes. The Fetcher relies on the Pipedrive "lost reason" field being populated when deals are marked as lost. If your team does not consistently record lost reasons, the analysis will be incomplete. The workflow flags deals with missing reasons as a data quality indicator.

How does it differ from Win Rate Trend Analyzer?+

Win Rate Trend Analyzer (#87) focuses on win rate trends, segment shifts, and conversion funnels. Lost Reason Trend Analyzer focuses specifically on why deals are lost, which reasons are trending, and what interventions could prevent future losses. They complement each other for a full win/loss picture.

Is there a refund policy?+

All sales are final after download. Review the Blueprint Dependency Matrix and prerequisites before purchase. Questions? Contact support@forgeworkflows.com before buying. Full terms at forgeworkflows.com/legal.

Read the full guide →

Related Blueprints