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

Direct Answer

The right cadence for one-on-one deal reviews with AEs is a weekly 25-minute pipeline 1:1 plus a bi-weekly 60-minute deep dive on the top three to five open deals above $50K ARR, anchored to a fixed calendar slot that is never moved. A separate monthly 45-minute career 1:1 keeps coaching about the human distinct from coaching about the pipeline, and a 10-minute Friday async forecast update front-runs the Monday review.

The cadence is not a ritual for ritual's sake: it exists because deals with no buyer engagement for 14 days close at roughly one-quarter the rate of actively-worked deals, and because weekly-cadence teams forecast inside a plus-or-minus 5 percent band while monthly-cadence teams miss plan by 18 percent or more.

Inspect what you expect — but inspect for coaching, not compliance. The cadence breaks below roughly $15K ACV (the deal closes or dies between two reviews, so weekly is too slow) and above eight direct reports per manager (the math stops working, so you tier or split). Install it over 90 days: run the script verbatim for weeks 1 through 4, let AEs lead in weeks 5 through 8, and measure forecast variance in weeks 9 through 12 to decide whether it stuck.

TL;DR

• Weekly 25-min 1:1 on this-quarter deals, pipeline hygiene, and blockers — same slot, never moved.
• Bi-weekly 60-min deep dive on the top 3-5 deals above $50K ARR, with the deal open in the CRM live.
• Monthly 45-min career 1:1 kept separate so deal cadence stays pure.
• Friday 10-min async forecast (commit / best-case / pipeline) so Monday is confirmation, not discovery.
• An AE who cannot state next step plus economic buyer plus close date in under 30 seconds has fake pipeline.
• Cadence breaks below ~$15K ACV (too slow) and above 8 direct reports (too expensive) — tier or split.
• 90-day install: script verbatim (wk 1-4), AE-led (wk 5-8), measure forecast variance (wk 9-12).
• ROI is roughly 100-200x: ~21 hours of manager time per AE per year drives a 5-10 point quota lift on a $1M+ quota.

1. The Core Cadence Architecture

1.1 The five-meeting system

Deal review is not a single meeting. It is a layered system of five distinct touchpoints, each tuned to a different decay rate and a different decision. Collapsing them into one weekly catch-all is the single most common failure mode, because a meeting that tries to cover pipeline hygiene, deep deal strategy, career development, and territory planning at once does all four badly.

The discipline is to separate cadences by what decays fastest.

Decay-rate logic: The interval of each meeting is set by how fast the underlying signal goes stale. 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 the development 1:1 is monthly. Territory composition decays in quarters, so the territory review is quarterly. Match the cadence to the decay and you stop wasting meeting time on signals that have not moved.

The async layer matters as much as the synchronous one: The Friday 10-minute forecast submission is what makes the Monday 1:1 short. If the AE has already committed numbers in writing, the live meeting is spent inspecting the *why* behind the numbers rather than extracting the numbers.

Teams that skip the async layer routinely watch their weekly 1:1 bloat from 25 minutes to 50, because the first half is just data entry that should have happened offline.

Why five and not three: Revenue leaders new to a cadence design instinct toward consolidation — fewer meetings, less calendar load, happier reps. That instinct is wrong, and it is wrong for a specific structural reason. Each of the five meetings has a different *audience for its output*.

The weekly 1:1 produces a next-step SLA for the AE. The bi-weekly deep dive produces a deal-strategy artifact for the deal team. The monthly career 1:1 produces a development plan for the AE and HR.

The quarterly territory review produces an account-scoring map for the planning function. The Friday async produces a forecast roll-up for the CRO and finance. Consolidate two of these into one slot and you force one audience's needs to crowd out another's — and in every observed case, the urgent (this-quarter forecast) crowds out the important (career development, territory strategy).

The five-meeting architecture is not bureaucracy; it is the minimum viable separation of concerns.

The calendar cost, stated honestly: Five meetings sounds heavy. The honest accounting is that for a single AE the total synchronous load is 25 minutes weekly, 60 minutes every other week, 45 minutes monthly, and 90 minutes quarterly — averaging out to roughly 70 minutes of manager-AE synchronous time per week, plus the AE's 10-minute async.

Seventy minutes a week to manage a $1M-plus revenue line is not heavy; it is light. The reason it *feels* heavy is that poorly-run cadences let each meeting overrun, so a nominal 70 minutes becomes a real 140. The scripts in sections 4 and 5 exist precisely to hold the nominal and the real together.

1.2 Why the slot is sacred

The fixed calendar slot is not an administrative nicety. Per RepVue's 2024 AE survey (n=12,400 verified reps), the most common complaint about pipeline reviews is not the meeting itself but its unpredictability — managers who reschedule erode the implicit SLA that says "by Monday at 10 a.m. your deals must be inspectable." Once an AE learns the meeting might slip, the pre-meeting hygiene work slips with it.

