How Lost Deal Re-Activation Agent Times Outreach Revival

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, 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. Lost Deal Re-Activation Agent automates the deal intelligence and crm enrichment workflow from data extraction through analysis to structured output, with zero manual CRM entry.

Four Agents. Weekly Closed-Lost Scan. Reasoned Re-Opening Outreach.

The Lost Deal Re-Activation Agent pipeline runs 4 agents in sequence. Fetcher pulls data from Pipedrive and Gmail, and Ghostwriter delivers the output. Here is what happens at each stage and why it matters.

• Fetcher (HTTP): Weekly scheduled trigger pulls all Closed-Lost deals from Pipedrive aged 30–90 days.
• Researcher (Tier 1 Reasoning + Web Search): the primary reasoning model researches each prospect company via web search for condition changes since the deal was lost: new funding rounds, leadership changes, competitor exits, org restructures, and market shifts.
• Analyst (Tier 1 Reasoning): the primary reasoning model scores each deal on Re-Activation Potential (RAP) across 4 weighted criteria: Condition Change Signal (35%), Original Deal Quality (25%), Relationship Warmth (20%), and Timing Alignment (20%).
• Ghostwriter (Tier 1 Reasoning + HTTP): the primary reasoning model generates a personalized re-opening email that references the specific condition change, acknowledges the original loss context, and proposes a concrete next step.

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 30-node n8n workflow — import and deploy
• Weekly automated scan of Closed-Lost deals aged 30–90 days from Pipedrive
• automated web research for condition changes at prospect companies
• RAP scoring across 4 criteria: Condition Change (35%), Deal Quality (25%), Relationship Warmth (20%), Timing (20%)
• Personalized re-opening emails referencing specific condition changes
• Gmail draft mode by default — rep reviews before sending. Configurable auto-send for high-RAP deals
• $0.26/deal ITP-measured blended 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 Lost Deal Re-Activation Agent 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 Lost Deal Re-Activation Agent execution flow.

Step 1: Fetcher

Tier: HTTP

The pipeline starts here. Weekly scheduled trigger pulls all Closed-Lost deals from Pipedrive aged 30–90 days. Extracts deal metadata, contact details, activity history, loss reason, and deal value. Deals outside the configurable age window are filtered immediately — no wasted processing on stale or too-recent losses.

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: Researcher

Tier: Tier 1 Reasoning + Web Search

the primary reasoning model researches each prospect company via web search for condition changes since the deal was lost: new funding rounds, leadership changes, competitor exits, org restructures, and market shifts. Returns structured evidence with source URLs. No LinkedIn scraping — public news and company announcements only.

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

Step 3: Analyst

Tier: Tier 1 Reasoning

the primary reasoning model scores each deal on Re-Activation Potential (RAP) across 4 weighted criteria: Condition Change Signal (35%), Original Deal Quality (25%), Relationship Warmth (20%), and Timing Alignment (20%). Deals below the configurable RAP threshold are filtered — only high-potential re-activations proceed to outreach.

This is where the pipeline applies judgment — not just data retrieval, but analysis.

Step 4: Ghostwriter

Tier: Tier 1 Reasoning + HTTP

This is the final deliverable — what lands in your inbox or dashboard. the primary reasoning model generates a personalized re-opening email that references the specific condition change, acknowledges the original loss context, and proposes a concrete next step. Creates a Gmail draft by default (rep reviews before sending). Configurable to auto-send for high-RAP deals above a second threshold.

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.

3 of 20 test deals had no activity history — no calls, no emails, no meetings. Without a dead letter queue, those 3 would have crashed the pipeline and blocked the other 17. The dead letter queue caught them; the pipeline processed the other 17 normally. Quarantine bad data, do not let it block good data.

— ForgeWorkflows Engineering

Every metric is ITP-measured. The Lost Deal Re-Activation Agent scans your Pipedrive Closed-Lost pipeline weekly, researches condition changes, scores re-activation potential, and generates personalized re-opening outreach at $0.26/deal.

The primary operating cost for Lost Deal Re-Activation Agent is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Deal: $0.26/deal (ITP-measured blended 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 $5–10/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, 80% exact match, 100% defensible. 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.

10 files — workflow JSON, system prompts, configuration guides, and complete documentation.

When you purchase Lost Deal Re-Activation Agent, 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
• analyst_system_prompt.md — Analyst system prompt
• ghostwriter_system_prompt.md — Ghostwriter system prompt
• lost_deal_reactivation_agent_v1.0.0.json — n8n workflow (main pipeline)
• researcher_system_prompt.md — Researcher 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.

Lost Deal Re-Activation Agent 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), Gmail account
• You have API credentials available: Anthropic API, Pipedrive API, Gmail OAuth2
• 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 active deals or deal movement — that is what Deal Intelligence Agent and Deal Stall Diagnoser do
• Does not scrape LinkedIn or personal social profiles — public news only
• Does not auto-send emails by default — creates Gmail drafts for rep review
• Does not work with HubSpot, Salesforce, or other CRMs — Pipedrive only
• Does not process deals lost more than 90 days ago — configurable window defaults to 30–90 days

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 active deals or deal movement — that is what Deal Intelligence Agent and Deal Stall Diagnoser do

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 scrape LinkedIn or personal social profiles — public news only

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 auto-send emails by default — creates Gmail drafts for rep review

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 Lost Deal Re-Activation Agent bundle is designed for the following tools: n8n, Anthropic API, Pipedrive, Gmail. Here is the recommended deployment path:

1. Step 1: Import workflow and configure credentials. Import lost_deal_reactivation_agent_v1_0_0.json into n8n. Configure Pipedrive API token, Anthropic API key, and Gmail OAuth2 credentials following the setup guide.
2. Step 2: Configure deal age window and RAP threshold. Set the Closed-Lost age window (default: 30–90 days) and RAP score threshold (default: 60/100). Optionally configure auto-send mode for deals above a higher threshold.
3. Step 3: Activate and verify. Enable the workflow in n8n. Wait for the next weekly run or trigger manually. Verify Gmail drafts appear with personalized re-opening emails that reference specific condition changes.

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 Lost Deal Re-Activation Agent product page for full specifications, pricing, and purchase.