--- title: "Forecast Commit Review Workflow With AI Agents | Kylon" description: "How a RevOps team categorizes open deals for the quarterly commit, audits the forecast sheet and re-checks deals when champions leave or discount rules change." url: "https://kylon.io/use-cases/forecast-commit-review" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Forecast Commit Review: Categories That Follow Every Late Change to the Deal Use Case8 min read # Forecast Commit Review: Categories That Follow Every Late Change to the Deal Commit categories, the weighted forecast, deal desk decisions, a departed champion and quarter-end slips run through one Kylon room. Agents work the Pipedrive deals and the deal desk's Notion pages, and the RevOps lead approves every category before it changes. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## A commit number built from deals, meetings and late deal desk decisions A commit review asks every open deal the same questions. Is there a champion? Has there been a recent meeting with the buyer? Is the discount approved? Is the close date believable? The answers are spread out. Deals, contacts and activities are in Pipedrive. Customer meetings are on Google Calendar. Discount approvals are pages in the deal desk's Notion space. The commit policy and the printed forecast sheet are in Google Drive, and the latest news from reps is in the mailbox. The forecast breaks in the cascade. A champion leaves, and the deal stays at commit because nobody ran the rest of the policy again. A new discount authority matrix lands, and only the deals the memo mentions are re-checked, not every deal above the threshold. A sheet printed from last week's export goes to the leadership meeting with categories that no longer match Pipedrive. ## Who works in the room People - RevOps lead Runs the commit review, approves every category and hold reason, and signs the regional closeout - Regional sales leaders Own their region's commit and review the weighted forecast - Deal desk Approves discounts, publishes the discount authority matrix and confirms its decisions - Account executives Keep deals current and confirm close dates with their customers Agents - FinCommit coordinator Categorizes each open deal from its contacts, activities, meetings, deal desk page and mail, builds the weighted forecast and writes approved changes to Pipedrive PipedriveGoogle Calendar[Gmail](https://kylon.io/integrations/gmail)Google Drive - RyanSheet checker Checks the printed forecast sheet line by line and re-checks every deal a matrix change or memo touches Google DrivePipedrive - AdaDeal desk and threads Records approved deal desk decisions on their Notion pages, drafts thread replies and collects deal news from Slack [Notion](https://kylon.io/integrations/notion) [Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) The RevOps lead posts each request in the room, and Fin, the default agent, takes anything unaddressed. The printed sheet belongs to Ryan; the deal desk pages and the threads belong to Ada. Fin writes commit category and hold reason to Pipedrive under a lasting grant from the RevOps lead, once each change is approved. Ada drafts Gmail replies as the person it is working for. Closed deals are out of bounds for every agent, and the room guidelines say so. ## How the commit review runs, section by section The commit policy is numbered by section, and each stage of the review applies one section, in order. ```mermaid flowchart TD categorize["Fin proposes a commit category and
hold reason for every open deal"] approve["RevOps lead approves before
Pipedrive changes"] forecast["Fin builds the weighted forecast
from the approved categories"] sheet["Ryan checks the printed sheet
against current categories"] desk["Ada records deal desk decisions
on their Notion pages"] matrix([The deal desk publishes a new
discount authority matrix]) champion["Fin clears the departed champion
and re-runs the policy from the top"] threshold["Fin re-checks every open deal at
or above the new threshold"] hold([On hold until the deal desk
records the higher approval]) confirm["Deal desk confirms,
RevOps lead approves"] slips["Fin applies the memo's moved close
dates and re-categorizes"] dates["Account executives
confirm each date"] close["Fin counts per-region totals,
checked by Ryan"] sign["RevOps lead signs the review"] categorize --> approve --> forecast --> sheet sheet --> desk & matrix desk --> champion matrix --> threshold threshold -->|higher approver| hold champion & threshold --> confirm confirm --> slips --> dates --> close --> sign class categorize,forecast,sheet,desk,champion,threshold,slips,close agent class approve,confirm,dates,sign person class matrix,hold event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Dispositions | Every open deal gets a commit category and hold reason from its contacts, activities, calendar meetings, deal desk page and mail | Fin | The RevOps lead approves before Pipedrive changes | | Weighted forecast | The weighted forecast is built from the approved categories | Fin | Regional sales leaders review their numbers | | Sheet review | The printed forecast sheet is checked line by line against current categories | Ryan | The RevOps lead corrects the sheet before it is shared | | Deal desk and champion | Deal desk decisions are recorded on their Notion pages, the departed champion is cleared, and affected deals are re-checked | Ada, then Fin | The deal desk confirms its decisions, and the RevOps lead approves | | Discount matrix | Every open deal with a discount at or above the new threshold is re-checked against the matrix | Fin, checked by Ryan | The deal desk confirms how the matrix reads | | Slips and pull-ins | Close dates moved in the quarter-end memo are applied and those deals re-categorized | Fin | Account executives confirm each date | | Closeout | Per-region totals are counted from final categories, with a closeout note for each region | Fin, checked by Ryan | The RevOps lead signs the review | Stages of one quarterly commit review. Deal IDs, regions and categories in this example are illustrative. ## A departed champion and a new discount matrix Clearing a champion is the start of the work, not the end. Fin clears the champion on the named deal, then runs the deal through the policy again from the top: a commit deal with no champion may drop to best case, take a new hold reason, or stay put if another contact qualifies. The change waits for the RevOps lead's approval, and Ada drafts replies on the two threads that asked, with each deal's ID and current category. A matrix change is wider than it looks. When the deal desk publishes a new discount authority matrix, every open deal with a discount at or above the threshold is re-checked, not just the deals the memo names. A deal whose discount now needs a higher approver goes on hold until the deal desk records that approval in Notion. Closed deals are never touched, even when a memo mentions them. ## What the checks catch - A closed deal that a memo mentions, left exactly as it is - A champion cleared without the rest of the policy re-run, so the deal stays at commit by accident - A deal above the discount threshold that the memo did not name, re-checked anyway - A printed sheet line whose category no longer matches Pipedrive - A reply that gives a deal's old category instead of its current one ## What stays with people - Approving every commit category and hold reason before Pipedrive changes - Approving discounts, which only the deal desk can do - Confirming close dates, which account executives own with their customers - Sending every reply and signing the regional closeout ## Integrations in this workflow Kylon is not a forecasting tool and it does not replace Pipedrive. It sits across the deals, meetings and approvals the team already keeps, and holds the commit reasoning in one thread. - [Gmail](https://kylon.io/integrations/gmail) - Google Calendar - Google Drive - [Notion](https://kylon.io/integrations/notion) - Pipedrive - [Slack](https://kylon.io/integrations/slack) - **Pipedrive** holds the deals, contacts and activities, and receives each approved commit category and hold reason - **Google Calendar** shows customer meetings, one of the signals the commit policy weighs - **Notion** holds the deal desk's discount approval pages, the only Notion records an agent writes - **Google Drive** keeps the commit policy, the printed forecast sheet and each memo - **Gmail** carries rep and leadership threads, answered with drafts a person sends - **Slack** is where regional leaders and reps post deal news between reviews, and Ada brings it into the deal's thread ## Where to start Start with one region's open deals for the current quarter. Connect Pipedrive with a lasting grant the RevOps lead approves, point the room at the deal desk's Notion space, and write the review's rule into the room guidelines: closed deals are out of bounds, every change re-runs the whole policy for that deal, and the RevOps lead approves each category before it is written. > “The commit number still comes from the reps. What changed is that every category can show where it came from.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our forecast commit review desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail, Google Calendar, Google Drive, Notion, Pipedrive and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the RevOps lead, the regional sales leaders, the deal desk and the account executives. Help me invite them to this Room. 3. Build a Commit Review App with Deal, Region, Category and Status columns, one record per open deal. Fill it from this quarter's open deals in Pipedrive. 4. For each deal, check its contacts, activities and close date in Pipedrive, customer meetings in Google Calendar, the discount approval page in Notion and the printed forecast sheet in Google Drive. Work through our checks one by one. When a champion is cleared, re-run the full policy for that deal. When a new discount matrix lands, re-check every open deal at or above the threshold we set, not only the deals the memo names. Show me every deal that fails a check. 5. Draft Gmail replies on open threads and propose each category and hold reason write to Pipedrive. Hold every draft and every Pipedrive write until the RevOps lead approves each category. The deal desk confirms its own discount decisions. Account executives confirm each close date. The RevOps lead signs the regional closeout before it is shared. 6. Write into this Room's guideline: closed deals are out of bounds, every change re-runs the whole policy for that deal, and the RevOps lead approves each category before it is written to Pipedrive. 7. After one clean review cycle, offer to turn our checks into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Price List Migration: Each Account Moves Once, at the Right New Amount Moving thirty wholesale accounts to a new price list means a disposition, an amount and sometimes a notice for each one. In a Kylon room, agents read HubSpot, Stripe and Mailchimp to propose them, and the revenue operations lead approves every change before a notice goes out. Retail & e-commerceRevenue operationsEmail operations ](https://kylon.io/use-cases/price-change-migration)[ ### SaaS Customer Renewal Desk: Renewals Closed or Held for a Reason That Is Still True Renewal dispositions, dunning, the order file review and late customer replies run through one Kylon room. Agents check every HubSpot deal against Stripe and both mailboxes, and the controller approves each stage change before it is written. Software & SaaSRevenue operationsFinance operations ](https://kylon.io/use-cases/saas-renewal-desk)