Get started

How we get ahead of contract renewals

The renewal manager we run on Kortix — a daily cron that surfaces every account 90, 60, and 30 days from renewal, preps a packet on usage and value delivered, drafts outreach, and flags at-risk accounts for the owner to review.

Written by
The OpenChatly Team
Published
May 28, 2026
Reading time
8 min read
Topics
Sales, Case Study, Enterprise

Renewals used to surface the way most bad news does — late. An account owner would open HubSpot, notice a contract expiring in three weeks, and start from zero: pull the usage numbers, remember what shipped since the last check-in, guess at expansion room, and write the outreach the same afternoon. The accounts that renewed smoothly were the ones an owner happened to remember to check. The ones that churned quietly were usually the ones nobody looked at until it was too late to do anything but apologize.

We run a renewal manager agent on Kortix that watches every HubSpot deal's renewal date and gets ahead of it — at 90, 60, and 30 days out — with a packet already built and outreach already drafted. It never sends anything and never touches price. It hands the account owner a head start instead of a deadline.

Team
Kortix
Runs on
Daily cron
Connected systems
HubSpot · Google Calendar · Slack · Email
Mode
Prep + draft only · account owner sends

The problem

A renewal date sitting on a HubSpot deal is just a date. It doesn't say whether the account is healthy, whether the team has actually used what they bought, whether there's a natural expansion to raise, or whether the deal has gone quiet in a way that should worry someone. That context lives scattered across old notes, a memory of the last QBR, and whatever the owner can reconstruct under time pressure.

The common fallback is a calendar reminder or a pipeline report sorted by close date — a flat list with no prep behind it. By the time an owner opens the account, the renewal is close, the packet doesn't exist yet, and the outreach gets written in a rush instead of shaped around what the account actually needs to hear.

What we built

On Kortix, a daily cron triggers an agent that reads every HubSpot deal's renewal date and surfaces the ones crossing 90, 60, or 30 days out. For each one, it builds a renewal packet — usage and value delivered since the last renewal, and one or two concrete expansion ideas — checks Google Calendar to see whether a renewal conversation is already on the books, and drafts the outreach email. Anything that looks stalled, quiet, or shrinking gets flagged separately as at-risk. The packet and the draft wait for the account owner; nothing goes out on its own.

How it works

1

Copy the setup prompt into a new session

Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the renewal-prep skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.

Setup prompt

Set up a daily renewal manager agent in this workspace.

  1. Create the agent agents/renewal-manager.md. Its job is to prepare every renewal that is 90, 60 or 30 days out and draft the outreach for the account owner. It may use the HubSpot, Google Calendar, Slack and Gmail connectors. Google Calendar is read-only.

  2. Create the skill skills/renewal-prep/SKILL.md with these rules:

    • Read renewal_date on every open HubSpot deal and put it in the 90, 60 or 30 day window. Skip a deal whose kortix_renewal_stage_alerted already matches its window.
    • Build a renewal packet: the value delivered since the last renewal, one or two specific expansion ideas, and the current contract terms.
    • Look in Google Calendar for a renewal or QBR meeting near the date, and reference it. Never create, move or accept an event.
    • Flag a deal as at-risk when its stage has stalled, its value is trending down, it has gone quiet, or its notes mention a competitor, a budget freeze or churn.
    • Write the outreach as an unsent Gmail draft for the owner. Never send it, and never put a discount, credit or price change in it.
    • Post the new renewals and the at-risk list to #renewals. The only HubSpot write is kortix_renewal_stage_alerted.
  3. Add a cron trigger daily-renewals to kortix.yaml. It runs the renewal-manager agent every day at 08:00 with the prompt "Load the renewal-prep skill and run today's renewal check."

  4. Tell me which of these connectors are not connected yet.

  5. Open a change request with all of it. Do not merge it.

2

Connect your tools

Open Connectors in your workspace and connect your CRM, your calendar, Slack and the mailbox where drafts go. Credentials are brokered server-side and never enter the agent's machine.

HubSpot

Reads renewal dates, deal history and account activity.

Or useSalesforce
Required
Google Calendar

Checks for an existing renewal call before drafting outreach.

Or useMicrosoft Outlook
Required
Slack

Posts the renewal packet, at-risk flags and the outreach draft.

Or useGmailMicrosoft Teams
Required
3

Run it once with this prompt

Merge the change request, then start a session with the renewal-manager agent and send this prompt. Read the first drafts before you let the schedule take over.

Prompt

