SALES
Publish a Monthly Renewal Health Scorecard
Once a month, scores the entire upcoming renewal book on usage, support, and engagement signals and publishes a ranked health scorecard to Coda for the renewals leadership review.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule fires
- ActionPull two-quarter renewal book and usageHubSpot
- ActionAdd open-ticket counts per accountZendesk
- LogicCompute weighted health score and risk band
- ActionWrite ranked scorecard tableCoda
- OutputPost summary to leadership channelSlack
What it does
This workflow produces the artifact a renewals leader needs for a monthly forecast review: a ranked scorecard of every account up for renewal, with a composite health score built from usage trend, open support load, and last-touch recency. Green, yellow, and red bands make the at-risk dollars obvious at a glance.
When to use it
Use it to replace the manual spreadsheet someone rebuilds before every renewals meeting. It standardizes how risk is scored so the conversation is about action, not about whose numbers are right.
How it works
- 1A monthly schedule starts the run.
- 2It pulls all accounts renewing in the next two quarters from HubSpot with their usage data.
- 3It enriches each with open-ticket counts from Zendesk.
- 4A logic step computes a weighted health score and assigns a risk band per account.
- 5The ranked scorecard is written to a Coda table and a summary is posted to leadership in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HubSpotCRM, deals, marketing, support.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect CodaDocs, packs, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.