When they say we do this in-house

"We do this in-house" is a statement about capacity and identity, not a rejection of the problem. The buyer is telling you they have a team. They're not telling you the team is enough.

Treat it as information about how they work, and the conversation keeps going.

What it usually means

Sometimes it's simply true. The company has a strong internal team, the work is under control, and they don't need outside help. Accept that and move on.

More often, it means something else. The team exists, but it's stretched. The leader is protective of their people and doesn't want to look like they need help. Or the buyer has had a bad experience with an outside firm and is defending against a repeat.

And sometimes it's a reflex. Every services seller hears it. It's the fastest polite way to close an email.

You don't know which one you've got until you ask.

Don't argue with it

The worst reply is a case for why outsourcing is better. "Many companies find that external partners bring fresh perspective." That's a pitch, and it tells the buyer you didn't hear them.

Don't question their team's ability. Nothing ends a conversation faster than implying someone's people aren't good enough.

And don't pivot to a different service. "Understood. We do that other thing too" reads like you're throwing things at the wall.

The reply to send

Respect the team. Then ask a question that tests whether the team has room.

Makes sense, and it sounds like the team knows the system better than anyone outside could. One question so I'm not guessing. Is the team keeping up with both the day-to-day and the migration, or is the migration the part that keeps slipping? If they've got both covered, I'll leave it there.

That reply does three things. It credits the team, which lowers the buyer's guard. It names a specific pressure, the gap between keeping things running and building something new. And it offers a clean exit.

If the team is truly fine, the buyer says so and you've lost nothing. If the team is stretched, the buyer often says that too, sometimes in more detail than you expected.

Where in-house teams get stuck

In-house teams are usually great at running what exists. They know the systems, the people and the history. Where they struggle is capacity for something new on top of the day job.

A migration, a new platform, an acquisition integration, a compliance deadline. Those land on the same team that keeps the lights on. The work competes for the same people. Something slips, and it's usually the new thing.

That's where a services firm earns its keep. Not replacing the team. Adding capacity around it, so the team can keep running what it runs best. Frame it that way and in-house stops being an objection.

Say you wrote to a VP of Engineering at a regional insurer about a claims system modernization. They reply, "Thanks, but we handle our engineering in-house."

You send the reply above, adjusted for claims. They write back that the team is fine on the existing system, but the modernization is six months behind and two senior engineers just left.

Now you know the real problem. It isn't skill. It's capacity, and it's getting worse. Your next message is about that, plainly, and maybe about how your people would work alongside theirs.

What to avoid

Don't send a capabilities deck after an in-house reply. It confirms their fear that you're there to sell, not listen.

Don't go around them. Writing to their boss after they told you they handle it in-house makes them an enemy.

And don't give up on the account for good. Teams change. People leave. Projects pile up. Watch for a cluster of hiring for the same work. It's often the first public sign that in-house has run out of room.

"We do this in-house" tells you who you're talking to. Respect the team, test the capacity, and let the buyer tell you where the gap is.