Clients who don't live in the technical weeds will sometimes ask for things that aren't feasible, or at least not in the timeframe and budget they're imagining. This is normal. The skill isn't in preventing these requests (you can't), it's in redirecting them without making the client feel stupid or dismissed.
The wrong response is "no, that's impossible." The right response is "here's what's possible, and here's how we get closest to what you want."
Why this matters
When you handle unrealistic requests poorly, clients feel shut down or think you lack ambition. When you handle them well, you demonstrate expertise, protect the project from overcommitment, and guide clients toward solutions that actually work, often ones they end up liking better than their original idea.
The principles
Understand the need before addressing feasibility. Ask "why" before you say "can't." The underlying need is often achievable even when the specific request isn't.
Validate the goal before discussing the approach. "I love the thinking behind this" is different from "yes, we can do that." Acknowledge what they're trying to achieve before getting into constraints.
Provide alternatives, not just rejections. "We can't do X, but we could do Y which gets you 80% of the value in half the time" is infinitely better than a flat no.
Quantify the trade-offs. "That would add 8 weeks and $40K" lets them make an informed decision. Vague objections sound like excuses.
What good looks like
Client: "Can we add video chat, AI recommendations, and blockchain integration before launch next month?"
"I love the ambition. These are all features that could meaningfully differentiate the product. Let me help think through what's realistic.
Video chat: technically feasible but needs 6-8 weeks with proper testing and security. Could we target Phase 2, two or three months post-launch?
AI recommendations: this depends on having user data to train on. We could build a basic recommendation engine now (adds about two weeks) and enhance it as we gather real usage data.
Blockchain: I want to make sure we're solving the right problem. What specific benefit does blockchain give your users? There might be a simpler approach that delivers the same value faster.
For next month's launch, I'd recommend focusing on the core features, launching well, then layering these on based on user feedback and priority. Which of these would deliver the most value first?"
Why It Works
Acknowledges the ambition. Gives specific, realistic assessments. Offers alternatives. Connects to user value. Empowers the client to prioritize.
What bad looks like
"No way, that's impossible. You clearly don't understand how this works."
Why It's Bad
Dismissive, condescending, kills the conversation.
Getting better at this
- Ask "why" before "can't." The goal behind the request is often achievable.
- Offer alternatives: "We can't do X, but Y achieves a similar outcome."
- Quantify: specific time and cost, not vague hand-waving.
- Prioritize together: "If this is critical, what should we defer?"
- Stay focused on what IS possible, not what isn't.
How this connects
This combines gentle pushback (saying no diplomatically), explaining complexity (why things take longer than they seem), setting expectations (calibrating what's realistic), and managing scope creep (protecting the project from overcommitment).
Things to try
- Next unrealistic request: start with "I love the thinking behind this, let me help us figure out what's possible."
- Practice quantifying trade-offs in time and cost.
- Build a library of alternative approaches for requests you hear often.
- Get comfortable with the phrase: "That's a great goal. Here are some ways to get there."