The Sales-to-Implementation Pre-Mortem
Thirty minutes at the sales-to-implementation handoff where the rep says out loud where they had to sell hardest. Implementation begins at the hard part instead of discovering it in week three.
One person in the room already has a clear read on where this implementation is most likely to struggle: the rep who closed it. A standard pre-mortem asks a whole team to imagine failure modes. This session asks the person closest to the deal to name the real ones directly, while they are still fresh.
Place the deal in one of three categories
We want deals closed, and we want the right deals closed. Before running the session, place the deal in one of three categories. Only the middle category is what this session is for; the definitions below keep them separate. If a deal could be read two ways, classify it into the more serious category and note why.
The third category is a coaching conversation for sales leadership, not a risk to plan around in this session. This session is not amnesty; if it turns into amnesty, it stops surfacing real risk.
What the salesperson brings
The rep writes answers to these before the session — written, not improvised. Most deals produce two or three real items. A deal that produces no real items is worth a second look — it may be a clean fit, or the prep may be incomplete.
- Where did you have to work hardest? What exactly did you say to move them?
- What do they believe today that isn't quite true — anything you didn't correct?
- Which of our commitments has a date attached, and who owns that date internally?
- Who in their org is still not sold? What's their objection, in their words?
- What did we agree to that we have never done before?
- What did you avoid demoing, and why?
- If this churns in month four, what will make you say "I knew it"?
- If the champion left tomorrow, what breaks?
Question seven tends to surface the most useful disclosures. If a rep can answer only one, make it that one.
Thirty minutes, after signature, before kickoff
Never inside the commercial handoff — that meeting has a customer in it. Four people, five at most, and one of them facilitates.
Frame
The facilitator restates the rules out loud, every single time: nothing here reaches a performance review, and nobody solves during the disclosure.
The disclosure
The rep walks their prepared answers. Implementation listens and takes notes. No fixing, no reassurance, no "that'll be fine."
Interrogate
Clarifying questions only. Who said it, in what words, how many times, and what did they accept in exchange.
Convert
Each disclosed item gets a severity tag, an owner, and a date. Anything without all three didn't make it out of the room.
Week one
Agree the single thing implementation leads with at kickoff — and the exact sentence they'll use to say it.
In the room
The rep who closed it. The implementation lead, plus whoever will actually do the work. One facilitator — implementation or CS leadership.
Not in the room
The rep's manager. The CRO. Anyone whose presence turns a disclosure into an evaluation. Revisit who's in the room only once the practice is well established and trusted — not before.
Tag each disclosed item once
Every disclosed item gets exactly one tag. The tag decides how much of the first thirty days it owns.
Watch
Raised once and dropped; no evidence it's currently blocking. Named owner, no plan, reviewed at the monthly check-in.
Active
A live concern the customer accepted a workaround for. Needs a written plan and a resolution inside the first thirty days.
Account-critical
The account does not survive this being wrong. It is the first sprint, and it is the only thing in the first sprint.
One account-critical item per deal is normal. Three, repeatedly, is a signal about the deal — or about the ICP — and it belongs in a different meeting. If an item sits between two tags, assign the higher one and note the reason.
From disclosure to plan
The output is a short list of moves implementation makes before the customer raises the issue. Three examples of the shape (hypothetical — illustrative, not case data):
| What was sold past | Surfaces as | The move, and who owns it |
|---|---|---|
| "Their ops lead thinks the migration costs her team forty hours. I said closer to ten with our help." | Week 2, the first time she opens the mapping sheet. | Do 60% of the mapping before kickoff and show her the half-finished sheet. Implementation lead · day 3 |
| "They asked about two-way billing sync. I said it's on the roadmap." | Month 2, first reconciliation. | Written interim process, plus a real date confirmed by product before kickoff. PM + rep · pre-kickoff |
| "The CFO never got comfortable with the seat model. The champion pushed it through." | Renewal, or the first true-up. | Month-one value recap with the CFO in the room, and the usage report she asked for, unprompted. CS lead · day 30 |
Keep selling while you implement
Implementation picks up the sale where the rep left it, and leads the first two weeks with the hardest item instead of the easiest. Say it to the customer in plain words: "I know the migration timeline was the sticking point. Here's what we've already done about it."
That sentence addresses an objection while it's still small. The alternative is waiting for it to surface on its own schedule — often the week the champion is away.
Get through the account-critical item and the rest of the implementation is far more straightforward. You are no longer working with a nervous buyer — you are working with a customer who watched you take their biggest worry seriously in week one and handle it. A customer who saw that tends to extend more goodwill on smaller issues afterward.
Implementation is where the customer decides whether the sale was true.
What leaders must guarantee
The session depends on a rep volunteering the least flattering version of their own win. Reps do that only when the room is safe, and that safety comes from guarantees leaders make and keep — four of them, made explicitly and kept without exception.
- Nothing disclosed here appears in a performance review, a deal audit, or a QBR slide.
- The rep is not the defendant. The facilitator interrupts blame in the moment, not afterwards.
- Compensation never moves because of a disclosure. Commission is settled at signature.
- The rep stays on the account until the account-critical item is retired, so a disclosure leads to shared ownership rather than a one-time admission.
The sales manager joins "just to listen." Disclosures get pasted into the CRM as risk fields. An implementer says "you shouldn't have sold that." A churn post-mortem quotes a pre-mortem note back at the rep who volunteered it. Any one of those, and reps stop disclosing candidly in that room — often for good.
How you know it's working
Four numbers, reviewed monthly. The first one tells you whether the room is safe; the rest tell you whether the practice is paying off.
Disclosure rate
Share of closed deals arriving with at least one real disclosed item. Set a target rate the team agrees on (a common starting default is a clear majority of deals). A rate well below that target usually means the room isn't safe, or the session has become a status update.
Implementation-stage churn
Accounts lost before first value, and how far into the process they were lost. This is the outcome the practice is designed to influence; track it to see whether the practice is paying off.
Account-critical retirement
Share of account-critical items closed inside thirty days, with the customer's own confirmation that it's closed.
Time to first value
The intent is to shorten this, because the team leads with the hardest item instead of the easiest. Track it to confirm.
Sales and implementation stop being two teams that hand things to each other. A rep who has been candid in that room and watched implementation act on it is more likely to trust them with the next deal.
What leaves the room
One page per deal, filled in during the Convert block. It lives with the implementation plan — never in the CRM, never in a deal review.