Run today's renewal check.

  1. Find open HubSpot deals whose renewal_date is 90, 60 or 30 days out and that are not yet surfaced for that window.
  2. For each one, build a renewal packet: value delivered, one or two expansion ideas, and the contract terms.
  3. Look in Google Calendar for a renewal or QBR meeting near the date.
  4. Write the outreach as an unsent Gmail draft for the owner. No discounts, credits or price changes.
  5. Post the new renewals and every at-risk deal with its signal to #renewals. Then set kortix_renewal_stage_alerted on each deal you prepared.
4

Let the daily schedule take over

The change request added this trigger to kortix.yaml. From now on the agent runs every day at 08:00, each run in a new session on its own cloud computer. To change the time, edit the cron line, or open Triggers in the workspace.

kortix.yaml
triggers:- slug: daily-renewals  name: Daily renewal check  on:    cron: "0 0 8 * * *"  run:    agent: renewal-manager    prompt: Load the renewal-prep skill and run today's renewal check.
5

Draft only, the owner sends

The agent never sends outreach and never offers a discount. The calendar is read-only, and the only HubSpot write is the window marker. The account owner edits each draft and sends it.

6

Read the renewal radar

Each run ends with one post in the channel and a draft for each renewal. This is what a run looks like in the session:

Daily renewal check · 08:00
Load the renewal-prep skill and run today's renewal check.
Worked for 4m 18s
hubspot · search dealshubspot · get notes × 5google calendar · list events × 5gmail · create draft × 5slack · post message → #renewalshubspot · update deal × 5

5 renewals crossed a window today: 2 at 90 days, 2 at 60 and 1 at 30. Five outreach drafts wait for their owners. 2 deals are at-risk: one has had no activity in 45 days, and one has notes that mention a budget freeze.

Illustrative example. Your renewals depend on your CRM.

The pattern

A daily cron spawns a session with read connectors into HubSpot and Google Calendar. The renewal playbook lives as a skill. The agent preps the packet and drafts the outreach; the account owner reviews, edits, and sends.

Make it do more

Once it works, paste any of these into the same session.

Weekly renewal forecast

Every Monday, post to #renewals the total contract value that renews in the next 90 days, split into on-track and at-risk.

Suggest a meeting

When no renewal meeting is on the calendar 30 days out, add three times from the owner's free slots to the draft.

Brief each owner

Send each account owner a Slack DM with their renewals this week and a link to each draft.

Guardrails

The agent touches revenue-relevant accounts, so what it can do is narrow and explicit:

  • Prep and draft only. The agent never sends the renewal outreach and never creates or moves a calendar event. The email is a draft in the owner's inbox until the owner sends it.
  • No pricing decisions. The agent never applies, offers, or proposes a specific discount or credit. Anything touching price is a conversation for the account owner, not a line in a draft.
  • Scoped writes. The only thing the agent writes back to HubSpot is which renewal window a deal has been surfaced for — never the deal stage, the amount, or the pipeline.
  • Isolation. Every run happens in its own isolated sandbox. Credentials for HubSpot and Google Calendar are encrypted in the Secrets Manager and injected at runtime, scoped to the agents you grant them to.
  • Everything is code. The renewal playbook, the at-risk criteria, and the per-system permissions are files in the repo, versioned and changed through a reviewed change request rather than a dashboard setting.

The outcome

Days out a renewal first gets a packet, not a deadline
90/60/30
Renewal list and at-risk flags recomputed from live HubSpot data
Every day
Outreach and discounts the agent sends or applies on its own
0 sent

Renewals that used to start with a blank page now start with a packet already built and a draft already written, so the account owner's first move is a review, not a scramble. The agent watches every deal and does the prep work; the person still decides what to say and when to send it.

On this page

  • The problem
  • What we built
  • How it works
  • Make it do more
  • Guardrails
  • The outcome

Run this yourself

Install this exact setup — agent, connectors, schedule, and guardrails — in a guided flow.

More use cases.

  • How we handle GDPR data-subject requests on a deadline

    Legal·July 11, 2026

  • OpenChatly

    How we keep our docs in sync with the code

    Documentation·July 5, 2026

  • OpenChatly

    How we QA every pull request automatically

    QA·July 5, 2026

Own your AI.Start today, in our cloud.

Start for free

OpenChatly is the AI workspace for everything. One person directing, agents executing, from goal to finished work.

©2026 OpenChatly AI.沪ICP备2025124785号-5

Resource guide

  • Product overview
  • Skills marketplace

Terms of service

  • User agreement
  • Privacy policy

Contact us