What's the right cadence for one-on-one deal reviews with AEs?

The cadence is a layered system, not one meeting

The most common failure in deal-review design is collapsing every purpose into a single weekly catch-all. A meeting that tries to cover pipeline hygiene, deep deal strategy, career development, and territory planning at once does all four badly, because each of those signals decays at a different rate and needs a different interval. The discipline is to separate cadences by what goes stale fastest.

Pipeline hygiene decays in days, so it is weekly. Deal strategy decays in weeks, so the deep dive is bi-weekly. Career trajectory decays in months, so development coaching is monthly. Territory composition decays in quarters, so account planning is quarterly. Match the interval to the decay rate and you stop spending expensive synchronous time inspecting signals that have not moved since the last look.

A practical five-layer shape looks like this:

The async layer matters as much as the synchronous one. When the AE has already committed numbers in writing on Friday, the Monday meeting is spent inspecting the reasoning behind the numbers rather than extracting them live. Teams that skip the async submission routinely watch a nominal 25-minute 1:1 bloat toward 50 minutes, because the first half becomes data entry that should have happened offline.

Why five layers and not a consolidated two or three? Each meeting has a *different audience for its output*. The weekly produces a next-step commitment for the AE. The deep dive produces a deal-strategy artifact for the deal team. The career 1:1 produces a development plan. The territory review produces an account map for planning. The Friday async produces a forecast roll-up for the CRO and finance. Merge any two and you force one audience's needs to crowd out another's — and in practice the urgent (this-quarter forecast) always crowds out the important (development, territory strategy). The separation is not bureaucracy; it is the minimum viable separation of concerns for roughly 70 minutes of manager time a week against a seven-figure revenue line.

The fixed slot is not an administrative nicety, it is the load-bearing rule. Once an AE learns the meeting might slip, the pre-meeting hygiene work slips with it. A moved 1:1 is an implicit license to carry a stale deal one more week, so the single most protective thing a manager does is refuse to reschedule.

Why weekly is the inspection floor

The case for weekly rather than bi-weekly as the *minimum* interval is arithmetic, not preference. Buyer engagement decays fast: deals that go roughly two weeks with no buyer activity — no returned emails, no accepted meetings, no new stakeholders added — close at a small fraction of the rate of actively-worked deals. If the decay window is about 14 days and your inspection interval is also 14 days, then in the worst case you catch a deal exactly when the decay has already completed — too late to act. A 7-day interval catches the same deal at the halfway mark, with a full week of runway to re-engage before it goes cold. Seven days against a two-week decay is a 2x safety margin; two weeks against two weeks is no margin at all.

The subtler point is *what* to inspect. Most AEs and many managers inspect stage — has the deal moved from demo to proposal. Stage is a lagging indicator; it moves after the buyer has already decided. Engagement is the leading indicator, and it decays before the stage does. A weekly cadence that inspects engagement catches the deal while it is still saveable; one that inspects only stage catches it after the verdict is in.

Weekly also surfaces forecast reality early. A zombie deal — one the AE has emotionally pre-closed into the commit category — becomes identifiable within about two weekly reviews. Under a monthly cadence the same zombie survives until roughly week eight, by which point the quarter is half over and the gap is unrecoverable. That timing difference is why weekly-cadence teams tend to forecast inside a tight single-digit band while monthly-cadence teams miss plan by high-teens percentages: not because the meetings are magic, but because they catch error while it is still small.

Coaching is the third reason weekly wins, and it compounds where status updates do not. Behavior change requires three things — a clear instruction, a chance to apply it, and feedback on the application. A weekly cadence delivers all three on a 7-day loop: the manager names a behavior Monday, the AE applies it across the week's deals, and the next Monday the manager checks whether it took. That is roughly twelve loops a quarter. A monthly cadence delivers three. Behavior change is a function of loop count, not calendar time, so the same nudge — "multi-thread before the demo" — becomes a reflex in a quarter when delivered weekly and never escapes the AE's notebook when delivered monthly.

Discipline also transfers downward. A manager who runs a sloppy, frequently-rescheduled cadence is implicitly teaching the AE that recurring commitments are negotiable, and that lesson reappears in the AE's own prospecting discipline. A manager who protects the slot models the exact behavior they want in the rep's calendar. Cadence is contagious in both directions.

