Use this as a working guide, not a passive read. Skim the sections, copy the frameworks, then connect the advice to a real role, interview, call, or account you are working on this week.
Start with a free resourceDownload the mutual action planNo signup required. Browse the free resource library
Put this guide to work
The Enterprise Playbook
$19 USD · One-time purchase · Downloadable PDF
Preview this playbookWhen your sales champion leaves mid-deal, first establish who now owns the business problem and which decisions still stand. A completed demo remains a completed demo; the departed person's support does not become the successor's approval. Your next job is a short requalification conversation, not a request to honor someone else's enthusiasm.
This guide focuses on an open sales opportunity. For an existing customer, coordinate with the account's customer-success owner before contacting anyone. The exercise and examples below are original and fictional. They are not a promise that a deal can be recovered.
Separate lost advocacy from lost evidence
GitLab's MEDDPPICC handbook distinguishes a champion's influence and internal advocacy from other qualification elements. That distinction matters here: knowing the product and supporting a purchase are different responsibilities. A friendly replacement contact is not automatically a champion.
Make three lists in your approved CRM or account workspace:
- Still evidenced: a documented workflow problem, completed evaluation results, or requirements confirmed by people who remain involved. Include the source and date.
- Needs reconfirmation: priority, funding route, sponsor support, decision criteria, and the target decision date.
- No longer owned: introductions, internal presentations, approvals, or follow-up tasks that belonged to the departing person.
Do not erase the history. Mark its limits. “Operations confirmed the reporting problem on October 8; current project owner not yet confirmed” is more useful than either “Everything is fine” or “The deal is dead.”
Ask for an authorized handover
If your contact is still working on the account and willing to help, ask who is taking responsibility and whether an introduction is appropriate. Give them an easy way to decline. Do not request internal documents they are no longer authorized to share, ask for personal contact details, or follow them to a new employer with the old company's information.
If they have already left, start with a remaining stakeholder you legitimately know. Confirm the change rather than relying on a rumor or an automated job-change alert. Avoid contacting a broad list of executives simply to find someone who will respond.
Fictional email to a known evaluation participant:
“Hi Morgan — we worked with you and Alex on the reporting evaluation. I understand ownership may be changing. The team had tested the export workflow, while approval and rollout timing were still open. Are you the right person to confirm whether the evaluation is continuing, or is there an appropriate project owner we should coordinate with? I can send a short factual summary if useful.”
This email asks for routing and permission. It does not imply a purchase commitment or blame the person who left. Respect a request to stop and follow your team's contact policy.
Reopen the decision, not the entire feature tour
Offer a short conversation with an agenda the new owner can change. Start by checking whether the problem remains theirs to solve. A successor may have different priorities, a revised budget, or no mandate to continue the evaluation.
- 1Ownership: “Which team owns this workflow now, and who decides whether to continue evaluating it?”
- 2Priority: “Is the original reporting problem still important relative to your other work?”
- 3Evidence: “Which previous findings are useful, and what would you need us to validate again?”
- 4Process: “Have the approval route, participants, or decision criteria changed?”
- 5Next action: “Would a summary, a specific retest, or a pause be the most useful next step?”
GitLab's opportunity guidance separately describes technical and business champion contributions. Use that as a reminder to ask about both evaluation evidence and the buying process; it is one company's process, not a universal scoring rule.
Work through a fictional decision reset
Example Software is evaluating a reporting tool. Alex, its operations manager, leaves after a successful export test. Morgan, an analyst who attended the test, remains. The old CRM entry says “Decision this month; Alex arranging finance review.”
Keep the test result with its scope: it showed the sample export worked. Remove the assumption that Alex will arrange finance review. Morgan confirms the problem still exists but cannot approve spending. Record Morgan as a knowledgeable participant, not a proven replacement champion or budget owner.
The useful next step is an agreed introduction to the new operations owner, with a brief that separates tested results from unapproved scope. If the owner wants a different workflow tested, agree on that question before booking another full demo. If the initiative is paused, record the pause and its stated reason. Do not offer a discount to solve an ownership problem.
Choose advance, pause, or close using evidence
Advance when a responsible owner confirms an active problem and agrees to a concrete next decision. Record what that decision requires and who participates. A meeting alone does not restore the previous forecast confidence.
Pause when the buyer confirms the project is on hold and identifies a legitimate review trigger. Use that trigger rather than inventing a weekly chase. Close according to your organization's rules when the initiative is canceled or no active evaluation can be established. Keep uncertainty visible while you investigate; do not manufacture a new close date to make the pipeline look tidy.
For the fictional example, an honest note is: “Export test completed. New operations owner pending. Finance review not scheduled. Next action: Morgan to confirm appropriate owner by the date we agreed. Timing unconfirmed.” Use the slipped close-date guide for the wider forecast discussion.
Practice before using the approach
Write a brief with five headings: current problem, evidence retained, assumptions reopened, ownership gaps, and agreed next decision. Use fictional names and data for practice. Have a willing colleague play a successor who does not share the former champion's priorities. Score whether you asked for their view before explaining your proposal.
The champion transition resource guide helps you decide whether this free exercise is sufficient or the existing Enterprise Playbook fits a broader account-planning gap. Once a new owner is confirmed, adapt the champion enablement brief and mutual action plan to the decisions they actually agree to.
Put this guide to work
The Enterprise Playbook
Plan complex accounts, align stakeholders, and guide evaluation through rollout.
$19 USD · One-time purchase · Downloadable PDF
Preview this playbookRead the sample and see what is included before you buy.
Need the broader set? Compare The Deal Execution Bundle for $39. Includes this book.