30-day sales gamification rollout plan template

Most gamification launches fail in the first fortnight, and the cause is nearly always sequencing rather than software. Rules arrive after scoring starts, the first week is loud and the second is silent, and nobody has decided in advance what happens when participation drops. This template fixes the order. Five days of pre-launch publishing, a launch day where points appear within the hour, a callout inside 24 hours, a scheduled mid-point reset, a conditional dip protocol for week two, then close, payout, results post, a second competition, and a scoring review on day 30. Every beat below states why it sits on that day.

Blueprint produces this calendar for your own team as part of AI onboarding — it reads the pipeline, sets the weights, and writes the rollout including the dip protocol. Use the template below either to run it manually or to sanity-check what you were handed.

The calendar at a glance

Days −5 to −1: publish before you announce

The single most common rollout error is announcing a competition whose scoring model has not been published. Reps then learn the rules by watching their own position move, which reads as arbitrary judgement rather than a stated system.

Day −5. Connect the CRM — HubSpot, Pipedrive or Salesforce — and generate the scoring model. You need at least 60 days of history for baselines to mean anything.

Day −4. Managers review the weights, and each weight must carry a stated reason. If a manager cannot explain why a demo held is worth six times a call logged, the weight is not defensible and neither is the board.

Day −3. Publish. One page, visible to everyone: the metrics, the points, the reason per weight, the guardrail per metric, the contest dates, the tie-break, and the prize. The guardrails matter more than the points — a metric published without its guardrail is an invitation.

Day −2. Brief the team leads separately. Give them the answer to the three questions you will definitely get: what stops someone spamming activity, why is my territory not a disadvantage, and what happens to the points if a deal is refunded. Put the leaderboard live in read-only so the layout is familiar before it means anything.

Day −1. Freeze the baseline. Per-rep baselines computed from a window that closed before the announcement cannot be sandbagged. Baselines calculated after reps know a most-improved prize exists are worthless.

Day 1: launch

Announce in the morning, in the channel the team actually reads, and make sure the first points land inside the hour. The proof that scoring is live is a rep seeing their own number move, not a paragraph promising it will.

We're running [contest name] from [date] to [date].
Scoring: [metric A] = X pts, [metric B] = Y pts, [metric C] = Z pts.
Why those weights: [one line]
Guardrails: [one line per metric]
Prize: [split, and what happens on a tie]
Board: [link] · TV in the [room] from today
Full rules: [link to the page you published on day −3]

Put the board on TV mode the same morning. Ambient visibility does the work that reminder messages cannot.

Day 2: the first callout

Inside 24 hours, name one person publicly for something specific. Not the leader — the leader will be named repeatedly for the rest of the period anyway. Name someone mid-table for a concrete act: the rep who logged eleven meaningful discovery calls, the rep who moved two stalled deals.

This beat sets the precedent that the board notices more than first place. Teams that skip it end up with a contest that only three people are playing. Automated celebrations in Slack or Microsoft Teams cover the routine milestones; the day-two callout should be written by a human.

Days 3 to 7: cadence

One automated celebration per meaningful event, one digest on Friday. Resist the urge to post more. The failure mode in week one is saturation — a channel where every event is announced trains people to mute the channel, and a muted channel is a dead programme.

Day 8: read participation, then decide

Count how many reps have scored at all in the past three days, as a share of the roster. That figure — not total points — tells you whether the programme is alive.

The dip is predictable and it has a cause: by day eight the leader is established, the mid-pack has done the arithmetic and concluded they cannot catch up, and the bottom third has stopped looking. Novelty carried week one; nothing has replaced it.

The week-two dip protocol

Four moves, in this order, and only as far down the list as the reading requires.

1. Change what the board displays. Show gap to the position immediately above, not gap to the leader. A rep four points behind seventh place will act. The same rep 140 points behind first will not.
2. Open a 48-hour side sprint on a single metric. Short, narrow, separate prize, resets to zero for everyone. This is the cheapest way to give the whole roster a live position again.
3. Publish a personal-baseline column. Ranking against your own trailing average gives every rep a number that is theirs to move, independent of territory and tenure.
4. Have managers make three private contacts. Not public callouts. Three reps who have gone quiet, one message each, asking what is in the way. If the answer is "the contest is unwinnable", the reading was right.

Do not extend the contest. Extending it tells the leader their effort was provisional and teaches everyone that deadlines are negotiable.

Day 9: the mid-point reset

