Your champion calls you on a Tuesday afternoon.
"Hey, so we had an internal meeting. The engineering team thinks they might be able to build something similar. We want to explore that route before moving forward."
You panic. You start listing features. You send a comparison doc. You drop your price by 15%.
The deal dies anyway.
Here is the thing you missed: this was never about your product. It was never about price.
It was a confidence gap dressed up as a technical objection.
And you tried to fix a confidence problem with a features argument.
What "We Might Build It" Actually Means
When a prospect says they are going to build your solution internally, they are saying one of three things.
They do not believe the problem is big enough to justify a vendor relationship.
They identified the pain. They agreed it was real. But somewhere between your demo and this call, the cost of the problem shrank in their minds and the cost of bringing in a vendor got bigger.
You did not reinforce the number. They forgot it. Now building sounds cheaper.
They are using internal build as leverage.
They want a better price and they are too polite to ask directly. Engineering raising a hand and saying "we could build this" is the perfect cover story for procurement to use.
Watch for this version: it usually comes with a specific discount number attached within 48 hours.
Someone new entered the evaluation and they have skin in the game for the build option.
A VP of Engineering who wants to grow their team. A CTO who wants to demonstrate internal capability to the board. A new stakeholder you never met who sees this as a career opportunity.
You did not see them coming. That is a multi-threading problem, not a product problem.
Run your deal through the diagnostic right now. If a build vs. buy conversation just surfaced and you do not know which of these three you are facing, you are already behind.
Why Internal Build Always Sounds Better Than It Is
The prospect's engineering team is not lying to them. They genuinely believe they can build it.
They are also wrong. Not because they lack talent. Because they are not accounting for the full picture.
The Standish Group analysed 50,000 software projects globally. They found that 66% of technology projects end in partial or total failure. McKinsey research puts it sharper: 17% of large IT projects go so badly they threaten the company's existence.
Those numbers apply to companies whose entire job is building software.
Your prospect's engineering team is going to build your product in their spare time, between product roadmap commitments, with shifting priorities and a leadership team that will defund the project the moment Q3 targets slip.
The internal build option is not a cheaper solution. It is an unquantified risk that sounds cheaper because nobody has done the math on what failure costs.
That is your job. And most reps never do it.
The Fatal Mistake
When reps hear "we might build it," they defend their product.
They send feature comparison tables. They run another demo. They drop price.
All of that assumes the objection is about your product being inadequate.
It is not.
The objection is about their internal team looking adequate. That is a totally different conversation.
You are not being compared to a competitor's product. You are being compared to an idea that does not exist yet, has no failure risk attached to it in anyone's mind, and has the political advantage of keeping budget and control in-house.
The rep who wins this situation does not defend their features. They make the risk of building visible.
This Friday, I am sending the full playbook.
The three-part internal build reframe. The cost of delay calculation that makes the math undeniable. The stakeholder question that surfaces who is actually driving the build conversation and why. And the exact script for the follow-up call that turns "we might build it" into "actually, let's move forward."
Active readers only.
Dingo
P.S. This objection killed a $420K deal I was tracking with a rep in Seattle. He handled it with a feature comparison. The prospect built nothing, bought from a competitor 8 months later, and the rep was on a PIP by then. The play that should have happened is straightforward once you know it. If you want the framework before you face this in your next deal, the diagnostic will show you exactly where your deals are stalling right now.