How do you structure a Gong coaching review for a rep who keeps losing deals to price objections in 2027?

Two competing review structures: call-level teardown vs. deal-pattern audit

Most managers default to a call-level teardown: open one recorded call, scrub to the objection, and workshop what the rep should have said differently. It is fast, concrete, and emotionally satisfying because both parties can hear the exact moment things went sideways. It also has a well-documented failure mode — it optimizes rebuttal wording while leaving the actual cause untouched. If a rep loses on price because they never quantified the customer's cost of inaction during discovery three weeks earlier, no amount of rebuttal polish at the objection moment will change the outcome. You are coaching the symptom.

The alternative is a deal-pattern audit. Instead of one call, you assemble the rep's closed-lost cohort — typically the last 8–12 deals where price or budget was the stated loss reason — and look across them for the repeating structural signature. Gong's deal boards and tracker analytics make this practical: you can filter opportunities by outcome, then surface which trackers ("pricing," "competitor mention," "budget," "discount," "procurement") fired, when in the deal lifecycle they fired, and how often. The audit is slower to prepare, roughly 45–90 minutes of manager prep against 10–15 minutes for a single-call teardown, and it demands the manager actually form a hypothesis before the meeting. What it buys you is a diagnosis instead of a reaction.

The honest trade-off: teardowns build skill fast on a narrow behavior and work well for new reps who genuinely lack a rebuttal vocabulary. Pattern audits change win rates but take longer to show movement — expect a full sales cycle plus a few weeks before the data confirms anything. For a rep who "keeps losing" — the word that matters in this question is *keeps*, implying repetition — the pattern audit is the correct structure, with one or two teardown segments nested inside it as illustration. Repetition is itself the diagnostic signal. A single price loss is noise; five in a row is a process defect.

There is a third structure worth naming because managers slide into it accidentally: the pipeline review disguised as coaching. You open the forecast, walk the open deals, and ask what the rep is going to do about each. That is inspection, not coaching, and reps read it instantly as pressure. It has its place on a different day of the week, but if you blend it into the price-objection review the rep spends the hour defending their forecast instead of examining their behavior. Keep the two meetings separate, ideally on different days.

A fourth variant shows up in larger orgs: peer-benchmarked review, where you pull the same trackers for a top performer on the same segment and put the two side by side. This is powerful but only when the comparison is behavioral and specific — "here is where Dana introduces the ROI conversation versus where you do" — rather than a scoreboard. Used carelessly it reads as public ranking and shuts the rep down. Used well, it converts an abstract instruction into an observable model the rep can imitate. The rule of thumb: benchmark the behavior, never the number.

How to decide which structure fits this rep

The decision hinges on three inputs you can gather before the meeting: how many losses share the price reason, whether the objection appears early or late in the call sequence, and whether the rep's talk patterns are the outlier or the norm for the team.

Start with volume. If fewer than three of the last ten losses cite price, you likely have a deal-selection or territory problem rather than a skill problem, and the review should shift toward targeting and qualification. If price shows up in five or more, you have a pattern worth auditing. Next, look at timing. Gong timestamps every tracker hit, so you can see whether "pricing" fires in the first discovery call or only in the second-to-last conversation. Early price talk usually signals a rep who leads with product and price to create momentum. Late price talk, appearing only when procurement enters, often signals the opposite — a rep who avoided the money conversation until it became someone else's decision.

Third, compare talk ratios and question counts against the team baseline rather than against an absolute ideal. Published aggregate research on sales conversations has consistently found that higher-performing discovery calls involve more balanced two-way dialogue and more open questions than lower-performing ones, but the exact numbers vary by segment, deal size, and product complexity. Use your own team's distribution as the yardstick. If the rep talks 72% of a discovery call while the team median is 55%, that gap is actionable and defensible. If the rep sits at the median, talk ratio is not your problem and you should stop looking there.

