Loading...
Goals

A contest with a business number on it

A 4-week team sales contest plan that declares the business number to move, tracks the live contest, and checks whether the change holds after it ends.

Trusted by frontline teams 15 years of frontline software

Built for: B2b Sales Organizations · Saas Revenue Teams · Field Sales Operations · Wholesale And Distribution

Overview

A contest with a business number on it is an operational improvement plan for turning a team sales contest into a measurable business test. It starts in Contests, where the owner declares the number the contest should move and records the comparison point. When the contest kicks off, the outcome plan opens alongside the live scoreboard so participation and business impact are tracked together.

The pattern is built for a four-week team contest followed by a 30-day measurement window. Use it when you want to know whether a focused push changed a defined outcome such as qualified opportunities, meetings booked, pipeline created, units sold, or expansion revenue. The final review should compare the selected number with the agreed baseline and account for normal reporting delays or sales-cycle timing.

This template is not a substitute for a compensation policy, annual quota process, sales forecast, or general performance dashboard. It is also a poor fit when the target number cannot be measured consistently, when the contest is too short for the outcome to appear, or when several major campaigns change the same metric at once. In those cases, narrow the claim, extend the observation period, or choose a more immediate leading indicator before launch.

How to use this template

  1. 1. Open the contest setup, name one business number it should move, record its baseline and data source, and set the four-week contest dates.
  2. 2. Define eligibility, scoring, tie-breakers, recognition, and the person responsible for checking the declared number before inviting participants.
  3. 3. Launch the contest and use the live scoreboard for participation while keeping the declared business number separate from points or rankings.
  4. 4. At the end of the contest, capture the result from the agreed source and note unusual factors such as territory changes, holidays, backlog, or delayed bookings.
  5. 5. Keep the outcome plan open for the 30-day follow-up window, then compare the post-contest number with the baseline and record whether the change held.
  6. 6. Share the verdict with sales and operations leaders, including the metric definition, evidence, limitations, and whether to repeat, revise, or stop the contest.

Best practices

  • Choose one business number with a precise definition rather than combining activity, pipeline, and revenue into one score.
  • Use the same report, filters, territories, and date logic for the baseline, contest, and follow-up readings.
  • Photograph or export the baseline before kickoff so later changes to CRM stages or dashboards do not rewrite the comparison.
  • Keep scoreboard points and business outcomes distinct because high participation does not prove commercial impact.
  • Record sales-cycle delays and bookings that were created during the contest but closed afterward before issuing the verdict.
  • Review performance by team, region, or segment when mix changes could hide a decline in one group behind growth in another.
  • Schedule the post-contest check before launch so the outcome is not forgotten when the contest closes.
  • If the number does not move, inspect offer quality, eligibility, data completeness, and timing before concluding that the contest itself failed.

What this template typically catches

Issues teams running this template most often surface in practice:

Nobody re-checks the business number after the contest, so the organization can describe activity but not persistence.
The selected number drifts because different teams use changing CRM filters, stage definitions, or reporting periods.
The scoreboard improves while the declared business outcome stays flat because points reward activity rather than quality.
A seasonal spike, territory change, product launch, or holiday period is credited to the contest without a documented comparison.
Results are declared before delayed opportunities, orders, or revenue have entered the source system.
The number rises during the contest and falls back during the follow-up window, revealing a short-lived behavior change.
Missing ownership leaves unanswered questions about who validates the baseline, resolves data gaps, and signs off on the verdict.

Common use cases

Revenue Operations for an Outbound Pipeline Contest
A revenue operations manager ties a four-week outbound contest to qualified opportunities created from a defined CRM report. The 30-day follow-up checks whether opportunity creation remains higher after the scoreboard and prizes end.
Regional Sales Manager Testing a Meeting-Building Push
A regional manager uses first meetings booked as the declared number for several account teams. The plan preserves a shared metric definition while allowing the manager to compare regions and investigate territory mix.
SaaS Account Leadership Measuring an Expansion Contest
An account leadership team connects an upsell contest to expansion pipeline or approved expansion bookings. The follow-up period helps separate temporary contest activity from sustained account coverage.
Wholesale Sales Director Reviewing a Product Focus Contest
A wholesale sales director runs a product-specific contest tied to units sold or qualified customer orders. The outcome review accounts for inventory availability, promotions, and delayed order entry before deciding whether to repeat it.

Frequently asked questions

What does this contest plan measure?

It measures the business number selected when the contest is created, such as qualified opportunities, sales calls, or closed revenue. The plan links the contest activity to that declared outcome rather than treating participation or points as the final result. Customize the metric and its baseline before launch.

How long should the contest and follow-up run?

The pattern is designed for a 4-week contest with a 30-day measurement window after the contest ends. Use the follow-up period to check whether performance remains above the baseline once prizes and scoreboard pressure are gone. Adjust the cadence if your sales cycle is longer.

Who should own and run the plan?

A sales manager, revenue operations lead, or contest owner should define the number, launch the contest, and review the verdict. Team leads can manage participation and data quality, while the owner remains accountable for the post-contest check. Assign one person to resolve missing or inconsistent results.

Does this replace a formal sales incentive or compensation plan?

No. This is an operational measurement plan for testing whether a contest moved a selected business number. Keep compensation rules, eligibility, approvals, tax treatment, and employment requirements in your existing incentive process.

What is the most common mistake when using it?

The common pitfall is declaring a vague goal such as 'sell more' instead of naming one measurable business number and its baseline. Another is stopping measurement when the contest ends, which leaves no evidence of whether the change held. Record the metric definition, source, owner, and review date before kickoff.

Can I customize the plan for different sales teams?

Yes. Change the target metric, baseline period, contest dates, eligible teams, scoring rules, and follow-up window. If teams have different territories or sales cycles, use comparable segments or separate plans so one mix shift does not distort the verdict.

Can the plan connect to existing tools?

Start the workflow in Contests, then use the system that owns the declared business number as the source for results. Common sources include CRM opportunity reports, call activity dashboards, order systems, or finance-approved revenue reports. Document the source and extraction method so the before-and-after comparison is repeatable.

How is this better than announcing a contest in a memo?

A memo communicates the contest but usually does not define how success will be judged or whether performance lasted. This template connects the kickoff to a named business number, a live contest period, and a post-contest verdict. It makes the result review part of the operating plan rather than an optional retrospective.

Ready to use this template?

Get started with MangoApps and use A contest with a business number on it with your team — pricing built for small business.

Get Started