The Internal Competition Playbook: Defeating "We Could Build This"

You opened Tuesday's email because this happened to you.

A deal you spent months building. A champion who was engaged. A business case that made sense. And then four words that rewrote the whole evaluation: "We might build it."

Most reps lose this deal. Not because their product is inferior. Because they play the wrong game.

They defend features against an idea that does not exist yet, has no deadline, no budget, and no accountability attached to it.

This Friday, here is the full playbook for winning.

But first: if you have a live deal where this objection just appeared and you want to know exactly which play to run, the 90-second diagnostic will show you where your deal is actually stalling. It takes 90 seconds and routes you to the right framework immediately.

Before you can win this conversation, you need to understand who is driving it and why.

The "we might build it" conversation almost never originates from a neutral cost analysis. It comes from one of three sources, and each requires a completely different response.

Source 1: The Engineering Leader Who Wants to Grow Their Team

A VP of Engineering or CTO who sees an internal build project as an opportunity. More headcount. More scope. More visibility to the board. A chance to demonstrate capability.

This person is not objectively evaluating cost vs. value. They are protecting territory.

If you try to win this with data, you will lose. They will counter every number with an estimate that conveniently favors building. You need to change the frame, not win the argument.

Source 2: Procurement Using "Build" as Price Leverage

The deal is real. The champion is genuine. But the procurement team has been briefed to push back, and "internal build option" is the most credible pressure they have.

This version is the easiest to spot: the build option gets raised without any specifics attached to it. No team identified. No timeline. No requirements document. Just the concept.

Watch for the tell: a specific discount number usually appears within 48 to 72 hours of this conversation. That is not a coincidence.

Source 3: The New Stakeholder You Never Met

You multi-threaded. You thought you had coverage. But somewhere in the organisation there is a person you never reached who has just entered the evaluation, and they have a different agenda.

Maybe a new CTO who joined six weeks ago. A VP of Product who sees this as their domain. A board member who mentioned at the last meeting that the company should own more of its technology stack.

This is the most dangerous version because it means your champion does not have full internal support, and they may not even know why.

Run your current deal against those three. If you do not know which one you are facing, you are guessing. And guessing in a live deal costs you the commission.

Below, I go through how you win the reframe… but first our sponsor:

Finance doesn’t run on “mostly right.” It runs on math.

In The Architecture Behind AI-Native Revenue Automation, Tabs’s CTO breaks down why LLMs alone aren’t enough—and what it actually takes to build audit-ready, AI-driven contract-to-cash systems for modern B2B teams.

Get the whitepaper

Here is where you win the reframe.

The internal build option looks cheap on the surface because the prospect is only counting one cost: engineering time to build the initial version. They are not counting what it actually costs to build, maintain, and own a piece of internal software over 3 to 5 years.

Your job is to walk them through the full calculation. Not aggressively. Curiously.

"I want to make sure we are comparing the right things. Can I walk you through how other teams have modelled this before making the call?"

Then you build the number together.

Step 1: The Build Cost

Enterprise software is not cheap to build internally. Development firms that do this for a living put the cost of a serious enterprise system at $250,000 to $600,000 and 12 to 24 months for the first version. That is for a team whose entire job is building software, with dedicated project management, QA, and architecture.

Your prospect's engineering team will be doing this part time, between their existing roadmap commitments.

The formula:

Engineers required x hours per week x fully loaded hourly rate x months to build

For a US-based senior engineer, the fully loaded cost is roughly $120 to $150 per hour. A modest internal project using two senior engineers working 20 hours per week each at $135/hour for 12 months:

2 engineers x 20 hours x $135 x 52 weeks = $280,800 in direct cost

Before the first line of production code ships.

Ask them: "Do you have an estimate of the engineering resources this would actually require? And have you factored in that those engineers are currently allocated to your roadmap?"

Step 2: The Opportunity Cost

This is the number that changes the conversation most dramatically.

Every hour an engineer spends building an internal version of your solution is an hour they are not spending on the company's core product. And the company's core product is what generates revenue, competitive advantage, and investor confidence.

