FP&A and RevOps Collaboration Charter
This document establishes the roles, decisions, and operating rhythm between Finance (FP&A) and Revenue Operations for joint ownership of the revenue plan and forecast.
Core Philosophy
RevOps and FP&A are equals in revenue planning. Neither function owns the forecast alone; both own it together. RevOps owns operational accuracy (deal inspection, pipeline health, forecast discipline). FP&A owns financial implications (cash flow, working capital, headcount cost). The forecast only exits to leadership when both functions have validated it.
Role Definitions
RevOps Role: Pipeline Operator
What RevOps owns:
Deal Inspection Discipline
- Forecast category accuracy (Is this deal really a Commit, or is it Best Case?)
- Deal qualification standards (Is this deal truly sales-qualified opportunity?)
- Rep calibration (Which reps tend to over-forecast? Under-forecast?)
- At-risk identification (Which deals are at real risk of slippage?)
Pipeline Health
- Pipeline coverage ratio (Is coverage sufficient to hit target?)
- Deal velocity (Are deals moving through stages at historical rate?)
- Stale-deal identification (Which deals have been stuck >30 days?)
- Pipeline-generation cadence (Are we creating enough new pipeline?)
Forecast Accuracy Measurement
- Tracking forecast vs actual monthly
- Diagnosing variances (Over/under forecast? By segment? By rep?)
- Recommending forecast-discipline improvements
Weekly Forecast Call Execution
- Running Monday-Thursday forecast cadence
- Challenging loose Commits
- Identifying pipeline-generation priorities
- Escalating at-risk scenarios
Forecast Signal Detection
- Monitoring reforecasting triggers (coverage, close rate, accuracy)
- Escalating to FP&A when a trigger fires
- Proposing reforecast timing and scope
What RevOps does NOT own:
- Financial modeling or implications of forecast changes
- Board communication or financial reporting
- Compensation structure or quota-setting (that is gtm-planning)
- Cash flow or working-capital forecasting
FP&A Role: Financial Modeller
What FP&A owns:
Financial Modeling of Revenue Scenarios
- Translating revenue forecast into P&L impact
- Modeling headcount and expense implications
- Calculating working-capital impact (if revenue is pushed into next period, cash implications)
- Stress-testing assumptions (if top 3 assumptions miss, what is downside case?)
Board Communication
- Presenting plan and forecast to board
- Explaining variances to board
- Managing board expectations
- Communicating downside scenarios to board
Top-Down Target Setting
- Developing strategic revenue targets (based on board guidance, fundraising narrative, growth strategy)
- Documenting drivers of top-down target
- Running sensitivity analysis on top-down assumptions
Validation of Operational Assumptions
- Challenging RevOps assumptions (e.g. "Is 38% win rate realistic? What is the market benchmark?")
- Requesting supporting data for key assumptions
- Proposing alternative scenarios based on financial constraints
Forecast Accuracy from a Financial Lens
- Variance analysis (how far off was the financial forecast)
- Root-cause analysis (was it an operational miss or a financial assumption miss?)
- Budget impact (if we miss revenue by $X, what is the impact to expense budget?)
What FP&A does NOT own:
- Deal inspection or forecast category accuracy (that is RevOps)
- Pipeline hygiene or velocity analysis (that is RevOps)
- Reforecasting trigger monitoring (RevOps detects; FP&A responds)
- Weekly forecast call execution
Joint Decisions Matrix
This matrix clarifies which decisions require both functions' sign-off.
| Decision | Owner | Validator | Process |
|---|---|---|---|
| Plan of Record | Both | Board/CEO | Reconciliation meeting; both functions present; both sign off |
| Reforecast Approval | Both | Board (if >10% variance) | RevOps proposes; FP&A models; both approve; escalate if diverge |
| Forecast Categories Accuracy | RevOps | FP&A (audit) | RevOps sets standards; FP&A spot-checks quarterly |
| Pipeline Assumptions | RevOps | FP&A (validation) | RevOps builds from data; FP&A benchmarks against market data |
| Headcount Plan | Hiring (HR) | FP&A (cost) + RevOps (capacity) | HR proposes; FP&A models cost; RevOps confirms capacity impact |
| Stretch Scenario Feasibility | RevOps | Both | RevOps says "operationally doable"; FP&A says "financially doable"; both confirm |
| Forecast Variance Root-Cause | Both | CFO (if systemic) | RevOps diagnoses operational causes; FP&A models financial implications |
| Reforecast Trigger Thresholds | Both | N/A | Jointly set at planning time; locked for 12 months |
Weekly Sync Agenda (30 minutes)
Attendees: VP RevOps (or Head of Sales Operations), CFO or Finance Lead
Cadence: Every Monday or Tuesday (same time, same attendees)
Standing Agenda:
TIME AGENDA ITEM OWNER NOTES
---- -------- ------ -----
0-2m Previous week summary RevOps "Coverage was 3.1x. Close rate was 62%."
2-10m Pipeline signals RevOps Coverage trend, velocity, slippage rate, at-risk deals
10-15m Financial implications FP&A "If pipeline slips by 10%, cash impact is $X."
15-20m Reforecast triggers RevOps "Any triggers firing? Do we need to reforecast?"
20-28m Ad-hoc signals / escalations Both New competitive threat, customer churn, hiring slip?
28-30m Next week outlook + action items Both "We're monitoring coverage closely. Escalate if drops below 2.8x."
Decisions in this sync:
- No formal decisions. This is an information sync.
- If a reforecast trigger fires, schedule a 2-hour deep-dive for the following day
Escalation path:
- If RevOps detects a trigger firing, notify FP&A same day
- FP&A has 24 hours to model implications
- Both meet with CEO/CFO within 2 days if trigger warrants board communication
Monthly Forecast Review (1 hour)
Attendees: VP Sales, VP RevOps, CFO/Finance Lead, VP CS
Cadence: Last Tuesday of each month
Agenda:
TIME AGENDA ITEM NOTES
---- -------- -----
0-5m Month-end close summary "Closed $XXX. Plan was $YYY. Variance: Z%."
5-10m Forecast vs actual tracking "Forecast at month-start was $YYY. Actual $XXX. Accuracy: Z%."
10-20m Segment performance "New Biz: XXX. Expansion: YYY. Renewal: ZZZ."
20-35m Leading indicators for next month "Pipeline coverage: 3.0x. Velocity: 35%/month. At-risk deals: $Z."
35-55m Variance analysis (if applicable) "Why did we miss? Was it conversion? Pipeline quality? Execution?"
55-60m Reforecast decision "Do we reforecast now, or wait for quarter-end?"
Decisions in this meeting:
- Confirm forecast accuracy tracking is on schedule
- Identify any emerging risks (coverage trend, conversion trend)
- Decide if monthly variance warrants escalation to board
Quarterly Full Reforecast (4 hours)
Attendees: VP Sales, VP RevOps, VP CS, CFO/Finance Lead, CEO/Board
Cadence: Last week of each quarter
Agenda:
TIME (HOURS) AGENDA ITEM OWNER NOTES
----- -------- ------ -----
0-0.5m Opening frame CEO "Here is where we are. Here is what we learned last quarter."
0.5-1.0 Bottoms-up segment analysis RevOps "New Biz forecast: XXX. Expansion: YYY. Renewal: ZZZ."
1.0-1.5 Operational assumptions review RevOps "Win rate 38%. Sales cycle 60 days. Pipeline coverage 3.0x."
1.5-2.0 Financial modeling FP&A "At $X revenue, headcount cost is $Y, cash impact is $Z."
2.0-2.5 Variance analysis Both "We forecasted $8.5M YTD. We closed $7.9M. Root cause: sales cycle lengthened."
2.5-3.0 Scenario development Both "If we invest in ABM, pipeline upside is +$Z. Cost is $C. Timeline is 90 days."
3.0-3.5 Updated forecast + board comms FP&A/CEO "Revised forecast: $8.2M. Board message: we are X% of plan; here is why."
3.5-4.0 Decisions + next steps Both "Plan of Record updated. Reforecast triggers recalibrated. Next sync: 2 weeks."
Decisions in this meeting:
- Updated forecast (revision to Plan of Record)
- Scenario approval (which scenarios will we pursue?)
- Reforecast trigger recalibration (do thresholds need to change?)
- Board communication (what story do we tell?)
Output:
- Updated Plan of Record (published within 24 hours)
- Board presentation materials (if needed)
- Reforecast trigger summary (any changes to when we reforecast next?)
Conflict Resolution Protocol
When RevOps and FP&A disagree on a forecast or assumption, use this protocol:
Disagreement 1: Forecast vs Actual Variance
Scenario: RevOps says "Close rate is 60%." FP&A says "Wait, historical close rate should be higher; something is wrong with your data."
Step 1 (24 hours): RevOps and FP&A sync on definitions. Are you measuring the same thing?
- RevOps: "My close rate = deals that closed in period / deals in forecast at start of period"
- FP&A: "Your definition includes deals with 20% probability. My definition is Commit + Best Case. Different denominator?"
- If definitions differ, align on one definition and recalculate
Step 2 (if alignment does not resolve): Audit the data
- Pull 10 random closed deals. Did they close? Yes.
- Pull 10 random deals in forecast. Are they real opportunities? Are they in-period?
- If data is sound, there is no conflict; close rate is what it is
Step 3 (escalation): If data and definitions align but numbers diverge, escalate to VP Sales
- "Reps are categorizing deals differently than we expected. Here is what we are seeing."
- VP Sales adjudicates: which reps are over-forecasting? Which are under-forecasting?
Disagreement 2: Reforecast Triggers
Scenario: RevOps says "Coverage dropped to 2.4x; trigger fires, we should reforecast." FP&A says "Let's wait until month-end to see if it stabilizes."
Step 1 (24 hours): Acknowledge the signal. Both agree coverage dropped to 2.4x.
Step 2: Diagnose the signal. Is it temporary or structural?
- RevOps: "Last 2 weeks we had 3 deals slip into next period, and new pipeline generation was 20% below trend."
- FP&A: "OK, is the slippage a timing thing (deals will close next period) or a qualification thing (deals are dying)?"
- RevOps: "Deals are solid; they just need more time. Sales cycle lengthened."
- Diagnosis: Temporary timing shift, not structural quality issue
Step 3: Decide on reforecast timing
- FP&A: "If deals are healthy and will close next period, let's reforecast in 2 weeks when we have more data on whether the new-generation gap is real."
- RevOps: "Agreed. But if new pipeline stays 20% below trend through next week, we reforecast immediately."
- Both agree: Reforecast if coverage falls below 2.3x OR if pipeline-generation trend doesn't improve within 5 days
Outcome: Disagreement resolved through data, not seniority.
Disagreement 3: Stretch Scenario Feasibility
Scenario: Finance proposes "New ABM motion will generate $300K incremental pipeline." RevOps says "That assumes $50K CAC and 20% conversion. Our ABM runs at $75K CAC and 12% conversion today. $300K is fantasy."
Step 1 (24 hours): Both agree on the gap. Finance says $300K is the target. RevOps says current ABM runs at lower efficiency.
Step 2: Gather evidence
- RevOps: "Here are our last 4 ABM campaigns. Avg cost per qualified deal: $75K. Conversion: 12%."
- Finance: "Where is this data coming from? Is it properly attributed? Are we comparing apples-to-apples?"
- RevOps: "HubSpot campaign tracking + closed-won attribution. It is reliable."
Step 3: Scenario rebuild
- Finance: "OK, if your $75K CAC and 12% conversion are right, let's model it:"
- To generate $300K pipeline at 12% conversion = $25M pipeline needed
- At $75K CAC = $1.875M ABM spend (we don't have that budget)
- Finance proposes alternative: "What if we invest $300K in ABM? How much pipeline will we generate?"
- $300K spend / $75K per deal = 4 deals. At 12% conversion = 0.48 deals won. Say 1 deal = $85K revenue
- More realistic: $300K ABM spend = $85K incremental revenue in Year 1
- RevOps: "Yes, that matches our historical productivity."
Outcome: Stretch scenario is revised to realistic number ($85K) with realistic timeline (12+ months). Both functions agree on assumptions. Plan is updated to reflect this.
Escalation Triggers (When to Escalate to CEO/CFO)
Either RevOps or FP&A can escalate to CEO/CFO if:
- Reforecast variance exceeds 10% of plan (e.g. plan was $8.5M; forecast is $7.65M or $9.35M)
- Operational and financial views diverge (e.g. RevOps says plan is achievable; FP&A's cash modeling says it is not)
- Reforecasting triggers fire in rapid succession (e.g. coverage drops + close rate drops + NRR drops within 5 days)
- A major assumption becomes invalid (e.g. key person leaves, major customer churn, market disruption)
Escalation process:
- Initiator notifies the other function: "I am escalating to CEO. Here is my rationale."
- Both functions present their view to CEO (not pre-aligned; CEO hears both perspectives)
- CEO decides: reforecast immediately, wait for more data, or execute an emergency scenario
- Both functions document CEO's decision and execute
Meeting Norms and Collaboration Rules
Come with data, not opinions. "I think close rate is soft" is not a signal. "Close rate was 65% last month, 58% this month" is a signal.
Separate the plan from the forecast. Plan is locked ($8.5M POR). Forecast is current projection ($7.9M). Sync on forecast, not plan.
No surprises. If either function learns something material (customer churn, competitor disruption, hiring delay), notify the other within 24 hours.
Disagree, then align. If you disagree in a meeting, it is OK. But walk out aligned. "You say X, I say Y. Let's collect data by Thursday and reconvene Friday with a decision."
Trust the data, challenge the interpretation. Accept pipeline data from RevOps. If you think the interpretation is wrong, ask: "Walk me through your logic again."
No heroics. If a reforecast looks like it will be painful, that is OK. The forecast is not a punishment; it is a reset to reality.
Success Metrics: How to Know If Collaboration is Working
By end of Q1:
- Weekly syncs happen consistently (attendance rate >95%)
- Revenue team and Finance team refer to each other's data without hesitation
- When a reforecast trigger fires, both functions are notified within 24 hours
By end of Q2:
- Forecast accuracy improves (±15% or better; up from industry baseline of ±20%)
- Plan of Record is updated only when triggers fire (not ad-hoc)
- Board is never surprised by forecast changes (all major changes communicated in advance)
By end of Q4:
- Variance analysis shows that 80%+ of plan misses trace to a specific assumption (and can be fixed next year)
- Collaboration between RevOps and FP&A is seen as a competitive advantage by the leadership team
- Year-over-year forecast accuracy improves (if Year 1 was ±18%, Year 2 target is ±12%)