One more decision input that managers skip: check whether the objection is real. Some percentage of stated price objections are proxy objections — the buyer did not want to say "I did not believe the business case" or "my champion lost internal support," so they said the price was too high because it is the socially easiest exit. Listen to two or three of the actual loss conversations end to end. If the buyer's language around price is vague and non-numeric ("it's just more than we were thinking"), that is usually a value gap. If they cite a specific competing quote, a budget cycle, or an approval threshold, that is a genuine commercial constraint and needs a different response entirely — packaging, timing, or a smaller entry point.

The numbers that make the review concrete

Coaching that stays qualitative does not stick. Bring five or six specific measurements into the room and let the rep see them.

Deal cohort size. Eight to twelve closed-lost deals is the working range. Below eight, you cannot distinguish pattern from streak. Above twelve, you spend the whole meeting on data review and the rep disengages. Pull the cohort from the trailing two quarters so seasonality does not distort it.

Time-to-first-price-mention. Measure, per deal, the elapsed days from first meeting to the first tracker hit on pricing. Write down the distribution, not the average — averages hide bimodal behavior. If half the deals show price on day zero and half show it on day 40, you have two different failure modes in the same cohort and they need separate coaching.

Discovery question count on call one. Count open-ended questions in the first meeting of each lost deal. Then count the same for three of the rep's *won* deals. The delta between the rep's own wins and losses is the most persuasive number you can put in front of them, because it removes the "your standard is unrealistic" objection. Their own winning behavior becomes the benchmark.

Longest customer monologue. Gong surfaces the longest continuous stretch of customer speech. In strong discovery this often runs a couple of minutes or more; in weak discovery, the customer never speaks uninterrupted for more than 20–30 seconds because the rep keeps filling silence. This single metric correlates tightly with whether real problems surfaced.

Discount depth and approval count. Track the average discount requested across the cohort and how many required approval escalation. A rep who discounts 8% and still loses is facing a value problem; a rep who discounts 25% and loses is often facing a fit problem. Both are diagnosable, but they are different conversations.

Multithreading count. Number of distinct contacts on recorded calls or email threads per deal. Price objections concentrate in single-threaded deals because a lone champion has no internal ally when the number lands. If the lost cohort averages 1.4 contacts and the won cohort averages 3.2, multithreading is the coaching target and price is just where the weakness surfaced.

Set the improvement target in behavioral terms, not outcome terms. "Raise your open-question count on first meetings from 6 to 12 and get a second stakeholder on the second call in your next five opportunities" is coachable and verifiable within three weeks. "Improve your win rate" is not — the rep cannot control it directly, and by the time it moves you will have lost the thread.

Running the session and sequencing what happens after

Prep first, and prep visibly. Before the meeting, assemble a short packet: the cohort list, the six numbers above, and two to three call clips of 60–120 seconds each. Clip length matters more than people expect. Anything over two minutes and the rep starts narrating context instead of hearing the behavior. Share the packet an hour or a day ahead so the rep arrives having already processed the sting — this alone changes the emotional temperature of the meeting substantially.

Structure the hour in five movements. Open with the pattern, not the person: "Across your last ten losses, price is cited in six. I want to figure out together where that gets decided." Second, have the rep self-diagnose before you offer your hypothesis — ask what they think is happening. Reps frequently name the real cause themselves, and a self-identified problem gets fixed far faster than an assigned one. Third, play the clips, one at a time, with a single question after each: "What was the customer actually telling you there?" Fourth, put the numbers up, including the wins-versus-losses comparison. Fifth, land on exactly one behavior change with a defined checkpoint.

One behavior. Not three. The most common coaching failure is over-prescription: the manager sees five fixable things, names all five, and the rep implements none because the cognitive load of changing five habits simultaneously is unrealistic under quota pressure. Pick the one that sits furthest upstream. Upstream fixes cascade; downstream fixes do not.

Sequencing after the meeting is where most coaching programs quietly die. The review generates a commitment and then nothing enforces it. Build a three-week cadence: week one is a role-play or a live-call shadow where the rep practices the behavior with no revenue at stake; week two the rep self-scores two of their own recorded calls against the specific behavior and sends you their assessment; week three you review two calls yourself and compare notes with their self-assessment. The gap between self-perception and reality is usually the most instructive artifact of the whole cycle.