A moved 1:1 is a license to carry a stale deal one more week.

1.3 The operating principle

Every line of this cadence resolves to one rule: inspect what you expect, but inspect for coaching — not compliance. A compliance review asks "did you update the CRM." A coaching review asks "why does the economic buyer believe this is worth solving in 2026." The first trains AEs to perform; the second trains them to sell.

The mechanics below — the scripts, the four happy-ear questions, the red flags — are all engineering to keep the review on the coaching side of that line, because the natural gravity of any recurring meeting pulls it toward compliance theater. See (q34) for the broader framework on coaching-versus-compliance management systems, and (q58) for deal-review templates that operationalize the next-step SLA.

2. The Dollar Math — Why This Is Non-Optional

2.1 The fully-loaded cost of an under-inspected AE

The cadence debate is usually framed as a time-management question. It is actually a capital-allocation question. An enterprise AE is one of the most expensive assets a revenue org deploys, and leaving that asset un-inspected is the equivalent of buying a $400K machine and never calibrating it.

The ROI is not close: Twenty-five weekly minutes times 50 weeks is 21 hours of manager time per AE per year. At a $250K manager OTE, that is roughly $2,500 of labor. If that $2,500 of inspection drives even a 5-point quota lift on a $1.05M quota, that is $52,500 of incremental booked revenue against $2,500 of cost — a 21x return on the labor alone, and 100-200x once you account for the gross-margin contribution of that revenue.

There is no other lever in a sales org with that return profile.

2.2 Forecast accuracy is enforced at the board level

Weekly cadence is not a first-line manager preference. It is, at scale, a board-mandated control. Public SaaS proxy filings make this explicit:

• Salesforce (CRM): The 2024 DEF14A discloses that named-executive variable compensation is gated on a current-quarter remaining-performance-obligation (RPO) target, which the company ties to weekly forecast tightness across the global field organization. When the CRO's pay depends on RPO precision, weekly inspection becomes structural.
• HubSpot (HUBS): The 2024 DEF14A discloses CRO compensation in the ~$8M range with explicit sales-productivity KPIs tied to forecast accuracy bands. A board does not write a forecast-accuracy band into an executive comp plan and then permit monthly reviews underneath it.
• ZoomInfo (GTM): The 2024 DEF14A ties CRO equity vesting to forecast accuracy above 90 percent. The company's own MD&A discussion frames that threshold as achievable only through weekly deal inspection.
• Snowflake (SNOW): Investor communications repeatedly emphasize disciplined consumption-forecasting rigor, and its field org runs weekly deal desks on large opportunities — the consumption model punishes forecast error harder than a seat model does.

The pattern: At every public company where a board has put forecast accuracy into executive pay, weekly cadence is the implementation detail that makes the metric hittable. The cadence flows downhill from the proxy statement to the AE's Monday calendar. See (q19) on how forecast-accuracy commitments cascade from the board to the front line.

The compensation-design read: There is a deeper lesson in the proxy filings than "weekly is mandated." It is that forecast accuracy has migrated, over the last decade, from an operational nicety to a *governance metric*. A governance metric is one a board uses to assess whether management is in control of the business.

When a CRO's equity vests on hitting a 90-percent accuracy band, the board is not rewarding good forecasting — it is using the accuracy band as a proxy for "does this executive have a credible operating system." A monthly cadence cannot produce the data density required to defend a 90-percent band; you simply do not get enough inspection cycles per quarter to correct course.

So the cadence is not chosen by the first-line manager and is not really chosen by the CRO either. It is implied by the metric the board wrote into the comp plan, and the metric was chosen because public-market investors punish forecast misses brutally — a SaaS company that misses guidance twice in a row routinely loses 20 to 40 percent of its market capitalization in a single session.

The Monday 1:1 is, in a real sense, a risk control on the stock price.

The private-company corollary: Private companies without a board-mandated accuracy band sometimes conclude this logic does not apply to them. It applies more. A private company's forecast credibility is tested not by quarterly earnings but by its next financing round, where a single quarter of forecast miss can reset the valuation conversation entirely.

The board-to-field chain in the diagram below operates identically; the only difference is that the forcing function is the term sheet rather than the earnings call.

2.3 The ramp-time dividend

Bridge Group's 2024 data puts median enterprise AE ramp at 6.2 months. Under consistent weekly inspection, observed ramp compresses toward 4.1 months — roughly two additional months of full productivity per new hire. On a $1.05M annual quota, two months of full productivity is approximately $175K of incremental attainment per rep.

For a team hiring 10 AEs a year, the ramp dividend alone is $1.75M of pulled-forward bookings, entirely attributable to cadence discipline. See (q72) for the SDR-to-AE promotion ramp playbook that pairs with this.

