What makes SaaS forecasting different from generic sales forecasting?
SaaS forecasting has to separate four distinct cohorts: new-ARR (new logo bookings), expansion (upsell, cross-sell, seat growth), downgrade (seat reduction, downsell), and churn (lost logo). Each has a different owner, cadence, risk profile, and financial impact. Generic forecasting that collapses all four into a single bookings number loses signal, a healthy new-ARR quarter can hide a looming renewal cliff, and expansion-driven NDR growth can offset soft new logo without the forecast surfacing why. Strkr runs the weekly commit lock on each cohort separately and projects net dollar retention from the renewal pipeline, expansion commit, downgrade commit, and churn risk directly.
How does the NDR projection work?
Net dollar retention is projected against the trailing twelve-month cohort baseline (the ARR of accounts that existed twelve months ago, read from account records on their quarter-ago anniversary date). The projection reads six inputs: cohort ARR as denominator, renewal pipeline for the quarter with per-account probability, in-cohort expansion commit, in-cohort downgrade commit, churn risk projection, and the save-motion recovery assumption. The CFO sees NDR with and without save-motion contribution so the base case and the optimistic case are both visible.
How does Strkr catch silent downgrades reps avoid logging?
Downgrade signals pull from product usage automatically: seat drop in the usage telemetry, feature usage decline, exec change on the account, support ticket pattern shift. The signals surface on the account record and in the downgrade commit on the forecast surface regardless of whether the rep has logged a formal downgrade deal. The CS team sees the real state rather than the optimistic rep-logged state, and the forecast reflects reality.
How does the forecast reconcile against the billing system?
Strkr integrates with Stripe, Chargebee, Zuora, QuickBooks, NetSuite, and the common SaaS billing stacks. Each committed deal ties to its invoice schedule, each account carries the live subscription state (active, past-due, canceled, pending), the cash-collected tile shows paid against sent, cancellations tie to the churn forecast, and ASC 606 revenue recognition reads from the bookings surface. The CFO reads bookings, cash, and revenue on the same records rather than reconciling across tools.
Can we handle multi-year prepaid contracts correctly?
Yes. Multi-year prepaid deals carry the full ACV in the new-ARR commit at close, and the invoice schedule from the billing system shows the cash timing (prepaid year one, invoice year two, invoice year three). The ASC 606 schedule reads from the bookings surface and the revenue recognition is deferred appropriately. The CFO sees the booking impact, the cash timing, and the revenue recognition on the same surface without manual reconciliation.
Who owns which cohort in the forecast?
New-ARR is owned by the AE team with sales management oversight. Expansion is co-owned by the AE and CS owner on each account (AE for product cross-sell and upgrade motion, CS for seat growth). Downgrade is owned by the CS team with product usage signals feeding the commit. Churn risk is owned by CS with CS leadership and the CRO reviewing at-risk accounts weekly. The ownership is enforced in the forecast UI so the right owner updates the right cohort, and the audit log carries the attribution.
