How do you coach a rep to expand a deal's scope and value?

The deal that stalled at one team and one use case

A mid-market rep on a RevOps team brings a $24K opportunity to the Thursday deal review. The customer is a marketing operations manager at a 900-person manufacturer. She asked for a campaign attribution tool for her four-person team, the rep quoted exactly that, and the deal has been in "proposal sent" for nineteen days waiting on a signature that keeps slipping to "next week."

Ask the rep three questions and the shape of the problem appears immediately. Who else have you spoken to? Just her, and once her director joined a call for ten minutes. What problem did she come to you with? Attribution reporting takes her team a week every month. What does her director get measured on this year? The rep doesn't know.

That last silence is the whole coaching opportunity. The rep took the customer's stated request at face value and quoted the corner of the problem the customer happened to name. Meanwhile the actual pain — a week of manual reporting every month, in a company where sales, marketing, and finance are all arguing about which channels produced pipeline — sits three stakeholders wide and nobody has named it out loud. The finance team is rebuilding the same numbers in a spreadsheet. The sales ops lead is manually stitching campaign data into the CRM before every board meeting. None of that is in the rep's notes, because the rep never asked.

Here is the trap most managers fall into at this exact moment: they jump onto the next call and widen the deal themselves. The manager asks the director what she's measured on, gets "pipeline contribution by channel by end of Q3," reframes the deal around cross-functional reporting, and the opportunity closes at $61K. Great quarter. Terrible coaching. The rep watched a magic trick and learned nothing repeatable, and next quarter the same rep brings you another $24K single-threaded deal.

The alternative takes longer and compounds. You send the rep back with two specific commitments: name every role touched by monthly attribution reporting, and get one question answered — what number is the director graded on. That is a week of work, not a call. But it converts a one-time deal rescue into a behavior the rep repeats on every opportunity for the rest of their career. The scope expansion is a byproduct. The skill is the deliverable.

Worth noting what this scenario is *not*. If that manufacturer only has four marketing seats total, no adjacent teams, and a hard $25K departmental budget, there is nothing to expand and the coaching conversation is cruelty dressed as development. Diagnose before you prescribe.

How the mechanism actually works

Expanding scope is a discovery output, not a closing move. The mechanism runs in a specific order, and reps who skip a step get the pushy-upsell result instead of the wider-solution result.

Step one — root-cause the small deal. A rep keeps deals small for one of four reasons, and each reason gets a different intervention. A *skill* gap means they don't know how to run multi-threaded discovery or build a case beyond the initial ask. A *will* gap means widening feels pushy and risky, so they protect the deal they already have by not touching it. A *knowledge* gap means they don't know the full product surface or the adjacent use cases, so they genuinely cannot see the expansion. A *system* gap means the accounts are capped, the comp plan pays identically on a $20K and a $60K deal, or the ICP is wrong. Coaching only fixes the first three.

Step two — coach the question, not the answer. The rep needs a portable move, not a scripted line for one deal. The portable move is: take the customer's stated problem and ask who else it costs money. Every operational pain has downstream victims. Slow reporting costs the person waiting on the report. Manual data entry costs the person who inherits the bad data. Coach the rep to chase the cost, not the org chart — asking "who else should I talk to" reads as prospecting, while asking "who else is waiting on this report every month" reads as understanding the business.

Step three — practice before contact. Role-play is the step managers skip and the step that determines whether any of this survives. The rep plays themselves, you play the champion, and the rep has to ask you for an introduction using a customer-value reason. Run it three times. The first attempt sounds transactional, the second sounds rehearsed, the third sounds like a person who actually wants to solve the problem.

Step four — inspect a named commitment. Not "try to multi-thread this week." Two named stakeholders on one named deal by Friday, plus the opening question they'll use. Behavior that isn't inspected dies by Tuesday.

Step five — measure the leading indicator, not the lagging one. ACV is a lagging number that moves a quarter late. Stakeholders-per-deal and use-cases-per-opportunity move in a week and tell you whether the coaching landed.

The routing matters more than the coaching content. Running a skill intervention against a will gap produces a rep who now knows *how* to widen a deal and still won't. Running any coaching intervention against a system gap produces a demoralized rep and an unchanged pipeline.

The Five Whys drill, adapted. The most portable version of step two is the Five Whys applied to a live opportunity, with one modification: after every "why," the rep writes down *who else is affected by that answer*. Start with the stated need. Attribution reporting takes a week. Why does that matter? The team misses the monthly planning deadline. Who else is affected? The director, who presents to the CMO. Why does the missed deadline matter? Budget reallocation happens a month late. Who else? Finance. Why does late reallocation matter? Spend keeps flowing to channels that have already stopped producing. Who else? The CFO and the VP of Sales, both of whom are looking at the same bad pipeline number from different directions.