Why cadence compresses ramp specifically: Ramp time is not a function of how much an AE knows; it is a function of how quickly their mistakes get caught. A new AE will mis-qualify deals, skip multi-threading, and happy-ear close dates — that is normal and expected. The variable is the lag between the mistake and the correction.

Under a monthly cadence, a ramping AE can build an entire quarter of pipeline on a flawed qualification habit before anyone inspects it closely, and then must unwind a full quarter of bad pipeline. Under a weekly cadence the same flawed habit is caught in the first or second 1:1, corrected, and never compounds.

Ramp time, properly understood, is the integral of uncorrected error over time — and cadence is the derivative that bounds it.

The attrition interaction: There is a second-order ramp effect. RepVue's 2024 data shows that AEs in their first year who hit early milestones are dramatically more likely to stay; those who flounder for two quarters frequently leave or are managed out, forcing the org to re-pay the entire ramp cost on a backfill.

A faster ramp therefore does not just pull forward $175K of attainment — it materially reduces the probability of a $390K-to-$475K fully-loaded backfill cost. Cadence discipline is a retention lever disguised as an inspection routine. See (q47) on the firing decision and (q52) on first-year AE development.

3. Why Weekly Is the Non-Negotiable Floor

3.1 Activity decay is measurable

Gong's 2024 revenue-intelligence research shows that deals with no buyer engagement for more than 14 days close at roughly 23 percent the rate of actively-engaged deals. This single statistic is the entire argument for weekly rather than bi-weekly as the *minimum* inspection interval.

A 14-day decay window means a bi-weekly review catches the deal exactly at the cliff edge; a weekly review catches it with a week of runway to intervene. The cadence interval must be shorter than the decay interval, or inspection becomes autopsy.

Lead-in — the next-step SLA: The weekly review forces every open deal to carry a written, dated, owned next step. The mechanism is not the meeting; it is the artifact the meeting produces. A deal without a logged next step is a deal nobody is accountable for, and nobody-accountable deals are where the 14-day decay does its work.

Lead-in — the decay-window arithmetic: The choice between weekly and bi-weekly is not aesthetic; it is arithmetic. If the decay window is 14 days and the inspection interval is 14 days, then in the worst case a deal can go fully cold and you catch it exactly at the moment the decay has completed — too late to act.

If the inspection interval is 7 days, you catch the same deal at the 7-day mark, with a full week of runway to re-engage the buyer before the decay completes. The inspection interval must be strictly shorter than the decay window, and by a comfortable margin. Seven days against a 14-day decay gives a 2x safety factor; 14 days against a 14-day decay gives a 1x safety factor, which in engineering terms means no margin at all.

Lead-in — engagement is a leading indicator, stage is a lagging one: 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. Buyer engagement — emails returned, meetings accepted, stakeholders added — 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; a cadence that inspects only stage catches it after the verdict is in.

3.2 Forecast reality surfaces in week 2, not week 8

Clari's 2024 RevOps benchmark puts forecast accuracy at 92 percent for weekly-cadence teams versus 71 percent for monthly-cadence teams — a 21-point gap. The mechanism is timing. A zombie deal (one the AE has happy-eared into the commit category) is identifiable within two weekly reviews.

Under a monthly cadence the same zombie survives until week 8, by which point the quarter is half over and the gap is unrecoverable.

3.3 Coaching compounds; status updates do not

RepVue's 2024 AE survey (n=12,400) shows reps with weekly manager 1:1s are 2.3x more likely to hit quota than those with monthly 1:1s. Discovery habits, multi-threading instinct, and objection-handling reflexes are built through repetition. One coaching conversation a month cannot rewire a behavior; a coaching conversation a week can.

The compounding is real — the same nudge ("multi-thread before the demo") delivered weekly becomes a habit in a quarter, while delivered monthly it never escapes the AE's notebook.

The repetition mechanism is worth spelling out, because "coaching compounds" is the kind of phrase that sounds true and gets ignored. A 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 the behavior on Monday, the AE applies it across the week's deals, and the next Monday the manager inspects whether it took.

Twelve loops happen in a quarter. A monthly cadence delivers the same three things on a 30-day loop — three loops in a quarter. Behavior change is a function of loop count, not calendar time, and weekly delivers 4x the loops.

This is why the 2.3x attainment gap is not surprising; it is roughly what you would predict from a 4x difference in coaching iterations, discounted for the fact that not every loop produces a clean behavior change.

There is also a selection effect inside the RepVue number that managers should not over-read. Some of the 2.3x is causal — weekly coaching genuinely makes reps better. Some of it is correlational — managers who run a disciplined weekly cadence are also, on average, better managers in other ways, and better managers attract and retain better reps.

The honest read is that the causal share is large but not the whole story, which is exactly why the counter-case in section 8.1 matters: a *badly run* weekly cadence does not deliver the 2.3x, because the loops are empty.

3.4 Discipline transfers from manager to rep

