Territories, quotas and crediting — governed, live, visible.
The management layer over the selling engine: territory design, quota setting, crediting rules and the dashboards both reps and leaders run on.
- Territory and quota capture
- Feeds and hierarchy
- Parallel crediting
- Cut-over and first cycle
- Operated
Comp plans fail upstream.
Territories are drawn in slides in the last week of the fiscal year. Quotas are set by argument: a top-down number from finance meets a bottom-up number from the field, and the gap is closed by whoever is louder in the room. Crediting rules live in one analyst’s head, or in a spreadsheet tab only that analyst opens. Then the incentive engine calculates on those foundations, and disputes about a payout often turn out to be disputes about a territory or a quota that nobody wrote down.
The sales performance module of Sales Performance puts the upstream under governance too. Territories are rules with effective dates. Quotas are versions with an owner and an approval. Crediting is configuration the engine reads, not a spreadsheet the engine hopes agrees with it. Reps see their standing as it moves; leaders see the season forming before the quarter closes it. The incentive engine downstream then calculates on foundations that hold.
The module deploys on its own — governance first, calculation second is one possible path — and pairs with direct sales incentives when the same organisation wants the payout engine to read the territories and quotas it now governs. Both run on the same instance, against the same ledger.
Four modules, one governed record.
Each module owns one of the inputs a comp plan depends on. Because they write to the same record, a quota knows which territory version it was set against, crediting knows which quota it is measured on, and analytics knows all three.
Territory design
Rules-based territories with what-if modelling before the reorg, not after. Accounts are assigned by rule — geography, segment, named list, industry — and every rule carries an effective date. A proposed reorg is modelled against last year’s bookings so its effect on coverage, workload and attainment is known before anyone announces it.
Quota management
Top-down and bottom-up reconciliation with a full history of who changed what. Finance publishes the number, the field builds theirs, and the platform shows the gap by region, team and rep. Every change is a version with an author, a reason and an approval, so every quota change carries an audit history.
Crediting rules
Role-based crediting as configuration — overlays and splits included. Who gets credit for a deal, in what share, and against which quota is written once as a rule set the engine executes on every booking. Crediting rules live on the platform, not in spreadsheets.
Leadership analytics
Attainment distributions, plan-cost projections and health signals per team. Leaders see where the season is forming — which teams are bunched below quota, which plans are about to cost more than budgeted, which territories have gone quiet — while there is still time to act on it.
What it does, in detail.
Quotas reconciled in the open.
Finance publishes the top-down number by region. Managers build the bottom-up number rep by rep. The platform puts both against each other at every level of the hierarchy and shows the gap, so the reconciliation happens on a screen both sides can read rather than in a meeting neither side remembers the same way. Each quota is a version: who set it, when, why, and who approved it. A mid-year change creates a new version with an effective date; the attainment ledger measures the right period against the right number, and the history is one click away when a rep asks.
- Top-down and bottom-up compared at region, team and rep level, with the gap shown at each
- Every quota change is a version with an author, reason, approval and effective date — all of it on the audit record
- Ramp schedules, leave and partial periods handled as rules, not manual proration
Crediting as configuration.
Who gets credit for a booking, in what share, and against which quota is decided by a rule set — primary owner, overlays, named splits, roll-ups to managers — that the engine executes on every transaction. Overlays and splits are rules with a role and a percentage, not adjustments typed in after the fact. Because the rules are versioned like everything else, a booking credited last quarter can be replayed under the rules that applied then, and gives the same answer. When the incentive module is deployed, it reads these credits directly; there is no second crediting layer to keep in step. The credit percentages shown here are examples.
- Primary, overlay, split and roll-up credit as rules by role; splits must sum to 100 %
- Credit follows the territory in force at close date, so reorgs do not rewrite the past
- Replayable: any credit can be recomputed under the rule version that applied and shown to the rep
The season, visible while it forms.
Leadership analytics reads the attainment ledger, not a monthly extract. The attainment distribution per team shows whether a plan is motivating or merely paying; plan-cost projection shows what the year will cost at current run rate against what was budgeted; health signals flag territories with no activity, quotas that no one in a team is on track to reach, and crediting rules that have started producing exceptions. Each figure opens to the records behind it, so the conversation with a regional leader is about specific territories and specific quotas, not about whose spreadsheet is right.
- Attainment distribution per team and plan, with the reps behind each band
- Plan-cost projection at current run rate against budget, updated as bookings land
- Health signals: quiet territories, unreachable quotas, rules producing exceptions
One record, three readers.
Run the planning cycle without rebuilding it.
Sales operations owns the annual cycle: territory model, quota roll-out, crediting rules, then the mid-year corrections. On the platform each step is a versioned artefact with an approval, so the cycle is a sequence of decisions on the record rather than a season of spreadsheets.
- Territory, quota and crediting versions with approvals in one place
- What-if runs before a reorg or a quota change is announced
- Exceptions queue for accounts, bookings and credits that no rule covers
The plan cost, before it is paid.
Finance sees the top-down number reconciled against the field’s number, the projected cost of each plan at current attainment, and the audit history behind every quota. Approval thresholds are theirs to set: a quota change above a percentage, or a territory move above a revenue figure, waits for a named person. When the incentive module is deployed, payout accruals are projected from the same ledger, so finance plans on the record the engine pays from.
- Top-down versus bottom-up gap at every level of the hierarchy
- Plan-cost projection against budget, updated as bookings land
- Approval thresholds and approvers as configuration
Standing that moves when the deal does.
A rep sees their territory, their quota and its version history, their attainment to date and how each booking was credited — with the rule that produced the credit shown in plain language. A manager sees the same for the team, plus the distribution and the exceptions waiting on them. Trust comes from being able to check the number on the screen.
- Own territory, quota history and attainment on one screen
- Every credit traceable to the booking and the rule that produced it
- Manager view: team distribution, exceptions and pending approvals
Org data in, one attainment ledger, every dashboard from it.
What ships, what is configured.
Hierarchies in, attainment back.
Salesforce
Account hierarchies, opportunities and splits in; territory, quota and attainment written back
HRIS
Roles, managers, start and leave dates with effective dating, landed under governed contracts
ERP
Bookings, invoices and credit notes as the transactions crediting runs on
Account master
Firmographics and segment data for assignment rules, kept in sync with your MDM
Direct incentives module
Territories, quotas and credits handed to the calculation engine of direct sales incentives — no second crediting layer
Data platform
Territory, quota, credit and attainment tables exported to your warehouse and BI
Workflow & Procurement
Approval flows for reorgs and above-threshold quota changes
Territories first, quotas second, crediting once the feeds agree.
Territory and quota capture
We read the current model with the people who own it — the slides, the spreadsheets, the exceptions everyone knows about — and rebuild it as rules, versions and approvers on the platform.
Feeds and hierarchy
CRM, HRIS and ERP land under governed contracts. The org hierarchy is effective-dated and reconciled against the territory model; the mismatches are a useful first finding.
Parallel crediting
The crediting engine runs alongside your current process until the numbers agree. Every difference is explained.
Cut-over and first cycle
Territories, quotas and crediting go live as the source of truth. Dashboards open to reps and managers; the next planning cycle runs on the platform from the first what-if.
Operated
The Odeontech team that built the module runs it to SLOs agreed with you, supports each planning season and each reorg, and hands credits to the incentive engine when that module is added.
Frequently asked questions
Elsewhere in the family.
See it on your own org chart.
A guided demo with an engineer who operates the platform — configured toward your territories and quotas, not a canned deck.