The 25-minute weekly script

The weekly 1:1 fails when it has no script, because an unscripted 25 minutes drifts toward the path of least resistance — a status update. The script is the guardrail, and every minute is allocated to enforce coaching over compliance.

The number check (0–5 min). Open with commit, best-case, and coverage against a target of roughly 3.5–4x quota. This segment is deliberately short because the Friday async already captured the figures — the five minutes confirms they are *believable*, not collects them. The manager listens for three things: did commit move more than ~10% week-over-week without a named reason (unstable read on the deals); is best-case a credible multiple of commit rather than 3x hedging; and is coverage drifting down toward 2.5x over three weeks, which means the funnel is emptying faster than it fills and no amount of deal coaching fixes an empty funnel.

The top-3 deal walk (5–15 min). Walk only the three deals closing this month. For each, the AE states — unprompted — the next step, who owns it, the date, the economic buyer, and the single biggest qualification gap. Three minutes per deal is enough to inspect, not enough to ramble. The "unprompted" requirement is the heart of it: if the manager has to ask "who is the economic buyer," the AE has learned to wait for the question, and a rep who waits for the question in a 1:1 will wait for it in front of a customer. Constraining the walk to three material, time-sensitive deals concentrates the scarce resource — manager attention — where it can still change the quarter. A fourth deal goes to the deep dive.

Blockers (15–22 min). Seven minutes on what the AE needs *from the manager*: legal escalation, an executive sponsor introduction, discount approval, a competitive battlecard. This inverts the usual dynamic — the AE assigns work to the manager. It is the highest-leverage segment because it is the only one where the manager does work rather than inspects it; a single email introducing an executive sponsor can unstick a six-figure deal in minutes. The failure mode is the AE who lists non-blockers — "the prospect is busy," "procurement is slow" — to explain away a stalled deal. A genuine blocker generates a manager action item; an excuse generates a coaching nugget. A weekly 1:1 with zero manager action items usually means the AE has stopped asking for help.

The coaching nugget (22–25 min). Three minutes, one behavior — not five. A list of five improvements is a list the AE will not action; one behavior practiced across every deal for a week reliably starts to set. A good nugget is specific ("multi-thread the Acme deal — get a second contact before Friday"), bounded to one week, observable next Monday, and tied to a deal in motion. Keep a running per-AE log of the weekly nugget: over a quarter it becomes a development record, and the nuggets that did not take become the agenda for the monthly career 1:1, where there is time for the root cause instead of the symptom.

The bi-weekly deep dive and the four questions

The deep dive is run with the deal open live in the CRM, not from a prepared slide. A slide is a curated narrative the AE built; it shows what the AE wants seen and conceals what they would rather not discuss. The live record reflects what the AE actually *did* — which contacts are logged, when the last activity happened, whether the qualification fields are filled or empty, whether the close date has quietly slipped twice. The gap between the confident slide ("strong champion engagement") and the record (no logged activity with that champion in three weeks) is the single most diagnostic signal in the review, and you only see it by inspecting the record live. Make "screen-share the CRM, not a deck" a non-negotiable rule.

The deals most likely to slip are the ones the AE has emotionally pre-closed. Four questions surface that gap:

1. Economic-buyer pain in dollars. What does it cost the economic buyer, quantified, if they do not fix this? A deal without a dollar-quantified pain is one the buyer can defer indefinitely.
2. Competitive displacement. Who else was evaluated, and specifically why did we win? An AE who cannot name the alternative does not understand the buying committee.
3. The mutual close plan. Show me the shared, dated, buyer-acknowledged document. If it does not exist, the close date is a guess.
4. The procurement stress test. If procurement goes dark for three weeks, are we still closing this quarter? This isolates real urgency from a single fragile thread.

The scoring rule is hard on purpose: if the AE cannot answer three of the four, the deal sits below ~40% probability regardless of the stage marked, and it moves out of commit — full stop. A soft rule that a persuasive AE can talk past is no rule at all, because a negotiable score becomes a negotiation. The hardness is the coaching: within a quarter, AEs start pre-running the four questions on their own deals before the deep dive, because they know the rule bites automatically. At that point the manager's inspection standard has migrated into the rep's own qualification reflex, which is the entire goal.

