SaaS Planning

Planning software built for SaaS metrics.

Anaplan and Pigment implementations built around the numbers that actually run a SaaS business: ARR, bookings, pipeline velocity, and net revenue retention.

30 minutes with our founders. No sales pitch, just answers.

Industry Challenges

Why SaaS planning is different.

The metrics that run a SaaS business are not the metrics on the P&L. Planning models built for traditional revenue break on the difference.

ARR Is Not Revenue, and Consumption Makes It Worse

ARR and GAAP revenue are different numbers, and consumption revenue makes them more different. The P&L recognizes revenue on a straight line, but the business is driven by bookings that become ARR that become revenue over time, plus usage-based commitments that recognize as customers consume. You need an ARR waterfall and a consumption forecast that reconcile to the same revenue line.

Quota and Comp Ride on Bookings

Reps close deals that generate ARR, but you can't pay them on revenue that recognizes over months. The commission engine has to tie payouts to bookings, with clear rules for contract terms, renewals, and expansion, or the numbers reps see never match the numbers finance holds.

Pipeline Velocity Leads Everything

Pipeline is the leading indicator. Your three-month forward pipeline says more about next quarter than the financial forecast does. The planning model has to sit on live Salesforce data to see pipeline turn into bookings turn into revenue.

Sales Capacity Is a Model, Not a Ratio

Rep productivity, ramp curves, attainment distribution, and attrition combine into required sales capacity, then you back into a hiring plan by quarter. Headcount as a flat percentage of revenue is what breaks the moment attainment shifts. Workforce planning has to live inside the revenue plan, or the two disagree the moment reality does.

Gross Retention and Net Retention Answer Different Questions

GRR is whether the base is holding under macro pressure. NRR is whether the base is growing. A real ARR waterfall separates both, so you can see whether growth is coming from new logos, expansion, or renewal strength, and where the actual leaks are. Reporting only NRR hides the GRR conversation the board is now having.

Efficiency Metrics Drive the Plan

Growth alone stopped being the story in 2023. The plan has to model NRR, GRR, Rule of 40, CAC payback, burn multiple, and ARR per FTE alongside the growth curve. Efficiency has to be visible in the forecast, not calculated after the quarter closes.

Core Services

What we build for SaaS companies.

Finance-first. We start with FP&A and the ARR waterfall, then layer in pipeline, quota, commissions, and workforce planning.

Finance

FP&A & 3-Statement Models

Integrated P&L, balance sheet, and cash flow driven by the revenue and headcount plans, with full GL integration. Rolling forecasts, scenario modeling, and the efficiency metrics your board tracks.

Revenue

ARR Waterfall & Revenue Forecasting

Beginning ARR + New + Expansion - Churn = Ending ARR, connected to Salesforce for bookings and reconciled to revenue recognition in your ERP. New business, expansion, and renewal modeled separately.

Pipeline

Pipeline & Bookings Forecasting

Pipeline to bookings to revenue in one system. Win-probability weighting, AI-assisted forecast bias correction, and a closed loop between the sales forecast and the revenue plan so the two stop disagreeing. Pigment's forecast agents work directly on live Salesforce data inside the governed model.

Sales

Territory & Quota Planning

Territory sizing by market potential and segment, quota allocation tied to pipeline and historical conversion, and plan-versus-actual tracking that waterfalls back to bookings.

Compensation

Commission Engine

Bookings-based commission logic with multi-tier plans, accelerators, SPIFs, and territory splits. Rapid recalculation when deal terms change, plus rep-facing visibility so payouts are never a surprise.

Support

Managed Services

Annual comp plan rewrites, quarterly ARR reconciliation, new segment or product rollouts, and standing support as the go-to-market motion evolves. We stay with your model through pricing changes, sales team reorgs, and every quarterly board review.

Client Examples

Proven outcomes for SaaS companies.

Renaissance Anaplan + Pigment
550+
seller commission engine

EdTech SaaS. Commission engine for 550+ sellers alongside ARR and headcount planning. 4+ years of managed services, quarterly refreshes, and annual structure changes.

MeridianLink Anaplan
12,500+
contract revenue model

SaaS for financial institutions. Contract-level ARR and bookings-to-revenue model with Salesforce integration. Reforecast time dropped from a week to hours.

Questions about SaaS planning

Why is SaaS planning different from traditional enterprise planning?
+
The numbers that run a SaaS business are not the numbers on the P&L. ARR is not GAAP revenue. Quota and commissions are paid on bookings, not recognized revenue. Pipeline velocity is the leading indicator of next quarter, and headcount scales with revenue targets rather than a flat percentage. A SaaS model has to be built around bookings to ARR to revenue, with net revenue retention and efficiency metrics in view.
Can you build an ARR waterfall in Anaplan or Pigment?
+
Yes. ARR waterfalls are a core specialty. We build Beginning ARR + New + Expansion - Churn = Ending ARR in both platforms, with GRR and NRR surfaced separately, bookings pulled from Salesforce, and revenue reconciled to your ERP. The hard part isn't the waterfall itself. It's the reconciliation: ramp deals that start small and step up over year one, multi-year TCV that has to spread by year rather than collapse into ARR, mid-term expansions that shift ARR mid-quarter, and consumption revenue that has to reconcile without breaking the waterfall math. These are what break spreadsheet models. We handle them explicitly.
How do you reconcile bookings to ARR to revenue to RPO?
+
The reconciliation is the whole game. Bookings feed the ARR waterfall on contract effective date. ARR flows into revenue recognition based on delivery timing under ASC 606. RPO is the unrecognized portion of contracted revenue, and the board sees it quarterly. In Anaplan and Pigment we build these as connected views on the same underlying data, so bookings, ARR, revenue, and RPO tie every period. If they don't tie, you find out in the model before it appears in the earnings release.
Which platform is better for SaaS: Anaplan or Pigment?
+
Both are strong for SaaS. Anaplan is the deeper engine for enterprises with very large seller teams, complex quota structures, and heavy multi-dimensional modeling. Pigment is faster to implement and easier for a finance team to own, which suits most growth-stage and mid-market SaaS companies. We hold no reseller agreement with either vendor, so we advise on fit rather than margin.
Can you connect Salesforce to our planning model?
+
Yes. Salesforce integration is essential for SaaS planning because pipeline, bookings, and quota data lives there. We build connectors in both Anaplan and Pigment to pull bookings on a daily or weekly basis and merge them with revenue recognition from your ERP. The typical flow is Salesforce to planning model to ERP, so the model stays in sync with the CRM.
Why Anaplan or Pigment over spreadsheets or a BI tool?
+
Spreadsheets work until the model has to reconcile bookings, ARR, revenue, headcount, and commissions at once. Then they turn slow, error-prone, and owned by one person nobody can replace. BI tools report the past well but do not plan. Anaplan and Pigment give you audit trails, version control, scenario modeling, and live CRM and ERP integration in one governed system.

Ready to build planning for your SaaS company?

Let's talk through your challenges: ARR waterfall, pipeline and bookings, commission complexity, and platform fit.

30 minutes with our founders. No sales pitch, just answers.