Per the Sandler 2024 Sales Effectiveness Survey, AEs whose managers run a fixed weekly cadence are 41 percent more likely to maintain personal weekly prospecting blocks. The manager's habit becomes the rep's habit. A manager who runs a sloppy, frequently-rescheduled cadence is implicitly teaching the AE that recurring commitments are negotiable — and that lesson shows up in the AE's own prospecting discipline.

Cadence is contagious in both directions.

3.5 The board-to-field accuracy chain

BVP's 2024 State of the Cloud found that best-in-class public SaaS companies — those with next-twelve-months revenue growth above 40 percent — inspect every deal above $50K weekly via a deal desk, not just through the rep's manager. Weekly is not the aspirational ceiling at elite companies; it is the floor, supplemented by a second inspection layer.

See (q88) on manager-to-AE span economics and second-line scaling, and (q23) on forecast-accuracy benchmarks by ACV band.

4. The 25-Minute Weekly Script

4.1 The minute-by-minute structure

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

4.2 Segment one — the number check (0-5 min)

Open with commit, best-case, and pipeline coverage. Target coverage is 3.5x to 4x of quota per SaaStr's 2024 sales-ops benchmark. This segment is deliberately short because the Friday async submission already captured the numbers — the five minutes is spent confirming the numbers are *believable*, not collecting them.

If the AE is fumbling for figures here, the async discipline has broken and that is the first thing to fix. See (q35) on pipeline-coverage ratios that actually predict attainment.

The five-minute number check has a specific job: catch the *direction* of the forecast, not the precision. The manager is listening for three things. First, did the commit number move from last week, and if so why — a commit that moves more than 10 percent week-over-week without a named reason is a sign the AE does not have a stable read on their deals.

Second, is the gap between commit and best-case credible — a best-case that is 3x the commit means the AE is hedging rather than forecasting. Third, is coverage drifting — a coverage ratio sliding from 4x toward 2.5x over three weeks means the funnel is emptying faster than it is filling, and no amount of deal coaching fixes an empty funnel.

None of this requires more than five minutes if the async submission was honest. If it does require more, that is itself the finding.

4.3 Segment two — the top-3 deal walk (5-15 min)

Walk the three deals closing this month. For each, the AE must state, unprompted: the next step, who owns it, the date, the economic buyer, and the single biggest MEDDPICC gap. Ten minutes for three deals is roughly three minutes per deal — enough to inspect, not enough to ramble.

The time pressure is intentional; it forces the AE to lead with the load-bearing facts.

Why only three deals and not the whole pipeline: a weekly 1:1 that walks every open opportunity becomes a recitation, and recitations are where coaching dies. The three closing-this-month deals are the deals where the manager's intervention can still change the quarter. Deals closing next quarter get inspected in the bi-weekly deep dive, not the weekly.

Deals that closed already need no inspection. By constraining the weekly walk to the three deals that are both material and time-sensitive, you concentrate the scarce resource — manager attention — exactly where it has leverage. An AE who wants to walk a fourth deal should be told to bring it to the deep dive; the discipline of the constraint is part of the coaching.

The "unprompted" requirement is the heart of segment two. 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 also wait for the question in front of a customer. The standard is that the AE volunteers the five facts — next step, owner, date, economic buyer, top MEDDPICC gap — as a fluent unit, the way a pilot runs a pre-flight checklist.

When that fluency is present, three minutes per deal is plenty. When it is absent, the missing fluency is the single most important coaching finding of the week.

4.4 Segment three — 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 segment inverts the usual dynamic — instead of the manager interrogating the AE, the AE assigns work to the manager. A weekly 1:1 with zero manager action items is a 1:1 where the AE has stopped asking for help, which is itself a red flag.

The blocker segment is the segment most often cut for time, and cutting it is a mistake with a specific cost. Blockers are, by definition, the parts of a deal the AE cannot move alone — which means they are precisely the parts where manager leverage is highest. A manager's reply to "I need an executive sponsor introduced at Acme" is a single email that can take minutes and unstick a six-figure deal.

Skip the blocker segment and that email never gets sent, and a deal that the manager could have rescued slips for want of seven minutes. The economics here are stark: the blocker segment is the highest-ROI seven minutes in the manager's week, because it is the only segment where the manager does work rather than inspects work.

A subtle failure mode in this segment is the AE who lists blockers that are not actually blockers — "the prospect is busy," "procurement is slow" — as a way of explaining away a stalled deal. The manager's job is to separate genuine blockers (something a specific action can unstick) from excuses (deal weather the AE is narrating).

A genuine blocker generates a manager action item; an excuse generates a coaching nugget. Conflating the two lets the AE outsource the deal's problems to the calendar.

4.5 Segment four — the coaching nugget (22-25 min)

Three minutes, one behavior. Not five behaviors — one. The discipline of picking a single behavior to fix is what makes coaching stick; a list of five improvements is a list the AE will not action.

