SaaS Planning

Planning infrastructure built for SaaS

SaaS metrics are fundamentally different from traditional enterprise planning. ARR is not revenue. Quota is tied to bookings, not revenue. Pipeline velocity drives everything. We specialize in helping mid-market and enterprise SaaS companies implement Anaplan and Pigment with the right model architecture from day one.

Why SaaS Is Different

SaaS planning requires different thinking

Traditional enterprise planning models don't work for SaaS. You need models built specifically around SaaS metrics and business logic.

ARR is not revenue

ARR (Annual Recurring Revenue) and GAAP revenue are completely different numbers. Your P&L recognizes revenue on a straight-line basis. But your business is driven by ARR: bookings → ARR → revenue over time. You need an ARR waterfall that flows into revenue recognition.

Quota and commissions are tied to bookings

Reps close deals that generate ARR, but you can't pay them on revenue (which recognizes over time). You need a commission engine that ties payouts to bookings, with clear rules for contract terms, renewal bookings, and expansion bookings.

Pipeline velocity drives everything

For SaaS, pipeline is the leading indicator. Your 3-month forward pipeline tells you more about next quarter revenue than your financial forecast. You need your planning model connected to your CRM (Salesforce) in real-time to see pipeline → bookings → revenue flow.

Headcount scales with revenue, not linearly

SaaS companies hire based on ACV and revenue targets. Your headcount plan needs to tie to your revenue plan: target ACV × target customers = target revenue, which drives hiring in Sales. Workforce planning must integrate with revenue planning, not sit in a separate model.

Renewals and expansion matter as much as new business

For SaaS, the renewal rate and expansion revenue are as important as new bookings. A true SaaS financial model breaks ARR into: Beginning ARR + New Business + Expansion - Churn. You need visibility into each component, not just "revenue."

What We Build

Use cases for SaaS companies

PlanFlamingo builds planning models across all the areas that drive SaaS business. From revenue planning to go-to-market to headcount to platform migrations.

📈
FP&A and 3-Statement Models

Full P&L, balance sheet, and cash flow models. Driven by revenue and headcount plans with full GL integration.

  • Revenue planning integration
  • Headcount cost modeling
  • Full financial statements
  • Scenario analysis & sensitivities
📊
ARR Waterfall & Revenue Forecasting

Beginning ARR + New + Expansion - Churn = Ending ARR. Connected to Salesforce and your ERP.

  • Beginning/ending ARR tracking
  • New business ARR modeling
  • Expansion & renewal revenue
  • Revenue recognition integration
👥
Headcount Planning Tied to Revenue

Connect hiring plans to revenue targets. Model Sales, CS, and product headcount by target ACV and revenue.

  • Revenue-driven hiring plans
  • Headcount by department & function
  • Cost per revenue metrics
  • Scenario analysis for hiring
🎯
Territory & Quota Planning

Assign quota based on territory potential, market size, and revenue targets. Track to plan vs. actual.

  • Territory sizing & assignment
  • Quota allocation methodology
  • Plan vs. actual tracking
  • Waterfall to bookings
💰
Commission Engines

SaaS commissions tied to bookings, not revenue. Multi-tier plans with accelerators, SPIFs, and territory splits.

  • Bookings-based commission logic
  • Multi-tier plan structures
  • Territory & quota assignments
  • Rep-facing visibility portals
🔄
Platform Migrations

Move from Anaplan to Pigment or vice versa. We handle model redesign, data migration, and testing.

  • Model assessment & redesign
  • Data extraction & migration
  • User testing & UAT
  • Parallel run & cutover support
SaaS Clients

SaaS companies we've worked with

Renaissance
EdTech SaaS — 4+ year managed services engagement for ARR waterfall, commission engine, and headcount planning.
"PlanFlamingo helped us build planning infrastructure that actually reflects how we run the business."
MeridianLink
SaaS for financial institutions — Implemented Anaplan ARR waterfall and bookings-to-revenue model with Salesforce integration.
"Gave us visibility into pipeline, bookings, and revenue flow for the first time."
Upwork
Marketplace SaaS — Built FP&A and headcount planning models connected to marketplace metrics.
"Helped us model hiring against marketplace growth and unit economics."
FAQ

Questions about SaaS planning

Does PlanFlamingo specialize in SaaS companies?
+
Yes. SaaS planning is fundamentally different from traditional enterprise planning because the metrics that matter (ARR, bookings, renewal rate, expansion revenue) are different from traditional revenue recognition. We have built planning models for SaaS companies in EdTech, financial services, HR tech, and vertical SaaS verticals. We understand the nuances of SaaS metrics and can help you structure your planning around what actually drives your business.
Can you build an ARR waterfall in Anaplan or Pigment?
+
Yes. ARR waterfalls are one of our core specialties for SaaS companies. We build beginning ARR + new business ARR + expansion ARR - churn ARR = ending ARR models in both platforms. These models integrate with your CRM (Salesforce) to pull bookings data, reconcile to revenue recognition in your ERP, and tie headcount planning to your revenue plan. The tricky part is getting the bookings → ARR → revenue recognition flow right, and we've done it dozens of times.
Which platform is better for SaaS — Anaplan or Pigment?
+
Both platforms are excellent for SaaS planning, but they have different strengths. Anaplan is stronger for enterprises with very large seller teams, complex quota structures, and multi-dimensional modeling. Pigment is faster to implement and easier to use for smaller SaaS companies, especially for revenue and headcount planning. In most cases, we recommend Pigment for Series A-D SaaS companies and Anaplan for enterprise-scale companies. We can advise which is better for your specific situation.
Can you connect Salesforce to our planning model?
+
Yes. Salesforce integration is critical for SaaS planning because your pipeline, bookings, and quota data lives there. We build Salesforce connectors in both Anaplan and Pigment to pull daily or weekly bookings data, merge it with revenue recognition data from your ERP, and keep your planning model always in sync with your CRM. Salesforce → Planning Model → ERP accounting is the data flow we typically implement.

Ready to build SaaS planning that actually works?

We'll spend 30 minutes understanding your SaaS metrics, current planning approach, and what's broken. Then we'll recommend the right platform and approach for you.

Response within one business day. hello@planflamingo.com