How we handle GDPR data-subject requests on a deadline
Legal
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.
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.
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.
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.
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.
Set up a daily renewal manager agent in this workspace.
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.
Create the skill skills/renewal-prep/SKILL.md with these rules:
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."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
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.
Reads renewal dates, deal history and account activity.

Checks for an existing renewal call before drafting outreach.
Posts the renewal packet, at-risk flags and the outreach draft.

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.
Run today's renewal check.
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.
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.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.
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:
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.
Once it works, paste any of these into the same session.
Every Monday, post to #renewals the total contract value that renews in the next 90 days, split into on-track and at-risk.
When no renewal meeting is on the calendar 30 days out, add three times from the owner's free slots to the draft.
Send each account owner a Slack DM with their renewals this week and a link to each draft.
The agent touches revenue-relevant accounts, so what it can do is narrow and explicit:
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.