peopleanalyst

Tools · People analytics

Sales Crediting

Crediting rules that end the split disputes — every rule carries the dispute it prevents.

The method

Sales crediting architecture (point-of-persuasion crediting within incentive-plan design)

Quarter-end, and the same fight again: the account executive and the overlay specialist both claim the enterprise deal, the CSM's expansion revenue credits to nobody, and the compensation administrator adjudicates by whoever escalates loudest. Every rule the plan never wrote is a dispute on a schedule.

David Cichelli's Compensating the Sales Force supplies the organizing principle: reward sellers at the point of persuasion. Credit belongs to whoever persuaded the customer — which sounds obvious until a deal touches four roles, and which is precisely why Cichelli treats crediting as a supporting program to be designed alongside quotas and territories, not improvised at payout time. A crediting rule is a claim about where persuasion happened in your sales model; if you cannot say where that is, no formula will save you.

Zoltners, Sinha, and Lorimer's The Complete Guide to Sales Force Incentive Compensation places the plan inside a larger sales management system and teaches the diagnosis discipline that follows: what presents as a compensation complaint is often a territory, quota, or crediting defect wearing a comp costume. Fix the rule, not the rate. Mark Donnolo's What Your CEO Needs to Know About Sales Compensation adds the executive-level version: crediting balance is vital in team-based selling, because it is how contribution gets measured and accountability held — and the design conversation starts with the strategic questions, never with commission rates.

Donnolo's team-selling point carries an uncomfortable arithmetic most plans discover by accident: when multiple roles genuinely contribute, aggregate credit can legitimately exceed one hundred percent of the deal. Overlay roles exist to be paid on shared deals. That is a spend decision to make deliberately, with a number attached — not a surprise to find at accrual time.

The service writes the rule for each canonical scenario — role splits, overlay credit, team credit, booking-versus-billing timing, clawbacks, windfalls, territory transfers — each carrying its rationale and the specific dispute it prevents, flags honestly where your described deal flow cannot support a ruling, and closes with the double-crediting budget note.

The books behind this tool

How it works

