Clay logo, go to homepage

Search Marketplace

Browse all Skills
SignalsSkill

Renewal Risk Radar

Delivers a weekly ranked digest of renewing accounts that grew riskier this week, each with dated evidence, without touching your CRM or contacting customers.

Sung Jo
Sung Jo

SEO/AEO Lead at Clay

About this Skill

When to use it

Use this Skill when you want to know which renewals got riskier this week, not just which accounts look bad overall, so you can act before a champion leaves, headcount drops, or a customer goes quiet. It builds a ranked weekly digest with dated evidence per signal, ready before your renewal conversations. Avoid using it for real-time champion job-change alerts, positive buying-signal tracking, single-company headcount trends, CRM data audits, or general account scoring.

What it delivers

You get a ranked Monday digest showing exactly which renewing accounts picked up new risk signals this week, each backed by dated evidence for a champion change, a headcount drop, or public silence. It also lists watched accounts with no change and any signals it could not measure, so coverage is always visible, and it never writes to your CRM or contacts a customer.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

Send me a weekly digest of which renewals just got riskier, with the evidence behind each one, so I know before the renewal call, not after.

Other ways to ask

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • 01CRM connection & fields
    • Name which CRM you use and where account records live
    • point to the renewal date field
    • state how you record your champion contact.
  • 02Risk rule definitions
    • Set how far ahead counts as coming up, default 90 days
    • set the headcount-drop threshold, default any decline vs trailing 90 days
    • define went-quiet, default 30 days no public activity
    • confirm the weekly comparison model, default recent-window.
  • 03Delivery & schedule
    • Choose where the digest lands, a Clay table, Slack, email, or both
    • set the day and time it runs, default Monday 7am workspace time.

Outputs

  • 01Weekly ranked risk digestA ranked list of in-window renewal accounts that fired at least one risk signal this week, ordered by number of signals fired then by renewal proximity, delivered to the Clay table (and Slack/email if connected) the installer named.
  • 02Per-account signal evidenceFor each account on the digest, the specific signals that fired (champion changed employer, headcount fell, company went quiet), each with one dated line of evidence sourced from the provider, rather than a blended risk score.
  • 03Unmeasured and watched-no-change accountsA visible listing of accounts whose signals could not be measured (marked unmeasured, never treated as safe) and accounts that were watched but showed no change this week, so coverage gaps and quiet weeks are shown rather than hidden.
  • 04Digest coverage summary and rules usedA header on each digest stating the renewal window, the headcount-drop and quiet rules, the recent-window model, and counts of accounts watched, accounts that fired a signal, and accounts with an unmeasured signal, so weeks are comparable.
  • 05Batch preview and cost gate summaryThe real 10-row test batch of signal results shown before any full run, paired with the calculated full weekly cost per in-window account and the confirmed digest destination, presented as the single approval checkpoint before scheduling.

Representative output

RankAccountRenewal inSignals firedEvidence
1Northwind21 dayschampion moved · headcount fellchampion now VP at a competitor (2026-08-19); 512 → 470 vs trailing 90d
2Contoso40 daysheadcount fell · went quiet1,180 → 1,090; no news/hiring since 2026-07-14
3Fabrikam66 dayschampion movedchampion left, no successor on file (2026-08-22)
—Acme12 days(champion unmeasured — none on file)headcount flat; not in risk list, flagged for missing champion

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

01
Confirm platform access

Verifies your Clay login and states upfront that the skill reads your CRM and public data but writes only its own digest, never your CRM, and never contacts a customer.

Step
02
Map CRM fields with you

Reads your CRM schema, shows the field mapping for account, renewal date, owner, and champion, and asks you to confirm each judgment call.

Step
03
Confirm the weekly model

Uses a recent-window approach so a signal counts when its event falls in the recent window, avoiding the need to store past run data.

Step
04
Verify signal costs live

Checks pricing and required inputs for the three paid signal lookups, champion job change, headcount drop, and public activity, directly against Clay's current catalog before any run.

Step
05
Run a test batch and pause

Runs the three signals on ten in-window accounts, shows the results and full weekly cost, then stops and waits for your approval before running the full book and scheduling it.

Step
06
Build the scheduled workflow

Builds the weekly Clay workflow on a schedule trigger, keeping all ranking logic in a code node rather than an AI node.

Step
07
Rank accounts by signals fired

Ranks each in-window account by how many signals fired, breaks ties by renewal proximity, and separates zero-signal accounts into a watched list.

Output
08
Deliver the weekly digest

Delivers each at-risk account with its fired signals, dated evidence, renewal timing, and a summary line showing coverage, including any unmeasured signals.

Step

Connections required

CRM systemRequired connection

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 3From submitted SKILL.mdCurrent

Related Skills

10k Value Prop MatchCompares a seller's value proposition against a target company's own 10-K language and returns matched initiatives with quotes and need status.View Skill →Alert Reps On Account SignalsLoads a rep's target-account list into Clay and posts a Slack alert whenever a watched account hires a leader, posts a job, or gets news coverage.View Skill →Icp Outbound CampaignTurns your ideal customer profile into a verified lead list saved in Clay Audiences and a drafted outbound email sequence, without sending or launching anything.View Skill →

Related searches

Signals skillsCRM system skills