Skip to main content
VA Horizon
Book a Call
Discovery Calls

Why “We Built This In-House” Is Sometimes a Bluff on a SaaS Discovery Call

Quick answer

No independently sourced figure exists for how often a “we built this in-house” claim on a SaaS discovery call is an exaggeration rather than a genuine internal build, and this piece does not invent one. What is measurable is the instinct the claim triggers in a rep, and the data on that instinct is not flattering: Gong Labs found that pitching, leading with a product description instead of a question, reduces cold email reply rates by as much as 57% across more than 28 million emails analyzed, evidence that defending a product under direct comparison backfires far more often than it feels like it should.

The more useful move is verification, not defense. A team that has genuinely built and is maintaining an internal tool almost always has an owner, a budget line, and a backlog for it, three specifics a bluff usually cannot produce under a few direct questions.

Why This Objection Feels Different From a Competitor Objection

Hearing “we already use a competitor” and hearing “we built this in-house” trigger the same reflex, but they are not the same objection. A competitor is an external vendor a prospect can swap out with comparatively little emotional cost. An internal build is different: someone on that prospect’s own team spent real hours, maybe months, making it, and questioning it too directly can read as questioning that person’s work, whether or not the tool is any good.

That distinction matters for how a rep should respond. The tactics built for a competitor objection, asking what is not working with the current tool, do not translate cleanly here, since the answer involves a colleague’s own effort, not a vendor relationship anyone feels neutral about ending.

What the Claim Is Actually Doing in the Conversation

Sometimes the claim is literally true. An engineering team, especially at a company with the resources to spare a few sprints, really can solve a narrow version of a problem for internal use only. Other times it functions as a softer exit, a way to end a call without saying “not interested” or “no budget” directly, since both of those land as a harder no than “we handled it ourselves.”

The two versions sound identical in the moment, which is exactly why the instinct to respond with a product pitch is the wrong first move in either case.

Want this handled for you?

Pay per booked meeting for your industry. No retainer.

Book a B2B Call

Why Arguing Back Is the Wrong First Move

Gong Labs’ analysis of more than 28 million cold emails found that pitching, leading with a description of the product rather than a question, reduces reply rates by as much as 57%. That is not email-specific behavior, it is the same over-explain reflex a rep falls into the moment “we built this ourselves” lands and the instinct is to list every reason the product is still worth a look anyway.

Here the cost is higher than a lower reply rate. Arguing hard against a claim that might be genuinely true also reads as dismissive of an internal team’s real work, a bad look regardless of whether the objection turns out to be a bluff.

Three Questions That Separate a Real Build From a Bluff

Practitioner guidance, not a cited statistic: who owns and maintains the internal tool day to day, what happens when it breaks or a new integration is needed, and what it would actually take for it to stop being good enough. A team running a real internal build answers all three quickly and specifically, because those are questions they have already had to answer for themselves.

A bluff tends to get vague fast, a shrug about ownership, a hand-wave about maintenance, no real answer for the third question at all. That hesitation is more revealing than anything a rep could say in rebuttal.

Why a Genuine In-House Build Still Has Not Solved Everything

B2B buyers spend roughly 70% of their buying journey doing independent research before ever talking to a vendor, a pattern 6sense states holds regardless of industry, company size, purchase cost, or how important the solution is. Even a team that genuinely built something internally has typically still looked around the market at some point in that process, since building in-house is itself usually a decision made after at least glancing at what already exists.

That gives a rep an honest, non-confrontational opening: asking what they saw when they looked at other options the first time, rather than what is wrong with what they built.

Ending the Call Well Either Way

If the three questions above surface a real, working, owned internal tool, that is a legitimate no for now, not a loss worth arguing away, and it is worth a respectful check-in months later rather than a harder pitch today. If the answers come back vague, that vagueness is the actual opening the conversation needed.

Human + AI SDRs are trained to ask these kinds of questions during the qualifying conversation itself, so if this objection surfaces before a meeting is ever booked, the client’s own rep walks into the call already knowing which version they are dealing with instead of hearing it cold.

Sources

The external data in this article draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.

FAQ

What does it mean when a SaaS prospect says they built this in-house?
Sometimes it is literally true, an engineering team solved a narrow piece of the problem for internal use. Other times it is a softer way to end a call without saying no budget or not interested outright, and the two sound identical on the surface.
Should a rep push back with product differentiators when they hear this objection?
The data argues against it. Gong Labs found that pitching, leading with a product description rather than a question, reduces cold email reply rates by as much as 57% across more than 28 million emails analyzed, the same reflex that tends to backfire here.
What questions actually reveal whether an in-house build is real?
Who owns and maintains it day to day, what happens when it breaks or needs a new integration, and what it would take for it to stop being good enough. A real internal tool has quick, specific answers to all three. A bluff usually does not.
Is there data on how often this specific objection is exaggerated?
No independently sourced figure exists for how often a we built this in-house claim is an exaggeration versus a genuine internal build, and this piece does not invent one. The guidance here is verification questions, not a statistic.
What if the in-house tool really is working fine for them?
That is a legitimate, honest no for now, not a loss to argue away. It is also useful information, worth a respectful check-in later rather than a harder pitch today.

Know the objection before the call starts.

Book a 15-minute call and see how Human + AI SDRs ask enough in the qualifying conversation to flag this objection early, so your rep is not hearing it cold.

Book a B2B Call

Pay per booked meeting · No retainer · Free no-show replacement