Build a revenue forecast committee that produces one board number

Start with a written charter that names the four permanent members, the decision rights, and the artifacts the committee produces. The CRO owns sales commit and overall revenue accountability. The CFO owns the plan, revenue recognition rules, and the submitted board number once signed. The CMO owns marketing sourced and influenced pipeline, campaign driven acceleration, and demand forecast. The Head of Customer Success owns the renewal forecast, churn risk, and expansion commit. Keep the roster to those four voting members plus a RevOps scribe. Observers can be invited to specific reviews, but they do not vote. Publish the charter inside Strkr so every committee member reads from the same document and new executives inherit the operating rules on day one.

• Write a one page charter covering purpose, members, decision rights, cadence, inputs, outputs, and escalation path
• Name a RevOps scribe who prepares the pre read, captures decisions, and owns the follow up log
• Lock the roster to four voting members so reconciliation stays a conversation, not a town hall

The committee runs monthly, not weekly. Weekly is where the sales forecast call lives. The committee meets once per month, usually in the second week, after close has settled and before the board packet locks. Set a fixed ninety minute window on the same day every month and treat it as unmovable. Each member submits their inputs forty eight hours before the meeting so RevOps can build a pre read that highlights the gaps. The output is a signed submission from the four members and a short decisions memo. Weekly forecast calls still happen inside sales. Monthly committee reviews reconcile the full revenue picture across functions.

• Lock a recurring ninety minute slot in the second week of each month with no rescheduling without CRO approval
• Require member inputs forty eight hours in advance so the pre read catches gaps before the room meets
• Keep weekly sales forecast calls separate; the committee is reconciliation, not pipeline inspection

Standardize the four inputs so the pre read reads the same every month. Sales submits the forecast as Commit, Best Case, Pipeline, and Omitted broken out by segment and new logo versus expansion. Marketing submits sourced pipeline, influenced pipeline, pipeline coverage by segment against the next two quarters, and the demand plan for the trailing and leading quarters. Customer success submits gross retention commit, net retention commit, named at risk accounts above a dollar threshold, and expansion commit by segment. Finance submits the plan broken down by month, the trailing variance against plan, and revenue recognition timing for any non standard contracts. All four submit through the same template inside Strkr so the pre read builds from one source of truth, not four PDFs.

• Publish an input template for each role with required fields, due date, and owner
• Store every submitted pack as an immutable snapshot in Strkr so monthly variance analysis has clean inputs
• Flag any input that arrives late or incomplete and escalate to the CRO before the meeting opens

The first reconciliation at every meeting is the sales commit against the marketing pipeline that is supposed to feed it. Walk the next two quarters by segment. For each segment, compare the pipeline coverage ratio marketing is holding against the coverage the segment needs to hit plan at historical close rates. Where coverage is short, decide whether to shift marketing spend, open a BDR play, pull expansion earlier, or lower the submitted number. Where coverage is high but late stage is thin, flag it as a timing risk even if the headline ratio looks safe. The output of this reconciliation is not a longer debate. It is a named decision: who does what by when to close the gap, logged in Strkr with an owner and a due date.

• Compare pipeline coverage per segment against the inverse of trailing close rate plus a slippage buffer
• Audit stage distribution per segment so thin late stage pipeline is not hidden by a strong headline ratio
• Log every gap closure decision as a task in Strkr with owner, due date, and the dollar amount at stake

Renewals and expansion often move the number more than new logo pipeline, especially in later stage SaaS. Walk the renewals cohort for the current and next quarter. For every named at risk account above the submission threshold, confirm whether the number assumes a full renewal, a partial downsell, or a full churn. Then walk the expansion commit by segment and verify it reconciles with what marketing and sales are forecasting on existing accounts. If the CRO is forecasting a large expansion deal that the CS lead has flagged as at risk, that gap gets resolved in the room, not inside a side channel. The committee submits one number for the renewal line and one number for the expansion line, both signed off by the Head of CS and the CRO together.

• Review every at risk renewal above the threshold with a current status, risk tag, and owner
• Reconcile expansion forecast between the account owner on the sales side and the CSM on the CS side
• Record the dollar impact of each at risk account so finance can model the downside scenario

Once sales, marketing, and CS have been reconciled, roll the three streams into one revenue number and compare it to the finance plan line by line. Walk new logo bookings, expansion bookings, and renewals against plan for the current quarter and the next two. Where the committee number is below plan, decide what mitigation is being committed to and quantify it. Where the committee number is above plan, decide whether to raise the submitted number or hold conservative buffer. The CFO owns the revenue recognition translation from bookings to recognized revenue, which often changes the apparent gap. Finance also calls out any one time revenue effects, such as early renewal pull forwards, that distort month over month comparisons.

• Compare the reconciled number against plan at the bookings level and at the recognized revenue level
• Separate structural gaps that need plan revisions from timing gaps that only need better execution
• Quantify every mitigation commitment in dollars so the next month variance analysis can grade it

The committee is not a reporting meeting. It is a decision meeting. Every month, close with three risk mitigation decisions that will be executed before the next committee meeting. One decision pulls a lever on pipeline, such as reallocating marketing spend or shifting a BDR team. One decision pulls a lever on retention, such as triggering an executive save motion or a pricing concession. One decision pulls a lever on execution velocity, such as compressing a legal cycle or sequencing a key hire. Each decision gets an owner, a dollar impact estimate, and a due date. The decisions and their owners are the primary artifact the committee produces, more important than any slide in the pre read.

• Force the room to pick exactly three decisions; more and nothing gets done, fewer and the committee is not earning its hour
• Attach a dollar impact estimate so the next month can grade whether the lever actually moved the number
• Assign a single named owner on each decision; a decision owned by two people is owned by neither

The output of the committee is two artifacts: the signed revenue number and a one page decisions memo. The signed number includes Commit, Best Case, and the plan variance for the current quarter and the next two, with sources broken out by new logo, expansion, and renewal. The memo captures the three mitigation decisions, their owners, their due dates, and the dollar impact assumed. Both artifacts are submitted inside Strkr with a timestamp and member signatures. The CFO carries the number into the board packet. The CRO carries the decisions into weekly operating reviews so the levers get pulled rather than filed. Variance analysis next month references the signed version, which is why the lock matters.

• Submit the number and the memo inside Strkr with timestamps and the four member sign offs
• Mirror the number into the board packet exactly as submitted; no quiet edits between committee and board
• Cascade the three decisions into weekly operating cadences so the levers actually get pulled

The committee compounds only if it grades its own work. Within five business days after the month closes, RevOps runs variance analysis against the signed number from the prior committee. Compare submitted versus actual at the Commit level, Best Case level, and plan level. For each miss, tag the cause: pipeline shortfall, renewal loss, slippage, deal shrink, forecast error, or external event. Grade each of the three mitigation decisions on whether the lever moved the dollar amount it was supposed to. Feed those tags into the next pre read so the committee can see the pattern. Teams that run this loop every month tighten their quarterly forecast error inside two quarters because the committee stops making the same mistakes.

• Grade submitted versus actual at Commit, Best Case, and plan for each of the three streams
• Tag every variance with a cause code and publish the distribution to all four members before the next meeting
• Grade each mitigation decision on whether the committed dollar lift actually arrived