BUILD VS BUY
When a buyer says they can build the capability internally, treat that as an unfinished evaluation—not a final no. The work is to find who owns the build, how they will judge “good enough,” what effort it pulls, and what continues if the build slips.
Published Updated By Pianpian Xu Guthrie, Founder and CEO
AEs and senior BDRs selling platforms, infrastructure, data, security, or internal tools where engineering can credibly propose a build.
Use this when you hear “we’ll build it,” “we have engineers for that,” or “this is on our roadmap,” especially before you compare feature lists.
Leave knowing whether a build is a leadership request or an assumption, who is accountable, what “good enough in six months” means, and what delay costs the business.
You cannot position against a build that has no owner, date, or bar for good enough. Diagnose the alternative first.
Price rarely decides a build-vs-buy that is really about control, staffing, or politics. Clarify those before commercial concessions.
It is often a hypothesis. Ask what would have to be true for buying to be simpler than staffing the work.
If the build slips, the current process continues. Name that cost in their language.
Use these as written. They are examples, not a script you must read in order.
Illustrative examples of the cue shape a rep might use. Not product screenshots, recorded calls, or proven outcomes.
Prospect
“This is already on our internal roadmap for later this year.”
Next question
“Who owns that roadmap item, and what would have to slip for it to actually get staffed this year?”
Why now
Roadmap language can be a parking lot. Find an owner and a staffing trade-off.
Listen for
A named PM or eng manager, competing priorities, and whether a date is real.
Prospect
“We have engineers who could stand this up in a few sprints.”
Next question
“After those sprints, who maintains it—and what does “done” mean besides a first demo?”
Why now
Standing it up is not owning it. Maintenance and the bar for done decide the real cost.
Listen for
On-call ownership, integration burden, and whether “a few sprints” has been estimated with the owner.
Prospect
“We’d rather control the roadmap ourselves than depend on a vendor.”
Next question
“Which parts do you need to control in the first six months, and which parts are you fine not staffing?”
Why now
Control is a criterion, not a veto. Split must-own from nice-to-own.
Listen for
Data, workflow, branding, or security as the real control need—and who set that bar.
You can run these questions from a doc. On a live call, Amotions can cue one diagnostic question when a build-vs-buy signal appears, so the seller does not jump into a feature comparison.
The first private prompt is usually about ownership, criteria, or delay—not a rebuttal about why vendors win.
Live coaching is designed as one next question so the rep can listen for a named owner and a date.
The buyer never sees the panel. The rep decides what to ask in their own voice.
It is the work of understanding an internal-build alternative: who owns it, how success will be judged, what effort it takes, and what continues if it slips—before you argue features.
Not first. Speed claims without their owner, date, and bar sound like a pitch. Ask what “good enough” means in six months, then compare paths against that bar.
Ask what is in production vs. prototype, who maintains it, and what would make them pause. A started build is still an evaluation if the bar is unclear.
Yes. The three scenarios on this page are designed as practice prompts. No product purchase is required to rehearse them.
Discovery calls drift into product talk before pain and impact are named.
The contact is engaged, but no executive owns the outcome yet.
Technical lists take over the call before anyone names the approver or the date.
Reps rebut the label instead of clarifying the real concern.
Calls end on recap emails instead of a named buying process.
Live BDR and AE discovery coaching when the alternative is an internal build.
Full discovery sequence with a dedicated build-vs-buy stage.
Live prompts when pushback is a rebuttal moment, not a discovery diagnosis.
Private in-call cues so sellers stay on diagnosis.
Live coaching, roleplay, and post-call feedback in one loop.