When to bring an executive into a deal

The idea

An executive in a deal is not free help. It is a small, fixed amount of attention that you spend, and once you have spent it on a call that bought nothing, it is not there for the call that needed it. The buyer notices too: a senior face that appears for no stated reason teaches them to route around you next time.

So there are only three honest reasons to bring one in. The other side asked for a peer at that level. Someone has to make a commitment only that person can make, such as a roadmap date, a non standard term, or an escalation path in writing. Or there is expertise in the room that you genuinely do not have.

Everything else is the three bad reasons wearing a suit: the deal is stalled and nobody has diagnosed why, a manager wants visibility, or it simply feels like momentum. Learn to tell those apart out loud, and most of these requests answer themselves.

How it works

Two questions, in this order. First, what would this person do that nobody already in the room can do. Second, who is asking, and are they asking for a person or for an outcome. Almost every request in the demo above collapses once you answer the second one honestly.

The three reasons that hold up

• a peer they asked for Their side named a level, not a person A vp wants to hear it from a vp. Match the level. Reaching above it is not generosity, it signals that you could not get the right person and had to borrow a bigger one.
• a commitment only they can make A roadmap date, a non standard term, an escalation path in writing You are not allowed to promise it, so a call where you promise it is worth nothing. Send the person whose signature the promise needs, and get the promise into the order, not just into the call.
• expertise you do not have They want the architecture, the security or the migration answered before signing This is the cleanest reason of the three, and the one people skip because it feels like admitting a gap. It is the opposite. Naming the gap and closing it by thursday is what a competent seller looks like.
• stalled, undiagnosed The deal is dying and nobody knows which step lost its owner Escalation does not diagnose. It only makes the answer you have not earned yet official, and in writing.
• a manager wants visibility Someone senior on your side wants to sit in and watch A legitimate management need with a management shaped fix: the recording, the notes, a debrief. The buyer is not paying for your reporting line to feel informed.
• it feels like momentum Nothing specific is wrong, a bigger name just seems like progress This is the one that quietly drains the counter. If you cannot write down the single sentence the person is there to say, you do not have a reason.

Four mechanics, and they matter more than who

1. Match the seniority, do not reach past it. The peer of the person asking, not the most impressive person who will say yes. A chief executive answering a retention question is a worse answer than a security engineer answering it, and the room can tell.
2. Brief them on the one thing they are there to do. One job, in writing, before the call. Including what is already agreed and must not be reopened.
3. Agree in advance who runs the room. Usually you. Say it out loud beforehand so the hand off on the call is a hand off and not a takeover.
4. Give them a clean exit. A stated point where they say thank you and drop. Without it they stay, the buyer starts addressing them, and your next email goes to the wrong inbox.

The brief is the whole discipline in six lines. Send it the day before, not an hour before:

subject: 11 minutes on thursday, retention question, acme

who you are talking to     dana osei, security lead. has a veto. not the buyer.
the one thing you are for  say how long deleted records persist in backups,
                           and what we will commit to in the order.
already agreed             price, term, escalation path. do not reopen any of them.
do not say                 no roadmap dates. no discount. no "we can do that".
who runs the room          i do. i open, i hand to you, i close.
your exit                  after the second follow up i thank you and you drop.
if it goes sideways        if they ask for a term we do not have, say
                           "let me take that back". not yes, not no.

And the arithmetic the demo is really about. One deal, roughly three units of senior time before people start declining or arriving unprepared:

one deal. three units. the counter does not refill.

  request 1  "can we get time with your chief executive"   assurance     spend 0
  request 2  "can i sit in on the final close call"        visibility    spend 0
  request 3  "it has gone quiet, let us escalate"          no diagnosis  spend 0
  request 4  "how long do deleted records persist"         expertise     spend 1
  ---------------------------------------------------------------------------
  spent 1 of 3. two left for the term negotiation and the reference call.

the same four, answered by reflex:

  request 1  chief executive joins                                       spend 2
  request 2  manager joins to watch                                      spend 1
  request 3  exec to exec escalation                        declined, nothing left
  request 4  the one that genuinely needed a person         declined, nothing left
  ---------------------------------------------------------------------------
  spent 3 of 3 on the two requests that bought the least.

When to use it

Watch out for

• Treating a request for a person as a request for a person. “Can we meet your chief executive” is almost always a request for assurance: that you will still be here in three years, that someone will pick up when it breaks, that the thing they were shown is the thing they are buying. Ask what the thirty minutes is for before you decide a person is the answer. Often the honest answer is a named escalation path and a support commitment in the order, which costs nothing and is worth more than a call.
• Escalating instead of diagnosing. A deal goes quiet, and the reflex is to go up a level on both sides. But an exec to exec call into a deal nobody has qualified does not find the problem, it publishes it. Their executive asks their team what this is about, hears that it is not funded this quarter, and now you have a no in writing plus a relationship that has been spent. Find the step that lost its owner first. Then decide whether anyone senior is needed at all.
• Reaching past the matched peer. Sending someone two levels above what was asked for feels like taking the deal seriously. To the buyer it reads as theatre, and it creates a problem for the rest of the cycle: the room now expects that person, and the peer you actually needed looks like a downgrade when you finally send them.
• The unbriefed guest. An executive who joins without a brief will do the thing executives do, which is be generous. They will agree to a date, hint at a discount, or open a term you had already closed. That is not their failure. Nobody told them what was already agreed, so they optimised for the room in front of them.
• No exit, so they never leave. Without a stated drop off point the senior person stays on the call, then on the thread, then on the deal. The buyer starts addressing them directly, your champion stops telling you things first, and you have lost the room without anyone deciding to take it from you.
• Guessing on the question you cannot answer. When a pointed question lands, on data retention or anything else, the losing answer is the confident approximation. Say you do not know, name who does, commit to a date, and hold it. One admitted gap costs a day. One wrong answer discovered in the documentation costs you every other thing you said on that call.

Worked example

An interviewer asks: “Your biggest deal is two weeks from signature. Your manager wants to join the final call, and the buyer has separately asked to meet our chief executive. What do you do?”

The weak answer says yes to both, because both sound like caring about the deal. The strong answer separates the two requests, because they are not the same request.

Start with the buyer, since that one is theirs. “I would go back to my champion and ask what the meeting is for. In my experience that ask is about assurance rather than about a person, so I want to know which assurance. If it is that we will still exist and still support them, that is a named escalation path, a support commitment and a reference call, and none of those need a chief executive. If it turns out their own chief executive is going to be on it, then it is a genuine peer request and I would match it, brief ours on the single commitment we are willing to make, and agree that I still run the call.”

Then your manager, which is the harder one to say out loud. “I would ask what they would do on the call. If there is a real job, opening it, or confirming the escalation path in writing so it is not coming from me, then they have a defined role and an exit and I would take that. If the answer is that they want to see how it goes, I would offer the recording and a written debrief instead. Two unexplained faces from our side on a close call makes the buyer wonder who they are actually dealing with, and I would rather not spend that two weeks before signature.”

Close with the budget, because that is the part that shows seniority. “I am also holding one exec ask in reserve. Their security lead has a retention question outstanding, and if it comes back before signature I need to be able to put our security engineer in front of them inside a day. I would rather spend it there than on a meeting whose purpose nobody could name.” That last sentence is the whole concept, and it is the one interviewers remember.

Check yourself