The First Ask Is Not THE Ask

You sent the deck on Tuesday. Kurt wrote back on Thursday.

"This is great. Really well put together."

That is the sound of nothing happening.

He is not being polite. He means it, and it is the correct response to what you actually asked him for. You handed him a finished thing and asked him to assess it.

He assessed it. Favorably. Nobody ever funded anything because it was well put together.

You Own the Proof. They Own the Case.

Here is the division that decides how this goes.

You own the proof. Every outcome you have delivered for somebody else, every before and after, every reference logo. And when you do not have those, you borrow them. New product, new category, two logos and neither of them famous, so you reach for analyst numbers and industry benchmarks instead. That works, because the job is identical either way.

Proof establishes what is possible. It does not establish what is true here.

Borrowed proof is even easier to agree with, which is the trap in it. A benchmark is about the industry. Nobody has ever had to defend a benchmark.

Either way, what you are holding is a key blank. Real brass, correct profile, cut for nothing. It will not turn in their door until somebody cuts it to the one lock it has to open, and the shape of that lock is information you do not have.

It is proof. It is not the case.

They own the case. All of it. The four hours somebody spends every Sunday night. The temporary help booked at every close. The renewal nobody has circled. The person who has absorbed this quietly for two years and has never been asked what it costs.

None of that is in your CRM and none of it is reachable from outside. Which means the first three gates, naming the friction, pricing the wait, and shaping the ask, cannot be cleared from your side of the table. Not partially. Not with a good guess.

So there are two asks, they go in one order, and inverting them is what produced the email from Kurt.

The First Ask: Build It With Me

What it is. Not a discovery call and not a workshop with your logo in the corner. You are asking for the working sessions where the two of you clear the first three gates together: who is absorbing the friction, what the waiting costs, what one decision would end it.

When to ask. After the proof has done its job and not before. The proof earns the meeting. It never fills it. If you ask before you have shown you can do the work, you get a requirements document instead of people, which is the polite version of no.

How to ask. Make it cost time and not budget, because a champion can authorize his own calendar and cannot authorize a purchase order. Name who you need and why: the person who does the work, the person whose budget absorbs it, the person who will eventually have to say yes. Three names is a real ask. "Some time with your team" is not.

Then, at the end of that work, make it portable. That is the fourth gate and it is the handoff. You are not writing a summary for the room you are standing in. You are building the version your champion carries into a review you will never attend, so that all four gates are in his mouth and he does not need you in the building.

The Second Ask: The Decision

What it is. One named action, one owner, one date. The thing you actually came for.

When to ask. Only once the fourth gate is done. Ask before the case is portable and you are asking somebody to defend an argument he cannot repeat.

How to ask. Usually you do not. That is the part sellers hate. By this point the ask gets made in a room you are not in, by somebody whose job is not selling it, and your job was to make sure he could.

You do not turn the key. You cut it and hand it to the person who does.

What the Order Buys You

Kurt said yes to the first ask. It cost him three sessions and, reluctantly, the director who owns the number.

Halfway through the second one somebody said a thing out loud that had never been said in front of that director. The platform team runs a manual failover drill every third Friday, because the automation was never finished, and it takes four engineers most of a day. Roughly thirty engineer-days a year, living entirely on a recurring calendar invite. The director had never seen it as a cost because it had never once been a line.

You did not know that. You could not have known it. It is not in any deck you have ever built and it is now the first thing out of his mouth.

Notice who found it. Nobody in that room had, and they had all been standing next to it for two years. It surfaced because somebody from outside asked a question they had stopped asking themselves.

That is the whole difference, and it has nothing to do with what you sell.

A vendor arrives with an answer and asks you to evaluate it. An advisor arrives with questions and helps you build one.

The reason most sellers never get treated as the second thing is that they never ask for the work. They ask for the decision, because the decision is what they are paid on, and asking for the decision is the most vendor-shaped move there is.

That is the real return on doing this in order. A case somebody helped build is a case he will defend. A case that arrives finished is a case he will evaluate.

Those are different verbs, and only one of them survives a closed-door review.

-BZ