One product manager guide put it precisely: "Your engineering time is your most precious, non-renewable resource. Every hour spent maintaining a non-core feature is an hour not spent building your Unique Value Proposition."

A fintech company evaluated a 9-month internal build and chose to buy instead. They were live in three weeks. That single decision let them launch their product two full quarters ahead of schedule, onboard their first 10,000 users, and close their next funding round while their competitor was still debugging their custom-built version of the same thing.

That competitor's build cost was not just the engineering hours. It was the market position they never recovered.

Ask them: "What features are on your Q3 roadmap that would be delayed if you redirect two engineers to this project for the next 12 months? What does that delay cost you in revenue or competitive position?"

Step 3: The Maintenance Cost

This is the cost that almost no internal build evaluation includes, and it compounds forever.

SimCorp, a financial technology firm, calculated that the initial build cost of an internal system is only 20% of the lifetime cost of maintaining it. The other 80% is ongoing: bug fixes, security patches, compliance updates, feature additions as your business evolves, and the engineering time required whenever something breaks.

When you buy from a vendor, that 80% is the vendor's problem. When you build, it sits permanently on your engineering team's plate. It never goes away. It only grows.

Ask them: "Who will own the maintenance of this after it is built? How does that affect your engineering capacity in years two and three?"

Step 4: The Failure Risk

This is the cost nobody wants to model but every CFO should insist on.

The Standish Group analysed 50,000 global technology projects and found that 66% end in partial or total failure. McKinsey research found that 17% of large IT projects go so badly they threaten the company's existence.

These are not bad companies. These are companies that underestimated the complexity of building software that is not their core competency.

Your prospect's team is going to build your product in their spare time, with shifting priorities, without dedicated project management, and without the institutional knowledge your company has accumulated over years of building exactly this thing.

Ask them: "If we modelled a 66% probability of partial or total failure on this project, what does that do to the expected value calculation?"

That is not a rhetorical question. Do the math with them.

Once you have walked them through the cost calculation, you apply the reframe in three steps.

This is not a debate. It is a business case that you are building together.

Step 1: Validate the Instinct, Not the Conclusion

"The instinct to own your technology stack is a good one. The most strategic companies in your industry think carefully about where to build versus where to buy. I want to help you make that decision well."

This takes the defensiveness out of the room. You are not attacking their idea. You are saying the question deserves a rigorous answer.

Step 2: Introduce the Full Cost Model

Walk through the four costs above. Do not present them as a counter-argument. Present them as an input to the decision.

"Before your team makes this call, I want to make sure we are comparing total cost of ownership, not just build cost. Can I share how other companies have modelled this?"

Then you build the number together, using their numbers. Their engineers. Their hourly rates. Their roadmap priorities.

When they say the total cost out loud, it becomes real. A number you give them is your number. A number they calculate is their number. Their number wins every time.

Step 3: Apply the Competitive Urgency Layer

"If this project takes 12 months to build and has a 66% probability of partial failure, you are looking at a 12 to 24 month window where your competitors who have already solved this problem continue to widen their advantage. What does 18 months of that gap cost you in market share?"

This is the question that shifts the conversation from "build vs. buy" to "act now vs. fall further behind."

When You Hear It Early in Discovery

Do not react to it. Acknowledge it as a legitimate option and plant a seed.

"That is definitely worth evaluating properly. A lot of the companies we work with have run that analysis. The ones who decided to build did so because the use case was genuinely core to their competitive advantage. The ones who bought did so because the opportunity cost of diverting engineering was higher than the vendor cost. What would you use to make that call?"

You are not arguing. You are asking them to define their own decision criteria. Then you return to those criteria at the right moment.

When It Surfaces Mid-Evaluation

This is the most common scenario. Everything was going well, and then engineering raised their hand.

"I am glad this came up before we got further down the road. Can we spend 20 minutes doing the real math together? I want to make sure your team is making this decision based on full cost of ownership, not just build cost. If building wins on that analysis, I would rather you know now."

