Ask finance, sales, and RevOps for the number.
If you get three answers, keep reading.
We build planning models in Anaplan and Pigment for SaaS companies. Not dashboards, not reports. The model your CFO, CRO, and RevOps team all agree to argue inside of.
Whose number is the number?
Most SaaS companies at $20M+ ARR are running at least four versions of next quarter at any given moment.
The board plan
Finance owns it. It was locked in December.
Street quota
What sales carries. The plan, plus cushion.
The CRM roll-up
Whatever the reps said last time they updated their deals.
Marketing's model
Pipeline-sourced. Agrees with none of the above.
Nobody is lying. They're four spreadsheets that have never met.
So the week-two forecast call turns into an argument about whose spreadsheet is right instead of what to do, and the reconciliation happens in slide decks the night before board. We've watched this at companies with excellent finance teams. The people aren't the problem. The disconnection is.
Here's the part that stings: even the pipeline math underneath those numbers is usually stale. The old rule says carry 3x pipeline coverage. That rule quietly assumes you win about a third of what you chase, and nobody wins a third of what they chase anymore.
A planning model earns its keep on one question: in week four, is the gap a conversion problem or a pipeline-creation problem?
The churn that renews at 85 cents on the dollar
Logo retention: 100%. Nobody canceled. The contract just renewed at 85% of last year's value.
Your customer runs leaner now and rationalized seats at renewal. Your ARR waterfall reports it months after it happened, filed under "contraction," lumped in with actual churn, which has a completely different fix.
Meanwhile expansion is quietly carrying the growth story. Benchmarkit's framing is the right one: past the 40% line, expansion has stopped amplifying new-logo growth and started substituting for it.
Twenty reps with $1M quotas is not $20M of capacity
This is the section where we lose people who plan headcount as a percentage of revenue. So let's do the math.
Run those honestly and a "twenty reps, $20M" plan holds maybe half its paper capacity. The plan didn't miss in Q3. It missed in the planning cycle, silently, before anyone sold anything.
And then quotas ship late.
Reps missing quota is a selling problem. Most of this isn't that.
One connected model. One number.
Built in Anaplan or Pigment, on live Salesforce and ERP data, where a change to a ramp assumption reprices the whole year without anyone reconciling anything by hand.
New, expansion, and renewal modeled separately, and carried past the bookings number: through billings, deferred revenue, and cash.
- Beginning + New + Expansion − Churn
- Contraction separated from logo churn
- Renewals forecast like a pipeline
- Bookings → ARR → revenue → cash
Heads × ramp × attainment × attrition, tied to the hiring plan. So the bookings target and the headcount plan stop disagreeing.
- Ramp curves by segment
- Attrition and backfill lag modeled
- Req-to-start lead times
- Capacity vs. plan, visible weekly
Bottom-up from territory potential, reconciled against the board's top-down number, with the gap made visible before comp plans go out.
- Territory scoring by potential
- Top-down vs. bottom-up reconciliation
- Mid-year re-carves without chaos
- Quotas out before day one
Bookings-based comp with accelerators, SPIFs, splits, and clawbacks, and rep-facing statements reps can check themselves.
- Model plan changes before announcing
- Rep-facing payout visibility
- Clawback and true-up automation
- No more shadow spreadsheets
If you've added usage pricing, consumption gets its own engine, reconciled against bookings. Forcing usage revenue into a contracted-ARR shape is how consumption quarters get missed.
- Cohort-level consumption curves
- Commit, drawdown, and overage
- Reconciled to the bookings forecast
The plan your board actually sees: P&L, balance sheet, and cash flow driven by the revenue and headcount models, with GL integration.
- Scenario and downside planning
- Board what-ifs in hours, not weeks
- Efficiency metrics in the forecast
Where this shows up first
In the reforecast. And in the commission run.
Two things we say that cost us deals
Under roughly $10M ARR, a strong analyst in Excel is usually the right answer.
And we'll tell you that in the first call. A planning platform pays for itself when the model has to hold revenue, capacity, quota, comp, and cash at once. Below that, it's overhead.
Even after go-live, some of your planning should stay in spreadsheets.
Anything exploratory, one-off, or owned by a single person thinking out loud belongs in Excel. The model is for the numbers the company runs on. An implementation partner who says otherwise is selling seats, not advice.
We hold no reseller agreement with Anaplan or Pigment. When we recommend one over the other, it's because it fits.
Questions about SaaS planning
Does PlanFlamingo specialize in SaaS companies?
+
Can you build an ARR waterfall in Anaplan or Pigment?
+
Which platform is better for SaaS: Anaplan or Pigment?
+
Can you connect Salesforce to our planning model?
+
Bring your last forecast.
And what actually happened.
We'll tell you in 30 minutes whether the gap is your model or your market. If the honest answer is "stay in Excel for another year," you'll hear that too.