Skip to main content
Churn is rarely a surprise to the data and usually a surprise to the team. The signals were there: the champion stopped replying in March, the executive sponsor left in April, support volume climbed and then went silent, nobody from your side had a real conversation in nine weeks. None of it triggered anything because nobody was watching for the absence of things. Churn and renewal risk watches continuously, and flags accounts drifting in either direction, because the same signals that precede churn also precede expansion when they run the other way.

Data Sources

Starter (required only): renewal dates, account ownership, and what the calls say about health and satisfaction. Full (required + recommended): the same, plus the signals that actually move first. Email engagement falling off, meeting cadence stretching, support volume rising or going quiet, and shared Slack channels going dead. Silence is the earliest indicator, and it only exists in email, calendar, and messaging. See the Context Graph for how each source feeds the watch.

Choose your path

Build in Clearskies

This is the use case where the workflow path matters most. An analysis you have to remember to run does not catch the account nobody was thinking about.

The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language:
The app configures the schedule, the accounts in scope, and the destination. Scheduled workflows have no meeting context, so the accounts come from a record lookup rather than a calendar. Record lookups cap at 100 records per step, so scope by renewal window or segment rather than sweeping the whole book at once. A 180-day renewal window is usually enough to keep it under the cap and still leave time to act. Flag only what changed. An account that has been quiet for a year and always will be is not a signal; an account that replied within a day for eight months and has not replied in three weeks is. Set the thresholds so the channel gets a handful of accounts a week rather than the whole list.

Deploy to Slack

Once published, only the accounts that trip a threshold arrive:

Customize the rollout

  • Set the renewal window: 180 days catches it early, 90 keeps the list short
  • Define your own thresholds for days since a two-way exchange, cadence change, and support-volume shift
  • Watch both directions, or only risk, depending on who reads the channel
  • Track whether a flag is new this week or repeating, so a persistent flag is visible as an unanswered one
  • Route it to CS, to the account owner’s DM, or to a leadership channel
  • Chain it with product feature requests so gaps raised by at-risk accounts read as retention risk rather than roadmap input
  • Chain it with handoffs so a departing sponsor triggers a fresh account brief for whoever picks it up

Build in Claude or ChatGPT

For the account in front of you, and for reading the whole book before a QBR or a board conversation.

The Prompt

Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs).
The last instruction is what separates a useful list from a list of your least chatty customers.

Make it yours

  • Add Just Meridian Systems, in detail, with a timeline when one account needs the full picture.
  • Add What would you do about the top three to get to action rather than diagnosis.
  • Add Which of these look like the accounts we lost last year, and what did those have in common when you have enough churn history to pattern-match against.
  • Add Draft a re-engagement email to the champion when the answer is that somebody needs to reach out today.

The Skill (Claude)

The clearskies:account-brief skill in the Clearskies plugin for Claude generates a full account brief from the Context Graph, across CRM, calls, email, calendar, and Slack. It is the right follow-up once an account is flagged and you need the whole story before deciding what to do.
Want this packaged for your team? Reach out and we’ll help you customize the skill to your workflow.

The Plugin

Ready to make this part of your team’s workflow? We’ll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works. Book 15 minutes →

Next steps

  1. Sign in to Clearskies
  2. Connect your data sources
  3. Get your Clearskies MCP server and try with Claude or ChatGPT