The manager keeps judgment over *what to do* about a low score — rework versus kill — but not over *whether the deal stays in commit*. A crude rule always applied beats a nuanced rule sometimes negotiated away.

Tuning cadence to deal size and team span

The weekly-plus-bi-weekly model is correct for the enterprise mid-band — roughly $50K to $500K ACV with 60-to-150-day cycles. It is wrong, in both directions, for the bands on either side, and importing an enterprise rhythm into a velocity motion (or the reverse) is the single biggest cadence mistake.

Below roughly $15K ACV with sub-30-day cycles, a weekly individual-deal review is too slow: the deal closes or dies between two reviews, so by the time you inspect it the outcome is decided. The right rhythm is a daily asynchronous standup plus a weekly forecast review of the *territory* rather than individual deals — at that velocity the unit of management is the funnel, not the opportunity, and inspection runs through dashboards and a deal desk rather than rep-by-rep walks.

Above $500K ACV with multi-quarter cycles, weekly stays correct but the deep dive upgrades into a weekly deal desk pulling in solutions engineering, legal, and an executive sponsor. Every deal is material to the quarter, so every deal gets deep-dive treatment every week. The cadence does not get less frequent as deals get bigger — it gets more cross-functional.

The other ceiling is span of control. Weekly 25-minute 1:1s across nine or more AEs consume more than 200 minutes of synchronous time before any deep dives, career 1:1s, or the manager's own cross-functional work. Above roughly eight direct reports the arithmetic stops closing, and the answer is not to run the cadence harder but to tier or split: a second-line manager might personally inspect only deals above a set threshold and trust the first-line layer beneath it, or move to peer-led pods on alternate weeks. Trying to force weekly across an oversized span produces rushed, low-quality reviews that deliver none of the coaching compounding that justified weekly in the first place.

Installing it over 90 days, and the honest counter-cases

Cadence failures are almost always execution failures wearing a design-failure mask, so install deliberately over three months. Weeks 1–4: run the 25-minute script and the four questions *verbatim*, no improvisation. The AEs will find it stiff — that is acceptable, because month one is about installing muscle memory, and muscle memory requires an identical repeated pattern. A manager who personalizes the script in week two prevents the pattern from setting. Weeks 5–8: the AE drives — walks the top three, self-scores the four questions, proposes the coaching focus — and the manager's job shifts to auditing whether it was internalized. Weeks 9–12: measure forecast variance against the prior-quarter same-team baseline and decide, on data rather than vibes, whether it stuck. If variance is tightening and attainment is trending up, it is installed; if not, record one 1:1 and check whether the manager actually asked the four questions or simply ran a status review.

A gold-standard answer has to argue against itself, and there are real counter-cases. Top-quartile reps can get worse under weekly inspection — elite reps often experience a poorly-run weekly review as a tax, wanting air cover rather than interrogation. The mitigation is to tier: top quartile gets a monthly 1:1 plus the async forecast, the middle gets weekly, the bottom gets twice-weekly inspection or an improvement clock. Inspection theater is the default outcome — a large share of pipeline reviews drift into pure status updates within a couple of months of rollout. If you cannot enforce that every 1:1 ends with a written next-step logged to the CRM, do not run weekly at all, because a weekly compliance ritual actively trains AEs to perform, which is worse than no review.

PLG and velocity motions need a different rhythm, as covered above — daily standup plus weekly territory review. Span economics break above eight reports, so split the org or tier the threshold. And weekly can create manager dependency that shows up as an attainment drop when a well-managed AE inherits a new manager. The mitigation is to make the system portable: write the script, the four questions, and the red-flag checklist down, document each AE's deal-strategy preferences, and rotate an occasional deep dive to peer-led so the AE is not solely dependent on one manager's judgment. A well-documented cadence survives turnover; an undocumented one resets every time a manager changes. Underneath all of it sits one operating principle: inspect what you expect, but inspect for coaching, not compliance — an AE who cannot state the next step, the economic buyer, and the close date in under 30 seconds has fake pipeline, and the whole cadence exists to find that out in week two instead of week eight.

Related questions

