We built something in-house: SaaS SDR sales
The short answer
Respect the build, then ask about its upkeep. Ask who maintains it today and what the team wishes it did. Ask what happens when that engineer leaves or moves to other work. Do not pitch against it. Offer to compare notes on the gaps they already named.
Take the 3-minute sample callWhy buyers say it
Somebody on their team built it, and that somebody has a name, a manager and some pride. Saying "we built it" protects that work and the hours already spent. It is also true that a custom build fits their workflow exactly on day one. What the buyer has not said yet is that it has one maintainer, a request queue, and a list of things it does not do.
How reps lose the deal on it
- They say building is a mistake and nobody should do it. The person who built it is often on the call or reports to the buyer, and you just called their work a mistake.
- They start a feature list. The buyer checks each item against what their own system does, finds the matches, and answers every gap with "we can add that."
- They ask "how long did that take to build?" like a trap. The buyer hears a trick and starts defending the hours.
The steps, in order
- Ask who maintains it today and what the team wishes it did.
- Ask what happens when that engineer leaves or moves to other work.
- Do not pitch against it.
- Offer to compare notes on the gaps they already named.
Stronger lines to say
- “That’s real work, and it probably fits how your team operates better than anything off the shelf. Who built it?”
- “What does it still not do that someone keeps asking for? And who has that on their list this quarter?”
- “I’m not here to replace what you built. Can I walk you through the two or three things a custom system tends to leave for later, and you tell me if you’ve already solved them?”
A call that goes right
Example exchange. The buyer and the call are fictional.
- BuyerWe actually built something in-house for this a while back, so we’re covered.
- RepGood for you, that’s not a small project. What did it need to do that nothing off the shelf did?
- BuyerOur data lives in a few odd places and the packaged stuff couldn’t touch it. One of our engineers wired it all together.
- RepThat’s exactly the case for building. What does it do less well than you’d like? Everything custom has a corner somebody avoids.
- BuyerIt breaks when source formats change, and there’s a queue of requests. But we’re not changing it. I’m not paying for something we already have.
- RepUnderstood, and I won’t ask you to. If that engineer got pulled onto the product roadmap next quarter, who’d keep that corner working?
- BuyerGood question. Nobody, probably. I’d have to think about that.
- RepThen that’s worth a note on your side whatever you pick. If you want, I’ll write down the two questions I’d ask before relying on a custom build, and you can use them with me or without me.
Same line, different meanings
| The buyer says | Usually means | Say instead |
|---|---|---|
| “Our engineering team already built that.” | Engineering owns it, and the buyer would have to overrule their own people to consider anything else. | “Then they know the problem better than anyone. What’s the one request they keep deferring? That’s the only thing I’d compare notes on.” |
| “We have scripts and spreadsheets that do the job.” | It works because one person runs it, and nobody has written that down as a risk. | “Scripts like that run on one person’s knowledge. What happens to a Monday morning when that person is out for a week?” |
| “Our CTO won’t let us buy what we can build.” | A build-first rule means the buyer cannot say yes alone, and may not agree with the rule. | “That’s a fair rule. Would it help if I wrote the questions your CTO would want answered about building versus buying, so you can raise them internally?” |
| “We’re actually rebuilding it right now.” | They have hit the limits of the first version, and a window is open. | “Then the timing could be good for a short conversation. What made you decide the first version wasn’t enough?” |
When to let the buyer go
If the buyer has told you the build handles everything, nobody is asking for changes, and an owner has time to keep it going, believe it. Say it sounds like a solid setup, ask whether you may check back if the owner's workload changes, and send nothing more. A buyer you respected will remember who did not argue with their own work.
Questions reps ask about it
How do I respond when a prospect says they built it in-house?
Treat the build as a real accomplishment, because it is. Then ask three plain questions: who maintains it, what it cannot do yet, and what happens if that person moves on. Do not pitch. The buyer will hear the gaps in their own answers, and the gaps are your opening, if there are any.
What questions expose the hidden cost of a homegrown system?
Ask who owns it day to day, how much of that person's week it takes, what sits on the request backlog, how it handled the last change in a source system, and who reviews its security. You are not trapping anyone. Many teams have never added these up, and saying them aloud is the useful part.
What if the engineer who built it is on the call?
Talk to that person as the expert, because they are. Ask what they would build next if they had the time and what they are tired of maintaining. Engineers usually know the backlog better than anyone and will answer honestly. Never suggest the build was a mistake. Ask for their view, and give it weight.
Should I compete on features against a custom system?
No. A custom build matches their workflow exactly, so you lose a feature contest on day one. Compete on what a build rarely has: someone whose full-time job is improving it, a team handling upgrades, and support when it breaks. Say it as a question about their situation, not as a boast about yours.
What do I say when they claim the homegrown version is free?
Their time is the cost. Ask what that engineer would be building if they were not maintaining this. If the answer is a product feature, the build has a price in delayed work. If the answer is nothing much, the buyer may be right, and you should say so. Do not argue with a fair point.
Related objections
Hear a buyer push back
The free call uses a sample scenario. Answer out loud, hear the buyer push back, and try a stronger answer.
The buyer is AI and the company is fictional. Want the whole team practicing? See pricing.