How we roll the pipeline into a weekly forecast

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.

The problem

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.

What we built

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.

How it works

Guardrails

Rolling up the entire pipeline every week is a trust question, so the agent's access is scoped and one-directional:

• Isolation. Every run happens in its own microVM sandbox. The session can reach only HubSpot and Slack, and only the forecast post leaves the sandbox.
• Scoped secrets. The HubSpot credential is encrypted in the Secrets Manager and injected into the sandbox at runtime, never exposed to the model or the logs.
• Read-only, no exceptions. The connector into HubSpot is read-only. The agent never changes a deal's amount, close date, stage, or owner — it can only report on what it finds.
• Everything is code. The weighting rule, the quarter window, and the slipping/at-risk criteria are files in the repo, versioned and changed through a reviewed change request rather than a dashboard setting.

The outcome

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.