How is a deal-review 1:1 different from a career development 1:1?

A deal review inspects this-quarter pipeline against a fixed script and produces next-step commitments; a career 1:1 covers skills, ramp, comp, and growth. Keep them on separate slots — when they share a slot, deal pressure always crowds out the development conversation, so the human coaching never actually happens.

What forecast categories should the AE submit in the Friday async?

At minimum commit (deals the AE will stake their name on), best-case (upside that could land with everything breaking right), and total pipeline coverage against quota. Submitting these in writing before Monday turns the live 1:1 into inspection of the reasoning rather than collection of the numbers.

How many deals should the weekly 1:1 actually walk?

Only the three deals closing this month — the ones where manager intervention can still change the quarter. Deals closing next quarter belong in the bi-weekly deep dive; closed deals need no inspection. Walking the whole pipeline turns the meeting into a recitation, which is where coaching dies.

What pipeline coverage ratio should trigger a prospecting blitz?

Coverage sliding below roughly 3x quota signals an emptying funnel that deal coaching cannot fix. When it drops there — or drifts steadily from 4x toward 2.5x over several weeks — stop inspecting individual deals and redirect the AE to top-of-funnel activity before the shortfall becomes unrecoverable.

Does this cadence work for a manager with more than eight reports?

Not as written. Above eight direct reports the weekly math exceeds the manager's available synchronous time. Split the team, move to peer-led pods on alternate weeks, or have the second-line manager personally inspect only deals above a set dollar threshold and trust the first-line layer below it.

FAQ

How long should a weekly deal-review 1:1 be? About 25 minutes when the Friday async forecast is working. The async submission moves data collection offline so the live meeting is pure inspection. If the 1:1 keeps expanding toward 50 minutes, the cause is almost always a broken async submission, not the meeting itself — fix the async discipline before blaming the meeting length.

Should deal reviews and career coaching be in the same meeting? No. Keep the monthly ~45-minute career 1:1 on its own slot with no deal walk permitted. When deal pressure and career conversation share a slot, the forecast questions always win and development gets cut. Contaminating the deal cadence with career topics also lengthens the weekly and blurs both agendas.

How do you keep a weekly review from becoming a status update? Enforce an artifact: every 1:1 ends with a written, dated, owned next step logged to the CRM. Run a fixed minute-by-minute script, require the AE to volunteer the load-bearing facts unprompted, and end with one specific coaching behavior. Without the logged next-step, the meeting functionally did not happen.

What cadence works for low-ACV, high-velocity sales? Below roughly $15K ACV with sub-30-day cycles, weekly individual-deal review is too slow because deals resolve between reviews. Switch to a daily asynchronous standup plus a weekly territory-level forecast review, and inspect the funnel rather than the opportunity. The unit of management at that velocity is the pipeline, not the single deal.

When should you review deals more often than weekly? For strategic named accounts above ~$500K, upgrade the bi-weekly deep dive to a weekly cross-functional deal desk with solutions engineering, legal, and an executive sponsor. For a bottom-tier rep on an improvement clock, twice-weekly inspection is reasonable. Otherwise weekly is the floor and going tighter mostly adds friction without new signal.

What are the clearest red flags inside a 1:1 that a deal is fake? The AE cannot recite the next step and date in under 30 seconds; the same deal has been carried three-plus quarters with no stage change; a closing-this-month deal has not moved stage in 21-plus days; or two straight deep dives on it produce zero new actions. Any of these means downgrade or kill, not hope.

Sources

• https://www.gong.io/
• https://www.clari.com/
• https://www.saastr.com/
• https://www.forcemanagement.com/
• https://www.repvue.com/
• https://hbr.org/
• https://blog.hubspot.com/sales
• https://www.salesforce.com/resources/

Related on PULSE

• [What's the right format for a weekly one-on-one with an AE?](/knowledge/q119)
• [What specific questions can I ask during a one-on-one to uncover a sales rep's biggest skill gap?](/knowledge/q14349)
• [What pipeline coverage ratio actually predicts quota attainment?](/knowledge/q35)
• [When should you fire an AE who consistently cannot forecast?](/knowledge/q47)
• [How do you run an enterprise deal desk for strategic accounts?](/knowledge/q91)