Forecast versus quota system blueprint
This system aligns quotas, opportunity forecasts, and booked revenue under one set of definitions. It updates attainment and pacing by rep and management hierarchy, highlights gaps and concentration risk, and prepares explainable forecast-versus-target views for sales reviews.
- Business function
- Revenue
- Operating context
- Across the business
- Primary owner
- VP Sales
Operating brief
What starts the system
Quota, opportunity forecast, booking, territory, or sales hierarchy data changes.
Quota and territory versions are effective-dated and approval-controlled
Operating sequence
How the system works
1. Normalize quotas, forecasts, and bookings to the active sales hierarchy and reporting currency.
2. Calculate attainment, pacing, gap, and concentration by rep, team, region, and period.
3. Flag exceptions, capture owner commentary, and publish the sales-review view.
Inputs
- Rep, team, territory, and period quotas
- Opportunity forecasts and probability categories
- Bookings, credits, currencies, and hierarchy assignments
Outputs
- Forecast-versus-quota dashboard
- Rep and team gap register with commentary
Controls
- Quota and territory versions are effective-dated and approval-controlled
- Forecast categories and booking credits follow governed definitions
Source landscape
Examples of systems it may connect to
- Salesforce
- HubSpot
- Clari
- Lime CRM
Reusable core
What can carry across companies
The reusable core is hierarchy alignment, quota pacing, forecast comparison, exception detection, and commentary workflow.
Your installation
What must be adapted
Quota periods, credit rules, forecast categories, currencies, territories, and roll-up hierarchies vary by sales model.
Start with the closest pattern–or start from your process.
The catalogue represents reusable operating shapes, not fixed off-the-shelf applications.