Sales Gamification Examples — 4 Complete Programmes

A working gamification programme is four decisions, not a feature list: which bottleneck you are targeting, what each activity is worth in points, how you correct for tenure and territory so the same rep cannot win every month, and what the first competition is. Below are four complete programmes for four common team shapes, with actual point values and the arithmetic behind the prize budgets. They are illustrative designs built from the numbers shown, not customer accounts — the point is that you can copy the structure and substitute your own figures.

The four shapes differ more than people expect. A five-person team should not run a ranked leaderboard at all. A 30-person floor cannot run brackets. A team with a 5x spread in territory size needs a divisor before any board is credible. If you want the same four decisions derived from your own CRM rather than adapted from these, Blueprint runs the seven passes in about four minutes.

Example 1 — 5-rep inbound SMB team

Setup. Five reps, all inbound, HubSpot as the system of record. Roughly 40 marketing-qualified leads a week reach the team, eight per rep. Median time from lead creation to first contact attempt is 3 hours 40 minutes. Demo booking rate on those leads is 21%.

Bottleneck. Not volume — the leads arrive. The gap between lead arrival and first touch is where they go cold. Every downstream number is healthy.

Scoring model.

A strong week for one rep: eight leads all touched inside five minutes (64), four discovery calls held (48), two demos (40), six recaps (24), one closed deal (40) — 216 points.

Fairness setting. No ranked leaderboard. With five people, a rank tells one person they are last every single week, and that person is the same person often enough to become a resignation. Instead, run two boards: personal-best scoring against each rep's own trailing eight-week average, and a single team total on the wall. The absolute numbers still exist in reporting; they just do not drive the board.

First competition. One-week speed-to-lead sprint. Score is the graded band above, applied only to round-robin assigned leads so nobody can cherry-pick.

Prize sizing, shown in full. Assume the sprint moves median first touch from 3h40 to under 30 minutes, and assume that lifts the demo booking rate from 21% to 26%. That is an assumption you should test, not a research finding. Five percentage points on 40 leads is 2 extra demos a week. At a 30% demo-to-win rate and £2,400 gross margin per SMB win, that is 2 × 0.30 × £2,400 = £1,440 of incremental margin for the week. A prize pool of £250 is 17% of that, which leaves comfortable headroom even if the assumed lift is half what you modelled.

Month two. The predictable problem is saturation. Once every rep is reliably touching leads inside five minutes, the 8-point band stops discriminating between anyone and the board goes flat. The month-two adjustment is to drop the under-5-minute band to 3 points, raise demo held to 25, and add a stalled-deal rescue at 6 points. The speed behaviour is now the floor rather than the achievement. Metric saturation of exactly this kind is one of the weekly signals the Blueprint coach pass watches for.

Connecting the data takes minutes through the HubSpot integration; the design decisions above are the part that matters.

Example 2 — 12-rep outbound SDR pod

Setup. Twelve SDRs, Pipedrive, all working the same segment with comparable list quality. Four of the twelve are inside their first 90 days. The pod books about 28 meetings a week. Held rate is 58%. Most meetings run with a single contact.

Bottleneck. Not booking. 28 booked meetings against 16 held is the entire problem — roughly 12 meetings a week evaporate between the calendar invite and the call.

Scoring model.

The booked-to-held ratio is the design. If booked and held scored the same, a rep would be indifferent between a real meeting and a soft one. At 4 versus 14, a no-show costs the rep 10 points and confirming costs them nothing.

Fairness setting. Two adjustments. Split the twelve into three pods of four for the team battle, which turns a twelve-way rank into three four-way contests where everyone is close to the top. Separately, the four SDRs under 90 days score in their own division — a rep in week six is not competing with a rep in year two on absolute output.

First competition. Two-week held-meeting team battle across the three pods. Individual contribution to the pod total is capped at 40%, so one strong SDR cannot carry three passengers and no passenger can hide.

