How do you coach reps to increase average deal size?

The Outcome You Should Expect

When this coaching lands correctly, average deal size rises gradually over one to two quarters, not overnight, because it is downstream of behavior change inside deals that are already open. The first visible shift is usually not the dollar figure itself but the leading indicators that predict it: reps start naming a second stakeholder on calls, they start asking discovery questions about adjacent problems instead of just the one the buyer mentioned, and they start writing a dollar or hours-saved estimate into the opportunity notes before they ever discuss price. Deal size follows two to four weeks behind those behaviors, once the rep has had enough live deals to apply the new questions.

Expect the improvement to be uneven across the team. Reps with a genuine skill gap — the ones who simply never learned to ask "who else is affected by this" — improve fastest, often inside a single quarter, because the fix is mechanical: give them the language, have them use it, watch the deal grow. Reps with a comfort or will problem improve more slowly and inconsistently, because the barrier is behavioral, not informational; they know what to ask, they just avoid asking it because a bigger deal means a longer cycle and more exposure to loss. And if a meaningful share of the team shows no movement at all after 90 days of consistent coaching, the honest read is usually that the territory itself caps deal size, and no amount of 1:1 coaching fixes an account list built from small logos. A well-run coaching program should produce a visible split between reps who respond to coaching and reps whose flat number is actually a routing signal — that split is itself useful data for RevOps to act on.

Realistically, a manager coaching six to eight reps should expect average deal size to move in the range of 10-25% over two quarters for reps who had genuine room to expand, with the increase concentrated in accounts that were previously single-threaded. Reps who were already multi-threading and value-selling will show smaller, steadier gains because they have less slack to capture. Do not expect uniform lift across the roster — expect concentrated lift among the reps who had the specific gap this coaching targets.

What Drives That Outcome

Three underlying behaviors drive the increase in average deal size, and each one maps to a specific root cause a manager has to diagnose before coaching, because the fix for a skill gap looks nothing like the fix for a comfort problem or a territory problem. A rep who doesn't know how to multi-thread needs scripts and reps at doing it. A rep who avoids multi-threading because it slows them down needs accountability and a reason to tolerate a longer cycle. A rep whose accounts are simply too small needs a different book of business, not a pep talk.

The diagnostic sequence matters because misrouting the cause wastes a coaching cycle. If a manager coaches "ask for a second stakeholder" to a rep whose entire territory is 20-person companies with one decision-maker, the rep will nod, agree, and see no change, because there often isn't a second stakeholder to find. Conversely, if a manager assumes a territory problem and reassigns accounts when the real issue is that the rep never asks a value-quantifying question, the new territory will produce the same flat number a quarter later.

Once the cause is correctly diagnosed, the mechanism that actually drives the dollar increase is straightforward: every additional stakeholder in a deal tends to surface an additional need, and every additional need that gets quantified in dollars or hours gives the rep a larger, more defensible number to propose. A deal with one stakeholder and one use case has a ceiling set by that one person's budget authority and that one problem's visible cost. A deal with three stakeholders and two use cases has a ceiling set by the combined budget and combined cost of the problems — which is mechanically larger. Coaching that increases stakeholder count and use-case count is, in effect, coaching that raises the deal's ceiling before a single pricing conversation happens.

Benchmarks And Realistic Ranges

Because "average deal size" varies enormously by industry, product, and company size, absolute benchmarks are less useful than relative ones — the ratios and trends that hold roughly true across most B2B sales organizations. Use these as directional anchors, not hard targets, and always compare a rep against their own segment and their own trailing average rather than an external number.

• Single-threaded vs. multi-threaded deals. Opportunities with only one identified contact close at meaningfully lower rates and smaller sizes than deals with three or more engaged stakeholders. A commonly cited pattern across B2B pipelines is that multi-threaded deals average roughly 1.5x to 2x the size of single-threaded deals in the same segment, because more stakeholders means more combined budget and more combined justification.
• Use cases per opportunity. Reps who surface a second use case during discovery, rather than only responding to the one the buyer named, typically expand deal scope by 20-40% when the second use case is quantified and included in the proposal, versus reps who stop at the buyer's original ask.
• Value statements logged in the CRM. Teams that require a written cost-of-problem estimate (hours lost, dollars leaked, risk exposure) on every new opportunity generally see that habit correlate with larger initial proposals, because the rep is anchoring the conversation on the cost of inaction rather than the price of the tool from the first call.
• Coaching cadence and time to visible movement. A weekly, pipeline-based coaching cadence (roughly 15-20 minutes per rep per week, reviewing live open deals) tends to produce visible behavior change — more stakeholders named, more use cases surfaced — within 3-4 weeks, and a measurable shift in average deal size within one to two full sales cycles. Sporadic or monthly coaching produces slower, less durable change because the rep reverts to habit between sessions.
• Territory ceiling. If a rep's accounts sit meaningfully below the segment's median company size, expect coaching alone to move average deal size by only single digits — the real lever is account reassignment, and RevOps should treat a flat number after 90 days of disciplined coaching as a routing signal, not a rep-performance signal.

