-
1
Set the Monday 30-minute standing hold
The sync lives or dies on cadence. Put it on the calendar Monday morning, 30 minutes, same time every week, and never move it. The point is to catch what shifted over the weekend and heading into the week, before deals slip further and before the heavier midweek forecast call. Monday is non-negotiable because by Tuesday any slip is already two days old. Keep the invite to the Sales Manager, the frontline reps on that team, and one sales operations partner who takes notes. Nobody else. Do not invite finance, do not invite the VP, do not invite marketing. A 30-minute meeting with 12 people is not a sync, it is theater. If the team is larger than 8 reps, split into two syncs rather than extending the clock. The whole exercise collapses the moment you add a 31st minute.
- Lock a recurring Monday 8:30 or 9:00 slot on everyone's calendar
- Cap attendance at the Sales Manager, reps on that team, and one scribe
- Hold the clock to 30 minutes exactly, use a timer if needed
- Reschedule the sync only for public holidays, never for individual conflicts
Tip: If reps are protecting the Monday slot for prospect calls, move the sync to 8am rather than canceling. The sync wins.
-
2
Pull the delta view before the meeting starts
The sync has no deck and no slides. It has one view: the delta between this week's forecast and last week's locked submission, per rep. Pull it before anyone joins. For each rep show commit this week versus commit last week, best case this week versus best case last week, risk-flag count change, and net dollar movement. If Strkr AI has flagged any commit deals as newly at-risk since Friday, surface those on the same view. The entire sync will run against this one screen. If the Sales Manager has to toggle between tabs or recompute math on the fly, the 30 minutes evaporate. Treat the delta view as the single source of truth for the meeting. Any disagreement with the numbers on screen gets resolved after the sync, not during it. Keep the room moving.
Tip: If the delta view does not exist yet, the first week of the sync is just building it. That is still a win.
-
3
Open with a 2-minute team-level roll-up
Start every sync by stating the team-level delta out loud. Last week's commit was X, this week's commit is Y, net change is Z, and the gap to quota moved by this much. Risk flags across the team went up by 3, down by 2, or stayed flat. That is the opener. No preamble, no context setting, no reading the agenda. Reps need to hear the team number first because it anchors every individual walk that follows. A rep who added 50k of commit matters more when the team is 100k short of quota and matters less when the team is already over. Context before detail. Keep this to 2 minutes. If the manager starts explaining why the number moved, cut them off. Explanations come rep by rep in the next step.
-
4
Walk each rep's commits lost
This is the heart of the sync. For every rep, in 2 to 3 minutes, walk the deals that fell out of commit since Friday. For each lost commit the rep answers three questions and only three: what deal, why did it slip, and where is it now (Best Case, Pipeline, Omit, or still Commit but at risk). No storytelling. No excuses. 'The buyer went dark' is a reason. 'They had a busy week' is not. If a rep lost two or more commits in a single week, the manager flags it for a 1 to 1 later, not now. The sync is not the place to coach a slipping deal, it is the place to acknowledge the slip and move on. Record every lost commit live in the CRM so the forecast call later in the week opens with an accurate picture.
- Name the deal, the dollar amount, and the new category
- State the single sentence reason for the slip
- Confirm the rep logged the category change in the CRM before moving on
- Flag any rep with 2+ losses in a single week for a separate coaching conversation
Tip: If the same deal slips 2 weeks running, the manager pulls it from commit entirely until the rep produces new evidence.
-
5
Walk each rep's commits gained
After losses, walk gains. For every rep, in 1 to 2 minutes, name the deals that moved into commit since Friday. For each new commit the rep states the deal, the dollar amount, and the specific evidence that justifies the move. 'Legal is reviewing redlines, signature target is Thursday' is evidence. 'They sounded excited on the call' is not. The Sales Manager has veto power. If the evidence is thin, the deal stays in Best Case and the rep tries again next week. The point is not to shame the rep, the point is to protect the integrity of the commit number so the Wednesday forecast call does not get surprised. New commits that survive the sync are the ones leadership can actually plan around. Everything else is noise dressed up as optimism.
-
6
Walk risk-flag changes and the net
After losses and gains, spend 5 minutes on risk-flag changes. For every commit deal that picked up a new risk flag since Friday (no activity in 14 days, no decision maker named, close date pushed, procurement not yet engaged), the rep states the deal and the plan to resolve the flag this week. For every deal that cleared a risk flag, the rep states what changed. Then the manager states the net: team commit went up or down by this much, net of losses, gains, and risk changes. The net is the only number anyone needs to remember from the sync. Write it in the recap. If the net moved more than 10 percent of the team's quota in a single week, the manager escalates to the VP before the Wednesday forecast call so there are no surprises.
- List each new risk flag and the single action to resolve it this week
- List each cleared risk flag and what changed to clear it
- State the net team-level movement in dollars and as a percentage of quota
- Escalate to the VP if the net exceeds 10 percent of quota in one week
-
7
Capture the recap in writing within 10 minutes
The scribe (usually the sales operations partner) posts a written recap to the team channel within 10 minutes of the sync ending. Three sections, no more. First, the team-level net: commit moved from X to Y, risk flags net up or down. Second, the list of deals that moved in or out of commit with rep, amount, and direction. Third, the action items with owner and due date, almost always 'resolve risk flag on deal X by Wednesday' or 'produce signed redline on deal Y by Friday'. Scannable in 60 seconds. The recap exists so the Wednesday forecast call opens with the sync's net already baked in. It also exists so a rep who missed the sync (travel, illness) can self-serve catch up without pulling the manager into a 1 to 1 replay.
Tip: If the recap takes more than 10 minutes to write, the sync ran too long or the scribe took bad notes. Fix both.
-
8
Hand off cleanly to the Wednesday forecast call
The sync is a feeder meeting. Its only downstream customer is the Wednesday forecast call. Hand off cleanly. By end of Monday, the Sales Manager confirms three things with the forecast owner (VP Sales or GTM leader): the current team commit, the net movement since Friday, and any deal that has moved category twice in two weeks. That third item is the early-warning signal the forecast call cares about most. A deal that pinballs between Commit and Best Case week over week is a deal the rep does not understand. Flag it before the forecast call so it gets the deep review it needs, not the drive-by it will get if nobody flags it. If the sync produced a surprise large enough that the forecast call cannot absorb it, the handoff is a phone call, not a Slack message.