"This week, multi-thread the Acme deal — get a second contact before Friday" beats a generic review of everything the AE could do better. See (q34) for the coaching-system framework behind the one-nugget rule.

The one-nugget rule survives contact with the real world for a reason rooted in how skill acquisition works. An AE practicing two new behaviors simultaneously practices each of them at roughly half the intensity, and a behavior practiced at half intensity often fails to cross the threshold into automaticity.

By contrast, one behavior practiced across every deal for a full week reliably starts to set. The manager's job in segment four is therefore an act of triage: of all the things this AE could improve, which single behavior, fixed this week, moves the most pipeline. A good coaching nugget is specific (a named behavior), bounded (one week), observable (the manager can verify it next Monday), and tied to a deal in motion.

A vague nugget — "be more consultative" — fails all four tests and should never be the nugget.

A useful manager habit is to keep a running per-AE log of the nugget given each week. Over a quarter that log becomes a development record: twelve nuggets, with notes on which took and which did not. The nuggets that did not take become the agenda for the monthly career 1:1, where there is time to address the root cause rather than the symptom.

This is how the weekly deal cadence and the monthly development cadence connect without contaminating each other.

5. The Bi-Weekly 60-Minute Deep Dive

5.1 Live in the CRM, not on a slide

The deep dive is run with the deal open in the CRM on screen, not from a prepared slide. A slide is a curated narrative; the live CRM record is the truth. The moment an AE is presenting a slide deck about a deal, the manager is reviewing the AE's storytelling rather than the deal's health. Pull up the record live and inspect the actual fields.

This is not a small stylistic preference. A slide is something the AE built; it reflects what the AE wants the manager to see and conceals what the AE would rather not discuss. The live CRM record reflects what the AE actually did — which contacts are logged, when the last activity happened, whether the MEDDPICC fields are filled or empty, whether the close date has quietly slipped twice.

The gap between the slide and the record is the single most diagnostic signal in the deep dive. An AE whose slide says "strong champion engagement" while the record shows no logged activity with that champion in 18 days has a deal that is in worse shape than the AE believes — and the manager only sees that gap by inspecting the record live.

Make "screen-share the CRM, not a deck" a non-negotiable rule of the deep dive.

5.2 The four questions that kill happy ears

Per Force Management's MEDDPICC research, the deals most likely to slip are the ones where the AE has emotionally pre-closed the opportunity. Four questions surface that gap:

1. Economic-buyer pain in dollars: What is the economic buyer's pain, quantified in dollars, if they do not fix this in 2026? A deal without a dollar-quantified pain is a deal the buyer can defer indefinitely.
2. Competitive displacement: Who else evaluated and lost, and specifically why did we win them? An AE who cannot name the loser does not understand the buying committee.
3. The mutual close plan: What is the mutual close plan — show me the shared document. If there is no shared, dated, buyer-acknowledged plan, the close date is a guess.
4. The procurement stress test: If procurement disappears for three weeks, are we still closing this quarter? This isolates whether the deal has real urgency or is riding on a single fragile thread.

5.3 The scoring rule

If an AE cannot answer three of the four questions, the deal is below 40 percent probability regardless of the stage the AE has marked it. This is a hard rule, not a discussion. The four-question score overrides the AE's self-reported probability, because the entire point of inspection is to correct for the AE's optimism bias.

The hardness of the rule is deliberate and serves a purpose beyond the individual deal. If the rule is soft — if a persuasive AE can talk their way past a 2-of-4 score — then the score becomes a negotiation, and a negotiable score is no score at all. The rule must bite automatically: 2-of-4 means the deal moves out of commit, full stop, and the conversation shifts to whether the gap is closeable this quarter.

AEs learn the rule quickly, and the learning is the point — within a quarter, AEs start pre-running the four questions on their own deals before the deep dive, because they know the rule will be applied. At that point the four questions have migrated from the manager's inspection toolkit into the AE's own qualification habit, which is the entire goal of coaching: to make the manager's standard the rep's reflex.

A reasonable objection is that a binary 3-of-4 cutoff is crude — surely some deals scoring 2-of-4 are healthier than others. True, and the manager retains judgment on *what to do* about a low score (rework versus kill, see the table below). But the manager does not retain judgment on *whether the deal stays in commit*.

The crudeness is a feature: a crude rule that is always applied beats a nuanced rule that is sometimes negotiated away.

See (q12) on MEDDPICC versus MEDDIC for enterprise deals, and (q47) on when to fire an AE who consistently cannot forecast.

6. Cadence by Segment — The ACV Bands

6.1 Cadence is not one-size-fits-all

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. The single biggest cadence mistake is importing an enterprise rhythm into a velocity motion or vice versa.

6.2 Velocity and PLG motions

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 already decided. The right rhythm is a daily asynchronous Slack standup plus a weekly forecast review of the *territory* rather than individual deals.

