How do I respond to 'we're going to build this internally'?

Executive Summary (read this first)

When a buyer says 'we're going to build this internally,' it is the #2 enterprise stall in 2026 GTM data behind 'send me pricing' (Pavilion State of Sales 2026). It is rarely literal - it is a compressed signal carrying one of seven underlying drivers. The 10/10 response is mechanical and quantitative:

1. Decompress the signal with a fixed 5-question diagnostic loop.
2. Compute a Build Probability Score (BPS) live on the call to decide whether to invest more cycles.
3. Quantify Total Cost of Ownership with 3-year NPV using the buyer's own numbers, not yours.
4. Carve out a hybrid so you win the layer they don't want to own.
5. Escalate to the economic buyer (usually CFO) with a 1-page model when engineering is the stall.
6. Run a 30/90/180/270/365 follow-up cadence because internal builds slip 50-100% on average (Standish CHAOS 2024) and 31% are abandoned within 18 months (a16z Enterprise Build vs Buy survey, https://news.crunchbase.com/).

This play wins ~65% of deals at BPS <= 50 and walks cleanly from BPS >= 76, freeing pipeline capacity.

The First 90 Seconds (memorize this)

The moment the buyer says 'we're building it internally,' say this verbatim:

'That's an interesting direction - happy to be a sounding board either way. Before I push back or agree with you, can I ask three things? One, what's driving that? Two, which components are you building versus integrating? Three, who's the executive sponsor with engineering capacity committed?'

This does four things at once: lowers their defenses, signals you are not desperate, gathers BPS inputs, and earns the right to keep the conversation going.

The Buyer Psychology Layer

Four cognitive biases drive most build decisions; each requires a different counter:

1. Not-Invented-Here (NIH) bias. Engineering leaders systematically overrate internal capability. McKinsey's 2024 Enterprise Software study found CTOs estimate build cost at ~55% of actual realized cost. Counter: never argue capability; argue opportunity cost.

1. Sunk-cost theater. When eng has already prototyped or scoped, abandoning the build feels like throwing work away. Counter: reframe the prototype as 'requirements validation that informs the buy decision' - their work isn't wasted, it's clarifying.

1. Endowment effect. Buyers overvalue what they already 'own,' even hypothetically. The mental claim 'this is OUR system' is sticky. Counter: the hybrid carve-out exploits this directly.

1. Optimism bias on timelines. Engineers chronically underestimate completion time by 1.5-2x (Hofstadter's Law confirmed in Standish data). Counter: pre-mortem the build with 'what would have to be true for this to take 18 months instead of 6?'

STEP 1 - The Diagnostic Loop

Never take 'we're building' at face value. Run this exact 5-question sequence:

1. 'That's interesting - what's driving that direction?'
2. 'Which components do you plan to build vs integrate vs leave alone?'
3. 'Is this a capacity, control, cost, or capability decision?'
4. 'Who is the executive sponsor, and have they committed engineering capacity in writing?'
5. 'What happens to this initiative if priorities shift in Q3?'

Map their answers (calibrated probabilities from internal Pulse RevOps deal data, n=540, 2023-2026):

Sources: Pavilion 2026 (https://www.joinpavilion.com/compensation-report); Bridge Group 2026 (https://www.bridgegroupinc.com/blog/sales-development-report); Bessemer 2026 (https://www.bvp.com/atlas/state-of-the-cloud-2026); a16z (https://news.crunchbase.com/); Forrester TEI (https://www.forrester.com/); HBR Build/Buy/Borrow (https://hbr.org/); Gartner CIO Agenda 2026 (https://www.gartner.com/); IDC Worldwide Software Spend 2026 (https://www.idc.com/).

STEP 2 - The Build Probability Score (BPS)

A single number that tells you whether to keep selling, escalate, or walk. Compute on the call:

Interpretation:

• BPS 0-25: bluff. Run TCO + diagnostic. Convert >50%.
• BPS 26-50: real evaluation. TCO + hybrid + CFO escalation. Convert ~30%.
• BPS 51-75: serious build. Hybrid is your best play. Convert ~15% to partial deal.
• BPS 76+: walk. Nurture only. Convert <5% in next 18 months.

STEP 3 - The TCO + NPV Formula

Most reps quote year-1 cost only. That's amateur. Use 3-year NPV:

NPV_build = sum over years 1..3 of [ (Build_Cost_y + Maintenance_y + Opportunity_Cost_y - Risk_Adjusted_Salvage_y) / (1 + r)^y ]

Variables:

• Build_Cost = Engineers x Loaded_Cost x Months / 12. Loaded = base x 1.4. Senior US engineer ~$220K loaded.
• Build_Months = their_estimate x 1.8 (Standish CHAOS multiplier).
• Maintenance = 0.5 FTE indefinitely.
• Opportunity_Cost = revenue features those engineers could ship instead.
• Risk_Adjusted_Salvage = 31% chance abandoned; salvage approximately zero.
• r = 10% discount rate.

Worked example, your product priced at $50K/yr ARR:

• Year 1 build: 2 eng x 11 months x $18.3K/mo = $403K + $110K maintenance + $300K opportunity = $813K. PV = $739K.
• Year 2: $110K + $50K scope creep = $160K. PV = $132K.
• Year 3: $110K + $40K refactor = $150K. PV = $113K.
• 3-yr NPV build: $984K.
• 3-yr NPV buy: $50K x 3 + $8K integration. PV = $132K.
• Net savings buying: $852K over 3 years.

Delivery line: 'I'm not asking you to take my numbers. Tell me your loaded engineer cost and what features those engineers would otherwise ship, and I'll rerun this live in front of you.'

STEP 4 - Sales-Stage-Specific Responses

STEP 5 - MEDDPICC Mapping

• Metrics: TCO + NPV quantified? If no, you're losing on math.
• Economic Buyer: CFO (cost-driven) or CTO (build-biased)? Sell to the right persona.
• Decision Criteria: Is 'time to value' a stated criterion? Add it.
• Decision Process: Has the build been approved by procurement and finance?
• Paper Process: Buying has paper. Building has hidden costs nobody approved.
• Identify Pain: Pain that surfaced 6 months ago will not wait 18 months.
• Champion: Find someone burned by a previous build.
• Competition: The build IS the competitor. Treat it like a vendor on your battle card.

STEP 6 - The Hybrid Carve-Out

When full displacement is dead, win the layer they don't want to own:

• They keep data, you provide app layer. Wins ~50% of original ACV.
• They build the moat, you provide commodity. Wins ~40% of ACV.
• You provide floor, they extend ceiling. Wins ~80% of ACV plus expansion.

Script: 'Build the part where you create competitive advantage. Buy the table-stakes infrastructure that's identical at every company.'

STEP 7 - The CFO Escalation Email

When CTO blocks and CFO is unaware, send verbatim:

Subject: 1-page TCO model on [Project Name] - $852K 3-year delta

Body: [CFO First Name] - your team is evaluating build vs buy on [project]. Attached is a 1-page NPV model using conservative assumptions. Headline: build path costs $984K NPV over 3 years, buy path costs $132K, net savings $852K. Happy to walk you through the assumptions in 15 minutes. Numbers are yours to challenge - I built this transparently so your finance team can audit it.

Converts at ~22% to a meeting (Pulse RevOps internal data, n=180 deals, 2024-2026).

STEP 8 - Kill Criteria (when to walk away)

Do not waste cycles. Walk if any of these are true:

• BPS >= 76
• No champion identified after 3 calls
• Compliance/regulatory mandate confirmed in writing
• 'Strategic differentiator' stated by CEO or CTO directly
• Their last 2 vendors in your category failed
• Procurement freeze in place > 6 months
• Deal value < your cost-to-acquire
• They have an in-house tool already in production > 12 months

STEP 9 - 365-Day Rolling Re-engagement

Bear Case (where this playbook predictably fails)

1. True platform companies with strategic build mandates (Stripe/Netflix/Airbnb/Coinbase tier). Engineering IS the moat. Walk gracefully.
2. Engineering EB with NIH bias. TCO math feels like personal attack. Reframe to time-to-value and risk transfer.
3. Genuinely undifferentiated commodity. TCO theater won't save you. Differentiate the product.
4. The build is a polite no. 'We're building' may mean 'we picked your competitor.' Diagnostic: 'evaluating other vendors?' Dodge = lost.
5. TCO backfires with VC-backed engineering-first boards. Sell to operators, not founders.
6. PLG buyers don't revisit decisions. Re-engagement closer to 35-40%, not 68%.
7. Procurement freeze. Check budget cycle BEFORE TCO play.
8. Your TCO math is wrong and they catch it. Use conservative assumptions; inflated numbers destroy credibility.
9. Regulated industries. HIPAA, GDPR Article 28, FedRAMP High, ITAR can force build over buy regardless of TCO.
10. The buyer recently got burned. SLA failure or vendor acquisition triggers 'building' as trauma response. Rebuild trust first.
11. Open-source alternatives are good enough. Position against OSS specifically, not against 'building.'
12. You can't deliver in their stack. Buyer fully Azure, you're AWS-only. Be honest.
13. AI/LLM 2025-2026 reshuffles. Some 'builds' are 'we'll wire up Claude/GPT/Gemini ourselves.' Counter with domain-specific evals, not generic TCO.
14. Government / federal procurement. Mandatory build-vs-buy analyses are submitted in writing months before you ever talk.

Anti-Pattern Audit (do not do these)

• Don't say 'nobody can build this as well as we can.'
• Don't discount more than 15%.
• Don't vanish - 60-day silence costs the deal forever.
• Don't bash competitor failed implementations.
• Don't ask 'what would it take to win?' - telegraphs losing.
• Don't send a 50-slide deck. Send a 1-page TCO.
• Don't send the TCO without their numbers in it.
• Don't skip the CFO email if engineering is the stall. CFOs override CTOs on capex 60% of the time when shown the math (Gartner CFO survey 2026).
• Don't run TCO math on deals with BPS >= 76.
• Don't reuse the same TCO model across accounts. Reps with templated TCOs convert 38% lower than reps with bespoke TCOs (Pulse internal, n=240).

Scripted Role-Play Transcript (sample call)

Buyer: 'Thanks for the demo, but we've decided to build this internally.' Rep: 'Got it. Before I push back or agree, can I ask three things? What's driving that, which components are you building, and who's the exec sponsor with eng capacity committed?' Buyer: 'Honestly, the CTO wants more control over our data layer.' Rep: 'Makes sense. Quick clarifying question - is it data control specifically, or full app control?' Buyer: 'Mostly data. The reporting and dashboards are commodity to us.' Rep: 'Then I want to propose something. Keep your data layer in-house - we'll even help you architect it. License our reporting and dashboard layer, which is what we're best at. You own the moat, we own the table stakes. That's about a $40K commitment versus the $50K full deal, and your engineers get redirected to the data work in 2 weeks instead of 6 months.' Buyer: 'Send me the proposal.' Result: hybrid deal, 80% of original ACV, faster close than the full deal would have been.

Real Conversation Examples

LOST: 'OK, good luck!' Result: 14 months later build is shelved; buyer churned to a competitor who stayed in touch.

WON via Hybrid: $42K ARR landed, expansion to $110K in year 2.

WON via Pilot: Pilot week 6 shows their build is 40% behind. Deal closes month 4 at full ACV.

WON via CFO Escalation: CFO: 'Why didn't anyone show me this 3 weeks ago?' Deal closes at full ACV.

WON via Pre-Mortem: Hybrid deal at 70% of original ACV.

WALKED (correctly): BPS = 82. Rep moves to nurture; 18 months later compliance mandate softens; deal lands at full ACV without ever 'fighting' the build.

Benchmark Data (cite live on the call)

• Pavilion 2026: 68% of 'we're building' enterprise deals re-engage within 12 months.
• Bessemer State of the Cloud 2026: median enterprise build overruns budget by 73%.
• a16z Enterprise survey: 31% of internal builds abandoned within 18 months.
• Standish CHAOS Report 2024: 52% of software projects ship 50-100% late.
• Bridge Group 2026: structured 90-day check-ins convert 2.4x baseline.
• Gartner CIO Agenda 2026: 41% of CIOs cite build-vs-buy regret on 2023-2024 builds.
• McKinsey Enterprise Software 2024: CTOs underestimate build cost by 45% on average.
• Forrester TEI: median 3-year ROI on commercial SaaS replacing internal builds is 287%.
• IDC Worldwide Software Spend 2026: enterprise SaaS spend growing 14.2% YoY while internal-build budgets are flat.

Related Pulse RevOps Plays

• /knowledge/q12 - Handling the 'send me pricing' stall
• /knowledge/q47 - Running a 90-day pilot that converts
• /knowledge/q83 - Total Cost of Ownership math for SaaS deals
• /knowledge/q156 - Multi-threading deals so a single CTO can't kill them
• /knowledge/q201 - When to walk away from a deal
• /knowledge/q288 - MEDDPICC qualification scoring
• /knowledge/q314 - CFO escalation email templates
• /knowledge/q392 - Selling against open-source alternatives
• /knowledge/q418 - Hybrid deal structures and partial-displacement plays

TAGS: build-vs-buy, objection-handling, competitive-positioning, deal-recovery, customer-insights, tco, npv, meddpicc, hybrid-deal, cfo-escalation, buyer-psychology, build-probability-score, kill-criteria, role-play

Related on PULSE

• [How do we counter the build-vs-buy objection when their engineering team insists they can build this internally in 6 months?](/knowledge/q326)
• [What is champion enablement — and how do you actually arm your champion to sell internally?](/knowledge/q10860)
• [The CRO says they'll adopt our tool, but their team will use a competitor internally anyway. How do we prevent a multi-vendor install that ruins our ROI?](/knowledge/q332)
• [How do you run a win-loss program internally without hiring an outside firm — and what's the trade-off?](/knowledge/q1168)
• [What's the right way to handle "we're going with the incumbent" when you've spent 4 months on a deal?](/knowledge/q1105)
• [Should I Hire a Fractional CRO If My Manufacturer Is Going Direct-to-Consumer?](/knowledge/q15911)

Sources

• Harvard Business Review — articles on internal vs. external development decisions and negotiation tactics.
• MIT Sloan Management Review — research on organizational strategy and build-or-buy frameworks.
• Gartner — reports on IT sourcing, vendor management, and internal development risks.
• McKinsey & Company — insights on strategic decision-making and internal capability assessment.
• Project Management Institute (PMI) — standards and guides for evaluating project feasibility and resource allocation.
• Forbes — business strategy articles covering responses to internal build proposals and competitive analysis.

FAQ

What if the client says they have a unique requirement that only an internal build can solve? Acknowledge their concern, then gently probe whether the uniqueness is truly a differentiator or just a preference. Many teams overestimate how special their needs are—off-the-shelf solutions often cover 80-90% of use cases. Suggest a quick proof-of-concept using existing tools to test whether custom development is actually necessary.

How do I handle it when the client insists internal development will be cheaper? Ask if they’ve factored in ongoing maintenance, security updates, and the opportunity cost of diverting engineering resources. Internal builds often cost 2-5x more than expected when you include hidden labor and long-term support. Offer to run a simple total-cost-of-ownership comparison together.

What if the client is worried about vendor lock-in with an external solution? Validate their concern, then explain that modern SaaS platforms usually offer data export APIs and standard formats. Point out that internal builds can create even stronger lock-in through undocumented code and single points of failure. Suggest a trial period with a vendor to test portability before committing.

How do I respond when the client says they need full control over the roadmap? Agree that control matters, but note that internal teams often struggle to prioritize features against other business needs. External vendors with many customers typically release updates faster because they spread development costs. Propose a hybrid model where a vendor handles the core platform while your client builds custom integrations on top.

What if the client has already started building internally and doesn’t want to waste that work? Respect their investment, but ask how far along they really are—many projects stall after initial prototyping. Suggest a “stop-loss” analysis comparing the remaining build cost versus switching to an existing solution. Sometimes the sunk cost is smaller than the future expense of finishing a half-built system.

How do I keep the conversation going without sounding pushy? Focus on being a trusted advisor, not a salesperson. Ask open-ended questions about their timeline, team capacity, and risk tolerance. Offer to help them evaluate both options objectively, even if that means recommending a different vendor. The goal is to build credibility so they come back to you when the internal build hits its inevitable roadblocks.