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:

1. Cost of delay: "If reps lose $500k in pipeline productivity while engineering builds, that's your real budget. We're 30 days to impact."
2. 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."
3. 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:

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