Crediting-architecture designer grounded in the sales-compensation corpus: crediting principles for THIS sales model, then a rule per canonical scenario — role splits, overlay/specialist credit, team credit, timing (booking vs billing vs payment), clawbacks, windfalls, territory transfers — each with rationale and the specific dispute it prevents; closes with the double-crediting budget note (aggregate credit % vs 100% and why it's deliberate). Honest flags where the described deal flow can't support a ruling. Pairs with the toolbox quota & pay-mix designer as the sales-comp set.

You bring

{ plan_context, roles?, cluster? }

You get

{ plan_summary, principles[], rules[7 scenarios] (rule · rationale · dispute_prevented · determinable), double_crediting_budget, data_flags[], grounded_in, provenance }

Use it for

See it work

example output

AE + SE + CSM pod model with 9-month enterprise cycles, constant AE/SE split disputes, and expansion revenue credited to no one.

Sales-Crediting Architecture — AE + SE + CSM enterprise pod model

This is an enterprise SaaS motion built on three-role pods — AE (closes new/expansion deals), SE (technical validation and solution design), CSM (post-sale adoption and renewal/expansion). Deals run ~9 months, long enough that territory ownership and rep staffing routinely shift before close. The plan has two festering wounds: (1) AE and SE fight constantly over how a deal's value splits between them, because no fixed split exists and each thinks their contribution was decisive, and (2) expansion revenue — the lifeblood of a land-and-expand model — is credited to no one, so nobody is motivated to drive or defend it. The architecture below fixes both by making role splits fixed and non-negotiable per deal type, by explicitly crediting expansion to the CSM and the AE who works it, and by tying credit to selling stage transitions so that mid-cycle reassignments and territory moves are decidable the day they happen rather than litigated at close.

Crediting principles

  1. Credit follows customer-facing selling work at the moment it occurs, not account ownership on paper or who is staffed when the deal closes — because 9-month cycles guarantee staffing changes.
  2. Every dollar of expansion revenue must land on a named role. Uncredited revenue is unmotivated revenue in a land-and-expand model.
  3. Role splits are fixed by deal type and set BEFORE the deal advances, never negotiated deal-by-deal — the AE/SE dispute is caused by discretion, so we remove discretion.
  4. Aggregate credit deliberately exceeds 100% of deal value; each role is measured against a quota calibrated to its share, so overlap does not mean overpayment.
  5. Crediting must be reconstructable from CRM stage/timestamp data, not memory or advocacy — disputes are settled by the system of record, not the loudest rep.

Rules by scenario

Splits between roles

Rule: New-logo and expansion bookings split by FIXED percentages set by deal type, applied automatically at close: New-logo = AE 100% of AE-quota credit + SE 100% of SE-quota credit (each carries a separate quota, not a shared pool); Expansion = AE 60% / CSM 40% of expansion-quota credit; SE carries expansion-quota credit at 100% ONLY when a formal Technical Validation stage is logged in CRM for that expansion. There is NO negotiable per-deal split — the deal type in CRM determines the split. If a deal type is ambiguous (mixed new+expansion), each ARR component is classified and split separately by its own line-item type. Why: The AE/SE split war exists precisely because the current plan asks reps to negotiate a shared pool. Giving AE and SE SEPARATE quota-credit streams (not a split of one pool) means SE credit no longer subtracts from AE credit, which is the mechanical root of the dispute. Fixed-by-deal-type percentages remove the discretion that fuels advocacy. Dispute prevented: The recurring AE-vs-SE argument over 'how much of this deal was mine' — AE claiming the relationship closed it, SE claiming the technical win closed it. With separate credit streams keyed to a logged SE stage, there is nothing left to split-fight over. Roles: AE · SE · CSM Grounded in: Territory Balance & Crediting Integrity · Performance Measures & Weighting · Payout Formula & Plan Mechanics · Perceived Fairness, Understanding & Trust

Overlay / specialist credit

Rule: SE is treated as an overlay carrying a dedicated SE quota credited at 100% of the ARR of any deal where the SE completed and logged the Technical Validation stage. SE credit is not reduced by, and does not reduce, AE credit. SE receives NO credit on deals that close without a logged Technical Validation stage (e.g., pure renewal or CSM-driven low-complexity expansion). If more than one SE touches a deal, credit goes to the SE named as owner of the Technical Validation stage at the time it was marked complete; secondary SEs get 0% unless a manager files a formal split-override, capped at 50/50. Why: In this pod model SE is the classic technical overlay; the corpus treats overlays as separately-quota'd rather than sharing the AE pool. Tying SE credit to a discrete CRM stage makes 'did the SE earn credit' a data question, not a judgment. Dispute prevented: SE-vs-AE fights over whether the SE was 'really involved enough' to earn a cut, and SE-vs-SE fights when a deal is reassigned between SEs mid-cycle. Roles: AE · SE Grounded in: Strategy, Role & Job Design Alignment · Territory Balance & Crediting Integrity · Administration, Analytics & SPM Technology

Team credit

Rule: The pod (AE+SE+CSM) does NOT share a single pooled quota; each role carries its own quota and earns its own credit stream per the role_splits rule. A pod-level accelerator applies only as an overlay bonus: if the pod's combined new+expansion ARR for the period exceeds 110% of the sum of the three individual quotas, each of the three roles earns a flat pod bonus of 5% of their individual attainment payout. No individual credit is transferred between roles under team credit. Why: A shared team pool would re-import the exact split disputes we just removed. Instead each role owns its number, and team credit exists only as a small top-side reward for the pod collectively over-performing — preserving individual line of sight while rewarding pod cooperation. Dispute prevented: The 'I did more than my podmate but we split evenly' resentment that shared pools create between AE, SE, and CSM. Roles: AE · SE · CSM Grounded in: Salesperson Motivation · Payout Formula & Plan Mechanics · Perceived Fairness, Understanding & Trust

Credit timing (booking vs billing vs payment)

Rule: Credit is recognized at BOOKING (signed order) for all three roles, measured on annualized ARR of the contract. Payout of booking-based credit is released 50% at booking and 50% at first customer invoice/go-live (whichever is first), to protect against 9-month-cycle deals that sign but never activate. CSM expansion credit is recognized at booking of the expansion order, not at renewal date. No credit waits for cash collection; collection risk is handled via clawbacks below. Why: 9-month cycles make pay-on-billing punishingly slow and would gut motivation; pay-on-booking keeps line of sight. The 50/50 booking/go-live split hedges the enterprise risk that a signed deal stalls before activation without deferring the entire payout. Dispute prevented: AE-vs-finance disputes over 'I booked it, why am I not paid' and CSM disputes over whether expansion counts at signature or renewal anniversary. Roles: AE · SE · CSM Grounded in: Payout Formula & Plan Mechanics · Business Context & Environment · Administration, Analytics & SPM Technology

Clawbacks

Rule: If a booked deal cancels or fails to activate within 6 months of booking, the go-live half of credit is voided (never paid) and any booking-half already paid is clawed back at 100% from AE and SE. If a customer churns or downgrades within 12 months of go-live, credit is clawed back pro-rata to the lost ARR: from the AE/SE on the original booking for the FIRST 6 months, and from the CSM for months 7–12 (because retention is the CSM's owned window). Clawbacks net against future payouts; no negative paychecks. Why: Booking-based pay requires downside symmetry or reps sell air. Shifting clawback liability from AE/SE to CSM over time mirrors who actually owns the account across the lifecycle, so no role is punished for another's failure. Dispute prevented: AE-vs-CSM finger-pointing over who eats the clawback when a customer churns 9 months after a booking the AE hasn't touched since. Roles: AE · SE · CSM Grounded in: Payout Formula & Plan Mechanics · Perceived Fairness, Understanding & Trust · Financial Results & Compensation Cost Efficiency

Windfall handling

Rule: A deal is flagged a windfall if its ARR exceeds 3x the largest deal in the rep's trailing-12-month history AND inbound/unsolicited origin is logged in CRM. Windfall deals credit at full ARR up to 200% of the AE's individual quota; ARR credit beyond that point is paid at 50% of the normal rate (a soft decelerator, not a hard cap). SE and CSM credit on windfalls is uncapped (their quotas are smaller and windfalls are rarer for them). Windfall flag requires VP-Sales sign-off within 30 days of booking; unflagged deals are credited normally. Why: 9-month enterprise cycles occasionally produce a mega-deal that had little to do with rep effort. A soft decelerator protects comp-cost efficiency without demotivating reps who genuinely worked a large deal, and the inbound+3x test keeps the flag objective. Dispute prevented: AE-vs-management fights over whether a giant deal 'counts fully' — the objective threshold and 30-day sign-off window remove retroactive haircuts. Roles: AE · SE · CSM Grounded in: Payout Formula & Plan Mechanics · Quota & Goal-Setting Quality · Financial Results & Compensation Cost Efficiency

Territory transfers mid-deal

Rule: For any deal where the account changes AE/territory owner mid-cycle, credit follows the last CRM stage each rep advanced: the outgoing AE keeps credit proportional to the furthest sales stage they advanced the deal to (Stage 1-2 reached = 25%, Stage 3 = 50%, Stage 4/verbal = 75%), and the incoming AE earns the remainder to 100%. Transfers must be logged with an effective date; the stage reached AS OF that date governs the split. SE credit does NOT transfer — it stays with whoever owned the logged Technical Validation stage. CSM credit is unaffected by AE territory moves. Why: 9-month cycles guarantee mid-deal reassignments, and 'credit follows selling work at the moment it occurs' means we pay both the rep who built the pipeline and the rep who closed it, using stage timestamps as the neutral arbiter rather than either rep's account. Dispute prevented: The outgoing-AE-vs-incoming-AE 'I built this deal / I closed this deal' war when a territory is rebalanced mid-cycle. Roles: AE · SE · CSM Grounded in: Territory Balance & Crediting Integrity · Administration, Analytics & SPM Technology · Perceived Fairness, Understanding & Trust

Double-crediting budget

Target aggregate credit of 200–240% of deal ARR on a fully-podded new-logo deal (AE ~100% + SE ~100% against their separate quotas + CSM 0% on pure new-logo), and roughly 200% on expansion (AE 60% + CSM 40% + SE 100% when validation is logged). This is deliberately high because each role carries a SEPARATE quota sized to its share — SE quotas are set so 100% SE credit on validated deals equals a full SE number, not a windfall. The budget is correct for this model because the pod's three functions each need independent line of sight, and the AE/SE split war can only be killed by giving each an uncontested full stream rather than carving one pie. The cost if it creeps: if SE-validation logging becomes routine on deals that don't need it, SE aggregate credit inflates comp cost with no incremental selling behavior — so the guardrail is the Technical Validation stage gate, which must be audited quarterly. Every 10 points of unearned aggregate credit creep translates roughly to comp-cost-of-revenue rising by the same proportion on affected deals, which is the number finance should monitor.

Run it on your data

Call it on your own inputs — over the API, or hand it to your AI agent via MCP. Discovery is open; running it is metered.

REST  POST /api/bicycle/sales-crediting
MCP   design_sales_crediting

← All tools