How we handle GDPR data-subject requests on a deadline
Legal
The win-loss agent we run on Kortix — a weekly cron reads every HubSpot deal closed-won or closed-lost since the last run and posts the patterns by segment, competitor, price, and stage of death to Slack.
Every closed deal is a data point about why customers choose us or choose someone else, but the reason usually lives in one line of a HubSpot field, written by a rep in a hurry between calls. Read one at a time, those lines say nothing. Read across a hundred deals a quarter, they say exactly where we're strong, where a competitor is beating us, and where our own pipeline quietly falls apart.
We run a win-loss analysis agent on Kortix that reads closed deals from HubSpot every week and posts the patterns to our sales Slack channel. It only reads deal data; the single output is the Slack post. This is how we watch our own win rate.
Close reasons and competitor mentions get logged in HubSpot because the CRM asks for them, not because anyone reads them back. A closed-lost deal gets a one-line reason and maybe a competitor field, then disappears into the pipeline history. Nobody aggregates it, so the same loss pattern — a competitor consistently winning on price in one segment, a deal category that reliably dies at the same stage — can repeat for two quarters before a sales leader notices it by gut feel in a QBR.
The common approaches don't fix this. A win-rate number on a dashboard tells you the score changed, not why. A quarterly deal-review deck is thorough but looks back three months too late to change this week's playbook. And nobody wants to be the person who reads two hundred close-reason fields by hand every Monday.
On Kortix, a weekly cron triggers an agent. It spawns a fresh session (a cloud sandbox) with read-only access to HubSpot, pulls every deal closed-won or closed-lost since the last run, and breaks the outcomes down by segment, competitor, price band, and the stage where lost deals actually die. It synthesizes the patterns into themes and concrete recommendations, and posts the summary to Slack. It writes nothing back to HubSpot.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the win-loss 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 win-loss analysis agent in this workspace.
Create the agent agents/win-loss-analysis.md. Its job is to find patterns in closed HubSpot deals and post them to Slack. It may use the HubSpot connector, read-only.
Create the skill skills/win-loss-patterns/SKILL.md with these rules:
Add a cron trigger weekly-win-loss-review to kortix.yaml. It runs the win-loss-analysis agent every Monday at 09:00 with the prompt "Load the win-loss-patterns skill and post this week's win-loss analysis to #sales."
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 with read-only access, and Slack for the post. Credentials are brokered server-side and never enter the agent's machine.
Reads deals closed won and lost in the lookback window.
Adds a call quote that supports each loss theme.

Posts the themes and recommendations.
Merge the change request, then start a session with the win-loss-analysis agent and send this prompt. Check the themes against what your reps tell you before you let the schedule take over.
Run one win-loss analysis on HubSpot. Read only. Change nothing.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 09: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-win-loss-review name: Weekly win-loss review on: cron: "0 0 9 * * 1" run: agent: win-loss-analysis prompt: Load the win-loss-patterns skill and post this week's win-loss analysis to #sales.The agent reads closed deals and writes nothing back, not even to fill a blank close reason. It never contacts a rep or a lost prospect. The Slack post is its only output, and the sales team decides what to change in the playbook.
Each run ends with one message in #sales. This is what a run looks like in the session:
31 deals closed this week: 12 won and 19 lost, a 39% win rate. Most lost deals died at Proposal, and the top theme is price on the enterprise tier. Recommendation: review enterprise packaging.
Once it works, paste any of these into the same session.
On the first Monday of each quarter, compare win rate by segment and by competitor to the previous quarter.
List the lost deals this week that have no close reason, with their owners, so a manager can follow up.
Once Gong is connected, add one quote from the last call of each lost deal that supports its theme.
The agent reads every closed deal in HubSpot, so its access is scoped and one-directional:
Win-loss reasons that used to sit unread in a HubSpot field now arrive as one weekly summary in the channel where the sales team already works, with the themes named and a recommendation attached to each. The agent only reads; the people decide what to change in the playbook.