How we handle GDPR data-subject requests on a deadline
Legal
The QBR-prep agent we run on Kortix — connected to Postgres, HubSpot, Google Slides, and Google Docs. Weekly, for every account due a quarterly business review, it pulls usage trends, account health, support activity, and expansion signals into a draft deck and briefing doc for the CSM to review and present.
A quarterly business review is only as good as its prep. The account's usage trend lives in the product database, its health score and CSM notes live in HubSpot, the support history is scattered across a quarter's worth of tickets, and the expansion angle is usually in someone's head. Pulling all of that into a deck by hand takes an afternoon per account, and with a book of a few dozen accounts, QBR week turns into a slide-building sprint instead of an account-strategy exercise.
We run a QBR-prep agent on Kortix that does that assembly every week. It reads across the source systems, drafts a deck and a companion briefing doc per account due a review, and stops there. It never writes back to a source system and never presents anything — the CSM opens the draft, edits the story, and walks into the room with it.
The material for a QBR is real but scattered. Product usage trends sit in Postgres. Account health, CSM notes, and the deal history sit in HubSpot. Support friction is a quarter's worth of tickets no one has time to reread. Expansion opportunities are pattern-matched from all of the above, usually from memory, right before the meeting.
Templates help with layout but not with assembly — someone still has to pull every number, read every note, and decide what's worth a slide. Doing that for one account is an afternoon. Doing it for every account due a review, every week, is the part that gets skipped, rushed, or handed to whoever has the least on their plate that week — which is exactly when a CSM walks in under-prepared for a renewal conversation.
On Kortix, a weekly cron triggers an agent. It spawns an isolated session with read-only access to Postgres and HubSpot, finds every account whose next QBR falls due in the coming window, and for each one pulls usage trends, value delivered, account health, a support summary, and expansion opportunities. It assembles that into a draft deck in Google Slides and a companion briefing doc in Google Docs with the backup detail, then stops. Nothing is shared, presented, or sent — the CSM reviews both and takes it from there.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the qbr-deck-assembly skill and the weekly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a weekly QBR-prep agent in this workspace.
Create the agent agents/qbr-prep.md. Its job is to draft a QBR deck and a briefing doc for every account with a QBR coming up. It may use the PostgreSQL, HubSpot, Google Slides and Google Docs connectors. PostgreSQL and HubSpot are read-only.
Create the skill skills/qbr-deck-assembly/SKILL.md with these rules:
Add a cron trigger weekly-qbr-prep to kortix.yaml. It runs the qbr-prep agent every Monday at 06:00 with the prompt "Load the qbr-deck-assembly skill and run one complete QBR-prep sweep."
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 product database, your CRM, Google Slides and Google Docs. Give the database connector a read-only user. Credentials are brokered server-side and never enter the agent's machine.
Pulls usage trends for each account due a QBR.
Finds accounts due a QBR and reads their health signals.

Holds the draft deck and briefing doc for each account.


Merge the change request, then start a session with the qbr-prep agent and send this prompt. Open one deck and check its numbers before you let the schedule take over.
Run one QBR-prep sweep.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 06: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: weekly-qbr-prep name: Weekly QBR-prep sweep on: cron: "0 0 6 * * 1" run: agent: qbr-prep prompt: Load the qbr-deck-assembly skill and run one complete QBR-prep sweep.PostgreSQL and HubSpot are read-only. The only things the agent writes are the new deck and the new doc. It never shares, presents or emails either one. The CSM reviews the draft and runs the meeting.
Each run ends with a list of the decks and docs it created. This is what a run looks like in the session:
4 accounts have a QBR in the next 10 days. Drafted 4 decks and 4 briefing docs in QBR Decks. One account shows usage down 18% quarter over quarter, called out on its usage slide. 2 accounts were skipped because they have no QBR date.
Once it works, paste any of these into the same session.
When a deck is ready, send its CSM a Slack DM with links to the deck and the briefing doc.
Add a slide that lists the goals from the account's previous QBR and whether the data shows each one met.
At the top of the run summary, list the accounts with a declining usage trend or a falling health score, with the reason for each.
The agent reads deeply across account data, so its access is scoped and its output is bounded:
The afternoon of pulling numbers and rereading tickets now happens automatically, every week, for every account that needs it. The CSM opens a draft deck that already has the trend, the health picture, the support summary, and a candidate expansion angle, edits the story into their own words, and presents it themselves.