Treat any of these ranges as a starting hypothesis to validate against the team's own historical data, not a target to force a rep toward regardless of context.

Risks, Edge Cases, And Failure Modes

Coaching for bigger deals carries real failure modes, and a manager who ignores them can make average deal size worse, not better, or damage the team in ways that don't show up until a quarter later.

• Win rate erosion. The most common failure mode is pushing reps toward bigger, more complex deals without also coaching the longer cycle and multi-stakeholder sales process those deals require. If a manager only tracks deal size and not win rate on expanded opportunities, a rep can "succeed" at the coaching by proposing bigger deals that then stall or die in committee, netting the team a worse quarter than if the rep had kept closing smaller, faster deals. Always pair average deal size with win rate on multi-threaded deals as a paired metric.
• Rep burnout and disengagement. Demanding bigger deals from a rep whose territory genuinely cannot support them is a fast way to tank morale and increase attrition. The rep will either quietly fail against an unreachable number or waste effort chasing deals that were never really there. This is the single most common misdiagnosis: treating a territory ceiling as a coachable skill gap.
• Manager rescues instead of coaches. When a manager jumps onto a stalled call and personally multi-threads the deal to save it, the deal might close, but the rep learns nothing repeatable. This produces a short-term bump in one deal's size with zero lift to the rep's average across the next twenty deals. The discipline required here is to let the rep run the expansion play themselves, even if it's clumsy, because the coaching goal is the rep's independent behavior, not this quarter's number.
• Comfort-problem reps who fake the behavior. A rep avoiding bigger deals for comfort reasons can learn to say the right words in a role-play and still quietly avoid applying them live, because the underlying aversion to a longer, riskier cycle hasn't changed. Verify against real call recordings and live pipeline notes, not just role-play performance, before concluding the coaching has worked.
• Comp plan misalignment. If variable compensation pays an identical rate on a small deal and a large one, reps have no structural incentive to slow down for the bigger, more valuable opportunity — coaching fights the comp plan and usually loses. Any RevOps team running this play should check whether the comp structure rewards deal size (e.g., a bonus or multiplier above a size threshold) before investing heavily in coaching that the plan quietly undermines.
• Inflated deals that never close. A subtler risk: reps who over-apply the "add a stakeholder, add a use case" lesson can bloat a deal with scope the buyer didn't actually want, which stalls the deal in internal buyer politics. The expansion has to be pulled from a real, confirmed need, not invented to hit a coaching goal — coach reps to ask, not to assume.

A Practical Rollout Plan

Roll this out as a structured 30/60/90 cadence rather than a single training session, because the underlying behaviors — multi-threading, use-case discovery, value quantification — only become durable habits through repeated, coached repetition on live deals.

Days 1-30 — make the gap visible. Add stakeholders-per-deal and use-cases-per-opportunity to the rep scorecard alongside average deal size, so the leading indicators are tracked, not just the lagging one. Run a weekly 15-20 minute 1:1 using three of the rep's own open deals: for each, ask who else is affected, what the next adjacent problem is, and what the quantified cost of the problem is. Do not answer for them — let the silence when they can't answer do the diagnostic work. Pull two recent call recordings per week and review them specifically for missed expansion moments, not overall call quality.

Days 31-60 — build the reps through repetition. Move from diagnosis to drilling. Each week, run a live role-play where the manager plays a champion who resists introducing the economic buyer, and the rep has to earn that introduction within roughly 60 seconds without alienating the champion. Require the rep to attempt multi-threading on at least one live deal per week and to log a written, quantified value statement in the CRM for every new opportunity they create. Score each open deal 0-3 on a simple bundling checklist — second use case surfaced, second product mentioned, second stakeholder engaged — and coach anything scoring under 2.

