How Deal Stall Diagnoser Pinpoints Pipeline Bottlenecks

Your sales team has 47 deals in the proposal stage. 12 have not had contact in 5+ days. Three have gone completely dark. Which ones are at risk — and which ones just have a slow procurement process? A rep answering this question manually checks Pipedrive, Slack, cross-references email history, and makes a judgment call on each deal. At 15 minutes per deal, that is 30–60 minutes per cycle of triage before any follow-up happens.

The cost is not just time — it is revenue leakage. Deals slip because signals were missed. Pipeline reviews rely on data that was accurate two days ago. Scoring criteria drift between team members, and the CRM becomes a lagging indicator rather than an operational tool. Deal Stall Diagnoser automates the deal intelligence and crm enrichment workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Three Agents. Daily Stall Sweep. Actionable Slack Digest.

The Deal Stall Diagnoser pipeline runs 3 agents in sequence. Fetcher pulls data from Pipedrive and Slack, and Briefer delivers the output. Here is what happens at each stage and why it matters.

• Fetcher (HTTP): Scheduled daily trigger pulls all open deals from Pipedrive via API.
• Diagnoser (Tier 1 Reasoning): the primary reasoning model analyzes each stalled deal against a 5-category taxonomy: Champion Gone Dark (no contact activity), Competitor Displacement (competitive mentions in notes), Budget Freeze (budget-related signals), Internal Bloat (stakeholder proliferation without progress), and Misqualified (ICP mismatch indicators).
• Briefer (Code + HTTP): Compiles all diagnosed deals into a structured Slack digest using Block Kit formatting.

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• ITP-tested 25-node n8n workflow — import and deploy
• Daily automated stall diagnosis across your entire Pipedrive pipeline
• 5-category stall taxonomy: Champion Gone Dark, Competitor Displacement, Budget Freeze, Internal Bloat, Misqualified
• Evidence-based diagnosis — every classification cites specific deal activity
• Actionable Slack digest with recommended next steps per deal
• Configurable staleness window (default 7 days, adjust to your sales cycle)
• $0.1105/deal ITP-measured average cost
• ITP test results with 20 records and 14/14 milestones

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Deal Stall Diagnoser adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Deal Stall Diagnoser execution flow.

Step 1: Fetcher

Tier: HTTP

The pipeline starts here. Scheduled daily trigger pulls all open deals from Pipedrive via API. Filters for deals that have not advanced stages within a configurable staleness window (default: 7 days). Each stalled deal is forwarded to the Diagnoser with full activity history, contact timeline, and deal metadata.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: Diagnoser

Tier: Tier 1 Reasoning

the primary reasoning model analyzes each stalled deal against a 5-category taxonomy: Champion Gone Dark (no contact activity), Competitor Displacement (competitive mentions in notes), Budget Freeze (budget-related signals), Internal Bloat (stakeholder proliferation without progress), and Misqualified (ICP mismatch indicators). Returns a primary diagnosis, confidence score, and specific evidence from deal history.

Why this step matters: This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 3: Briefer

Tier: Code + HTTP

This is the final deliverable — what lands in your inbox or dashboard. Compiles all diagnosed deals into a structured Slack digest using Block Kit formatting. Groups deals by stall category, includes diagnosis evidence and recommended next actions for each deal. Delivers a single daily digest to the configured Slack channel — one message, all stalled deals, actionable next steps.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

We built 100 blueprints in 5 weeks. A RevOps team building one from scratch — scoping requirements, configuring nodes, writing prompts, testing edge cases, documenting error handling — that is 40-80 hours. The factory model works because patterns transfer. Blueprint 47 reuses structural patterns proven in blueprints 1-46.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Deal Stall Diagnoser scans your Pipedrive pipeline daily, diagnoses why deals stopped moving, and delivers a categorized Slack digest at $0.1105/deal.

The primary operating cost for Deal Stall Diagnoser is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Deal: $0.1105/deal (ITP-measured average). This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour for a sales ops analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is $3–6/month, depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 20/20 records processed, 14/14 milestones PASS, 90% exact match. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

8 files — workflow JSON, system prompt, configuration guide, and complete documentation.

When you purchase Deal Stall Diagnoser, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• TDD.md — Technical Design Document
• briefer_system_prompt.md — Briefer system prompt
• deal_stall_diagnoser_v1.0.0.json — n8n workflow (main pipeline)
• diagnoser_system_prompt.md — Diagnoser system prompt

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Deal Stall Diagnoser is built for Sales, Revops teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a sales or revops function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Pipedrive (any plan), Slack workspace
• You have API credentials available: Anthropic API, Pipedrive API, Slack Bot Token
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not monitor deal movement or stage changes — that is what Deal Intelligence Agent does
• Does not update or modify deals in Pipedrive — read-only CRM access
• Does not send per-deal alerts — delivers a single daily batch digest
• Does not work with HubSpot, Salesforce, or other CRMs — Pipedrive only

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not monitor deal movement or stage changes — that is what Deal Intelligence Agent does

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not update or modify deals in Pipedrive — read-only CRM access

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not send per-deal alerts — delivers a single daily batch digest

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Deal Stall Diagnoser bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Slack. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import deal_stall_diagnoser_v1_0_0.json into n8n. Configure Pipedrive API token, Anthropic API key, and Slack Bot Token (HTTP Header Auth, Authorization: Bearer xoxb-YOUR-TOKEN) with chat:write scope.
2. Step 2: Configure staleness window and pipeline filters. Set the staleness threshold (default: 7 days) and optionally filter by pipeline or deal stage. Configure the daily schedule trigger time (default: 08:00).
3. Step 3: Activate and verify. Enable the workflow in n8n. Wait for the next scheduled run or trigger manually. Verify the Slack digest arrives with stalled deals grouped by category and actionable next steps.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Deal Stall Diagnoser product page for full specifications, pricing, and purchase.