The most valuable thing you can hand a client is sometimes the thing they didn't ask for. Here's how to know when, and how to say it.
Early in a career, every client request looks like a work order. Someone asks for a thing, you quote the thing, you build the thing. It feels like service. It's actually something closer to transcription.
It took me years to learn that the request is rarely the point. The request is the client's best guess at how to get somewhere. The somewhere is the point.
A request is a hypothesis
When a client says "we need a new website," they aren't really asking for a new website. They're telling you something isn't working, and that from where they sit, a new website looks like the fix. That's a hypothesis. Maybe a reasonable one. But they're forming it from outside the problem, without the tools or the vantage point you have.
If you simply build what's asked, you've accepted their diagnosis without examining it. If they're wrong, you're wrong with them, and you're the one whose name is on the work.
So before I quote anything, I ask two questions. The first: What are you trying to accomplish? Not the deliverable, the outcome. More leads. Fewer support calls. A site that doesn't fall over every time a newsletter goes out. The second, once I understand the answer: Will what you're asking for actually get you there?
Sometimes the answer is yes, and we get to work. Sometimes the answer is no. That moment is what separates a vendor from a partner.
A client's request is a hypothesis about how to reach a goal. Test it before you build it.
The redesign that wasn't
A while back, a client came to us convinced they needed a full redesign. Inquiries through their contact form had fallen off a cliff over a couple of months. Their conclusion: the site looked dated, visitors were bouncing, time to start over. They had budget set aside and a competitor's site bookmarked for inspiration.
It would have been an easy yes. Real project, real budget, eager client.
Instead, I asked to look at the form. Submissions hadn't dropped at all. They were sitting in the database, right where they'd always been. What had changed was where the notification emails were landing, which was nowhere. The site was sending mail as the client's own domain, straight from the web server, a server their SPF record had never authorized, with no DKIM signature attached. That had squeaked by for years. Then the major mailbox providers tightened their sender requirements, and those messages started quietly failing. No bounce. No error. The leads just stopped arriving in anyone's inbox.
0
form submissions actually lost
2
DNS records corrected
1
afternoon to fix what a redesign never would have touched
Now picture the other version. We do the redesign. It takes two months. It looks great. It launches, and the form still sends from the same unauthenticated server, and the leads still vanish. The client has spent their budget, the problem is still there, and the new site becomes "the one that didn't work." Nobody wins that project.
Why yes is so tempting
Let's be honest about why this is hard. Yes is billable. Yes avoids an awkward conversation. Yes makes the client happy today. And when someone arrives with a fully formed request, pushing back can feel presumptuous. They know their business. Who are you to second-guess them?
But they didn't hire you for your hands. Plenty of people can execute. Whether they'd put it this way or not, they hired you for your judgment. Withholding it to protect a sale isn't service. It's a quiet form of dishonesty.
It's also bad business. Saying yes to the wrong project earns you one invoice. Being the person who told them the truth when it cost you something earns you years of trust, and every project that comes with it.
They didn't hire you for your hands. They hired you for your judgment.
How to say no without just saying no
A bare "no" is a closed door. What works is a no with a path attached. In practice, it goes something like this.
Listen all the way through.Let the client explain what they want and why, without jumping to a solution. The details they drop in passing, "it started around March" or "our old developer moved us to a new host," are often where the real answer lives.
Play the goal back to them."So what you really need is for inquiries to reach your sales team again. Is that right?" Agreeing on the goal first changes the whole conversation. You're no longer disagreeing with their request. You're both looking at the same target.
Show the gap.Explain, in plain language, why what they asked for won't hit that target. No jargon as armor. If they can't follow your reasoning, they can't trust it.
Offer the better route.Every no should come with "here's what will." If the right answer is smaller and cheaper than what they asked for, say so. That's the moment clients remember.
Respect their call, with one exception.It's their business. If they've heard you out and still want to proceed, put your recommendation in writing and do the work well. The exception is a request that puts them at real risk: turning off two-factor authentication because it's inconvenient, or leaving an admin panel open to the internet. Some no's aren't negotiable, and a good partner says so plainly.
The word that builds trust
That client did eventually get a new site, about a year later, for the right reasons and with the right goals. They trusted that recommendation because they remembered the time we talked them out of one.
That's the thing about no. Said carelessly, it's a rejection. Said well, after listening, with the goal in view and a better path in hand, it's one of the most valuable things you can deliver.
Sometimes the best work you'll do for a client is the project you talk them out of.
How to say no without just saying no
A bare "no" is a closed door. What works is a no with a path attached. In practice, it goes something like this.
Listen all the way through.Let the client explain what they want and why, without jumping to a solution. The details they drop in passing, "it started around March" or "our old developer moved us to a new host," are often where the real answer lives.
Play the goal back to them."So what you really need is for inquiries to reach your sales team again. Is that right?" Agreeing on the goal first changes the whole conversation. You're no longer disagreeing with their request. You're both looking at the same target.
Show the gap.Explain, in plain language, why what they asked for won't hit that target. No jargon as armor. If they can't follow your reasoning, they can't trust it.
Offer the better route.Every no should come with "here's what will." If the right answer is smaller and cheaper than what they asked for, say so. That's the moment clients remember.
Respect their call, with one exception.It's their business. If they've heard you out and still want to proceed, put your recommendation in writing and do the work well. The exception is a request that puts them at real risk: turning off two-factor authentication because it's inconvenient, or leaving an admin panel open to the internet. Some no's aren't negotiable, and a good partner says so plainly.
The word that builds trust
That client did eventually get a new site, about a year later, for the right reasons and with the right goals. They trusted that recommendation because they remembered the time we talked them out of one.
That's the thing about no. Said carelessly, it's a rejection. Said well, after listening, with the goal in view and a better path in hand, it's one of the most valuable things you can deliver.
Sometimes the best work you'll do for a client is the project you talk them out of.