What to Say When You Have to Say ''I Don't Know'' to a Client

The client’s face is a clear, high-resolution block on your monitor. They’ve just asked a perfectly reasonable question about the next phase of the project, a question about cost implications based on a new variable. And your mind is a complete, static-filled blank. The silence stretches. You feel your shoulders tighten as your brain scrambles, searching for an answer that sounds competent, definitive, and not like the panicked guessing it would be. Your cursor hovers over your notes, but there’s nothing there. You’re the expert they hired. And the only honest answer is “I don’t know.” But you can already feel the words “how to say I don’t know without losing credibility” forming in your head as a future, desperate search query.

This moment feels like a personal failure, but it’s not. It’s a design flaw in the professional-client relationship. You’re caught in a double bind: the client hired you for your expertise, which they equate with having answers. If you admit you don’t have an answer, you risk violating your role as the expert. But if you bluff and are wrong, you permanently damage your credibility as a trusted advisor. You are trapped between being an honest non-knower and a competent, all-knowing expert. The pressure of this trap makes you feel like any answer besides the right one is a confession of incompetence.

What’s Actually Going On Here

The core of the problem isn’t the knowledge gap; it’s the unspoken assumption that an expert’s job is to be a repository of facts. When a client asks a question, we often assume they are not just asking for information, but testing our competence. We hear the question underneath the question: “Are you really worth what I’m paying you?” This makes us filter our response through a defensive lens, bracing for a negative judgment that may not even be there. We assume they will interpret “I don’t know” in the worst possible way, as a sign of weakness, unpreparedness, or even deceit.

This pattern is often reinforced by the systems we work in. Your own organisation might implicitly punish uncertainty. A manager who responds to “I’m not sure” with a clipped “Well, find out” teaches you that not-knowing is a problem to be hidden, not a reality to be managed. The project plan, with its fixed deadlines and concrete deliverables, creates an illusion of certainty that leaves no room for exploration or honest gaps in knowledge. The whole structure is built on the myth of predictability, and your “I don’t know” is a crack in the foundation. So you feel compelled to patch it over, quickly, with whatever material you can find.

What People Usually Try (and Why It Backfires)

Faced with this pressure, most of us reach for one of a few logical-seeming moves. They feel like the right thing to do in the moment, but they almost always make the situation worse.

• The Vague Bluff. You offer a cloud of jargon that sounds authoritative but contains no actual information. “We’ll be leveraging our agile framework to synergize the data points and optimize for a forward-looking outcome.” This backfires because it’s transparently evasive. The client didn’t get an answer, and now they suspect you’re hiding something or don’t respect them enough to be direct.

• The Subject-Change. You answer a question they didn’t ask, shifting the focus to a topic where you feel more confident. “That’s an important point about the budget. And what’s really critical here is our user engagement strategy for Q3…” This move is so obvious it’s almost insulting. It signals that you’re either not listening or are actively avoiding the question, which erodes trust even faster than a simple “I don’t know.”

• The Impossible Promise. In a rush to prove you’re on top of it, you commit to an unrealistic deadline. “Good question. I’ll get you that analysis by the end of the day.” You’re making a promise to soothe your own anxiety, not based on a realistic assessment of the work. When you inevitably miss the deadline or deliver a rushed, sloppy answer, you’ve created a second failure on top of the first.

A Better Way to Think About It

The way out of this trap is to change your objective. Your goal is not to have the answer. Your goal is to demonstrate a trustworthy process for getting the answer.

Stop thinking of yourself as a database of facts and start acting as a guide with a map and a compass. The client isn’t just buying your current knowledge; they are buying your ability to navigate uncertainty. When you say “I don’t know,” it’s not the end of the conversation. It’s the beginning of a demonstration of your competence in action.

This shift is profound. It moves the conversation from a test of your memory to a collaboration on a problem. The moment you admit a knowledge gap, you have a perfect opportunity to show the client exactly how you think, how you solve problems, and how you handle a challenge. You are making your invisible process visible, which is one of the most valuable things you can do. You’re not just providing a service; you’re modeling how a professional deals with reality. And reality is full of things we don’t know yet.

A Few Lines That Fit This Move

These aren’t scripts, but examples of what this move sounds like in practice. Notice that each one pairs the admission of not-knowing with a clear, confident action.

• “That’s the right question to be asking. I don’t have a precise answer right now because it depends on the latest supplier data. Let me go pull that report and I’ll have a firm number for you by tomorrow morning.”

  • What this does: It validates the client’s question, provides a concrete reason for the knowledge gap (it’s about data, not incompetence), and commits to a specific, bounded follow-up.

• “My immediate thought is that it will increase costs by about 10%, but I don’t want to give you an answer based on an assumption. I need to verify that with the engineering team. I can have a confirmed answer for you after their stand-up tomorrow.”

  • What this does: It shows you’re already thinking about the problem (you’re not blank), demonstrates intellectual honesty by refusing to guess, and names the exact next step in your process.

• “I haven’t encountered that specific configuration before. To give you a reliable answer, I need to understand it better. Can you walk me through where that variable came from?”

  • What this does: It turns the pressure back into a collaborative inquiry, buys you time to think, and positions the client as a resource in solving the problem together.

• “To be honest, I don’t know the answer to that off the top of my head. My commitment to you is that I will always either have the answer or have a clear plan to get it. I’m making this my top priority and will follow up by EOD.”

  • What this does: It is directly honest and reframes your value proposition from “knowing everything” to “being a completely reliable problem-solver.”