Days 61-90 — make it the default, not the exception. Pull back from prescriptive coaching to a self-diagnostic model: the rep opens the pipeline review and identifies, unprompted, where each deal is still narrow. The manager's job shifts to spot-checking and reinforcing rather than teaching from scratch. At this point, look at the trend across the full quarter — average deal size, stakeholders per deal, win rate on multi-threaded deals — rather than any single closed-won number, because a single big deal can mask a team that hasn't actually changed its habits.

Throughout the rollout, RevOps should own the scorecard fields and the reporting cadence so the manager isn't manually reconstructing stakeholder counts from memory — if the CRM doesn't capture stakeholder count and value statements as structured fields, that's a data-model fix to make before the coaching cadence starts, not after.

Related Questions

How do you get a rep to stop selling to just one person?

Coach them to identify the buying committee during discovery, not after a stall. Rehearse a specific line — "who else would need to be aligned for this to move forward" — and require it on every new opportunity before it advances a stage.

What if a rep's deals are small because their territory has small accounts?

That's a segmentation and routing issue, not a skill gap. No amount of coaching raises average deal size when the account list is structurally capped; escalate to RevOps for reassignment or ICP review instead.

Should managers tell reps to simply ask for more money?

No. Anchoring on price instead of the cost of the problem rarely works and can damage trust. Coach reps to quantify the business impact first; the larger number becomes a natural conclusion, not a hard ask.

How do you coach a rep to bundle multiple products in one deal?

Start from the customer's broader pain, not the product catalog. In pipeline review, pick one open deal and brainstorm an adjacent use case together, then rehearse the exact transition sentence before the next call.

What if a rep resists coaching because they're already hitting quota?

Show them their own numbers: if adding one stakeholder or use case to even 20% of their deals would lift ACV without needing more leads, frame the coaching as leverage on effort they've already spent, not as criticism of current performance.

FAQ

Does coaching for bigger deals slow down a rep's overall pipeline velocity? It can, temporarily, because multi-threaded deals with more stakeholders take longer to close than single-threaded ones. Offset this by tracking win rate alongside deal size so the team can confirm the larger deals are still closing at a healthy rate, not just getting bigger and stalling.

How long before a manager sees average deal size actually move? Expect visible behavior change — more stakeholders named, more use cases surfaced in notes — within three to four weeks of consistent weekly coaching, but the dollar-figure movement in average deal size typically lags one to two full sales cycles behind the behavior change.

Is this coaching approach different for a RevOps-led team versus a sales-manager-led team? The coaching conversation itself is run by the frontline manager, but RevOps plays a critical enabling role: building the scorecard fields for stakeholders and use cases, wiring value-statement fields into the CRM, and flagging when a flat number is actually a territory signal rather than a coaching failure.

Can this be coached in a group training session instead of 1:1s? A single group session can introduce the concepts, but the durable skill change comes from repeated 1:1 coaching against each rep's own live pipeline, because the specific stakeholders, use cases, and value math differ deal by deal and can't be generalized in a group format.

What's the single biggest mistake managers make with this coaching? Coaching "ask for more money" as if deal size were a negotiation skill, when it's actually a discovery and scoping skill. Reps who widen the deal on stakeholders, use cases, and quantified value get to a bigger number without ever having to ask for one directly.

How do you know if a rep's flat deal size is a skill problem versus a territory problem? Check whether the rep's accounts contain plausible second stakeholders and adjacent use cases at all. If the territory is genuinely too small to support expansion, coaching will produce no movement regardless of effort — that's the signal to escalate to account reassignment instead of continuing 1:1 coaching.

Sources

• Gong Labs — sales conversation research
• Harvard Business Review — The New Sales Imperative
• Gartner — Selling to the Buying Group
• Salesforce — Land and Expand Strategy resources
• RAIN Group — Value Selling research and blog
• Winning by Design — Account Expansion and Bow-Tie Model
• McKinsey — B2B sales growth research

Related on PULSE

• Top 10 questions to increase a rep's average deal size
• How do you coach reps to compete in a competitive deal?
• How do you coach reps to walk away from a bad deal?
• How do you coach reps to confirm budget without killing the deal?
• Top 10 deal coaching agendas for remote reps
• Top 10 deal coaching agendas for ramping reps