How Deal Stall Diagnoser Automates Deal Intelligence

Diagnose why deals stall. Get unstuck. That single sentence captures a workflow gap that costs sales, revops teams hours every week. The manual process behind what Deal Stall Diagnoser automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Pipedrive, Slack, copies it into a spreadsheet or CRM, applies a mental checklist, writes a summary, and routes it to the next person in the chain. Repeat for every record. Every day.

Three problems make this unsustainable at scale. First, the process does not scale. As volume grows, the human bottleneck becomes the constraint. Whether it is inbound leads, deal updates, or meeting prep, a person can only process a finite number of records before quality degrades. Second, the process is inconsistent. Different team members apply different criteria, use different formats, and make different judgment calls. There is no single standard of quality, and the output varies from person to person and day to day. Third, the process is slow. By the time a manual review is complete, the window for action may have already closed. Deals move, contacts change roles, and buying signals decay.

These are not theoretical concerns. They are the operational reality for sales, revops teams handling deal intelligence and crm enrichment workflows. Every hour spent on manual data processing is an hour not spent on the work that actually moves the needle: building relationships, closing deals, and driving strategy.

This is the gap Deal Stall Diagnoser fills.

Three Agents. Daily Stall Sweep. Actionable Slack Digest.

Deal Stall Diagnoser is a multiple-node n8n workflow with 3 specialized agents. Each agent handles a distinct phase of the pipeline, and the handoff between agents is deterministic — no ambiguous routing, no dropped records. The blueprint is designed so that each agent does one thing well, and the overall pipeline produces a consistent, auditable output on every run.

Here is what each agent does:

• 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. Specifically, you receive:

• Production-ready 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

Every component is designed to be modified. The agent prompts are plain text files you can edit. The workflow nodes can be rearranged or extended. The scoring criteria, output formats, and routing logic are all exposed as configurable parameters — not buried in application code. 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

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 is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Fetcher identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

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.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Diagnoser identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

Step 3: Briefer

Tier: Code + HTTP

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.

This stage is critical because it ensures that downstream agents receive structured, validated input. Each agent in the pipeline trusts the output contract of the previous agent. If Briefer identifies an issue — a missing field, a low-confidence score, or an unexpected input format — the pipeline handles it explicitly rather than passing garbage downstream. This is the difference between a prototype and a production-grade workflow: every handoff is defined, every edge case is documented.

The entire pipeline executes without manual intervention. From trigger to output, every decision point is deterministic: if a condition is met, the next agent fires; if not, the record is handled according to a documented fallback path. There are no silent failures. Every execution produces a traceable audit trail that you can review, export, or feed into your own reporting tools.

This architecture follows the ForgeWorkflows principle of tested, measured, documented automation. Every node in the pipeline has been validated during ITP (Inspection and Test Plan) testing, and the error handling matrix in the bundle documents the recovery path for each failure mode.

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 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 at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 20–40 minutes per cycle, that is $17–50 per execution in human labor. 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: 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.

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:

• deal_stall_diagnoser_v1_0_0.json — The 25-node n8n workflow
• README.md — 10-minute setup guide with Pipedrive and Slack configuration
• system_prompt_diagnoser.txt — Diagnoser system prompt (5-category taxonomy, evidence extraction, CoT-enforced)
• staleness_config_guide.md — Staleness window and pipeline filter configuration
• slack_setup_guide.md — Slack Bot Token setup with chat:write scope
• itp_results.md — ITP test results — 20 records, 14/14 milestones, 90% exact match
• blueprint_dependency_matrix.md — Prerequisites and cost estimates
• CHANGELOG.md — Version history

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.

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.