Versus the In-House Build
vs. we'll just build it ourselves
An engineering-capable buyer believes they can build this internally. Your wedge is opportunity cost: every hour spent building and maintaining undifferentiated infrastructure is an hour not spent on the product their customers pay them for.
Buyer mindset
The buyer, often technical, sees your product and thinks it does not look that hard. They overweight the cost of the initial build and almost entirely ignore the cost of maintaining it forever. They also enjoy building, so there is an emotional pull toward DIY that has nothing to do with the business case.
Where they win
- ›Total control over the roadmap and zero dependency on an outside vendor
- ›Perfect fit to their exact internal workflow and data model
- ›No recurring license line item, which looks great in a budget review
- ›No procurement, security review, or vendor risk to clear
Where you win
- ›Opportunity cost: senior engineers building commodity infrastructure are not building the company's actual product
- ›Maintenance forever: the build is the cheap part, the ongoing upkeep, on-call, and edge cases are the expensive part
- ›Time to value: you are live now, the build is a roadmap item that slips
- ›Key-person risk: when the one engineer who built it leaves, the company owns an unmaintained black box
- ›Compliance, security, and reliability that you have already invested years in and they would have to recreate
- ›Your product improves automatically while their internal tool stagnates the day the project ships
Traps to avoid
- ›Arguing they cannot build it, which insults smart engineers and turns the deal into a pride contest
- ›Pitching the initial build cost while they have already mentally written that off, instead of hammering perpetual maintenance
- ›Talking only to the engineer who wants to build it instead of the leader who owns the opportunity-cost decision
- ›Underestimating the genuine emotional appeal of building, and failing to give the champion a business reason to say no to it
Discovery questions
- ›If your engineers build this, what is the highest-value thing they are not building while they do?
- ›Who maintains it after it ships, and what happens when that person changes teams or leaves?
- ›How do you handle the unglamorous parts, the edge cases, the compliance updates, the 2am pages?
- ›What is your honest track record on internal tooling projects shipping on time and then staying maintained?
- ›Is this capability something your customers pay you for, or is it plumbing that needs to just work?
- ›What does the build cost you in calendar time before it delivers any value at all?
Landmines to plant
- ›Ask them to estimate the fully loaded annual cost of the engineers who will maintain it, not just build it, then compare that to license.
- ›Ask who is on call for it at 2am the night before their biggest launch.
- ›Ask them to name one internal tool that shipped on schedule and is still well maintained two years later.
Objection talk tracks
“Our engineers could build this in a couple of sprints.”
I believe they could, your team is clearly strong. The build was never the hard part though. The hard part is the next three years of maintenance, edge cases, security updates, and on-call, all of which is undifferentiated work that does not move your product forward. The real question is not can you build it, it is should your best engineers spend the next three years owning plumbing instead of the thing your customers actually pay you for.
“Buying means we are locked into your roadmap.”
Fair, and here is the trade. With us you get a roadmap that improves every month with zero effort from your team. With a build, your roadmap is your own engineers, who have a day job, so realistically the internal tool ships once and then freezes. If there are specific things you need control over, let me show you our API and extensibility, because in most cases you get the control without owning the burden.
“Building it ourselves has no recurring cost.”
It has the biggest recurring cost there is, it is just hidden in salaries instead of an invoice. Two senior engineers maintaining this part time is easily several hundred thousand a year, every year, forever. Our license is a fraction of that and it is a line item you can actually see and control. Let me put both numbers side by side so it is a real comparison.
Proof to gather
- ›A fully loaded opportunity-cost model: maintenance engineer salaries versus license, over three years
- ›Win-loss stories from buyers who built first, hit the maintenance wall, and bought later
- ›Examples of build projects at similar companies that shipped, froze, and became liabilities
Make this card yours in 60 seconds
Drop your product and competitor into the builder to generate a tailored, exportable version of this play.
Open the builder