How Customer Renewal Intelligence Agent Scores Readiness

Weekly renewal intelligence with 5-dimension scoring, 4-tier readiness classification, and personalized outreach drafts from Stripe + Pipedrive. That single sentence captures a workflow gap that costs customer success, revops teams hours every week. The manual process behind what Customer Renewal Intelligence Agent automates is familiar to anyone who has worked in a revenue organization: someone pulls data from Stripe, Pipedrive, Gmail, 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 customer success, revops teams handling renewal management and churn prevention 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 Customer Renewal Intelligence Agent fills.

Five Agents. Weekly Renewal Scoring. Personalized Outreach Drafts.

Customer Renewal Intelligence Agent is a 31-node n8n workflow with 5 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:

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

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

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

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

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 The Assembler 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: 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.

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 The Analyst 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 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.

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 The Writer 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 5: The Formatter

Tier: 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.

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 The Formatter 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.

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 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 $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 Weekly cost ~$0.25/run (~$1.00/month), depending on your usage volume and plan tiers.

Quality assurance: 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.

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.

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.