A prospect asks, “So how would you work with our internal team?” Most reps hear an objection. They start explaining: the onboarding steps, the rollout timeline, the security review, the dedicated contact. Ten seconds later the prospect is worried about something they weren’t worried about before.
I’ve reviewed enough call recordings to see the pattern. That question is not a challenge. It’s a buyer checking whether this will work inside their company. They’re asking who will do the work, how much time it will take, and whether it will get stuck in their internal process. That means they’re past “is this relevant?” and into “could we actually run this?” Treat it as a buying signal.
The mistake is answering with a full plan. Every extra detail is a new thing to object to. Mention a six-week rollout and they start counting the cost of six weeks. Describe a multi-stage security review and they wonder what that review will cost them. You haven’t answered the question. You’ve handed them a list of reasons to slow down.
A review of one of my cold calls to a CFO showed the same dynamic in a different form. The CFO said no early. The instinct is to push back, make one more case, and try to win the point. CFOs are decisive, though, and challenging a no reads as pressure. The better move was to stop defending and get curious. Instead of pitching, ask about their “secret sauce”: how they’ve handled the problem so far and what’s working. That disarms the no and opens a conversation instead of a debate.
Apply the same discipline to the implementation question. Give a short, honest answer in one or two sentences: “We’d work alongside your people, not around them.” Then hand the question back: “Who on your side would need to be involved?” That’s the whole answer. Their reply tells you who the real stakeholders are, what they’ve tried before, and what would make them nervous. You now have discovery that will shape the deal, and you didn’t have to oversell anything to get it.
Connectors help here too. A line like “I know I’ve caught you at a busy time” or “Does this sound familiar?” creates a human moment before you go deeper. It makes the conversation feel like two people working through a problem rather than a rep reading a script.
Before you answer, think three or four steps ahead. If they ask about implementation, the next questions are usually predictable: How long will it take? Who has to sign off? What happens to the tool we already use? Plan the discovery path that gets you through those in order, so you’re not reacting one step at a time. A rep who can see the route can keep the conversation moving toward a useful outcome.
Keep your tone level, too. Once the answer sounds like “we’d love to get started with you,” you’ve shifted the power to them. You’re evaluating whether this fits, and so are they. When the prospect is hesitating, a calm, slightly skeptical question such as “What would make this a bad idea for your team?” often surfaces the real concern faster than another round of reassurance.
My rule for this moment is simple:
- Answer in one or two sentences.
- Ask who on their side would be involved.
- Ask what would make it hard.
- Stop talking.
The question is a gift. It tells you the prospect is already thinking about the work after the sale. Use the next two minutes to learn what that work looks like, not to convince them it will be easy.