Set a Gong tracker or scorecard aligned to the behavior so the measurement is automatic rather than dependent on your memory. If the target is "quantify cost of inaction," a tracker on phrases like "what does that cost you" or "how much is that worth" gives you a passive signal on whether the behavior is actually happening in live calls. Do not over-engineer this — one tracker per coaching cycle is plenty, and trackers require tuning against real transcripts before they produce clean signal.

Re-pull the cohort metrics at week six. If the behavioral metric moved and price objections did not, your diagnosis was wrong and you should return to the audit rather than doubling down. That admission is important: coaching hypotheses fail regularly, and a manager who treats the first diagnosis as final will grind a rep down over something that was never the cause.

Where RevOps owns this and where the manager does

The line is worth drawing explicitly because it gets blurred constantly. RevOps owns the instrumentation: tracker definitions, scorecard templates, the closed-lost reason taxonomy in the CRM, and the reporting that lets a manager pull a clean cohort in five minutes rather than forty. Managers own the diagnosis and the conversation. When RevOps starts writing coaching prescriptions, it produces generic advice untethered from the individual rep; when managers start hand-building their own tracker logic, you get twelve incompatible definitions of "pricing objection" and no cross-team comparability.

The highest-leverage RevOps contribution here is usually taxonomy hygiene. If closed-lost reasons are a free-text field or a picklist with overlapping options ("Price," "Budget," "Too expensive," "No funds"), the entire audit rests on garbage. Collapse the list to five or six mutually exclusive reasons, make it required at close, and add a mandatory short free-text note explaining the primary reason in the buyer's own words. That note is often the most valuable single field in the whole analysis because it captures nuance the picklist flattens.

The second RevOps contribution is a saved deal board or report that produces the audit cohort on demand. If a frontline manager has to reconstruct the query every time, the review happens once and never again. Ship it as a template, document it in one page, and check quarterly whether managers are actually using it. Adoption of coaching infrastructure decays fast without a light audit.

The third is calibration. Pull three managers into a room quarterly, have them independently score the same two calls against the same scorecard, and compare. Scoring divergence across managers is normal and large the first time you do it, and it tells you exactly where your rubric is ambiguous. Without calibration, "coaching scores" become non-comparable and any org-level trend built on them is fiction.

Adjacent scenarios where this same review structure applies

The audit shape — cohort, pattern, timing, one upstream behavior, cadence — generalizes past price objections, and recognizing that saves you from building a separate playbook for every symptom.

Losses to a specific competitor. Same structure, different tracker. Filter for competitor mentions, then measure when in the cycle the competitor first appears. Late appearance means the rep is not asking who else is being evaluated; early appearance with a loss means the differentiation message is not landing. The coaching target differs, but the review architecture is identical.

Stalled deals and no-decision losses. Arguably a bigger revenue leak than competitive losses at most companies, and structurally similar to analyze. Pull the no-decision cohort, look for whether a compelling event was ever established, and check multithreading. The tell is usually a deal with strong early engagement that quietly flattens — the champion liked it, nobody else needed it.

Renewal and expansion conversations. Customer success teams recording calls can run the same audit against churn cohorts. Price objections at renewal are usually value-realization failures that started at onboarding, which means the coaching target might not even be the person having the renewal conversation. That upstream-cascade insight is exactly what a pattern audit surfaces and a call teardown never would.

Onboarding new reps. Run the audit proactively at day 60 rather than reactively after a losing streak. You will not have enough closed deals yet, so use discovery-call behavior against the team distribution instead of outcomes. Catching a value-articulation gap in month two is dramatically cheaper than catching it in month eight.

SDR-to-AE handoff quality. Upstream of everything above. If price objections cluster in deals from one SDR, the qualification bar is the actual problem and no amount of AE coaching fixes it. Run the same cohort logic on the source of the meeting rather than the rep who worked it — this is the kind of cross-boundary analysis RevOps is uniquely positioned to catch because managers only see their own team's slice.

A closing caution on tooling: conversation intelligence platforms have grown substantially more capable at automated summarization and pattern detection, and it is tempting to let the tool produce the diagnosis. Automated summaries are excellent for triage and terrible as a substitute for a manager listening to three full loss calls. The tool narrows where to look. A human still has to decide what it means, and the rep can tell the difference between a manager who listened and a manager who read a summary.

