What Do You Do When Your Champion Leaves Mid-Deal?

What do you do when your champion leaves mid-deal?

Assume the deal has reset and behave accordingly. Do not send a cheerful note asking who picked up their work. Go back to the problem the company was trying to solve, find out whether it still exists, and find out who owns it now. Those are two different questions and the second one is worthless without the first.

Most sellers do the opposite. They treat the departure as an administrative interruption, ask for a new point of contact, and resume the old sequence. That reads as though you were selling to a person rather than to a company, and it rarely survives contact with whoever inherited the inbox.

I have lost deals this way and I have saved a few, and the difference was never persistence. It was whether I had any relationship in that company that did not depend on the person who left.

Why does one champion make a deal fragile?

Because a champion is not just an advocate, they are your only source of information. When they go, you lose the advocacy and you also lose the map. You no longer know who else cared, what the internal objection was, or how the budget was framed to the person who approves it.

HubSpot's documentation for its buying groups feature names this risk plainly. It says the buying group org chart is there to help you understand each buyer's role, identify missing connections and weak relationships before they become roadblocks, and understand how contacts are engaging with your team. Missing connections and weak relationships is exactly what a single-threaded deal is made of.

The quiet part is that a strong champion hides the problem. When somebody inside the company is doing your selling for you, the deal feels healthy right up until it is not, because you never had to meet anybody else to make progress. Momentum and fragility look identical from the outside.

So I no longer treat an enthusiastic champion as good news on its own. It is good news plus a risk, and the risk is proportional to how much of the deal only exists in one person's head.

How do you know you are single-threaded?

Count the people who have replied to you. Not people who were copied, not names your champion mentioned. People who have written you a sentence or spoken on a call. If that number is one, you are single-threaded, whatever your notes say.

The second test is harder and more useful. Ask yourself whether you could describe the internal objection in the words of someone who is not your champion. If everything you know about the buying committee came through one narrator, you do not have information about the company, you have one person's account of it, and those diverge in predictable directions.

This is where a CRM earns its keep, and it is the reason HubSpot's guidance for founders names a CRM as one of the most important tools you will need, so that relationships are managed and nothing falls through the cracks. The specific thing you want recorded is not activity, it is who on the other side has actually engaged.

If you are doing this in HubSpot, the buying groups feature is designed for precisely this reading. Its documentation describes four ways to build the org chart: from a user-defined template, automatically with AI for companies with fewer than a hundred associated contacts, by hand, or through its assistant. The value is not the chart. It is that an empty chart is visible, and a single-threaded deal stops being invisible.

What does mapping the committee actually involve?

Names, roles, and what each person is afraid of. The first two are easy and almost useless on their own. The third is the part that lets you keep a deal alive when your main contact disappears.

HubSpot's own template structure points at the same idea. Its documentation says a buying group template lets you outline the roles and relationships of a typical buying committee, including personas, job titles, and the value propositions and pain points specific to those personas. Pain points per persona is the operative phrase, because a security reviewer and a finance approver are not blocked by the same thing.

My practical version is three columns and nothing more. Who they are, what they would have to explain to their own boss if this goes wrong, and whether I have ever heard from them directly. The middle column is the one that predicts behaviour, and it is the one nobody writes down.

Do this while the deal is healthy, because doing it after a champion leaves is archaeology. You will be reconstructing a committee from email headers and a memory of one call, and the reconstruction will be wrong in ways you cannot detect.

What do you say in the first week after they leave?

Nothing that asks for anything. Your first message should be short, addressed to the most senior person who has actually engaged with you, and should offer a summary rather than request a meeting.

The summary is the whole move. Write two paragraphs: what the company was trying to solve, and where the evaluation had reached. Send it with a line saying you wanted to make sure the context did not leave with the person who left. That is genuinely useful to whoever inherited the project, and it is useful whether or not they buy from you.

