How do you answer "we'll just build it in-house"?

Don't argue. Price the build with them: engineer time, the maintenance that never ends, and the months the problem stays unsolved while the build happens. Most in-house plans look cheaper only until someone writes those numbers down.

Why do buyers say they'll build it in-house?

There are three reasons, and each gets a different answer.

1. They really can. They have the engineers, the data, and a reason to own it. Sometimes they're right.
2. It's a stall. "We'll build it" is the polite version of "not now." It's no decision wearing a hard hat.
3. It's a price play. They want a lower price, and the build threat is cheaper than finding a competitor.

Ask: "If you build it, who would own it, and when would it ship?" A real build has a name and a date. A stall has neither. A price play goes vague fast.

How do I price the build with the buyer?

Make a short worksheet with them, using their numbers instead of yours.

Line	Question to ask
Build time	How many engineers, for how many months?
Opportunity cost	What doesn't ship while they work on this?
Maintenance	Who fixes it when an API changes or a model gets swapped?
Time unsolved	How much does the problem cost each month until the build ships?
Ownership risk	What happens when the engineer who built it leaves?

Two engineers for one quarter is six engineer-months before anything ships. Then maintenance starts and never stops. The line that usually moves the room is time unsolved: if the problem costs them real money every month, every month of building is another month of that cost.

Fill it in together. The same rule makes an ROI calculator buyers trust: their assumptions, in plain view.

When should I agree they should build it?

When the thing you sell is core to their product, or the build is small and they already own the data and the people.

Say so. "If this is how you compete, build it. If it's plumbing, buy it and put those engineers on the product." Telling a buyer the truth when it costs you the deal is how you get the next call when the build stalls.

Then log the account with a check-in date. In-house builds slip, and when one does, you want to be the first call.

How do I handle the stall version?

Name the real alternative, which is doing nothing.

If no one owns the build and no date exists, the actual plan is to keep living with the problem. Ask what that costs: "If nobody builds this quarter, what does the current workaround cost you?" Then offer a smaller first step. A scoped pilot, one team, a short term. A small yes beats a big imaginary build.

How do I answer it before the call?

If the objection comes up every week, answer it on the page buyers read first.

Add a short "Build or buy?" block to your product or pricing page: what it takes to build, what maintenance looks like, and who should build instead of buying. That's objection handling on the page, and it filters out buyers who were always going to build.

What mistakes make it worse?

• Telling an engineering team their build will fail. They hear a dare.
• Quoting your own made-up build cost instead of using theirs.
• Dropping the price to beat the build. You just confirmed the build was the right comparison.
• Ignoring the champion's boss, who often cares more about time than cost.
• Losing track of the account once they say they'll build.

What should I do this week?

1. Pull the last five deals where "we'll build it" came up. Sort them: real, stall, or price play.
2. Write the five-line build worksheet and use it on the next call.
3. Add a "Build or buy?" block to the page buyers read before the call.
4. For every "we'll build it," set a check-in date three months out.
5. Track "built in-house" as its own loss reason so you can see how often it really happens.

A build with no owner and no date is a stall. A build with both has a price. Either way, the buyer's own numbers make the case.

Start Signals, Convert, Grow

FAQ

Is "we'll build it in-house" a real objection?

Sometimes. If they can name an owner and a ship date, take it seriously and price it with them. If they can't, it's usually a stall or a price push.

Should I lower my price to beat an in-house build?

No. Compare total cost and time to value on their numbers. A price cut tells them your product and their build are the same thing at different prices.

What if their engineers already started building it?

Ask what's done and what's left. Partial builds often stall on maintenance and edge cases. Offer to take over the part they least want to own.

How do I talk to technical buyers about build vs buy?

Talk about maintenance, ownership, and what their team ships instead. Engineers already know they could build it. The question is whether it's the best use of their time.