Customers Need Clarity

The meeting that felt good

“You can leave a customer meeting feeling great and still leave the customer with a problem.”

You know the meeting I mean. The demo worked, the questions were good, and somebody who barely spoke during the first call started leaning forward. Your engineer caught the thing you forgot to mention. The customer said, “This is really helpful,” and you closed your laptop thinking, finally, we’re getting somewhere.

Then you’re having a beer with another rep later, telling them how it went, and it all sounds pretty convincing. You had the right people. They understood the value. There were no obvious objections. Maybe you even mention that they asked for the deck, because asking for the deck feels like evidence that something is happening. We’ve all given that little detail more weight than it probably deserved.

What’s harder to describe is what the customer can do with the conversation now that you’re gone. They can probably explain the product better than they could an hour ago. But can they explain why their company should put other work aside to do this? That’s a different question, and it doesn’t always get answered during the part of the meeting we’re most proud of.

That gap is what this week’s free field guide, Customers Need Clarity, is about. It’s worth keeping alongside the deck you’re preparing, especially when you already know the product story and you’re still trying to understand the customer’s decision.

The deck we send afterward

“Another attachment is easier to send than an uncomfortable question is to ask.”

Suppose a few days pass and your contact says they need to talk things through internally. Nothing alarming about that. So you send the deck, a customer story, and maybe a short explanation of the feature they seemed interested in. You’re trying to be useful. You also get to feel like you did something, which matters more than we usually admit when a deal goes quiet.

I don’t think the instinct comes from laziness. We’ve worked hard to know our stuff, and information is something we can actually give somebody. It’s a lot less comfortable to ask what they’re still struggling to decide, especially when the answer might spoil the version of the meeting we’ve been carrying around.

They might already believe the product works. They might be stuck on whether the benefit is worth pulling two engineers away from a project their boss promised would ship this quarter. A reference call could help with that. A migration discussion might help even more. But a beautiful case study about a company with different staffing and different priorities could leave them exactly where they started, only with another email to read.

The room after your room

“Your customer has to carry the conversation into rooms you’ll never enter.”

Now picture your contact trying to explain the meeting to their boss. It’s late in the day, somebody is standing in the doorway waiting for a signature, and the boss asks, “Why are we doing this now?” There’s no slide on the screen. Your engineer isn’t there to clean up the answer. Your contact has a few minutes, maybe less, to make the conversation mean something to a person who wasn’t part of it.

They start with what the platform does. The boss asks about the work involved. Your contact mentions the benefits. The boss asks which existing commitment would slip. Before long, they’re talking about a question your meeting never really settled, and the deck you sent is sitting unopened somewhere in their inbox.

It’s tempting to call that a champion problem. Maybe it is. But I’d be careful about blaming somebody for failing to carry a conversation we never helped them make sense of. Being enthusiastic about a solution and being able to defend a decision are different jobs. We sometimes leave people prepared for the first one and assume they’re ready for the second.

Everybody heard something different

“One person’s clarity doesn’t guarantee the group’s clarity.”

There’s another wrinkle here. The people in your meeting can agree with you and still leave thinking about completely different things. The finance person heard a possible return. The person running technology heard six months of work that somebody has to own. Operations heard another transition landing on a team that’s already tired. Nobody has to be unreasonable for those reactions to coexist.

That’s why I don’t put much faith in a room full of nodding heads by itself. Sometimes everybody is agreeing with a different version of the proposal. The tension only shows up later, when they have to choose what gets funded or who does the work. At that point we’re surprised by an objection that was sitting in the room the whole time.

The useful conversation might be the one where somebody finally says, “We want the improvement, but we can’t absorb that disruption until the current rollout is finished.” You might not love the timing. At least now you understand the decision they’re actually facing. You can talk about a smaller first step or find out whether waiting changes the economics. There’s something real to work with, instead of another vague assurance that everybody sees the value.

If a deal came to mind while you were reading that, the free field guide gives you a place to sit with it. Particularly that meeting where everyone agreed, but you’re still not sure they agreed on the same thing.

The part that bruises your ego

“Your knowledge is valuable when it helps someone else think.”

If we’re being honest over that beer, there’s a personal piece to this too. It feels good to be the person with the answer. You remember the product detail, explain the architecture, and connect it to something the customer said three weeks ago. That’s part of being good at the job. Nobody is suggesting you stop knowing things.

But there’s a point where answering becomes a way to avoid listening to uncertainty. Someone hesitates and we jump in, partly because we think we can help and partly because silence makes us feel less useful. The question they were trying to form gets buried under a response to something they hadn’t actually asked.

You can get through a whole meeting that way and look competent. You can also miss the sentence that would have told you what mattered. I’d rather have the customer say, “Hang on, I think the issue is this,” than spend another ten minutes admiring how smoothly I explained something they already understood. That moment might be awkward. It might even reveal a problem we can’t solve. Still beats finding out a month later.

What they remember on the way home

“Your explanation has to survive without you.”

I keep coming back to that request for the deck. Sometimes it really is a good sign. Sometimes it’s just the most polite way to end a meeting that gave somebody plenty to look at and very little they can use. From our side, those two meetings can feel almost identical.

The difference may show up on their drive home, when they’re turning the conversation over without any of us talking. Can they see the choice more clearly? Do they understand what would have to be true for the effort to make sense? Or are they trying to remember which of the twenty things we showed them was supposed to matter most?

Before your next customer conversation, you can grab Customers Need Clarity, the free Forge for Sellers field guide. Keep that drive home in mind when you look through it. What would you want the customer to be able to explain after the slides are closed?

You don’t get a notification when that finally clicks for someone. They might never compliment you on it. But when they sit down with their boss the next morning, they can explain what’s worth considering, what still needs an answer, and why. I’d take that over being remembered as the rep who knew every feature. We can have a good meeting either way. Only one leaves the customer better prepared for the meeting after ours.