What does a sales operating cadence look like?
The short answer
A sales operating cadence is the fixed rhythm of meetings that runs the motion: a daily 10–15 minute standup, a weekly 60–90 minute pipeline review with a scorecard of five to fifteen numbers, a monthly forecast and one-to-ones, and a quarterly plan of 90-day priorities. EOS calls the weekly meeting a Level 10; what matters is never skipping it.
The four layers
A cadence is the part of the playbook that keeps the rest of it honest. The ICP, the messaging and the process describe how selling should work; the cadence is how you find out, every week, whether it is. It has four layers, and each exists to catch a different kind of drift.
| Layer | Length | Who | What it is for |
|---|---|---|---|
| Daily standup | 10–15 minutes | Everyone who sells | Today's priorities, blockers, one deal that needs help. No pipeline review |
| Weekly pipeline review | 60–90 minutes | Sales team and whoever leads it | The scorecard, stage-by-stage pipeline movement, and solving the issues that surfaced |
| Monthly forecast and one-to-ones | 60 minutes for forecast, 30–45 per rep | Leader with each rep, then leadership | Commit versus likely versus best case; coaching against what the call recordings show |
| Quarterly plan | Half a day | Leadership, with the sales team for the readout | The three to five 90-day priorities, the ICP and pricing review, and the playbook revision |
The daily standup is the one most often done badly, because it turns into a pipeline review that runs 45 minutes. Keep it to what changes today. The weekly meeting is where the pipeline gets inspected, and it should be the one meeting on the calendar that is never moved. The monthly layer is where coaching happens — the weekly meeting is too public for it. The quarterly layer is where you revise the system itself, which is why the playbook review lives there and not in a weekly meeting where it would never get airtime.
What the weekly meeting looks like
The most widely used template for the weekly meeting comes from EOS, the Entrepreneurial Operating System, which calls it a Level 10 Meeting. It is a fixed 90-minute agenda: Segue (5 minutes), Scorecard (5), Rock Review (5), Customer and Employee Headlines (5), To-Do List (5), IDS — identify, discuss, solve (60), and Conclude (5) (EOS Worldwide). The scorecard it reviews is "five to fifteen weekly numbers that give you an absolute pulse on the business," and the rocks are the 90-day priorities set in the quarterly meeting.
You do not have to run EOS to borrow the structure, and the thing worth borrowing is the proportion. Twenty-five minutes of the ninety are reporting; sixty are solving. Most sales meetings invert that: an hour of each rep narrating every deal, and no time left to fix the two things that are actually blocking the number. A sales version of the agenda looks like this: five minutes of wins, five on the scorecard (are the numbers on or off track, no discussion yet), five on the quarter's priorities, five on customer and market headlines, five reviewing last week's to-dos, then the bulk of the meeting on the issues list — a stalled deal, a stage where conversion has dropped, a sequence that has stopped getting replies — worked one at a time until each has an owner and a next step. Close by confirming who does what by when.
Two rules make it work. The pipeline is reviewed in the CRM, live, not from a slide someone made the night before; if the CRM is wrong, that is the first issue on the list. And the same agenda runs every week, in the same slot, whether or not the founder can attend. A cadence that depends on one person's calendar is a habit, not a system.
Which numbers belong on the scorecard
The scorecard is the cadence's instrument panel, and the discipline is keeping it short. Five to fifteen weekly numbers is the EOS guidance and it is a good limit for a sales team. Each number needs an owner, a weekly goal, and a rule for what counts. For a small B2B team the usual set is: new contacts added that fit the ICP, outbound touches sent, replies, meetings booked, meetings held, opportunities created, proposals sent, closed-won revenue, and one leading deliverability number if you run outbound email — bounce rate or reply rate by channel. Add stage conversion rates once you have enough volume for them to mean something; before that they swing too much week to week to act on.
The number to resist is the one that measures activity without a link to pipeline. "Calls made" is fine if you also track what the calls produced. Reported on its own it rewards dialing.
When a cadence is too much
A two-person company does not need four layers. If the founder and one rep sell together, the honest cadence is a weekly 45-minute pipeline look with a short scorecard, and a quarterly half-day to revise the ICP and the sequences. The daily standup happens anyway because you sit next to each other, and the monthly one-to-one is the same conversation as the weekly one. Add the layers when the team grows past the point where everyone already knows what everyone else is doing — usually the third or fourth seller — and add them because something is drifting, not because a framework says to.
The opposite failure is more common: no cadence at all, a pipeline reviewed when the founder is nervous, and a playbook nobody has opened since it was written. The weekly meeting is the minimum, at any size.
Where SalesARC fits
The operating cadence is a section of SalesARC Playbook, written with a strategist alongside the ICP, the messaging and the process, so the scorecard numbers, the stage definitions and the weekly agenda match the sequences your team is actually running in Prospect. The pipeline you review in the weekly meeting is the one the playbook's sequences feed. If you want someone else to run the cadence, that is SalesARC Perform — our sales leadership running the weekly review, the call scoring and the coaching on your platform, from $2,499/mo — but the cadence itself is yours to run from the playbook at any size. A founder and one rep can follow the weekly agenda above from a shared document. Playbook is for making sure the numbers on the scorecard and the steps in the sequences are the same system.
See SalesARC Playbook or build a plan.