Build vs Buy Objection: Scored Drills

What does the build vs buy objection actually mean?

It means one of three things, and your second move depends on which. Sometimes the buyer means it literally: a CTO with capacity, a roadmap slot, and a genuine preference for owning the code. Sometimes it is a price lever, raised by a sponsor who wants your number to move before procurement opens. Sometimes it is a borrowed line, carried into the room by a champion who heard it from a blocker and could not answer it.

Check your own recordings for when the engineering alternative objection lands, and whether the room had gone senior by then. The rep is invested, the audience is unfamiliar, and improvisation under those conditions produces one of two bad outputs: a defensive argument about engineering quality, or a quiet concession that the build is a fair comparison.

A buyer who says their engineers could build it is describing a competitor with an internal budget code.

File it in your objection library as the in-house build objection, recorded in the buyer's own words, tagged with which branch you heard. Our objection library guide covers how to capture buyer language without sanding it down. Then drill one agreed first response until it is automatic, and let strong reps improvise the branches from understanding rather than from panic.

The one agreed first response

Three moves, in order, before you know which buyer you are facing. Acknowledge, trade, re-anchor. The order matters more than the wording, and reps may use their own words once they can hit all three under pressure.

Move one: acknowledge the capability, specifically. Your team could build a version of this. I'd assume that going in. One sentence. No hedge, no "but", no pause to list reasons the build will fail. Arguing against a buyer's engineers costs you the champion and wins you nothing the transcript can score.

Move two: trade for the true cost and the maintenance owner. Before we compare them, two questions. Who owns it after the person who builds it moves teams? And what comes off their roadmap to make room for it? You are asking the buyer to supply the cost line themselves. The scoreable behavior is simple: by the end of the exchange, the buyer - not the rep - has named an owner and named what the build displaces.

Move three: re-anchor on the dated outcome the buyer already named. Earlier you said [outcome] has to be live by [date]. If the build slips a cycle, what happens to that date? Use their outcome and their date, quoted back. If nobody in the room ever named a date, that is the real finding, and the objection is a symptom of weak discovery rather than a competitive threat.

Three buyer branches worth drilling

Same three moves, three different buyers, three different ways to run the trade. The same sentence from a CTO, a sponsor, and a champion requires three different deliveries of move two.

Branch one: the CTO who means it. They have staffed similar systems and they are not bluffing. Do not sell against the build. Scope it. Ask the two questions straight, then ask what the first release covers, what it deliberately leaves out, and who fields the support tickets in the first bad week. Your best outcome may be an honest split - they build the part they care about, you carry the part they do not want to own. If neither is true, disqualify cleanly rather than discount your way into a build they will finish anyway.

Branch two: the sponsor using it as a price lever. Check the timing: note whether the build appeared after pricing rather than during discovery, and whether the sponsor can name an engineer. Do not move the number in response. A Sandler negative reverse gets you to the same two answers by a different road - soften against their momentum so they argue the truth: It sounds like building it internally is the better path. Should we stop the commercial conversation and let your team scope it? Then ask who would own it and what it displaces. Score whether the rep holds silence after the pull-back.

Branch three: the champion repeating a blocker's line. Your champion is quoting someone who is not in the room. Arm them instead: hand them the owner question and the roadmap question as their questions to take back, and ask who needs to be in the next session. That is a multithreading problem, and multithreading drills handle the follow-up motion.

Rubric rows a manager can grade from the transcript

Grade the behavior, not the confidence. A rubric row that cannot be graded from the transcript alone is a manager's opinion wearing a number. Load these rows against your own call stages so the coaching note cites your playbook rather than generic advice.

Talk/listen ratio belongs on the report as an input to investigate, not as a pass bar. If a rep talks most of the objection response, open the transcript at that flag and read what they were defending.

Why do reps lose this objection?

Because the response was improvised. The objection arrives late, the rep has no agreed first three moves loaded, and improvisation under pressure collapses into one of two predictable failures - both visible early in the transcript.

Failure one: arguing against the buyer's engineers. The rep hears a threat and defends. They cite complexity, edge cases, security work, the years of product investment behind the thing being compared. Every sentence of it may be accurate. It still loses, because the buyer's engineers are colleagues the buyer has to keep working with, and you are the outsider calling their judgment poor. The champion stops advocating, the CTO stops talking, and the rest of the call is polite.

Failure two: conceding the build is viable without pricing maintenance. The rep, coached not to argue, over-corrects into agreement. "That's fair, a lot of teams do that." Conceding the build is viable without pricing maintenance hands the buyer a cheaper option you helped them justify. Acknowledgment is a move you make in order to earn the trade. Without the trade, it is just capitulation delivered warmly.

Our position is that rehearsal is what makes improvisation safe: teams need a small inventory of real objections with one agreed first response drilled until automatic. Reps who have the first three moves automatic are the ones who improvise the fourth move well. Our objection handling program guide covers how to build that inventory without turning it into a script library nobody opens.

The week-one drill, its pass bar, and the failing attempt

Run it as an objection first response drill: one opening line, three buyers, scored the same way each time. We recommend a 30-minute manager run cost - 5 minutes setup, 15 minutes drilling, 10 minutes debrief - with about 10 minutes of prep beforehand to pull the scenario from a live deal and pick the rubric row you will grade. Take the buyer's exact sentence from a recorded call. Do not clean it up.

Structure: the rep gets the same cold open in all three reps of the drill - the buyer says the engineering team could build it - but the buyer persona changes each time, and the rep is not told which branch is coming. In XL Roleplay, run this against three personas built from your own accounts so the coaching note grades against your call stages instead of generic advice; a peer playing the buyer works too, provided they hold character when pushed.

Pass bar, all six in a single unaided attempt: the rep acknowledges the capability in the first sentence; the buyer names a maintenance owner or admits there is none; the buyer states what leaves the roadmap to make room for the build; the rep restates the buyer's outcome and date in the buyer's words; the rep's delivery matches the buyer type in the brief; and the rep lands a next step that tests the comparison. A drill without a pass bar is a conversation, and conversations do not certify anything.

A failing attempt sounds like one of two things. Arguing: "I hear you, but honestly, by the time your team scopes the integrations and the compliance work, you're looking at a serious investment." No acknowledgment, no owner named, no date, and the rep is now debating people who are not in the room. Conceding: "That's completely fair - a lot of teams go that route. Let me know how the scoping goes." The capability was granted and nothing was traded for it, so the buyer leaves with a cheaper option the rep helped justify.

Debrief and re-run: isolate one moment, ask the rep to self-diagnose before you render a verdict, and schedule the re-run before the session ends. One behavior, not six. The debrief guide has the script. A failed attempt gets re-run within the same week against the branch that broke it.