Revenue Operations
•
CRM operations
Forecast Manager
Rolls up the forecast call, tests each Commit and Best Case deal against buyer evidence from meetings, email, and the CRM, flags slippage and coverage gaps, and compares every past forecast with actuals so the number becomes a range the team can trust.
Last updated
Watch this agent work in Nex
See a Nex session move from your instructions through integration work to the finished outcome.
Goal
Rolls up the forecast call, tests each Commit and Best Case deal against buyer evidence from meetings, email, and the CRM, flags slippage and coverage gaps, and compares every past forecast with actuals so the number becomes a range the team can trust.
What Nex will do
1. Fix the period, target, segments, and revenue types, then snapshot every open deal with its stage, amount, close date, and forecast category. 2. Test each Commit against six conditions — buyer-confirmed intent this period, an engaged economic buyer, agreed price and scope, a dated close plan, procurement or legal started, and a close date inside the period — using the buyer’s own words, not the CRM field. 3. Build two independent numbers — a category roll-up with a slippage haircut and a stage-weighted number from the workspace’s own win rates — and explain every deal behind a gap. 4. Flag slippage and risk: close dates pushed twice or more, deals with no dated next step, stale late-stage deals, and coverage below what the win rate requires. 5. Compare past forecasts with actuals at company, segment, and owner level, name the direction of the miss, and propose at most three fixes for approval.
Integrations and actions
Best for
Designed for CROs, sales leaders, and RevOps teams who own the forecast call and need a number built from deal evidence rather than rep sentiment.
What you will get
• A forecast range against target with the rate and source behind every number. • A Commit audit that confirms or downgrades each deal with the missing condition and its evidence. • Slippage, coverage, and pipeline-gap flags with the deals behind them. • A forecast-versus-actuals history that shows where and why the number misses.
What you will need
• A connected CRM with deal history; past forecast snapshots help but can be reconstructed. • The period, target, revenue types in scope, and who approves forecast-field changes.
Approvals and control
Reading pipeline history, notes, and meetings and building the range need no approval. Saving forecast snapshots, creating Tasks, changing a forecast category, stage, or close date, and messaging owners or managers require approval, and CRM changes also need the deal owner’s agreement.
Full agent guide
Rolls up the forecast call, tests each Commit and Best Case deal against buyer evidence from meetings, email, and the CRM, flags slippage and coverage gaps, and compares every past forecast with actuals so the number becomes a range the team can trust.
What this agent does
Fix the period, target, segments, and revenue types, then snapshot every open deal with its stage, amount, close date, and forecast category. Test each Commit against six conditions — buyer-confirmed intent this period, an engaged economic buyer, agreed price and scope, a dated close plan, procurement or legal started, and a close date inside the period — using the buyer’s own words, not the CRM field. Build two independent numbers — a category roll-up with a slippage haircut and a stage-weighted number from the workspace’s own win rates — and explain every deal behind a gap. Flag slippage and risk: close dates pushed twice or more, deals with no dated next step, stale late-stage deals, and coverage below what the win rate requires. Compare past forecasts with actuals at company, segment, and owner level, name the direction of the miss, and propose at most three fixes for approval.
Who this is for
Designed for CROs, sales leaders, and RevOps teams who own the forecast call and need a number built from deal evidence rather than rep sentiment.
When it runs
Weekly, the day before the forecast call; when a Commit deal changes stage, amount, or close date; and at period close to compare the forecast with actuals.
How the workflow works
Snapshot the open pipeline → test every Commit against the evidence → build category and stage-weighted numbers as a range → flag slippage and coverage gaps → compare past forecasts with actuals → propose fixes and CRM changes for approval.
Inputs and prerequisites
Connect the CRM with stage, amount, close-date, and forecast-category history; define the period, target, and revenue types in scope; and name who owns the forecast call. The agent should not change forecast fields without the deal owner’s agreement.
Typical inputs include open deals with owner, stage, amount, close date, forecast category, and change history; twelve months of closed-won and closed-lost deals; past forecast submissions or reconstructable snapshots; and the meeting notes, email threads, and Nex context behind each deal.
Outputs
The agent returns a conservative, expected, and optimistic forecast against target, a Commit audit with every downgrade and its evidence, slippage and coverage flags, an accuracy history by period, segment, and owner, and up to three fixes. For this agent, the core flow is: Snapshot the open pipeline → test every Commit against the evidence → build category and stage-weighted numbers as a range → flag slippage and coverage gaps → compare past forecasts with actuals → propose fixes and CRM changes for approval.
Approvals and safeguards
Reading pipeline history, notes, and meetings and building the range need no approval. Saving forecast snapshots, creating Tasks, changing a forecast category, stage, or close date, and messaging owners or managers require approval, and CRM changes also need the deal owner’s agreement.
Integrations
This agent can use approved HubSpot, Salesforce, Attio, Gmail through optional Annex access, Outlook, Google Calendar, Outlook Calendar, and Slack, plus meeting notes, relationship context, and forecast snapshots saved in Nex. Connections, permissions, and available actions vary by the workspace configuration.
What it can replace
Consolidates parts of forecast roll-up, deal inspection, and forecast-accuracy reporting commonly handled in Clari, Gong Forecast, and CRM forecasting views. It does not replace every revenue-intelligence or call-recording capability. Referenced workflow tools include Clari, Gong.
Estimated software savings
Est. $300–$800/mo. Illustrative monthly software-stack consolidation range based on overlapping workflow categories and public self-serve prices reviewed on September 25, 2026. Actual savings vary by plan, seats, usage, retained tools, and data costs; Nex may complement rather than replace every capability.
Use the agent prompt
Use Deploy Agent in Nex on this page to open the agent in your current workspace. Review integrations, permissions, thresholds, tone, and approval gates before deploying it.
Frequently asked questions
What does the Forecast Manager agent do?
Rolls up the forecast call, tests each Commit and Best Case deal against buyer evidence from meetings, email, and the CRM, flags slippage and coverage gaps, and compares every past forecast with actuals so the number becomes a range the team can trust.
What data and integrations does the Forecast Manager agent use?
It uses only approved context and connected systems relevant to the workflow. In this agent, that can include HubSpot, Salesforce, Attio, Gmail through optional Annex access, Outlook, Google Calendar, Outlook Calendar, and Slack, plus meeting notes, relationship context, and forecast snapshots saved in Nex. Exact access depends on the integrations and permissions configured in Nex.
Does this agent replace Clari, Gong?
Consolidates parts of forecast roll-up, deal inspection, and forecast-accuracy reporting commonly handled in Clari, Gong Forecast, and CRM forecasting views. It does not replace every revenue-intelligence or call-recording capability. The Est. $300–$800/mo figure is an illustrative software-stack consolidation range, not a guaranteed outcome.
Last updated
September 25, 2026. Agent behavior and third-party pricing can change; verify operational and pricing details before publishing or running the workflow.
Deploy this agent in Nex
Use Deploy Agent in Nex to open this agent in your current Nex workspace. Review integrations, permissions, thresholds, and approval gates before deploying it.

