How do we counter the build-vs-buy objection when their engineering team insists they can build this internally in 6 months?
Build-vs-Buy Technical Objection
40w bait: Engineering always says they'll build cheaper. Counter: what's one rep's fully-loaded cost over 6 months? That's your price ceiling. They won't beat it.
Operator Play
The build-vs-buy objection is a proxy for control and technical debt. Engineering doesn't want external dependencies; sales wants faster time-to-impact.
SaaStr and Pavilion data converge: In-house builds take 8-14 months (not 6), require 2-3 headcount, and create 18+ months of maintenance burden. The true cost: $240-400k all-in.
Three-layer counter:
- Cost of delay: "If reps lose $500k in pipeline productivity while engineering builds, that's your real budget. We're 30 days to impact."
- Feature creep reality: "Internal tools always expand scope. Day 1 is forecasting. Month 3 is territory modeling, pipeline forecasting, commission calc. Scope doubles. Timeline triples."
- Maintenance tax: "Once built, you own all patches, all upgrades, all bugs. Competitors iterate while you debug. That's $80-120k/year in forever-tax."
Force the engineering conversation to the CFO level:
| Layer | Build Cost | Buy + Integrate | Winner |
|---|---|---|---|
| Development | $150k | $0 | Buy |
| Maintenance (Year 1) | $60k | $0 | Buy |
| Opportunity (6mo delay) | $500k lost productivity | $0 | Buy |
| Technical debt (Y2+) | $100k/year | Minimal | Buy |
| Total 2-Year | $810k | Software + Integration | Buy by 3x-4x |
Force Move: Offer a 30-day pilot with their data. "If we can't prove $200k in annualized productivity gain by month 1, you have a baseline for your build estimate. If we do, you have your ROI math for the executive team."
Use MEDDPICC pain anchor: The build timeline is a symptom of lack of Urgency. Raise urgency by quantifying what stays broken while they code.
TAGS: build-vs-buy,engineering-objection,opportunity-cost,technical-debt,TCO-calculation,scoping-reality,feature-creep,maintenance-burden,ROI-timeline,MEDDPICC-application
FAQ
Why do SaaStr and Pavilion data say in-house builds take 8-14 months instead of the 6 months engineering promises? Engineering's 6-month estimate ignores feature creep and maintenance. Real builds require 2-3 headcount and run 8-14 months, plus 18+ months of maintenance burden afterward. The all-in true cost lands at $240-400k.
How does the 30-day pilot force move work in a build-vs-buy fight? You offer a 30-day pilot using their own data with a defined target of $200k in annualized productivity gain by month 1. If you miss, they have a baseline for their build estimate; if you hit it, they have the ROI math for their executive team.
Either outcome moves the deal off the build assumption.
What does the 2-year cost table show for build versus buy? The table totals build at $810k across development ($150k), Year-1 maintenance ($60k), 6-month opportunity cost ($500k lost productivity), and Year-2+ technical debt ($100k/year). Buy comes out ahead by roughly 3x-4x once integration is included.
Why frame the build-vs-buy decision as a CFO conversation rather than an engineering one? Engineering optimizes for control and avoiding external dependencies, not for time-to-impact. Moving the conversation to the CFO level forces the real numbers—cost of delay, maintenance tax, and technical debt—into view.
That reframes a technical preference as a financial decision.
How does MEDDPICC apply to countering the build timeline? The build timeline is treated as a symptom of low Urgency in the MEDDPICC pain anchor. You raise urgency by quantifying what stays broken—like $500k in lost pipeline productivity—while engineering codes. That converts an abstract "we'll build it" into a measurable cost of delay.