Related questions

How many calls should a manager review per rep each week?

Two to three focused reviews of 60–120 second clips beats one full-call listen. Most sustainable cadences land around 30–45 minutes of actual listening per rep per week, concentrated on a single coaching behavior rather than scattered across everything the rep does.

Should the rep watch their own calls before the review?

Yes — self-review first, always. Send the clips ahead with one specific question. Reps who self-diagnose commit to the fix far more reliably than reps who receive a verdict, and the gap between their self-assessment and yours is diagnostic in itself.

What if the price objection is genuinely a budget problem?

Then it is a targeting problem, not a coaching problem. Check whether the lost accounts fit your ICP on company size and spend profile. If they do not, fix the entry criteria and lead routing before spending another hour on rebuttal technique.

How long before coaching shows up in win rate?

Plan on one full sales cycle plus three to four weeks. For a 60-day cycle that means roughly a quarter before outcome data is trustworthy. Track the behavioral metric weekly in the interim so you are not flying blind while you wait.

Can this review be run without a conversation intelligence platform?

Partially. You lose automated tracker timing and talk-ratio data, but the cohort logic, CRM loss-reason analysis, and multithreading counts all work from CRM data alone. The review gets slower and less precise, not impossible.

FAQ

What exactly do I filter on in Gong to build the cohort?

Filter opportunities by outcome closed-lost, restrict to the rep, set the date range to the trailing two quarters, and add a filter on the CRM closed-lost reason field for price or budget. Then layer tracker filters for pricing, discount, and competitor mentions to see which conversations actually contained the discussion. Save the filter as a shared board so you and the rep can both return to it, and so the next manager who needs it does not rebuild it from scratch.

Should I share the numbers with the rep before or during the meeting?

Before, roughly an hour to a day ahead. Reps who see the data cold in the room spend the first fifteen minutes in defensive processing rather than analysis. Advance sharing lets them arrive past the initial reaction and ready to think. Include the wins-versus-losses comparison in the advance packet specifically, because it frames the whole session as "you already know how to do this" rather than "you are failing."

What if the rep disagrees with the diagnosis?

Take it seriously and ask what they would look at instead. Reps often have context the data lacks — a specific deal that skewed the cohort, a product gap, a pricing change mid-quarter. If their alternative hypothesis is testable, test it. If they simply reject the pattern without an alternative, agree on a behavioral experiment for three weeks and let the next cohort pull settle it. Data beats debate, but only if you actually go get the data.

How do I avoid this feeling like a performance-improvement plan?

Separate the meetings and say so out loud. Coaching reviews look at behavior and are forward-looking; performance conversations look at attainment and carry consequences. Blending them poisons coaching permanently — the rep will treat every future review as evidence-gathering. Also coach your strong performers with the same structure, so the review is visibly a normal part of the job rather than a signal that someone is in trouble.

Does this work for a rep selling a genuinely expensive product?

Yes, and arguably it matters more. High-price products lose on price constantly, so the coaching target shifts from rebuttal to business-case construction and stakeholder mapping. The audit will typically show a multithreading gap and thin quantification rather than weak objection handling. Same structure, different upstream behavior.

What is the single most common root cause you should expect to find?

Insufficient quantification of the problem during discovery. When the buyer has never articulated a number for what the status quo costs them, any price becomes an expense rather than an investment, and the objection surfaces at proposal. It is not the only cause, but it shows up often enough that it is the right first hypothesis to test.

Sources

• https://www.gong.io/resources/
• https://help.gong.io/
• https://hbr.org/2011/07/selling-is-not-about-relationships
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://sloanreview.mit.edu/topic/marketing/
• https://www.rain.today/blog
• https://www.saleshacker.com/

Related on PULSE

• How do you build a closed-lost reason taxonomy that survives contact with reps?
• What does a healthy talk-to-listen ratio look like by deal size?
• How should RevOps instrument sales coaching without owning the coaching?
• When is a price objection actually a multithreading failure?
• How do you separate coaching conversations from performance management?