Twenty minutes into a client call, it becomes clear that what the prospect is asking for won’t fix what’s actually holding them back.
It looks different in every field. A managing director wants a new AI tool rolled out across the team, when what needs restructuring first is how the team communicates overall. A company asks for help writing a sustainability policy, when what it needs first is a plan for how that policy will work in its day-to-day operations. A founder wants a cost-cutting review, when the real reason margins are shrinking is prices that haven’t moved in three years.
You recognise it in the way they describe the problem, and you know that if you deliver exactly what was asked, six months later nothing will have changed.
So you have a choice.
You quote for what they asked for, or you tell a prospect the truth they might not expect to hear.
Why staying quiet feels like the safer option
Saying it out loud feels risky. They came with a clear idea of what they want, they have the budget for it, and pointing out that it won’t solve their problem can sound like you’re telling them they got it wrong. Underneath that sits a very practical worry: if you question the project, there may not be a project.
So it’s tempting to soften it. You mention the real issue briefly, agree that what they asked for could help, and send over a proposal for exactly that.
That’s where it tends to go wrong.
Either the proposal sits unanswered because they sensed you were holding something back, or they sign, you deliver, and nothing improves. The AI tool is in place, and the teams still talk past each other. The sustainability policy looks good on paper and changes nothing in practice.
At that point it’s your name attached to the thing that didn’t work, the client feels they didn’t get a return on their investment, and the referral you were hoping for never comes.
What a prospect hears when you’re honest
When you tell a prospect something they didn’t expect, in a calm and specific way, it won’t sound negative to them. It sounds like someone who asked the right questions, listened properly to the answers, and knows their field well enough to see past the initial request.
That’s often the moment you stop being one of three people quoting for the same thing and become the person they want to talk to about the actual problem.
It also changes what they’re weighing up. Instead of comparing your price with two other quotes, they start thinking about what the real problem is costing them every month, which is a far better place for both of you. I wrote more about that in why prospects say yes when you talk about the cost of the problem.
How to tell a prospect the truth without losing them
Honesty works best when it doesn’t arrive as a verdict, and it’s much easier when you’re leading the conversation rather than following it. A few things make a real difference in the moment itself:
- Ask before you share. Something as simple as “Can I tell you what I’m hearing?” gives the prospect a moment to lean in instead of bracing themselves.
- Use their own words. “You mentioned the team rarely shares updates between departments, and that’s what stood out to me.” It’s hard to argue with your own observation.
- Say where you would start instead. Pointing out a problem without a way forward leaves people stuck, whereas even one sentence on what you would tackle first turns honesty into direction.
- Leave the decision with them. They may still want what they came for, and that’s their call. You’ve given them the full picture, which is what they came to an expert for.
When the honest answer changes the project
Sometimes telling the truth changes the shape of the work. The AI rollout becomes a short piece of work on communication first, or the sustainability policy comes with a practical plan for rolling it out.
In the moment, that can feel like talking yourself out of revenue.
In practice, it tends to work the other way round. The client remembers who told them what was really going on, and that’s who they call when the next problem comes up, and who they recommend when a colleague asks.
When a prospect asks for something that won’t solve their problem, how do you usually bring it up?
If you’d like help building client conversations where your expertise comes across from the first few minutes, including the moments that feel risky to say out loud, that’s a big part of what I do in BOOST. You can get in touch here.
