Platform · Sales incentives

Every point on the board has a receipt.

Sales gamification and incentives on one ledger. Twenty two actions score, from a logged note worth one point to a closed deal worth a hundred, and a lost deal worth minus ten. Each one writes a single durable row keyed to the event behind it, so a rep can trace a score back to the thing they actually did.

Included at $499 per seat per month

Twenty two actions that score

minus 10 to 100

Deal closed won
100
Referral generated
40
Opportunity created
30
Meeting held
25
Opportunity advanced
20
Meeting booked
15
In-person meeting recorded
15
Positive reply
12
Sequence completed
10
Positive call outcome
8
Email reply received
5
Daily streak bonus
5
Task completed
3
Voicemail left
3
Call made
2
SMS sent
2
LinkedIn message sent
2
Record enriched
2
Email sent
1
Note logged
1
Daily login
1
Deal lost
-10
penalty

Losing a deal is the only action worth negative points, and the catalog flags it as a penalty rather than hiding it. The ledger records the one that got away, not just the one that closed.

How a score is built

Sales gamification with one row per action. Everything else is read from it.

A scored action writes a single row carrying the rep, the action, the points and the moment it actually happened. Lifetime totals, the weekly and monthly boards, the badge wall and the streak all read that one ledger, so the number on a leaderboard and the number on a rep's profile come from the same rows rather than from two counters that drift apart.

The streak bonus doubles every fifth day

consecutive active days

0
25
50
100
200
1 to 4 d5 d10 d15 d20 d

Only completed milestones count, so a seven day streak is worth what a five day streak is worth. Below five consecutive active days the schedule returns zero rather than a prorated fraction, which is the part a rep needs to know on day four.

Ten badges, each with the moment it was earned

A badge here is not a flag recomputed on page load. The ledger stores the timestamp its threshold was first crossed, taken from the event that crossed it, so an award survives a rebuild instead of being reissued with today's date. Streaks are stored the same way, and the longest streak a rep has ever held only ever moves up.

  • First Blood
  • Deal Closer
  • Rainmaker
  • Pipeline Builder
  • Voice of Reason
  • Inbox Hero
  • Meeting Machine
  • Positive Pro
  • Marathoner
  • Social Seller

Why this is different

The engine tells you why a deal did not qualify.

Motivation software asks a team to trust a number, and it is usually a number the person running the program could quietly adjust. This one is built so they cannot. The points ledger only ever appends, its idempotency is a unique index rather than a convention, and the bonus engine names the rule that stopped a deal instead of returning nothing. Incentive software its own operator cannot game is a property of the architecture, not a promise in a settings page.

How a closed deal meets a SPIFF

first failure wins

Is the spiff switched on

no: inactive

Did the deal close inside its window

no: outside_window

Is the product one it covers

no: product_mismatch

Is the customer segment one it covers

no: segment_mismatch

Is the deal above the minimum amount

no: below_min_amount

Qualifies, and pays one of three ways

  • flata fixed bonus
  • percent_of_amounta share of deal value
  • per_unita rate times units

A deal that misses on two counts is told about the earlier one, because the engine returns the first failure and stops. A rep gets the rule, not a shrug, and a manager gets something to answer with.

  • Double counting is rejected, not discouraged

    Every ledger row is keyed to the event that produced it by a unique index on the workspace, the source type and the source id. Replaying the same activity writes nothing at all. That is a constraint in the database, so it holds even when a job runs twice or a backfill overlaps a live write.

  • It explains the no

    Five named reasons, evaluated in a fixed order, and the first failure is the one a rep is told about. The category is good at showing people the bonuses they won and quiet about the deal that missed by one rule, which is the only case where the answer changes behaviour.

  • Rolling windows, not convenient ones

    The weekly board is the trailing seven days and the monthly board the trailing thirty, measured from the moment you look rather than from a calendar boundary. There is no closed period to reopen, and a rep's longest streak only ever moves up, so a partial rebuild can shorten nobody's record.

FAQ

The questions buyers actually ask.

  • MOST ASKED

    No, and it is worth being blunt about that before you spend a demo on it. There are no commission plans, no payout runs, no statements to approve, no clawbacks, no draws and no revenue recognition here. What this is, is the layer that sits above payroll: a durable points ledger, streaks, badges, leaderboards, quota pacing and time boxed SPIFF bonuses. Two more limits worth hearing now rather than in week three. Quota attainment is entered rather than derived from closed revenue. And a SPIFF narrowed to one product or one customer segment is not wired end to end, so today a bonus is scoped by its window, its minimum deal size and whether it is switched on. If paying people is the reason you are shopping, keep the system that does that.

Score a real week

We will not tell you what a rep earned. We will show you what they did.

Bring a week of real activity to a demo and watch it score row by row: the points, the streak, where it lands on each board, and any bonus that did or did not fire with the rule that decided it. If the model does not fit how your team sells, you will know inside the call rather than inside a rollout.

We use these details to contact you about SAGARIS. See our privacy policy.

Book a demo