Five layers down, the rep is no longer selling a reporting tool to a four-person team. They're selling cross-functional revenue visibility to a group that includes finance and sales leadership. That is a genuinely different deal — different scope, different stakeholders, different price — and it got there without a single upsell sentence. Run the drill for ten to fifteen minutes a week on a real pipeline deal, and require the rep to map each answer to a specific stakeholder title and a specific product capability.

Real numbers, ranges, and benchmarks

Coaching without measurement is opinion. These are the numbers to instrument, with realistic ranges rather than invented precision.

Stakeholders per opportunity. For committee-driven B2B deals, published research on buying groups consistently finds that a typical purchase involves somewhere in the range of six to ten people, and that number grows with deal size and organizational complexity. If your reps' CRM records show one or two contacts on deals of that shape, the gap between reality and your data is the coaching target. Set a stage-gate: no opportunity advances to proposal without at least three named roles and their relationship to the problem documented.

Use cases per opportunity. Count how many distinct problems the rep has documented per open deal. A single-use-case opportunity is a fragile opportunity — it dies when its one champion changes jobs. Moving a team's average from roughly one to two or three documented use cases is a realistic quarter-long goal and shows up in deal size before it shows up in win rate.

Deal-size movement. Be honest with the rep about the timeline here. Because most B2B cycles run somewhere between two and nine months depending on segment, a coaching change made in month one shows up in closed-won ACV two to three quarters later. What moves in weeks is the leading behavior. Managers who promise a rep that better discovery will change their commission next month are setting up a credibility failure.

Multi-product attach rate. The percentage of closed-won deals that include more than one product, module, or service line. This is the cleanest proxy for whether adjacent-use-case discovery is actually happening, because a rep cannot accidentally attach a second product — they have to have found a reason for it.

Expansion-discovery completion. The percentage of opportunities with both a documented stakeholder map and a value case before proposal stage. This is a pure process metric and the fastest one to move, which makes it useful early in a coaching cycle when the outcome metrics haven't budged yet and both you and the rep need evidence that the work is doing something.

Win rate on expanded deals versus single-threaded ones. The critical control. Track this specifically to answer the objection "expanding scope kills my deals." If expanded deals win at a materially lower rate, the rep is widening the quote rather than the problem, and you have a framing bug to fix, not a discovery volume problem.

The cadence numbers. Run the loop on a 30/60/90 structure. Days 1–30, the rep produces a stakeholder map with three or more named roles and two or more use cases for every deal in the review — you inspect the map, not the number. Days 31–60, the rep builds a one-page value case per target deal tying scope to a metric the economic buyer owns, and you role-play the multi-threading ask before they run it live. Days 61–90, the rep runs expansion discovery solo and you coach from recorded calls rather than from their recap. Weekly one-on-ones throughout, twenty to thirty minutes of which is actual coaching rather than pipeline interrogation — pipeline review and coaching are different meetings that managers habitually merge into one, and the coaching always loses.

The business-case template. Three sections, filled in *during* discovery rather than after the proposal. Current-state cost: what the customer is losing by not solving the broader problem, in the customer's own numbers, not yours. Expanded-solution impact: which specific metric improves, expressed as a range the customer helped you calculate. Stakeholder ROI: for each additional person identified, their personal win — the CFO sees cost avoidance, the operations lead sees hours back, the IT director sees one fewer integration to maintain. Have the rep present it in a five-minute internal review before it ever reaches the customer. The template's real function is that it converts a pitch into a recommendation built from the customer's own data.

Where the data lives. Stakeholder counts and use-case documentation belong in required CRM fields, not free-text notes, or you cannot report on them. Call-based behavior — did the rep actually ask about adjacent teams — comes from conversation intelligence recordings. Coaching from a rep's optimistic recap of a call is coaching from fiction.

Trade-offs and alternatives

Scope expansion is not free, and a manager who pretends otherwise loses the rep's trust the first time a widened deal falls apart.

Speed versus size. Adding stakeholders adds calendar time. A deal that could close in three weeks with one enthusiastic champion may take seven weeks once finance and IT are in the room. The mitigation is sequencing: coach the rep to widen *in parallel* with advancing the core deal, not in series. Keep the original scope moving toward signature while running discovery on the adjacent problem, so the base deal is never held hostage to the expansion. If the wider case comes together, the rep merges it before contract; if it doesn't, they close the original and keep the expansion as a documented next-cycle opportunity.

Expansion now versus planted seeds. Sometimes the current budget is genuinely maxed and the honest move is to plant rather than push. Coach the rep to end discovery calls with a forward-looking question — "if this works well, what would you want to tackle next?" — and log the answer in the CRM as a dated future opportunity. During implementation, the rep follows up with that stakeholder with a short demo of the adjacent capability. This removes the pressure from the current cycle entirely and builds next quarter's pipeline out of this quarter's closed-won. For teams with tight departmental budgets, the planted-seed path frequently produces more expansion revenue than in-cycle widening does, because the customer has by then experienced the value rather than merely been promised it.

