Back to Playbooks

Weekly Renewal Risk Sweep

ScoutMaintain
~5 min setup

Example scout operating loop for weekly renewal review. Combine Gremlin renewal checks, export evidence for CSM review, and hand the result to team workflows or a separate governed CRM step.

Architecture guide: How to Generate Renewal Opportunities in Salesforce Safely

Where this fits in Gremlin Scouts

This page is one scout playbook, not the whole scout definition. It is an example operating loop built from Gremlin renewal scouts plus adjacent team workflows.

This example shows a renewal-review operating loop: run the renewal scouts on demand or on a customer-managed schedule, export the evidence, and route the result into customer-success workflows. For the concept hub, start at Gremlin Scouts. For the execution boundary, see Scouts vs. Modules.

The Prompt

It's Monday. I need our weekly renewal risk report before the CS standup at 10am.

Use Gremlin's renewal scouts as the detection layer:
1. Run renewals_due_soon for contracts expiring in the next 90 days
2. Run renewals_due_no_activity for expiring renewals with weak recent activity
3. Merge the findings into one reviewable renewal-risk report
4. Export CSV for CSM review
5. Share a Slack digest and optional Notion summary
6. If we choose to write back to Salesforce, do that as a separate governed step

Run this as a weekly scout workflow on customer-managed infrastructure before the CS standup.

How It Works

1. Run Renewal Horizon Scout

Use renewals_due_soon to find contracts expiring in the next 90 days

2. Run No-Activity Scout

Use renewals_due_no_activity to find expiring renewals with weak recent engagement

3. Export Evidence

Merge scout findings into a CSV for CSM review

4. Optional Governed CRM Write

If needed, write renewal-risk markers through a separate approved step

5. Slack Digest

Share a summary with the customer-success team

6. Notion Summary

Publish the weekly renewal review to the CS workspace

Execution Log

After you paste this prompt, Claude Code:

"Monday morning renewal review. Let me run Gremlin's renewal scouts, merge the findings, and package the CS handoff."

Running
$ g-gremlin scout run renewals_due_soon --param horizon_days=90 --format json --output renewals_due_soon.json
[Scout] Check: renewals_due_soon [Scout] Querying renewals due in the next 90 days... [Scout] 47 contracts found
Running
$ g-gremlin scout run renewals_due_no_activity --param horizon_days=90 --param inactive_days=14 --format json --output renewals_due_no_activity.json
[Scout] Check: renewals_due_no_activity [Scout] 20 renewals flagged with weak recent activity or missing next steps

"Now I will merge the two scout outputs, rank the highest-risk renewals for review, and prepare the handoff for customer success."

Running
$ merge renewal scout findings into one review artifact
[Review] Merged scout findings highlight 20 renewals for CS review across expiring contracts and low-activity accounts

Exporting the merged renewal review to CSV

weekly_renewal_review_2026-02-02.csv generated (20 rows)
Running
$ optional governed Salesforce writeback
[Optional] No Salesforce writeback applied yet. The merged renewal review is ready for approval if the team wants CRM updates.
Running
$ handoff artifact: Slack digest for #customer-success
[Slack] Posted to #customer-success: šŸ“Š Weekly Renewal Risk Sweep - Feb 2, 2026 šŸ”“ HIGH risk: 12 accounts 🟔 MEDIUM risk: 8 accounts Top 5 risks: 1. Acme Corp - NPS 3, 12 support tickets 2. GlobalTech - Usage down 40%, no champion 3. DataSystems - NPS 4, contract ends in 14 days 4. CloudFirst - 8 support tickets, escalated case 5. EnterpriseAI - No activity in 45 days
Running
$ handoff artifact: CS workspace summary
[Workspace] Weekly Renewal Risk - Feb 2, 2026 - Full table with 20 at-risk accounts - Risk breakdown charts - CSM assignment mapping

Weekly renewal scout workflow complete. Expiring renewals and no-activity risk were surfaced, exported, and handed to the CS team for follow-through.

The Result

In this example, a weekly scout workflow identifies expiring renewals and weak-activity accounts, packages the evidence, and delivers it to customer-success workflows. Any CRM writeback remains a separate governed choice.

47
Contracts reviewed
20
At-risk flagged
12
HIGH risk
2m 14s
Execution time

Detection pattern

Example weekly workflow built from Gremlin's shipped renewal scouts.

Evidence shape

Renewal findings merged into a reviewable CSV and team handoff summary.

Execution boundary

Detection lives here. Any Salesforce writeback or downstream workflow still belongs to a separate governed step.

Ready to Automate Your Renewal Risk Tracking?

Start your free 30-day trial. No credit card required.