Distinct from the dip protocol: this one is scheduled and runs regardless of participation. Post a short mid-point summary — standings, distance between the top three, one statistic nobody expected, and a restatement of the close time. Its purpose is to convert a background board into a foreground event once, halfway through, when attention naturally dips.

Days 15 to 18: run-in and close

No rule changes in the run-in. If you discover a scoring flaw on day 16, note it for the day-30 review and finish the period on the published rules. A contest whose rules moved is a contest whose result nobody accepts.

Close at a named time, freeze the board, and adjudicate ties by the published tie-break. Ties are common on small teams and the tie-break must have been in the day −3 publication.

Days 19 to 20: payout and results post

Pay within 48 hours. The reasoning is straightforward: a prize only reinforces the behaviour it was attached to while the behaviour is still recent. A prize that lands three weeks later is not a prize, it is an anecdote, and reps discount the next one accordingly.

Then publish the arithmetic. Final standings, the winning margin, total volume of the scored activity versus the prior period, and — this is the part most teams omit — what the guardrails caught. Naming the guardrail activity publicly is what stops the second contest being gamed.

Days 22 to 25: the second competition

Brief on day 22, launch on day 25. Change the format deliberately: if the first was an individual points race, run a team battle or a bracket. Repeating a format twice teaches the same three people to win it. The competition formats guide covers the alternatives; competitions supports brackets, team battles, sprints and ladders.

The gap between periods is a design choice. Under three days and the team never gets a break from being measured. Over a week and the habit dissolves.

Day 30: scoring review

One scheduled revision of the model, then hold it. Review four things:

• Baseline drift. Have per-rep baselines moved enough that the fairness calibration needs recomputing?
• Metric saturation. Has any scored activity flattened at a ceiling? A saturated metric no longer discriminates and should lose weight.
• Guardrail hits. Which metrics were padded, and did the guardrail catch it before payout?
• Participation floor. Which reps never scored across the whole period? That is a coaching signal, not a scoring one.

Change at most two weights. Models that change every month are not models. On Sales Gamification these four checks arrive weekly from Coach rather than waiting for a calendar reminder, but the discipline is the same either way: scheduled revision, bounded scope.

What this costs to run

The plan above assumes one manager spending roughly two hours in pre-launch and about twenty minutes a week thereafter. The pre-launch block is where teams under-invest, and it is the only block where the work cannot be automated away — publishing rules is a decision, not a task. Pricing is flat per team rather than per user, so a 30-day rollout costs the same whether you run it with six reps or twenty-six; the pricing page has the tiers, and you can start a 14-day trial with no card required.

For the wider decision sequence that precedes this calendar — picking the bottleneck, setting weights, checking fairness — see the implementation guide.

FAQ

How long should the first competition run?

Two to three weeks. Under two weeks and slower-cycle activity never registers; over three and the outcome is usually settled by the halfway mark, which is what produces the disengagement this plan is designed to prevent. The template above uses an 18-day window: long enough for a full sales cycle of leading activity, short enough that the mid-pack still has a live position at day nine.

What is the week-two engagement dip?

A predictable drop in participation around days eight to fourteen of a gamification rollout. Novelty has worn off, the leader is established, and the mid-pack has concluded they cannot catch up. It is a design problem, not a motivation problem. The fix is to give every rep a live position again — display gap to the next place rather than to the leader, run a short side sprint, and publish a personal-baseline ranking.

Should we publish scoring rules before launch?

Yes, at least two days before. If reps learn the scoring model by watching their own position change, the board reads as a judgement rather than a system, and the first disputed result becomes unanswerable. Publish the metrics, the points, a stated reason for each weight, the guardrail for each metric, the tie-break and the prize on one page that everyone can read before any scoring begins.

When should contest prizes be paid out?

Within 48 hours of the close. The argument is about timing rather than amount: a prize paid three weeks after the period ends arrives detached from the behaviour it was meant to reinforce, so it does not function as a reward. Teams that pay late usually find the next contest gets a flatter response, because reps discount a prize they expect to wait for.

How soon should the second competition start?

Around a week after the first one closes — day 25 in this template. Under three days gives the team no break from being measured, which is how gamification fatigue starts. More than a week and the habit dissolves and you are relaunching from cold. Change the format for the second run so the same reps do not win by repetition rather than performance.

How often should the scoring model change?

Once a month at most, on a scheduled review, and by no more than two weights at a time. A model that changes whenever someone objects to their position is not a model. Review baseline drift, metric saturation, guardrail hits and the participation floor, make bounded changes, publish what changed and why, then hold the model for the next period.