Manager-led rescue versus rep-led development. Covered above, but worth stating as an explicit trade. Jumping on the call gets you the deal this quarter. Sending the rep back gets you the skill for every quarter. The correct answer depends on the deal's materiality — if this one opportunity determines whether the team hits the number, take the call and then run the coaching retroactively from the recording. Just don't tell yourself the rescue was the coaching.

Coaching versus fixing the system. If a rep's accounts are structurally capped, the highest-leverage intervention isn't a one-on-one — it's a conversation with the person who owns segmentation or comp design. A comp plan that pays identically on a $20K and a $60K deal is actively teaching your reps to stay small, and it will beat any amount of coaching, every time. RevOps usually owns this diagnosis: territory design, ICP definition, and quota-to-comp mechanics are the structural upstream of everything a manager can do downstream.

Depth versus breadth of coaching focus. You can coach one rep deeply or five reps shallowly. Deep single-rep coaching on two live deals over 90 days produces durable behavior change. Broad team-wide coaching produces awareness and very little else. If you have limited coaching hours, concentrate them on the reps in the middle of the distribution — top performers have already built their own version of this, and bottom performers usually have a will or fit problem that a discovery framework won't touch.

The adjacent-motion argument. Everything above transfers to account management and renewals with the labels changed. Coaching an AM to grow net revenue retention inside a flat renewal is the same mechanic — find the adjacent problem, find who owns it, quantify it, tie it to a metric the sponsor is graded on. The difference is that the AM has usage data the new-business rep doesn't, so the discovery starts from evidence rather than from questions. If you manage both motions, teach one framework and vary the entry point; two frameworks means neither gets practiced enough to stick.

Common pitfalls and how to avoid them

Coaching the deal instead of the skill. The most common and most seductive failure. You solve the opportunity in front of you, the number lands, and the rep's capability is exactly where it was. Test yourself with one question after every deal review: could the rep run what just happened without me next time? If not, you did deal work, not coaching. The fix is discipline about which meeting you're in — deal review is for decisions about this deal, coaching is for capability, and merging them means the urgent always eats the important.

Confusing expansion with upsell pressure. If your coaching language is "ask for more budget" or "see if they'll take the enterprise tier," you are training reps to be pushy and your win rate on expanded deals will tell you so within a quarter. The correct language widens the problem: *"I want to make sure we're solving the whole thing and not patching one corner — can I ask how this shows up for the finance team?"* Same conversation, opposite customer experience. Reps who internalize the distinction stop feeling like they're imposing, which resolves most will gaps without a single motivational speech.

Setting a commitment and never inspecting it. A Friday commitment that nobody checks on Friday teaches the rep that commitments are decorative. Write it down where you'll both see it, and open the next one-on-one with it before anything else. Two minutes of inspection makes the previous week's coaching real.

Same coaching for every gap. A will gap gets reframing and role-play. A knowledge gap gets enablement and a written cross-sell map. A skill gap gets structured practice on live deals. Giving all three reps the same speech about multi-threading fixes exactly none of them, and it costs you credibility with all three simultaneously.

Skipping the role-play because it feels awkward. It is awkward. Do it anyway. Advice that hasn't been rehearsed does not survive contact with a live buyer who pushes back, and the moment a rep feels friction on a real call they revert to the safe, single-threaded version. Three reps of the same ask in a one-on-one is the cheapest insurance available.

Ignoring the structural ceiling. Telling a rep to grow accounts that cannot grow is demoralizing and it makes you look like you haven't read your own territory design. Before any coaching cycle, check whether the accounts, the ICP, and the comp plan permit the outcome you're asking for. If they don't, your job is to escalate the structure, and the rep needs to hear that you're doing it.

Expanding before the base value is proven. Reps who widen scope in the first discovery call, before they've established that the core problem is real and that they can solve it credibly, come across as opportunistic. Sequence matters: establish credibility on the stated problem, then earn the right to ask what else is broken. The customer needs a reason to believe you before they'll hand you access to their colleagues.

Documenting nothing. If the stakeholder map lives in the rep's head, it doesn't exist for forecasting, it doesn't survive a territory change, and you can't coach from it. Required CRM fields for stakeholder role and use case turn a coaching conversation into an inspectable process.

Measuring only ACV. Deal size moves two to three quarters after the behavior changes. If ACV is your only metric, you'll conclude the coaching failed and abandon it roughly a month before it would have shown results. Instrument the behavior and let the revenue confirm it later.