The cap arithmetic: target 42 held meetings per pod over two weeks, 40% of 42 is 16.8, so the cap is 17 held meetings per rep. Above 17 the meetings still score on the individual board; they stop moving the pod number.

Margin arithmetic for the prize. Moving held rate from 58% to a target 75% on 28 booked meetings is 21 held rather than 16.2 — about 4.8 extra held meetings a week. At 70% AE acceptance, that is 3.4 extra accepted opportunities. At a 25% win rate and £6,000 gross margin, the expected value of one week's extra cohort is 3.4 × 0.25 × £6,000 = £5,100. A two-week prize pool of £1,200 sits comfortably inside that even at half the assumed lift.

Month two. Held rate improves first and multi-threading does not, because 14 points for a held meeting is already easy to reach and 20 for a multi-attendee meeting is not enough extra to justify the harder work. The month-two adjustment is a fortnight-long 2x multiplier on second-contact meetings, announced one day ahead so nobody banks activity waiting for it, then removed. Multipliers are for exactly this — a short push on one metric, never a permanent setting.

Pipeline data flows in through the Pipedrive integration.

Example 3 — 30-rep inside-sales floor

Setup. Thirty reps, Salesforce, physical floor with screens. About 340 demos a quarter, roughly 26 a week. Demo-to-proposal conversion is 31%. Proposal-to-win is 44%. Median gap between demo and proposal issued is 6.2 days.

Bottleneck. The 6.2-day gap. Deals that wait a week for paperwork lose the urgency the demo created, and the 31% conversion reflects that rather than any weakness in the demo itself.

Scoring model.

Margin weighting matters here. A £20,000 deal at 60% margin scores 24 points; the same deal discounted to £16,000 at 50% margin scores 16. The rep can see the cost of the discount in the same currency as everything else.

Fairness setting. Thirty reps with a tenure range from six weeks to nine years cannot share one board. Three divisions — 0-6 months, 6-24 months, 24 months and over — each with its own standings, plus one floor-wide team total on the TV leaderboard that everybody contributes to equally. Divisions keep the individual boards competitive; the floor total keeps them a single team.

First competition. Two-week proposal velocity ladder. A ladder rather than a bracket, because a 30-person bracket produces byes, idle weeks and a lot of people watching.

Prize arithmetic. Assume the sprint moves demo-to-proposal conversion from 31% to 38%. Seven percentage points on 26 demos a week is 1.8 extra proposals. At 44% proposal-to-win and £3,800 gross margin, that is 1.8 × 0.44 × £3,800 = £3,010 a week, or £6,020 across the two weeks. A prize pool of £1,800 split 50/30/20 across three places is about 30% of that. Three prize places rather than one is deliberate — winner-takes-all on a 30-person floor switches off 28 people by day four.

Month two. With 30 reps, someone always finds the cheapest scored activity. The predictable failure is two or three reps farming demo-held by running short, unqualified demos. The month-two adjustment is a cap: demo-held points stop accruing after 12 demos a week, set near the 90th percentile of current output so it constrains farming without capping genuine productivity. Review the cap quarterly, because a cap set at launch becomes a ceiling once the floor improves. Salesforce objects map through the Salesforce integration.

Example 4 — 20-rep mid-market team, wide territory spread

Setup. Twenty reps on named accounts. Account counts run from 40 to 190 per rep, with a team median of 95. The same three reps — all holding books above 150 accounts — have topped the board every month since it launched. Board engagement outside the top five has collapsed.

Bottleneck. Not any funnel stage. The bottleneck is the board itself. A raw activity leaderboard on a 5x territory spread measures territory size, and everyone below the top five worked that out immediately and stopped looking.

Scoring model. Raw points first, then normalised.

Fairness setting. Divide each rep's activity points by their account count divided by the team median. Closed-won margin points are not normalised, because revenue is revenue.

The divisors, worked: a rep with 190 accounts divides by 190/95 = 2.00. A rep with 40 divides by 40/95 = 0.42.

