When a prospect tells me “we’re too big for outside help,” I used to take it as a brush-off. I’d argue, or I’d start pitching, and both moves ended the call fast. Now I treat it as one of the most useful things a prospect can say, because it tells me where their process is hardest to manage.
What changed is that I stopped pitching and started running a peer check-in. I frame the call as a comparison: “We work with enterprise finance and operations teams with setups similar to yours. I’m curious how yours compares on a few points.” There’s no deck, no demo, and no ask yet.
The structure has two steps.
First, acknowledge. Something like: “That makes sense. Teams your size usually have strong internal processes, and they don’t want another vendor adding complexity.” You’re agreeing with the objection, not fighting it. Prospects relax when they feel understood, and the rest of the call depends on that.
Second, ask. “Out of curiosity, how does your team handle the reconciliation step today?” Then stop talking and let them describe the process.
Here’s a pattern from a recent meeting. A prospect’s team insisted their billing and collections setup ran cleanly. When we asked them to walk through a typical month, they described two manual steps: someone reconciling exports by hand, and a status check that lived in a spreadsheet only one person could edit. Neither was a crisis on its own. But once they said both out loud, the “we’re fine” position softened.
The technical side mattered too. The platform they were evaluating connected cleanly to a different ERP than the one they ran. That kind of mismatch is almost impossible to resolve over email. Someone has to look at the actual configuration, ask which fields feed which reports, and decide what’s feasible. You can’t do that in a three-message thread.
That’s the real lesson. When a process is complex enough that the prospect says an outsider can’t handle it, that complexity is also the reason email won’t work. You don’t need to argue for a call. You point out that the details are too involved to cover in writing, and you propose a short live session to walk through them together.
Here’s how I close it now: “Based on what you’ve described, this is too detailed for email. Would 20 minutes this week work to look at the two steps you mentioned? If it’s a fit, we’ll know quickly. If it isn’t, you’ll have a clearer picture of your own process.”
A few practical notes. Keep the peer comparison honest, and only reference accounts you’re allowed to describe. Keep the detail general: “teams with a setup like this usually…” works, while specific names and numbers don’t. Don’t rush the acknowledge step. If you skip straight to the question, it sounds like a sales technique, and prospects notice. And let silence work. The most useful answers usually come in the second or third sentence after your question, once the prospect stops defending their position.
The objection isn’t a wall. It’s a description of the problem, given to you for free. Ask the follow-up question, and let the prospect show you where the complexity actually lives.