Companies in the product-led and velocity segments — the model historically associated with Datadog (DDOG) and Atlassian (TEAM) — run deal-desk and dashboard-driven inspection rather than rep-by-rep 1:1 deal walks, because at that velocity the unit of management is the funnel, not the opportunity.

See (q66) on building inspection cadences for product-led growth motions.

6.3 Strategic and named-account motions

Above $500K ACV with 6-to-18-month cycles, weekly is still correct but the bi-weekly deep dive is upgraded to a weekly deal desk involving solutions engineering, legal, and an executive sponsor. At this size every deal is material to the quarter, so every deal gets the deep-dive treatment every week.

The cadence does not get less frequent as deals get bigger — it gets more cross-functional. See (q91) on running enterprise deal desks for strategic accounts.

6.4 The span-of-control ceiling

The cadence also breaks above eight direct reports per manager. Weekly 25-minute 1:1s across nine or more AEs consume more than 200 minutes of synchronous time, before the bi-weekly deep dives, before the monthly career 1:1s, before the manager's own pipeline of cross-functional work.

At that span you do not run the cadence harder — you split the team or tier the inspection. See section 8.4 and (q88) for the span economics in detail.

7. The 90-Day Installation Plan

7.1 Weeks 1-4 — run the script verbatim

In the first month the manager runs the 25-minute script and the four-question deep dive *verbatim*. No improvisation. The AEs will find it stiff, and that is acceptable — the goal of month one is to install the muscle memory, and muscle memory requires repetition of an identical pattern.

A manager who personalizes the script in week 2 prevents the pattern from setting.

7.2 Weeks 5-8 — let the AEs lead

In month two the AE drives the meeting. The AE walks the top-3, self-scores the four questions, and proposes the coaching focus. The manager's job shifts from running the script to auditing whether the AE has internalized it. An AE who can run their own deal review honestly is an AE whose forecast you can trust.

7.3 Weeks 9-12 — measure and decide

In month three you measure forecast variance against the prior-quarter same-team baseline and decide whether the cadence stuck. The decision is data-driven, not vibes-driven. If forecast variance is inside 5 percent and quota attainment is trending up, the cadence is installed. If not, you audit a recorded 1:1 to find the execution gap.

7.4 The week-6 diagnostic

If the team is not hitting day-30 numbers by week 6, the cadence design is not the problem — execution discipline is. The diagnostic is to record one 1:1 and check whether the manager actually asked the four happy-ear questions or simply ran a status review. Cadence failures are almost always execution failures wearing a design-failure mask.

See (q58) for the templates that close the execution gap.

8. Counter-Case — Five Genuinely Adversarial Arguments

A gold-standard answer has to argue against itself. Here are the five strongest cases against the weekly-plus-bi-weekly model, each with the honest concession and the mitigation.

8.1 Top-quartile reps can get worse under weekly inspection

This is the strongest critique and the data partially supports it. RepVue's free-text analysis of top-decile AE responses flags that elite reps describe weekly 1:1s as friction — they have already built the deal hypothesis and they want air cover, not interrogation. The concession: for a genuine top-quartile rep, a poorly-run weekly review is a tax on their time.

The counter-counter: even Sandler-trained top reps benefit from a 10-minute async forecast plus a monthly 1:1; the answer is not to skip inspection but to thin it. The mitigation — tier the AEs: top quartile gets a monthly 1:1 plus async, the middle 50 percent gets weekly, and the bottom quartile gets twice-weekly inspection or a 60-day improvement clock.

See (q47) on the firing decision for the bottom tier.

8.2 Inspection theater is the default outcome

Per Force Management's MEDDPICC research, more than 60 percent of pipeline reviews drift into pure status updates within eight weeks of rollout. The concession: the cadence is correct but the execution failure mode is the *expected* outcome, not the exception. The mitigation: if you cannot enforce that every 1:1 ends with a written next-step SLA logged to the CRM, do not run weekly at all — a weekly compliance ritual actively trains AEs to perform, which is worse than no review.

The cadence is only worth running if the artifact discipline holds. See (q34) on preventing compliance drift in management systems.

8.3 PLG and velocity motions need a different rhythm

For ACV below $15K with sub-30-day cycles, weekly individual-deal review is structurally too slow — the deal resolves between two reviews. The concession: the weekly-deep-dive model is genuinely wrong for this segment. The mitigation: run a daily Slack standup plus a weekly territory-level forecast review, and inspect the funnel rather than the opportunity.

This is covered in detail in section 6.2 and (q66).

8.4 Manager span economics break above eight reports

A second-line manager with 40 reports across five first-line managers cannot sustain weekly 25-minute 1:1s — that is 200 minutes a week at the second line alone, before deep dives and career 1:1s. The concession: above eight direct reports per manager the arithmetic simply does not close.