Letting the champion stay a gatekeeper. Some champions guard access, and reps accept that as fixed. Coach the rep to give the champion a customer-value reason for the introduction — "your director is going to be asked to sign this, and I'd rather she hear the business case from you and me together than read it in a contract" — which makes the intro a favor to the champion rather than a risk to them.

Related questions

How long before scope-expansion coaching shows up in revenue?

Behavior metrics — stakeholders per deal, documented use cases — move within two to four weeks. ACV moves after a full sales cycle plus a quarter, typically two to three quarters out. Judge the coaching on leading indicators early, or you'll abandon it prematurely.

Can you coach this remotely?

Yes, and arguably better. Conversation-intelligence recordings let you review what the rep actually asked rather than what they remember asking. Role-play works fine over video. The only thing lost is the hallway follow-up, which you replace with a written weekly commitment.

Does this work for transactional, high-velocity sales?

Partially. In sub-$10K, single-buyer deals the expansion surface is small and added stakeholders genuinely slow things down. The transferable piece is the second-use-case question. Skip the full stakeholder-mapping discipline below roughly $25K deal sizes.

Who owns fixing a system gap?

RevOps, usually, in partnership with sales leadership and finance. Territory design, ICP definition, and comp mechanics sit upstream of any manager's coaching. Escalate with data — deal-size distribution by segment — rather than as an anecdote about one frustrated rep.

What if the rep expands scope and loses the deal?

Debrief the recording. Almost always the rep widened the quote before widening the problem, or brought in a stakeholder without giving the champion a value reason for the introduction. Both are framing errors with specific fixes, not evidence that expansion is dangerous.

FAQ

How is coaching scope expansion different from coaching an upsell?

Upsell coaching pushes more product against an existing ask. Scope-expansion coaching teaches the rep to discover a bigger problem with more stakeholders and more use cases, so the deal grows because it solves more of what's actually broken. The customer experiences it as better discovery rather than a harder sell, which is the entire point of the land-and-expand framing. The tell is in the sequence: if the number moved before the problem definition did, it was an upsell.

Should reps expand scope before the first deal closes, or after?

Both, but the discipline starts in the first cycle. Coach reps to map the wider problem during initial discovery so the option to expand exists at all. Some of that scope lands in the current contract; some becomes a documented twelve-month expansion path with a date attached. Waiting until after the close means re-entering an account cold, without the discovery momentum you already had.

What if expanding scope slows the deal down?

Sometimes it should — a fast single-threaded deal is a fragile deal that dies when one champion leaves. But coach the rep to expand in parallel rather than in series: add stakeholders while the core deal continues advancing toward signature. Track win rate on expanded deals against single-threaded ones so you have evidence rather than an argument when a rep pushes back.

How do I coach a rep who's afraid that asking for more makes them look greedy?

That's a framing gap, not a skill gap. Reframe it: they aren't asking for more money, they're refusing to let the customer under-solve their own problem. Then role-play the actual language — "I want to make sure we solve the whole thing, not one corner" — until it stops feeling like a sales move. Reps rarely talk themselves out of this; they practice their way out of it.

Which metrics prove the coaching is working before revenue moves?

Stakeholders per opportunity, documented use cases per opportunity, multi-product attach rate, and the percentage of deals with a completed stakeholder map and value case before proposal stage. All four are inspectable weekly. ACV and win rate are the confirmation, and they arrive a quarter or two later.

When is a small deal size not a coaching problem at all?

When the territory, the ICP, or the comp plan caps it. If the accounts genuinely can't grow, or comp pays the same regardless of deal size, that's a structural issue. Escalate it to whoever owns segmentation and compensation design — running a coaching cycle against a ceiling the rep cannot move damages the rep and changes nothing.

Sources

• Gartner — Sales research on buying groups and consensus purchase
• Harvard Business Review — The New Sales Imperative
• Gong Labs — Research on discovery calls and multi-threading
• RAIN Group — Sales coaching research and frameworks
• Winning by Design — Revenue architecture and land-and-expand
• Sandler — Sales coaching and questioning methodology
• Salesforce — Sales coaching resources and best practices
• MEDDIC Academy — Qualification, champions, and economic buyers

Related on PULSE

• [How do you coach an account manager to expand NRR inside a flat renewal?](/knowledge/cg0930)
• [What question can you ask during a deal review that forces the rep to quantify the value they brought to the customer?](/knowledge/cg0874)
• [How do you coach reps to close on value, not price?](/knowledge/cg0088)
• [Top 10 questions to improve a rep's value proposition delivery](/knowledge/cg0879)
• [What question do you ask when a prospect objects on price but hasn't identified any specific value yet?](/knowledge/cg0912)
• [How do you handle a prospect who says 'just send me a proposal' before you've presented any value?](/knowledge/cg0906)