Sales Leaderboard

It tracks a monthly contest based on booked revenue, with each rep ranked by the external number you enter or import. The template is designed for manual scoring because the metric usually lives in your CRM, not in the platform itself. The board shows standings, points by rank, and the current winner. It is meant for a fixed contest window, not an always-on leaderboard.

This template is set up for individual competition, so each entrant is a single rep. That makes it a good fit when you want clear ownership of booked revenue and a simple rank order. If you need a team-based format, you would customize the structure before launch. For mixed-size teams, individual contests are usually easier to explain and audit.

The default duration is 30 days, which matches a monthly sales cadence well. That gives reps enough time to influence outcomes without turning the contest into a permanent leaderboard. You can rerun it each month with a fresh reset and new prize structure. Shorter or longer windows can work, but the contest should always have a clear end date.

A sales manager, revenue ops lead, or enablement owner usually runs it. They are responsible for posting the numbers, importing the CSV, and resolving any disputes before standings are finalized. The organizer should also define what counts as booked revenue so the contest stays consistent. Good governance matters because the board should reflect verified CRM outcomes, not self-reported claims.

You can customize the template, but this version is built for a manual external KPI like booked revenue. If you want to score verified on-platform actions such as calls, tasks, or course completions, a metric-based template is usually a better fit. Using manual scoring for a metric the platform already tracks can create avoidable errors. Keep the scoring mode aligned with the source of truth.

For raw booked revenue, fairness depends on whether the contest is meant to reward absolute output or relative performance. If territories differ a lot, consider customizing the scoring rules, using per-capita logic, or switching to a most-improved format. This template uses highest_score, so it works best when the field is reasonably comparable. If not, the leaderboard can unintentionally favor the biggest accounts.

The biggest mistake is running it as an open-ended leaderboard with no end date, which turns it into a permanent ranking instead of a contest. Another common issue is mixing manual entries with unverified numbers, which weakens trust in the standings. Teams also sometimes reward only the top seller and ignore the rest, which can reduce participation. Clear rules, a fixed duration, and verified inputs prevent most problems.

Yes. This template uses points as the prize type, with suggested points by rank already included, but you can change the reward to fit your program. You can also adjust how many ranks you display, how often you update standings, and what data fields you collect. If you want a different contest style, you can adapt the same structure for first-to-target or threshold-based goals. The key is to keep the rules simple enough for reps to understand at a glance.

A spreadsheet can hold the numbers, but this template turns them into a visible contest with standings, prizes, and a defined end date. That makes it easier for reps to see where they stand and for managers to communicate progress. It also gives you a repeatable format for monthly rollout instead of rebuilding the process each time. Use the spreadsheet as the data source if you want, but let the contest page handle the experience.