This framing positions you as the person who wants them to make the right decision, not just buy your product. That builds trust and gives you the right to lead the conversation.

When the Final Objection Comes After a Verbal Agreement

This is the hardest version. You had a yes. Now it is gone.

"I understand. Before you move forward with the build, can I ask one question? If your team starts this project and hits the same issues that 66% of internal software projects hit, what is your backup plan, and what does the delay cost you? I am not trying to talk you out of it. I just want to make sure you have modelled the downside."

You are introducing a pause. Pauses are your friend. Irreversible decisions are not.

If the build objection is being driven by an engineering leader protecting territory, the only way to resolve it is at a level above them.

You need the CFO or CEO to weigh in on the total cost of ownership question. Not because you are going over your champion's head. Because you are giving your champion ammunition to escalate with.

Here is the framing for your champion:

"I want to help you make this decision well internally. The build vs. buy question ultimately comes down to a total cost of ownership calculation that finance should be part of. I have put together a model that shows all four cost dimensions. Would it be worth sharing this with your CFO before your team makes the call? If the math favours building, great. If it doesn't, you want to know before you're two quarters into a project."

You are not asking your champion to fight engineering. You are asking them to introduce financial rigour into a decision that currently has none.

That is not a political move. It is a reasonable request. And most champions, when given the right tools, will make it.

The internal brief, the cost model, and the CFO framing script are all in the Discovery Architect. The Tactical Tier ($197) includes the full Problem Archaeology library with the build vs. buy cost calculation framework you can run live on a call. It takes 15 minutes and produces a number your prospect did not have before you started.

There is one more thing worth saying before you apply any of this.

The build vs. buy objection is almost always a symptom, not a cause.

It surfaces when the cost of the problem has not been quantified clearly enough in the prospect's mind. When the urgency of solving it is not tied to a hard deadline. When your champion has not built sufficient internal consensus for the vendor path.

In other words, it surfaces when earlier stages of the deal were not completed well.

If you are hearing this objection on deals consistently, the fix is not a better reframe script. The fix is earlier and deeper discovery. Quantifying the cost of inaction before your champion takes your solution into internal meetings. Building urgency that is tied to their business milestones, not your quarter end.

The reframe in this playbook works. It has closed deals that looked dead. But the reps who never face this objection in the first place are doing the foundation work in months one and two, not trying to rebuild it in month seven.

That foundation work is what the Discovery Architect is built around. The reps who use it stop fighting the build objection because they collapse it before it can form.

Get the Discovery Architect here. The Tactical Tier is $197. The War Room tier at $497 adds a 1-on-1 deal audit where you send me the details of your specific build vs. buy situation and I send you back the exact play, the exact email, and the exact escalation sequence for your deal.

Both come with a 30-day money-back guarantee.

For your next call where this objection is live:

Before the call: Identify which of the three sources is driving the build conversation. Prepare the four-part cost model using publicly available data for their industry.

On the call: Validate the instinct. Do not attack the idea. Walk through the cost calculation using their numbers, not yours. Ask the opportunity cost question about their roadmap. Introduce the failure rate data as a risk modelling input, not a scare tactic.

After the call: Send your champion the one-page internal brief with the full cost model. Include a request for CFO involvement in the total cost of ownership analysis. Set a follow-up call for 5 to 7 business days.

Do not follow up in 24 hours. Give the numbers time to land.

Next week: the deal you thought was yours until your economic buyer had never heard of you.

86% of enterprise deals that die in late stage had zero economic buyer contact before month four.

The fix is not complicated. Most reps just never do it.

Active readers only.

Dingo

P.S. A rep I know in Austin faced this exact situation on a $480K deal. Engineering raised the build option in month five. She ran the four-part cost model with her champion on a Wednesday afternoon call. By Friday, the CFO had asked for a meeting. The deal closed three weeks later at full price. The numbers did the work. The tool that helped her build the model in 15 minutes is right here.