How we handle GDPR data-subject requests on a deadline
Legal
The sales-forecast agent we run on Kortix — a weekly cron rolls up HubSpot's open pipeline into a weighted forecast vs quota by stage, rep, and segment, flags deals slipping the quarter, and posts it to Slack. Read-only — it never touches a deal's amount or close date.
Every sales org has a number it's chasing every quarter, and every sales org reconciles that number the same way: someone pulls open deals out of HubSpot, weights them by gut feel or a spreadsheet formula nobody remembers building, and calls it the forecast. It's accurate for about a day — the day it was built — and it says nothing about the deal whose close date quietly slid past last week, or the six-figure deal that hasn't had a logged activity in a month.
We run a sales-forecast agent on Kortix that reads HubSpot every week and posts a weighted forecast to our sales Slack channel — broken down by stage, rep, and segment, measured against quota, with the deals putting that number at risk called out by name. It only reads the pipeline; the single output is the Slack post. This is how we forecast our own quarter.
A stage-by-stage pipeline view and a real forecast are different things. The pipeline view says a deal is "open" and sitting in "Proposal Sent"; it doesn't say whether that deal is on track to close this quarter, whether the rep's commit number matches what the stage actually implies, or whether a big deal has quietly gone stale while still counting toward the total. Turning open deals into a forecast means weighting every deal by how likely its stage really is to close, then rolling that up three different ways — by stage, by rep, by segment — and comparing it to quota.
The usual fix is a spreadsheet rebuilt the week before the forecast call: someone exports deals, applies a weighting rule by hand, and reconciles it against every rep's stated commit. It's stale the moment it's built, it depends on someone remembering to run it, and it rarely catches a deal whose close date has already passed or one that's gone quiet in a late stage until the quarter is nearly over.
On Kortix, a weekly cron triggers an agent. It spawns a fresh session with read-only access to HubSpot, pulls every open deal — stage, amount, close date, owner, and its segment — weights each one by the probability already configured on its HubSpot pipeline stage, and rolls the weighted amounts up by stage, by rep, and by segment. It compares the total to this quarter's quota, flags deals whose close date has already slipped or that don't have enough runway left in their current stage to realistically close this quarter, flags large deals that look at risk for other reasons — no recent activity, stalled in a late stage — and posts the whole forecast 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 forecast 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 sales forecast agent in this workspace.
Create the agent agents/sales-forecast.md. Its job is to roll the open HubSpot pipeline into a weekly forecast. It may read HubSpot and post to Slack.
Create the skill skills/forecast-rollup/SKILL.md with these rules:
Add a cron trigger weekly-sales-forecast to kortix.yaml. It runs the sales-forecast agent every Monday at 09:00 with the prompt "Load the forecast-rollup skill and run one complete weekly forecast rollup."
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 open deals, stage probabilities and close dates, read-only.
Posts the weekly forecast rollup and slipping deals.

Merge the change request, then start a session with the sales-forecast agent and send this prompt. Check the totals against your own pipeline view before you let the schedule take over.
Build this quarter's forecast from 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-sales-forecast name: Weekly sales forecast on: cron: "0 0 9 * * 1" run: agent: sales-forecast prompt: Load the forecast-rollup skill and run one complete weekly forecast rollup.The agent reads the pipeline and writes nothing back. It never changes a deal's amount, close date, stage or owner, even when a deal is clearly slipping. The Slack post is its only output, and the sales team decides what to do about each flagged deal.
Each run ends with one message in #sales-forecast. This is what a run looks like in the session:
Weighted forecast is $842,000 against a $1,000,000 quota: 84% attainment and a $158,000 gap. 5 deals are slipping the quarter, and 2 large deals look at risk with no activity in three weeks.
Once it works, paste any of these into the same session.
After each forecast, send each rep a Slack DM with only their slipping and at-risk deals, so they can update close dates before the forecast call.
Split the forecast into commit (late-stage deals only) and best case (all open deals), and show both against quota.
Every Thursday, post only the deals whose close date passed since Monday to #sales-forecast.
Rolling up the entire pipeline every week is a trust question, so the agent's access is scoped and one-directional:
The forecast that used to get rebuilt by hand the week before the call now arrives every Monday in the channel where the team already works, weighted by HubSpot's own stage probabilities and carrying the specific deals putting the number at risk. The agent only reads and reports; the sales team still owns every deal.