How Proposal Follow-Up Automator Automates Deal Recovery

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, Gmail, 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. Proposal Follow-Up Automator automates the deal recovery and follow up automation workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Five Agents. Daily Stall Classification. Personalized Follow-Up Drafts.

The Proposal Follow-Up Automator pipeline runs 5 agents in sequence. The Fetcher pulls data from Pipedrive and Gmail and Slack, and The Dispatcher delivers the output. Here is what happens at each stage and why it matters.

• The Fetcher (Code-only): Retrieves all active deals at the configured proposal stage from Pipedrive API — deal value, contact details, activity history, stage entry date, and last communication timestamp.
• The Classifier (Tier 1 Reasoning): Classifies each stalled deal into one of 4 stall reason categories: decision_delay (stakeholder alignment stalled), budget_review (procurement or finance hold), champion_ghosting (primary contact unresponsive), or competitor_evaluation (active competitive comparison).
• The Scorer (Code-only): Computes urgency tier for each stalled deal: CRITICAL (≥7 days stalled), WARNING (4-6 days), or MONITOR (3 days).
• The Writer (Tier 3 Creative): Generates personalized follow-up email drafts tailored to each stall reason category.
• The Dispatcher (Code-only): Creates Gmail draft emails for each stalled deal (draft mode by default, configurable to auto-send) and posts a daily Slack digest with stall counts by category, urgency distribution, and top 5 deals requiring immediate attention..

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 n8n workflow (28 nodes + 3-node scheduler)
• 4-category stall reason classification (decision_delay, budget_review, champion_ghosting, competitor_evaluation)
• 3-tier urgency scoring (CRITICAL ≥7d, WARNING 4-6d, MONITOR 3d)
• Personalized follow-up email drafts tailored to each stall reason
• Configurable follow-up limit to prevent over-contact
• Gmail draft creation (or auto-send) with deal context
• Daily Slack digest with stall counts and top 5 urgent deals
• Configurable: proposal stage name, stale threshold, follow-up limit, draft mode
• Full technical documentation and system prompts

Scoring thresholds, output destinations, and CRM field mappings are configurable in the system prompts — no workflow JSON edits required. This means Proposal Follow-Up Automator 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 Proposal Follow-Up Automator execution flow.

Step 1: The Fetcher

Tier: Code-only

The pipeline starts here. Retrieves all active deals at the configured proposal stage from Pipedrive API — deal value, contact details, activity history, stage entry date, and last communication timestamp. Calculates days-since-last-activity for stall detection threshold comparison.

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: The Classifier

Tier: Tier 1 Reasoning

Classifies each stalled deal into one of 4 stall reason categories: decision_delay (stakeholder alignment stalled), budget_review (procurement or finance hold), champion_ghosting (primary contact unresponsive), or competitor_evaluation (active competitive comparison). Uses deal activity patterns, email response gaps, and stage duration signals.

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

Step 3: The Scorer

Tier: Code-only

Computes urgency tier for each stalled deal: CRITICAL (≥7 days stalled), WARNING (4-6 days), or MONITOR (3 days). Factors in deal value, stall reason category, and number of prior follow-up attempts. Enforces configurable follow-up limit to prevent over-contact.

Every field in the output is structured for the next agent to consume without parsing.

Step 4: The Writer

Tier: Tier 3 Creative

Generates personalized follow-up email drafts tailored to each stall reason category. Decision delay gets stakeholder alignment hooks, budget review gets ROI reinforcement, champion ghosting gets multi-thread outreach, competitor evaluation gets differentiation talking points. Each draft includes the deal context and specific next-step recommendations.

Why this step matters: This step narrows the dataset so downstream agents only process records that matter.

Step 5: The Dispatcher

Tier: Code-only

This is the final deliverable — what lands in your inbox or dashboard. Creates Gmail draft emails for each stalled deal (draft mode by default, configurable to auto-send) and posts a daily Slack digest with stall counts by category, urgency distribution, and top 5 deals requiring immediate attention.

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.

41% dead letter rate from a brace-matching parser. The model would embed JSON inside prose, or start JSON after a preamble, or include trailing text. Progressive extraction tries JSON.parse starting from each opening brace position in the string. First valid parse wins. Dead letter rate dropped from 41% to 11%.

— ForgeWorkflows Engineering

Daily proposal follow-up with 4-category stall classification, 3-tier urgency scoring, and personalized email drafts delivered via Gmail and Slack.

The primary operating cost for Proposal Follow-Up Automator is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.015 per deal. 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 Daily cost ~$0.015/deal (~$10-15/month for 30+ deals/day), 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, all milestones PASS. 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.

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

When you purchase Proposal Follow-Up Automator, 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
• docs/TDD.md — Technical Design Document
• proposal_follow_up_automator_v1_0_0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/writer_system_prompt.md — Writer system prompt
• workflow/pfa_scheduler_v1_0_0.json — Scheduler workflow

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.

Proposal Follow-Up Automator 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 CRM with active pipeline, Anthropic API key, Gmail account, Slack workspace (Bot Token with chat:write)
• You have API credentials available: Anthropic API, Pipedrive (API Token), Gmail (OAuth2), Slack (Bot Token, httpHeaderAuth Bearer, chat:write)
• 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 modify deal stages or values — read-only analysis with email drafts as output
• Does not replace human judgment on when to send — draft mode lets reps review before sending
• Does not predict deal outcomes — it classifies current stall reasons and generates follow-up content
• Does not monitor real-time deal changes — daily batch analysis at configured schedule
• Does not handle initial outreach — designed for deals already at proposal stage that have stalled

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 modify deal stages or values — read-only analysis with email drafts as output

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 replace human judgment on when to send — draft mode lets reps review before sending

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 predict deal outcomes — it classifies current stall reasons and generates follow-up content

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 Proposal Follow-Up Automator bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Gmail, Slack. Here is the recommended deployment path:

1. Step 1: Import workflows and configure credentials. Import both workflow JSON files into n8n (main + scheduler). Configure Pipedrive API Token, Gmail OAuth2, Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), and Anthropic API key following the README.
2. Step 2: Configure proposal stage and thresholds. Set PROPOSAL_STAGE_NAME (your Pipedrive stage name for proposals), STALE_THRESHOLD_DAYS (default 3), FOLLOW_UP_LIMIT (default 3), GMAIL_DRAFT_MODE (default true), and SLACK_CHANNEL in the scheduler Build Payload node.
3. Step 3: Activate scheduler and verify. Update the webhook URL in the scheduler to match your main workflow webhook path. Activate both workflows. Send a test POST with _is_itp: true and sample deal data. Verify Gmail drafts are created and the Slack digest appears.

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 Proposal Follow-Up Automator product page for full specifications, pricing, and purchase.