Apply it. Rep A holds 190 accounts and holds 6 sourced meetings: 6 × 15 = 90 raw, 90 / 2.00 = 45 normalised. Rep B holds 40 accounts and holds 3 sourced meetings: 3 × 15 = 45 raw, 45 / 0.42 = 107 normalised. Rep B leads by a distance, which is correct — three meetings from a 40-account book is a far higher strike rate than six from 190.

Publish the divisor table on the board. A handicap that reps discover rather than read looks like rigging and destroys the board's credibility in a week. A handicap that is stated in the rules at launch is just arithmetic.

First competition. Four-week dormant territory dig, normalised on the same divisors, scoring only accounts with no activity in 120 days. This format suits the shape well: reps with small books have deep dormancy to work, reps with large books have breadth, and neither structurally wins. Competition formats for other team shapes are set out in sales contest ideas.

Month two. The number to watch is not revenue — it is how many distinct reps appear in the top five across four consecutive weeks. If it is still five or six people out of twenty, the divisor is not doing enough and the normalisation should extend to opportunity value as well as activity count. If it is twelve or more, the design is working and you can leave it alone. The month-two adjustment on a concentration problem is almost always to the fairness setting, not to the point values.

What the four have in common

Every one of them starts from a bottleneck identified in the data, not from a mechanic somebody liked. Every scoring model has a stated reason attached to each weight. Every prize budget comes out of a margin calculation shown on the page rather than a round number. And every one has a planned month-two adjustment before launch, because the failure mode of a gamification programme is not a bad launch — it is a launch nobody revisits.

The cost side is flat regardless of which shape you are: $49/mo up to 10 seats, $99/mo up to 30, $249/mo unlimited, with a 14-day trial and no card required. Full detail on pricing, or start with the scoring model and let the programme follow it.

FAQ

What does a complete sales gamification programme include?

Four components. A named bottleneck taken from funnel data rather than opinion. A weighted scoring model of five to seven activities, each weight carrying a written reason. A fairness setting matched to the team's actual tenure and territory spread. And a first competition with a defined format, tie-break and prize pool sized from incremental margin. Anything missing one of those four is a leaderboard, not a programme.

How do you set point values for a scoring model?

Compare how often each activity appears in the period before a win against the period before a loss, and weight in proportion to the gap. Then check the ratios read as sensible instructions — if a booked meeting and a held meeting score the same, you have told reps that no-shows are acceptable. Keep the model to seven activities or fewer so reps can hold it in their heads without looking it up.

Should a five-person sales team use a leaderboard?

Not a ranked one. With five people, a public rank tells the same person they are last most weeks, which produces resentment rather than effort. Personal-best scoring against each rep's own trailing average works far better at that size, paired with a single team total everyone contributes to. Ranked boards start earning their keep at roughly eight to ten reps, where the middle of the table is genuinely contested.

How do you handle unequal sales territories in a leaderboard?

Normalise activity points by account count relative to the team median. A rep holding twice the median divides by two; a rep holding half divides by 0.5. Leave closed revenue unnormalised, since revenue is revenue. Publish the divisors in the rules at launch — a handicap reps discover on their own reads as rigging, while the same handicap stated up front reads as arithmetic and is accepted without argument.

How much should a sales contest prize cost?

Size it from incremental margin, not from a round number. Estimate the lift the contest produces, convert it to expected gross margin, and set the pool at 15-30% of that. A one-week sprint expected to generate £1,440 of incremental margin supports a £250 pool comfortably. Split across three places rather than winner-takes-all, since a single prize concentrates effort in the top two reps and disengages everyone else by mid-week.

What usually needs changing in month two of a gamification programme?

Three things, in rough order of frequency. Metric saturation, where a scored behaviour becomes universal and stops discriminating — fix by lowering that weight and raising the next constraint. Farming, where one cheap activity gets over-produced — fix with a cap near the 90th percentile of current output. And concentration, where the same few reps keep winning — fix at the fairness setting rather than by changing point values.