The mitigation: split the org, move to a bi-weekly cadence with peer-led pods on alternate weeks, or accept that the second-line manager only personally inspects deals above $250K and trusts the first-line layer below that threshold. See (q88) for the full span-economics model.

8.5 Weekly creates rep dependency that breaks at manager turnover

There is a real longitudinal effect: when a top-quartile-managed AE moves to a new manager, attainment drops 11 to 14 points in the first quarter per Pavilion data. The concession: a high-touch weekly cadence builds a dependency on a specific manager's judgment, and that dependency is a single point of failure.

The mitigation: write the script down so it is portable, rotate one bi-weekly deep dive to peer-led every other quarter so the AE is not solely manager-dependent, and document each AE's deal-strategy preferences so a new manager inherits context, not just a spreadsheet of numbers.

See (q44) on building manager-turnover resilience into revenue teams.

9. Red Flags — The Diagnostic Checklist

9.1 Deal-level red flags

These are the signals, inside a 1:1, that a specific deal is not what the AE thinks it is.

• Cannot recite next step plus date in under 30 seconds: The deal is fake. SaaStr ops data shows fuzzy-next-step deals slip 78 percent of the time. A real deal lives in the AE's head with its next step attached.
• Same deal carried 3+ quarters with no stage change: This is pipeline pollution. Kill it — a deal that has not moved in nine months is not a deal, it is a hope.
• Top-3 deals have not changed stage in 21+ days: Stalled, not progressing. Twenty-one days of no stage movement on a closing-this-month deal means the close date is fiction.
• Bi-weekly deep dive produces zero new actions for two cycles: The deals are dead and the AE is in denial. A live deal always generates new actions.

9.2 Process-level red flags

These signal that the cadence itself, not a single deal, has broken.

• Forecast variance above 10 percent week-over-week: The AE does not understand their own deals. Variance is the cleanest single proxy for deal comprehension.
• Manager talks more than 50 percent of the 1:1: Inverted coaching — the manager is presenting, the AE is receiving. Fix immediately; the AE should be doing the cognitive work.
• AE pipeline coverage drops below 3x: Stop coaching deals and start a prospecting blitz. There are no deals to inspect if the top of the funnel is empty.
• A 1:1 ends without a next-step SLA logged to the CRM within two hours: Functionally, the meeting did not happen. The artifact is the meeting.

See (q23) for forecast-variance benchmarks and (q35) for the coverage-ratio thresholds.

10. Tooling and Instrumentation

10.1 The instrumentation stack

The cadence runs on calendars and discipline, but it is measured with software. The point of instrumentation is to make the red flags in section 9 visible without the manager having to hunt for them.

10.2 What to instrument versus what to leave human

Lead-in — instrument the decay signals: Activity gaps, stage-age, and forecast variance are mechanical and should be dashboarded. A manager should walk into a 1:1 already knowing which deals have decayed; the meeting is for the *why*, not the discovery.

Lead-in — keep the four questions human: The four happy-ear questions in section 5.2 cannot be automated. Whether the economic buyer has a dollar-quantified pain is a judgment call that requires a human conversation. Do not let a CRM field stand in for the conversation.

Lead-in — use call recording as the audit layer: Gong-style call recording is the mechanism behind the week-6 diagnostic in section 7.4. The recording is not surveillance of the AE — it is surveillance of the manager's coaching quality. See (q15) on building a revenue-intelligence stack and (q27) on CRM hygiene instrumentation.

10.3 The anti-pattern — tooling as a substitute for cadence

The most expensive instrumentation failure is buying a forecast tool and treating the dashboard as a replacement for the 1:1. A dashboard tells you a deal decayed; it does not coach the AE on multi-threading. Tools surface the question; the cadence answers it.

A team with a $200K Clari contract and no weekly 1:1 has bought a very precise way to watch its forecast miss. See (q30) on avoiding tooling-as-strategy failure modes.

11. Named Operators and Real-World Reference Points

11.1 How elite revenue leaders frame cadence

• The deal-desk model: BVP's 2024 State of the Cloud documents that best-in-class public SaaS companies with NTM growth above 40 percent inspect every deal above $50K weekly through a deal desk. The named beneficiaries of this rigor — Snowflake (SNOW), CrowdStrike (CRWD), Datadog (DDOG) — all run multi-layer weekly inspection.
• The forecast-accuracy proxy chain: As covered in section 2.2, Salesforce (CRM), HubSpot (HUBS), and ZoomInfo (GTM) all encode forecast-accuracy targets into executive compensation in their 2024 DEF14A filings, which forces weekly cadence downstream.
• The Pavilion operator community: Pavilion's 2024 GTM Benchmark, drawn from thousands of operator members, found weekly-cadence teams forecast within plus-or-minus 5 percent while monthly-cadence teams miss by 18 percent or more — the cleanest community-sourced datapoint on cadence.

