Built for teams designing and running sales incentive plans
Run incentive plans where the deals live.
Spreadsheet commission math breaks the moment a plan has a kicker, a clawback, or a split credit. Dedicated incentive tools (Spiff, CaptivateIQ, Xactly) solve the math but orbit the CRM, which creates reconciliation drift every month. Strkr builds the plan engine onto the deal record so commissions, SPIFFs, and team bonuses calculate on the same source of truth the forecast runs on.
Three facts about sales incentives drive every design conversation. First, the WorldatWork benchmark pegs total sales compensation at 50 to 70 percent variable for AE roles, which means plan design directly controls roughly 300,000 dollars per rep per year on a 500k OTE. Second, Gartner reporting on sales-comp disputes shows 10 to 15 percent of payouts generate a rep dispute each quarter at mid-market B2B companies. Third, the finance team closes commissions 7 to 14 days after month-end on average, which is one of the biggest friction points in a monthly rhythm. Teams running on Spiff or CaptivateIQ solve the math problem but still own the reconciliation gap because the plan engine lives in a different system from the deal. Strkr folds the plan engine onto the deal so the dispute, the payout, and the forecast all read from the same column.
Reconciliation drift between CRM and comp tool
The comp tool says 42,100 dollars. The CRM says 43,800.
Every month a rep opens the comp statement and compares against their deal list. The two numbers never match exactly because the comp tool imported deals on a schedule, missed late amendments, and did not catch a stage-change reversal from the last week of the quarter. The reconciliation ticket consumes finance ops for three to five days every month. Strkr computes payouts off the deal record itself, so the only source of truth is the one the rep already reads.
Plan versioning that nobody actually tracks
Q1 plan versus Q2 plan versus mid-quarter kicker.
Plans change. A kicker gets added mid-quarter for a new product launch. The clawback clause changes after a bad churn month. The old plan still applies to open deals that closed under the previous rules. Spreadsheet-based plans do not track this cleanly, and the dedicated comp tools charge per plan version. Strkr stores plan versions on a timeline, applies the version in effect at deal close, and shows the rep which plan rev their check reflects.
SPIFF stacking creates double-payment risk
The product SPIFF plus the territory SPIFF plus the Q4 kicker.
Mid-size RevOps teams run three to five concurrent SPIFFs on top of the base plan. Without a formal engine, the AP team pays the stack through manual overrides and someone always double-pays or under-pays. Strkr lets each SPIFF carry a stacking rule (additive, replace, cap-at-N) and the engine resolves at calc time, so the finance team sees "SPIFF-stack-result" on the record with the component breakdown.
Clawbacks that run quietly in the background
Rep gets paid in January. Customer churns in March.
Standard SaaS comp plans include a clawback window of 90 to 180 days against the first-year ARR. The clawback runs rare but non-zero. Tracking it manually on a 50-rep team is a quarterly spreadsheet exercise. Strkr watches the customer-status field on the account linked to the closed deal and triggers a clawback entry on the next statement when churn hits inside the window, with full audit of why.
Split credit that nobody agrees on
Was that 70-30 or 50-50 on the Acme deal?
When an AE pulls in an SE and an ISR to close a complex deal, the split-credit decision usually gets made verbally in the deal-review meeting and lost by month-end. Strkr lets the sales leader set the split on the deal record with a required reason field, routes an acknowledgment task to each named rep, and the comp engine honors the split automatically on close.
Real-time earnings dashboard that reps actually trust
The commission math should not be a monthly surprise.
Reps who do not see running earnings during the quarter end up disengaged from the plan. Those who see a weekly running total manage their own activity against pacing. The incentive tools do ship earnings dashboards; the problem is the data is one or two days stale and loses credibility fast. Strkr computes YTD and quarterly earnings on the deal record in real time, so a rep logging in Tuesday morning sees Monday's updates reflected immediately.
What Strkr sales incentives does
The plan engine on the deal record.
The capability stack below is designed to replace a spreadsheet, a comp tool, or both. The common pattern across customer tenants: finance ops picks it because the reconciliation gap closes; reps keep it because the earnings dashboard is credible; sales leaders keep it because plan changes ship same-day instead of taking an engineering ticket.
Plan builder
Base + accelerator + decelerator + kicker on a visual canvas.
Build a plan with base commission rate, accelerator tiers triggered by quota attainment, decelerator floors for underperformance, and SPIFFs stacked with explicit stacking rules. The canvas shows the resulting payout curve against sample deal sizes so a sales leader sees the plan behavior before shipping it to reps.
Deal-record payout preview
Open a deal and see the exact commission.
Every deal record shows the commission calculation inline: base rate applied, accelerator tier if quota is cleared, SPIFF stack, split credit percentage, and the final payout number. The rep sees the number before close, the AE manager sees it during pipeline review, and the finance team sees it on the audit log.
Quota tracker
Running attainment against the plan quota.
The quota tracker lives on the rep home surface. It shows quarterly quota, YTD attainment, pacing against the quarter end, and the implied accelerator tier if current pacing holds. The visual uses the same deal data the forecast runs on, which means a deal moved to "Closed Won" updates the quota tracker in under a second.
SPIFF campaign manager
Spin up a two-week product SPIFF in under five minutes.
A sales leader creates a SPIFF with a target product, a bonus amount or percentage, a date window, and a stacking rule. The SPIFF applies to every eligible deal that closes in the window and shows on the rep earnings dashboard with a dedicated line. The two-week kicker that used to take a comp-tool change request now ships before the leader finishes the Monday meeting.
Clawback engine
Automatic clawback entry on churn inside the window.
When a customer account changes status to churned inside the clawback window (configurable 60 to 365 days), Strkr files a clawback entry on the responsible rep's next statement with the reason, the original payout, and the clawback percentage from the plan. The rep sees the entry in the audit log; the finance team never has to remember to run the quarterly clawback sweep manually.
Split-credit workflow
Multi-rep deal splits with acknowledgment routing.
Set the split on the deal: AE at 60 percent, SE at 20, ISR at 20. Each named rep gets an acknowledgment task. The deal cannot move to "Closed Won" until all three ack the split, which forces the credit decision early rather than at month-end reconciliation. The split is honored by the comp engine automatically on close.
Payout statement generation
PDF or CSV statement with full line-item traceability.
Finance ops generates monthly or quarterly statements from the comp dashboard. Each statement includes the deal list, the plan version applied, the SPIFF stack if any, the split applied, and the final payout. The PDF is DocuSign-ready for the rep acknowledgment signature; the CSV feeds the payroll system directly.
Dispute workflow
Open a dispute from the statement, resolve in one thread.
A rep opens the statement and clicks "Dispute" on a specific line. The dispute creates a Strkr task routed to sales leadership and finance ops with the deal context attached. Resolution happens in-thread with an audit of what changed and why. The 10 to 15 percent dispute rate becomes a visible, measurable workflow instead of a Slack-channel scramble.
Plan modeling
Simulate a new plan against last year's deal data.
Before shipping a plan change, run it against the historical deal set and compare the resulting payouts against the current plan. The modeler shows the aggregate change, the per-rep change, and the tail-impact on the top and bottom quartile. The exercise that used to take a RevOps analyst three days in Excel runs in under 10 minutes with higher fidelity.
What this replaces
The stack decision versus Spiff, CaptivateIQ, or spreadsheets.
The incentive-tool category sold on the "spreadsheet is a nightmare" argument during 2018 to 2022 and converted most mid-market B2B teams. The next-stage argument is "the dedicated tool is a reconciliation nightmare." Here is where Strkr's approach lands on each of the common alternatives teams are evaluating in 2026.
Versus spreadsheet-based comp
The math is formulaic and the audit trail is real.
Spreadsheet comp works at 5 reps and breaks at 25. The formulas get copy-pasted wrong, the SPIFF columns accumulate as hidden sheets, and the finance ops hire ends up spending 40 percent of their time on monthly reconciliation. Strkr replaces the spreadsheet with a plan engine, keeps the data on the deal, and gives finance ops back the two weeks a month they used to lose.
Versus Spiff (Salesforce) or CaptivateIQ
No parallel system to reconcile against the CRM.
Spiff and CaptivateIQ are solid plan engines; the structural issue is they pull data from the CRM on a schedule, which creates a drift window where the two systems disagree. The monthly reconciliation ticket is the price of a dedicated tool. Strkr collapses the two systems by putting the plan engine on the deal record itself, which eliminates the reconciliation step entirely.
Versus Xactly or Varicent
Enterprise plan complexity without an eight-week implementation.
Xactly and Varicent handle enterprise plan complexity (multi-level credit, matrix compensation, country-specific rules) at the cost of a six to twelve week implementation and a six-figure annual contract. Strkr covers roughly 85 percent of the complexity Xactly covers at a fraction of the setup time, which is the right trade for mid-market teams up to roughly 300 reps.
Versus home-grown Looker dashboards
A plan engine is not a dashboard.
Some teams build the comp view in Looker or Metabase on top of raw CRM data. The dashboard shows the math but cannot execute the SPIFF, trigger the clawback, or run the dispute workflow. Strkr adds the execution layer on top of the data layer, which is what finance ops actually needs to close the month.
Versus consultancy-built custom
No annual re-implementation when the plan changes.
Mid-market RevOps teams sometimes hire a consultancy to build a bespoke comp solution. The build works for the plan it was built for and breaks when the plan changes. Strkr's visual plan builder lets a RevOps lead update the plan during a Monday meeting and ship the change by Monday afternoon, with full audit of what changed.
Versus the finance team manual
The commission team scales with the sales team.
Comp admin workloads scale linearly with rep count on manual systems: one admin per 25 to 40 reps is the industry benchmark. Strkr's automation moves that ratio to one admin per 100 to 150 reps because the engine handles the repetitive work and the admin only touches disputes and edge cases.
How the plan touches the sales motion
Where the design decisions actually show up in rep behavior.
Incentive plans are either shaping rep behavior or they are a tax on finance ops. The pattern that distinguishes high-functioning programs: reps know their running number, understand the accelerator math, and can see the effect of a late-quarter deal on their check before it closes. Here is how Strkr makes that pattern the default.
Earnings transparency
Rep sees running YTD payout on the home screen.
The rep home surface shows YTD earnings as the first number. Clicking in opens the deal-by-deal breakdown with plan version, SPIFF applied, and split applied per deal. Rep behavior changes when they see the number weekly instead of monthly: the deal they are tempted to push to next quarter becomes an obvious choice to close now.
Accelerator pacing
The pacing bar shows the threshold distance.
A rep at 92 percent quota attainment sees a pacing bar showing the gap to the 100 percent accelerator trigger. The commission on the next deal is calculated two ways: pre-accelerator and post-accelerator, so the rep sees the real stakes of landing one more deal before quarter end. Behavior shifts predictably: closes concentrate in the last two weeks.
SPIFF visibility
Active SPIFFs show in the sidebar with running progress.
When a sales leader fires a SPIFF, every eligible rep sees it on the sidebar with the target, the window, and their current progress. SPIFFs that disappear into email get ignored; SPIFFs that live on the surface get worked. The common pattern on live tenants: SPIFF attainment runs 30 to 50 percent higher when the SPIFF is visible on the home surface versus pushed via email alone.
Deal-level what-if
What is this deal worth to me after my split?
Open a deal with a 60-40 split and the record shows the AE take-home at the current plan version. The rep can run a what-if on the deal size to understand the marginal commission from pushing the deal from 85k to 100k. The what-if is not a selling point; it is a tool reps use multiple times a week.
Team bonus visibility
Team-level bonuses roll up on the manager view.
When a plan includes a team-level bonus (overall team quota attainment, team pipeline coverage), the manager view shows the team pacing against the bonus threshold. The weekly team meeting opens with the number instead of a vague "we need more pipeline," which translates to specific actions on named accounts.
Clawback transparency
Rep sees pending clawbacks on the earnings dashboard.
Pending clawbacks (customers inside the window at risk) show as a separate pane on the earnings dashboard. The rep sees that a specific account is at risk of churn and the implied clawback dollar amount, which creates an incentive to engage the account on retention before the churn triggers. The alternative (surprise clawback in the next month's check) damages trust in the plan.
Head-to-head
Strkr vs Spiff for the sales-incentives workflow.
Spiff was acquired by Salesforce in 2024 and is now the native commission layer inside Sales Cloud. It is the strongest incumbent in the mid-market segment Strkr targets. Here is the head-to-head on the dimensions that drive the buying decision.
Feature
Strkr
Spiff (Salesforce)
Where the plan engine lives
On the deal record inside the CRM
Separate Salesforce app with Sales Cloud sync
Pricing model
Flat per seat, included on paid tiers
Per-rep add-on to Sales Cloud license
Plan versioning
Timeline-based with per-deal version resolution
Yes, with plan effective dating
SPIFF stacking rules
Explicit per-SPIFF stacking (add/replace/cap)
Via plan logic, team configures per SPIFF
Clawback engine
Automatic on churn-status change inside window
Via Salesforce flow + custom field
Deal-record payout preview
Inline on the Strkr deal record
In Spiff UI, linked from deal
Dispute workflow
Native workflow with audit log
Yes, built into Spiff statement UI
Plan modeling against history
Simulate against prior-year deal set
Yes, with Spiff Studio modeling
Implementation time
Days (plan builder is visual)
Weeks on standard mid-market plans
Payroll export
CSV export + API endpoint
Native payroll integrations library
How teams use Strkr
How teams run incentive plans on Strkr today.
The patterns below come from customer tenants running incentive programs on Strkr as the primary engine. Common thread: the plan became the plan the finance team and the sales team both read, not two separate stories.
Series B SaaS, 30-rep team
Spreadsheet retired, Strkr adopted mid-year.
A 30-rep team was running comp in a Google Sheet with four SPIFFs, two accelerator tiers, and a 120-day clawback. Finance ops closed each month 7 to 10 days after month-end. They moved comp onto Strkr during the Q2 plan refresh. First-month close dropped to day 3; dispute volume dropped from 11 cases to 4 because the deal-record payout matched the statement exactly. The RevOps analyst got back roughly 15 hours a month that had been going to reconciliation.
Multi-product SaaS, SPIFF-heavy motion
Nine concurrent SPIFFs with explicit stacking rules.
A multi-product SaaS runs nine concurrent SPIFFs most quarters: new-logo bonus, specific-product kickers, multi-year-term bonus, enterprise-tier bonus, upsell SPIFF. Each one has its own stacking rule in the engine. The sales leaders fire new SPIFFs weekly, and the comp engine handles the stack math automatically. Rep adoption of the active SPIFFs runs 60 percent higher than the previous CaptivateIQ setup because the SPIFF is visible on the deal preview, not on a separate statement.
Agency comp with retention clawback
Account book owner clawbacks run quarterly.
A sales agency compensates reps on year-one book revenue with a 180-day retention clawback. The engine watches the client-status field on every account book and runs clawbacks automatically on churned clients inside the window. The quarterly manual sweep that used to take two days of spreadsheet work now runs in the background with the audit log attached to each clawback entry.
Enterprise, split-credit workflow
AE plus SE plus ISR on every deal with ack required.
A 65-rep enterprise team runs mandatory split-credit on every deal over 100k ARR. The deal cannot move to Closed Won until the AE, the SE, and the ISR (named on the record) acknowledge the split. The acknowledgment task hits the rep home surface and takes under 30 seconds. The disputed-credit conversation that used to happen monthly at month-end now happens at deal-close and gets resolved cleanly.
Mid-market, plan-change velocity
Quarterly plan revision shipped in a single afternoon.
A mid-market RevOps team ships a plan revision every quarter: new accelerator curve, new SPIFF suite, revised split rules. On the previous Xactly setup, each revision was a four to six week change-request cycle. On Strkr, the RevOps lead opens the plan builder, applies the changes, runs the model against prior-year data, and ships the new plan in an afternoon. The pace of plan iteration directly correlates with rep engagement because the plan actually responds to market changes.
Put the plan engine on the deal record where it belongs.
Start a 14-day Strkr trial with the plan builder enabled. Rebuild your current comp plan in the visual canvas, run it against your last quarter's deals, and see the payouts resolve on the exact records your forecast reads from.
Does Strkr replace a dedicated incentive tool like Spiff or CaptivateIQ entirely?
For most B2B teams up to roughly 300 reps running standard commission plans with accelerators, SPIFFs, splits, and clawbacks, yes. Strkr covers roughly 85 to 90 percent of the plan complexity that Spiff or CaptivateIQ ships, with the significant advantage that the engine lives on the deal record itself so there is no reconciliation step. Teams running enterprise-scale complexity (multi-currency, country-specific comp law, matrix compensation across business units, 500-plus reps) may still need Xactly or Varicent. The honest advice is to list the plan features you actually use and run them against the Strkr plan builder in a 90-minute scoping session.
How does the SPIFF stacking engine actually resolve conflicts?
Each SPIFF carries an explicit stacking rule set at creation: "additive" (SPIFF adds on top of base commission), "replace" (SPIFF replaces base commission for the eligible deal), "cap-at-N" (combined SPIFF payout caps at N percent of base), or "priority" (if two SPIFFs are eligible, the higher priority applies). When a deal closes, the engine evaluates every eligible SPIFF, applies the stacking rules in a documented order, and shows the resolved payout on the deal record with the component breakdown. The finance team can audit the stack logic per deal, which is the governance surface spreadsheet-based plans never shipped cleanly.
What happens to historical commission data when the plan changes mid-year?
Strkr stores plan versions on a timeline with explicit effective dates. When a deal closes, the engine resolves which plan version was in effect at the close date and applies that version. If a plan rev shipped on March 1 and a deal closed on February 28, the deal pays under the old plan. If the deal closed on March 2, it pays under the new plan. The deal record shows which plan version was applied, which eliminates the "wait, which plan was I on?" conversation entirely. Historical statements remain anchored to their original plan version even after new revs ship.
Can we run team-based bonuses in addition to individual plans?
Yes. The plan builder supports team-level bonus tiers that trigger on aggregate team quota attainment, team pipeline coverage, or team retention metrics. The team bonus pays out proportionally to the configured split (equal, by individual contribution, by seniority weighting) and shows on each rep's earnings dashboard as a dedicated line. Common patterns: a sales-leader team bonus tied to overall team attainment, a cross-sell bonus tied to multi-product penetration, a team churn-prevention bonus tied to net dollar retention.
How does the clawback window work when a customer churns?
Each plan defines a clawback window (common defaults are 90, 120, or 180 days from deal close) and a clawback percentage (common defaults are 100 percent for churn inside 90 days, 50 percent for 91 to 180 days). When a customer account status changes to "churned" or "cancelled" inside the window, Strkr automatically files a clawback entry on the responsible rep's next payout statement. The entry shows the deal, the original payout, the clawback percentage, and the reason. The rep sees pending clawback risk on the earnings dashboard (customers inside the window at churn risk) before the clawback actually triggers.
Does the payout export integrate with ADP, Rippling, Gusto, or other payroll systems?
Strkr exports payout statements as CSV with a configurable column set that matches the common payroll import formats (ADP Workforce Now, Rippling, Gusto, Paylocity, Paycom). The finance team runs the export on the monthly or quarterly close cadence and uploads to the payroll system. For teams that want automated flow, the REST API ships a /payouts endpoint that payroll systems with API connectors can poll. A native Rippling connector is on the roadmap for mid-2026; the CSV export covers every current customer need in the meantime without creating a brittle sync dependency.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
