Why this exists.
Forecast learns what your normal cancellation and revenue pattern looks like — then pings you the moment the numbers start drifting.
A patchwork that breaks.
- A shared spreadsheet nobody opens on time
- Prompts copy-pasted into a chat window
- A contractor who disappears for two weeks
- Output that lands in a different shape every run
A workflow that ships.
- One brief, one cadence, one place to read it
- Every claim cited, every step reviewable
- A finished artifact in your team’s format
- Churn gets caught upstream, not explained downstream.
Four moves.
Forecast runs each move with a preview attached — so you know what lands before you ever hit send. Skip freely once you know which parts carry the weight.
- 01Kickoff
Connect weekly cancellation and revenue data.
Forecast starts with the brief and asks only for what's missing. No boilerplate intake form, no setup meeting.
Chat · marieteYConnect weekly cancellation and revenue data.FForecast is working - 02Gather
Add the early-warning step.
Sources are pulled, cleaned, and cross-checked against prior runs — every claim carries a citation you can trace.
checklist · step-02Source connected · add the early-warningContext loadedFirst pass completeSource connected - 03Reason
Set the thresholds for alerts.
The agent thinks out loud where it matters — trade-offs named, assumptions surfaced, judgments explained.
ranked results01Catch · anomaly early0.9402Cancellations · anomaly early0.8203Early · anomaly early0.67 - 04Draft
Your customer success team steps in before it hits a board deck.
A first draft lands in the format your team already uses. You edit the last 10%, not the first 90%.
delivery · inboxFnewForecast → your teamjust now · scheduled weeklyCatch cancellations earlyChurn gets caught upstream, not explained downstream.Open briefing
Wire this in Forecast.
Forecast is a visual node-flow workspace — not a chat window. Here's the graph that runs this playbook, node by node. Each one is a real block you can drop in and wire yourself.
Inputs in, outputs out.
Forecast runs on the inputs on the left and hands back the artifacts on the right. Skip any input — the agent will ask for it the first time it needs it.
- One source of truth (CSV, CRM, or warehouse)
- A one-paragraph brief on the goal
- The KPI you want to move
- A scored, cited brief you can forward
- A structured file for downstream automation
- An alert when anything material changes
A finished artifact, not a todo list.
Every run ends the same way — a packaged brief in the channel your team already reads. Here's a preview of what shows up.
Here's the brief for this week. I ran the playbook end-to-end, flagged anything that shifted against last run, and packaged the output for Slack and the shared drive.
- Connect weekly cancellation and revenue data.
- Add the early-warning step.
- Set the thresholds for alerts.
- Your customer success team steps in before it hits a board deck.
Where teams stall.
Three ways we see this go sideways — and how to avoid each one.
Pointing the agent at stale or half-connected data. Clean the source once, compound every run after.
Running it once and forgetting. Put it on a weekly cadence so the numbers actually move.
Skipping the first review. Check the first run by hand — trust compounds from there.
Before you start.
Usually one source is enough to see value. Forecast can run on a CSV paste for the first pass; connect the CRM, the data warehouse, or the tool of record once you want it to run on its own.
Most teams put this on a weekly cadence. That's the sweet spot between "too noisy to read" and "too stale to act on". Adjust once you see how the numbers behave.
Whoever owns the downstream action. Forecast hands back a finished result — the value is in somebody actually reading it and shipping the decision the same day.
It usually isn't. The first pass is calibration — tell Forecast what was off, rerun, and the second is close. By the fourth it reads like a teammate.