11.2 Reference benchmarks

11.3 The capital-markets angle

Carta's 2024 State of Private Markets shows seed-to-Series-B SaaS companies with structured weekly RevOps reviews raise their next round roughly 14 months faster than peers without. The mechanism is forecast credibility: a founder who can show an investor a tight, weekly-inspected forecast history is de-risking the diligence conversation.

Cadence discipline is not only an attainment lever — it is a fundraising lever. See (q103) on RevOps maturity as a fundraising signal and (q110) on building investor-grade forecast reporting.

The causal chain runs as follows. A weekly cadence is installed and forecast variance compresses below 5 percent. Tight variance produces two simultaneous outputs: a quota-attainment lift of 5 to 10 points, and an investor-grade forecast history.

The attainment lift drives higher reported net revenue retention; the forecast history drives faster diligence on the next round. Together they close the round roughly 14 months faster per Carta's data, which in turn supplies more capital to hire and ramp AEs — and the cycle compounds.

This is the under-appreciated reason cadence discipline belongs on the CEO's dashboard, not just the CRO's: it is one of the few operating habits that simultaneously improves the current quarter and the next financing event.

12. Frequently Missed Nuances

12.1 The career 1:1 must stay separate

The single most common cadence-design error after "no script" is merging the career 1:1 into the weekly deal review. When deal pressure and career conversation share a slot, the deal pressure always wins, and the AE's development conversation gets cut to make room for forecast questions.

Keep the monthly 45-minute career 1:1 on its own slot, on its own agenda, with no deal walk permitted. See (q52) on structuring AE development conversations.

12.2 The async forecast is what protects the 25 minutes

If the weekly 1:1 keeps expanding past 25 minutes, the cause is almost always a broken Friday async submission. The async layer is load-bearing — it moves data collection offline so the synchronous meeting can be pure inspection. Fix the async discipline before you blame the meeting length.

12.3 Cadence is a leading indicator of culture

A revenue org's cadence discipline predicts its overall operating maturity better than almost any other single observable. A team that protects its 1:1 slots, runs scripts, and enforces next-step SLAs is a team that will also protect its other commitments. When diligence teams or new CROs assess a sales org, the first thing they inspect is whether the cadence is real or theatrical.

See (q77) on diagnosing revenue-org health in the first 30 days.

12.4 The cadence outlives the manager

The final nuance, tying back to counter-argument 8.5: a cadence that lives only in one manager's head is a liability. Write it down. The script, the four questions, the red-flag checklist, and each AE's documented deal-strategy preferences should be portable artifacts.

A well-documented cadence survives manager turnover; an undocumented one resets attainment by 11 to 14 points every time a manager changes. See (q44) on turnover-resilient revenue operations.

13. Summary — The Operating Standard

The right cadence for one-on-one deal reviews with AEs is a layered system, not a single meeting. A weekly 25-minute 1:1 inspects this-quarter deals against a fixed script. A bi-weekly 60-minute deep dive stress-tests the top three to five deals above $50K ARR with the four happy-ear questions.

A monthly 45-minute career 1:1 keeps the human conversation separate so deal cadence stays pure. A Friday 10-minute async forecast makes the Monday review confirmation rather than discovery. A quarterly 90-minute territory review handles the strategic layer.

The cadence is non-negotiable because the dollar math is not close — roughly $2,500 of manager labor per AE per year drives a 5-to-10-point quota lift on a $1M-plus quota, a 100-to-200x return — and because forecast accuracy is enforced from the board down through executive compensation at every serious public SaaS company.

It breaks predictably in two places: below roughly $15K ACV, where deals resolve faster than the review interval and you should inspect the territory instead; and above eight direct reports per manager, where the arithmetic stops closing and you must tier or split. The honest counter-cases — top reps getting worse, inspection theater, PLG mismatch, span economics, and manager-turnover dependency — are real, and each has a specific mitigation rather than a reason to abandon the cadence.

Install it over 90 days, measure forecast variance to confirm it stuck, and remember the operating principle that governs every line of it: 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 entire cadence exists to find that out in week 2 instead of week 8.

Related

• (q12) — MEDDPICC vs MEDDIC for enterprise deals
• (q23) — Forecast accuracy benchmarks by ACV band
• (q35) — Pipeline coverage ratios that actually predict attainment
• (q47) — When to fire an AE who cannot forecast
• (q58) — Deal review templates that drive next-step SLA
• (q72) — SDR-to-AE promotion ramp playbook
• (q88) — Manager-to-AE span economics and second-line scaling
• (q34) — Coaching versus compliance management systems
• (q44) — Building manager-turnover resilience into revenue teams
• (q66) — Inspection cadences for product-led growth motions

TAGS: ae-coaching,deal-reviews,forecast-accuracy,cro-ops,sales-rhythm,meddpicc,pipeline-hygiene