How Customer Renewal Intelligence Agent Scores Readiness

Your support team closed 340 tickets last week. Average resolution time: 4.2 hours. But 23 of those tickets were escalations that sat for 6+ hours before anyone noticed the SLA clock. A team lead spends 1–2 hours daily pulling reports from Stripe, Pipedrive, Gmail, Slack, cross-referencing with CRM data, and writing up findings. By the time the analysis is done, the queue has moved on.

The result is reactive support instead of proactive operations. SLA risks surface after the breach. Routing problems persist because nobody has time to audit the rules. Agent coaching happens based on gut feel, not pattern data. Customer Renewal Intelligence Agent automates the renewal management and churn prevention workflow, delivering structured analysis from Stripe, Pipedrive, Gmail, Slack data without manual report-building.

Five Agents. Weekly Renewal Scoring. Personalized Outreach Drafts.

The Customer Renewal Intelligence Agent pipeline runs 5 agents in sequence. The Fetcher pulls data from Stripe and Pipedrive and Gmail and Slack, and The Formatter delivers the output. Here is what happens at each stage and why it matters.

• The Fetcher (Code-only): Retrieves customer data from Stripe (subscription status, billing history, payment patterns, MRR, plan tier) and Pipedrive (deal history, activity recency, contact engagement, support interactions).
• The Assembler (Code-only): Computes 5 renewal intelligence dimensions: billing_health (25%) — payment consistency and dunning history, engagement_depth (25%) — login frequency, feature usage, support ticket trends, expansion_signals (20%) — usage growth, seat additions, plan upgrade inquiries, risk_flags (20%) — payment failures, support escalations, usage decline, renewal_readiness (10%) — contract alignment and stakeholder responsiveness..
• The Analyst (Tier 2 Classification): Classifies each customer into a Renewal Readiness Score tier: EXPAND (≥8) — upsell candidates, RENEW (6-7) — standard renewal, AT_RISK (4-5) — needs CS intervention, CHURN_LIKELY (<4) — urgent save required.
• The Writer (Tier 3 Creative): Generates personalized outreach email drafts for each customer based on their RRS tier.
• The Formatter (Code-only): Creates Gmail draft emails for each customer requiring outreach and posts a weekly Slack summary with renewal pipeline health: customer count by tier, total MRR at risk, top 5 accounts needing immediate attention, and week-over-week tier movement..

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)
• 5-dimension renewal intelligence scoring (billing_health, engagement_depth, expansion_signals, risk_flags, renewal_readiness)
• 4-tier Renewal Readiness Score (EXPAND ≥8, RENEW 6-7, AT_RISK 4-5, CHURN_LIKELY <4)
• Personalized outreach drafts per RRS tier with account-specific context
• Cross-system customer profile from Stripe + Pipedrive
• Gmail draft creation with tier-appropriate messaging
• Weekly Slack summary with MRR at risk and tier distribution
• Configurable: renewal window, expansion/risk/churn thresholds, draft mode
• Full technical documentation and system prompts

SLA thresholds, escalation rules, and routing logic are configurable in the system prompts — customize for your ticket volume and priority structure. This means Customer Renewal Intelligence 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 Customer Renewal Intelligence Agent execution flow.

Step 1: The Fetcher

Tier: Code-only

The pipeline starts here. Retrieves customer data from Stripe (subscription status, billing history, payment patterns, MRR, plan tier) and Pipedrive (deal history, activity recency, contact engagement, support interactions). Identifies customers within the configurable renewal window and assembles a unified customer profile for scoring.

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 Assembler

Tier: Code-only

Computes 5 renewal intelligence dimensions: billing_health (25%) — payment consistency and dunning history, engagement_depth (25%) — login frequency, feature usage, support ticket trends, expansion_signals (20%) — usage growth, seat additions, plan upgrade inquiries, risk_flags (20%) — payment failures, support escalations, usage decline, renewal_readiness (10%) — contract alignment and stakeholder responsiveness.

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: The Analyst

Tier: Tier 2 Classification

Classifies each customer into a Renewal Readiness Score tier: EXPAND (≥8) — upsell candidates, RENEW (6-7) — standard renewal, AT_RISK (4-5) — needs CS intervention, CHURN_LIKELY (<4) — urgent save required. Generates per-customer renewal strategy recommendations with specific talking points.

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 outreach email drafts for each customer based on their RRS tier. EXPAND customers get upsell proposals, RENEW gets value reinforcement, AT_RISK gets proactive check-in, CHURN_LIKELY gets executive attention templates. Each draft references specific account data and recommended actions.

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

Step 5: The Formatter

Tier: Code-only

This is the final deliverable — what lands in your inbox or dashboard. Creates Gmail draft emails for each customer requiring outreach and posts a weekly Slack summary with renewal pipeline health: customer count by tier, total MRR at risk, top 5 accounts needing immediate attention, and week-over-week tier movement.

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.

n8n's webhook v2 nests data under a body key. The webhook receives { body: { email: "..." } } instead of { email: "..." }. Two lines of defensive code prevent the most common deployment failure: const data = raw.body || raw. Every blueprint ships with this guard.

— ForgeWorkflows Engineering

Weekly renewal intelligence with 5-dimension scoring, 4-tier readiness classification, and personalized outreach drafts from Stripe + Pipedrive data delivered via Gmail and Slack.

The primary operating cost for Customer Renewal Intelligence Agent is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.25 per run. 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 $40–60/hour for a support team lead’s analysis time at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 1–2 hours daily, 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 Weekly cost ~$0.25/run (~$1.00/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, 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 Customer Renewal Intelligence 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
• customer_renewal_intelligence_agent_v1_0_0.json — n8n workflow (main pipeline)
• docs/TDD.md — Technical Design Document
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/writer_system_prompt.md — Writer system prompt
• workflow/cria_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.

Customer Renewal Intelligence Agent is built for Customer Success, 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 customer success 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: Stripe with active subscriptions, Pipedrive CRM with customer contacts, Anthropic API key, Gmail account, Slack workspace (Bot Token with chat:write)
• You have API credentials available: Anthropic API, Stripe (API Key), 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 Stripe subscriptions or Pipedrive records — read-only analysis with email drafts as output
• Does not automate renewal processing — it identifies risks and generates outreach for human follow-through
• Does not replace CS platforms like Gainsight — it adds renewal intelligence to your existing Stripe + CRM stack
• Does not predict exact churn dates — it scores current renewal health for prioritized CS attention
• Does not handle contract negotiation — focused on pre-renewal intelligence and outreach generation

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 Stripe subscriptions or Pipedrive records — 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 automate renewal processing — it identifies risks and generates outreach for human follow-through

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 replace CS platforms like Gainsight — it adds renewal intelligence to your existing Stripe + CRM stack

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 Customer Renewal Intelligence Agent bundle is designed for the following tools: n8n, Anthropic API, Stripe, 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 Stripe API Key, 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 renewal window and thresholds. Set RENEWAL_WINDOW_DAYS (default 60), EXPANSION_THRESHOLD (default 8), RISK_THRESHOLD (default 5), CHURN_THRESHOLD (default 4), GMAIL_DRAFT_MODE (default true), SLACK_CHANNEL, and STRIPE_API_KEY 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 customer data. Verify Gmail drafts are created and the Slack renewal summary 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 Customer Renewal Intelligence Agent product page for full specifications, pricing, and purchase.