What it does for you is more subtle. It makes the deal legible to somebody who has not been in the conversation, and it puts your framing of the problem in front of them before an internal one hardens. It also tests whether anybody still cares, which is information you need in week one rather than week six.

Do not attach a proposal. Do not restate pricing. The moment your summary contains an ask, it becomes a sales email and it gets treated like one. Keep the ask out entirely, and let the reply tell you whether there is a deal here.

How do you rebuild without restarting?

Bring the new person the decisions, not the discovery. They do not need to answer the questions your champion already answered. They need to know what was decided, what was still open, and what the open items would cost them to leave unresolved.

The mistake is running discovery again from the top. It feels thorough and it signals that you were not paying attention the first time. Worse, it hands the new contact a reason to postpone, because a project that needs a fresh discovery call is a project that can wait until next quarter.

What you should redo is the part that genuinely depends on the person: their own stake in the outcome, their own risk, and what success would look like to them specifically. That is not repeating discovery, it is extending it, and the difference is obvious to the person on the other end.

Expect the timeline to move regardless and plan for it rather than fighting it. A deal that changes owners mid-cycle almost always slips, and a seller who pretends otherwise starts pressing at exactly the moment the new contact is least able to move. Reset the date in your own forecast honestly, which is also the version of events your CRM should hold.

What if the deal should actually die?

Then let it, quickly, and take the information with you. A champion leaving is a reasonable moment to find out that the project only ever existed because one person wanted it, and that is worth knowing rather than worth fighting.

The signal I watch for is whether anybody else can articulate the problem without prompting. If the new contact needs you to explain why this mattered, the answer is usually that it did not matter to the company, it mattered to a person, and that person is gone. Persistence there costs you months and buys nothing.

Closing it out cleanly is worth doing well. Say plainly that the timing looks wrong, leave the summary with them, and ask one question: what would have to change for this to come back. The answer to that question is the most honest qualification data you will get all quarter, and it costs you one email.

Then record the loss reason properly, in the words the buyer used rather than the words that make you feel better. Champion departed is a description of what happened. Nobody else owned the problem is the actual reason, and only one of those two teaches you something.

How do you stop this happening on the next deal?

Make a second relationship a requirement rather than a nice-to-have, and set the threshold early enough that it is easy. My rule is that before any proposal goes out, I need one substantive exchange with somebody other than my main contact. Not a copied email. A reply.

Ask your champion to make that introduction, and ask in a way that helps them. The framing that works is offering to do the internal work they would otherwise have to do themselves: I can walk your security reviewer through this directly so you do not have to relay it. That is a favour, not a request, and champions usually say yes.

Where tooling helps is in making the gap visible rather than in managing it. HubSpot's buying groups documentation frames the org chart around identifying missing connections and weak relationships before they become roadblocks, which is the right time to identify them. Note that its own page says the feature is available on its professional and enterprise tiers for its sales and service products, and that editing requires an assigned seat, so check what you actually have before planning around it.

If you have none of that, a text file works. The tool matters far less than the habit of asking, every week, whether this deal still depends on one person. That question is free and it is the entire practice. I use the same logic to decide who should own the demo, because both are questions about concentrating a deal in one human being.

What should you do next?

Open your three largest open deals and count, for each one, how many people on the buyer's side have replied to you with an actual sentence. Write the number down. Any deal sitting at one is your priority this week, regardless of how well it seems to be going.

Then pick the easiest second relationship in each and ask your champion for the introduction, framed as taking work off their plate. That is a fifteen minute task per deal and it is the highest-value fifteen minutes in your pipeline, because it converts a fragile deal into a merely difficult one. Keeping the record straight afterwards is where turning sales calls into CRM notes pays off, since the mapping only helps if it survives the call it came from.

If you are early enough that this feels premature, it is not, and your first ten customers are exactly where the habit is cheapest to build. If you want to talk through a deal that has just lost its champion, reach out. It is usually salvageable and the first week decides it.