A sales sprint is a 2-week push with a single metric, a tiny tactic list, a daily score, and a retro at the end. It is not a quarter plan, not a kickoff, and not a contest with prizes. The job is to close one specific gap in the business, like pipeline coverage, stage-one conversion, speed to lead, or renewal rate, before it compounds. This guide walks the full cycle from naming the gap to deciding whether to repeat, scale, or stop the sprint design, so your team learns which plays work and which do not without burning a quarter to find out.
Time: 2 weeks per sprint
A sprint without one named metric is a to-do list. Pick the one number the sprint is accountable for, write down the current baseline, and write down the target for day 14. Keep it to one metric per sprint, even when the business has three problems, because splitting focus across two numbers almost always means neither moves. Good sprint metrics are leading indicators the team can touch inside two weeks: meetings booked into a target segment, stage-one to stage-two conversion rate, speed-to-lead median in minutes, discovery calls completed per rep, or at-risk renewals saved. Write the metric as a sentence a rep could repeat: move stage-one to stage-two conversion from 22 percent to 32 percent by Friday the 24th.
The single biggest reason sales sprints fail is tactic sprawl. A sprint that tries 10 plays in 2 weeks runs none of them well, and the retro cannot tell which one, if any, moved the number. Hold the tactic list to 1-3, and make every tactic a direct, auditable play tied to the metric. If the metric is stage-one to stage-two conversion, the tactics might be a tightened discovery script, a 48-hour follow-up SLA on every stage-one call, and a daily manager spot check of the next 10 stage-one deals. Each tactic needs an owner, a cadence, and a definition of done. Tactics that cannot be run inside 2 weeks belong in the next sprint or in a project, not in this one.
Every sprint needs a sprint owner who runs the scoreboard and the retro, and every tactic needs a tactic owner who runs the play. Avoid the trap where the sales leader owns everything, because when the sales leader is in a customer meeting the sprint goes quiet for a day and the momentum dies. Pair each tactic with a first-line manager or senior rep who shows up to the daily check-in with a one-line update. The daily check-in is a 10-minute stand-up at the same time every day, not a status meeting. Each tactic owner says the number they moved yesterday, the one thing they will do today, and anything blocking them. If a check-in runs longer than 15 minutes, the sprint has drifted and the owner needs to tighten it the same afternoon.
Two weeks is short enough that every day counts and long enough that a mid-sprint shake-up is possible. Week one is for ramp and friction removal: the first 2-3 days you will find out which tactics the field cannot actually run, where the CRM data is wrong, and which managers are not showing up to the stand-up. Fix those issues in week one, not at the retro. Week two is for push: once the plays are running clean, every daily score should move, and the sprint owner can call a mid-sprint shake-up on Monday of week two if the number is flat. A shake-up is a 48-hour layered play on top of the sprint, like a double-points day on a specific activity or a manager spot-check thread on the exact deals the metric depends on. Do not change the sprint metric mid-flight, only the plays underneath it.
The scoreboard is the most important asset in the entire sprint. It needs to show the sprint metric, every rep's contribution, and the distance from the target, and it needs to update at least daily without a human in the loop. Post the score in the sprint channel at the same time every day with a one-line read: on pace, slightly behind, or at risk. The daily score is not a stick to beat the field with. It is a shared signal that lets reps self-correct inside the sprint instead of finding out on Friday that they drifted on day four. A sprint that goes dark on the scoreboard after day three almost always ends in a retro where nobody can agree on whether the sprint worked, which teaches the field that sprints are theater.
The second half of a sprint runs on social proof. When a rep hits a daily high, moves a deal to the next stage inside the SLA, or runs the new discovery script on a hard call, call it out by name in the sprint channel the same day. Celebration is not about the dollar value of the deal, it is about the behavior you want more of. Keep the callouts short, specific, and tied to the sprint metric, not generic praise. First-line managers should name sprint wins in every one-on-one for the duration, and the sprint owner should post one win per day minimum. If the channel goes quiet for two days, the field reads it as the leaders losing interest and the sprint loses momentum before Friday.
The retro is where the sprint actually earns its keep. Block 30-45 minutes on Friday of week two, the same day the sprint closes, with the sprint owner, tactic owners, and 2-3 reps who ran the plays. Walk four questions. First, did the metric move versus the baseline you captured on day zero, and by how much. Second, which of the 1-3 tactics actually drove the movement, which were neutral, and which cost time with no return. Third, what friction got in the way and what will the next sprint do differently. Fourth, is this gap closed enough to move on, or does it need a second sprint. Write the answers down in a one-page retro and store it next to the next sprint plan. A sprint without a retro is a scrimmage, not a sprint.
Every sprint ends in one of three decisions, and the sprint owner owns the call. Repeat means the design worked but the gap is not closed yet, so you run a second sprint with the same metric and refine the tactics based on the retro. Scale means the design worked and the gap is closed on this team, so you roll the winning plays into the standard sales motion or run the same sprint design on a second team. Stop means the sprint did not move the number or the gap turned out to be smaller than it looked, so you take the lesson, close the sprint, and move the team to a different metric next cycle. Document the decision in the retro doc and announce it in the sprint channel within 24 hours of the retro so the field sees sprints as a loop that actually produces decisions, not an open-ended drill.
A sales sprint is a 2-week focus push on one metric with 1-3 tactics, a daily score, and a retro. A SPIFF or contest is an incentive program layered on top of comp, usually tied to prizes and a leaderboard. Sprints are about tightening the sales motion and learning which plays move the number. Contests are about buying short-term behavior with cash or prizes. You can run a sprint without any prize money at all.
Two weeks is long enough to run a play, see the daily score move, and course-correct once mid-sprint, but short enough that focus does not drift. A month-long sprint collapses into a project by week three and the team stops paying attention to the daily score. A quarter-long push is not a sprint, it is a plan. If the gap you are closing truly needs more than two weeks, run back-to-back sprints with a fresh retro between them.
Pick a leading indicator the team controls directly inside two weeks. Discovery calls completed per rep, stage-one to stage-two conversion rate, speed-to-lead median in minutes, or meetings booked into a specific target segment are all good first picks. Avoid lagging metrics like closed-won revenue or quota attainment for the first sprint, because the sales cycle is often longer than two weeks and the retro will not be able to tell whether the sprint moved the number or the pipeline did.
A single named sprint owner, usually a sales manager or senior RevOps lead, runs the scoreboard, the daily stand-up, and the retro. The sales leader sponsors the sprint and shows up to the kickoff and the retro, but the sales leader should not own the day-to-day because when they are pulled into customer work the sprint goes quiet. Every tactic inside the sprint also gets its own named owner, usually a first-line manager or senior rep.
Run the retro anyway, grade each tactic honestly as moved it, neutral, or cost time, and document the lesson. A sprint that did not move the number is still a sprint that produced a clear decision, which is the point. Common reasons the number does not move: the metric was lagging and 2 weeks was too short to see it, the tactics were not actually run cleanly in week one, or the gap was smaller than it looked. All three are useful findings for the next sprint.
Most teams land on a cadence of 2 weeks on, 1-2 weeks off, so reps are not permanently sprinting on something. Back-to-back sprints without a gap tend to burn the field out and make every sprint feel the same. A good rule is to run a sprint when there is a specific gap worth closing and skip the sprint when the business is executing cleanly. Sprinting out of habit teaches the team to tune them out.
Strkr makes it easy to name the sprint metric, pull a baseline from CRM data, publish a daily score the whole team can see, and track tactic ownership so every sprint ends in a decision instead of a debate.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
