If your team has a final-round pitch to an enterprise buyer next week, prepare on a seven-day countdown rather than one late rehearsal. Seven days out, call your champion and confirm who will be in the room, what they have to decide and who else is on the shortlist. Five days out, rebuild the agenda around that decision: two minutes confirming the goal, the business case in the buyer’s own numbers, then the implementation plan and its risks, finishing on a specific ask. Four days out, give every person one role and every likely objection one owner. Three days out, run a timed red-team rehearsal with colleagues playing each member of the buying committee. The day before, drill only the opening, the pricing answer and the hand-offs. On the day, warm up for an hour and change nothing. A final round is a risk decision, not a product demo, and the plan below is built for that.
This is the longer companion to the Friday pitch rehearsal countdown, which covers the last few days in more detail. Use this plan when you have a week and the meeting will decide the deal.
What changes in a final round
In a first meeting you are proving the product can do the job. By the final round the buyer already believes that, or you would not be on the shortlist. What they are deciding now is which vendor is least risky to choose, and the audience widens to match: the economic buyer, procurement, IT security and the person whose team will live with the decision are all in the room.
That changes what wins. Proof in the buyer’s own numbers beats a feature tour. A credible implementation plan beats a roadmap. A team that answers each question once, cleanly, beats a team with more senior people in it. Most of the week below is spent on those three things.
The countdown at a glance
| When | Job | Done when |
|---|---|---|
| 7 days out | Find out what the room must decide | A one-page brief names every attendee, the decision criteria and the shortlist |
| 5 days out | Rebuild the agenda around the decision | Every agenda section maps to a decision criterion |
| 4 days out | Give every person one job | Each attendee has a role; each likely objection has one owner |
| 3 days out | Red-team rehearsal | The team has run the full meeting once inside its time |
| 2 days out | Fix, then freeze | Three fixes made; the champion has confirmed the agenda |
| The day before | Drill the opening, pricing and hand-offs | Each moment repeated three times without notes |
| On the day | Warm up for an hour, then settle | Nobody is editing slides |
| The day after | Follow up within 24 hours | Mutual action plan sent with dates and owners |
Seven days out: find out what the room must decide
Call your champion. Do not start on slides until you have answers to five questions:
- Who will attend, and what does each person care about? Get names and roles, not just “the committee”.
- What will be decided, and when? In the meeting, or at a later session you will not attend?
- What are the evaluation criteria? Ask whether they are written down, and ask to see them.
- Who else is on the shortlist, and what did they do well? Champions often answer this if asked directly.
- What would make this an easy yes for the economic buyer?
Confirm the format too: how long, in person or on video, and whether a demo is expected. Then write a one-page brief listing every attendee, the question each is most likely to ask, the decision criteria and the one thing you will ask for at the end. Every later step works from this page.
Five days out: build the agenda around the decision
Rebuild the agenda from the brief rather than editing the deck you used in earlier rounds. For a 60-minute slot:
| Minutes | Section | What it must do |
|---|---|---|
| 0–2 | Confirm the goal | Say what the buyer needs to decide today and what you will ask for at the end |
| 2–20 | Business case | Their baseline, the change you expect, and proof from a comparable customer, in their numbers |
| 20–35 | Implementation and risk | The first 90 days, who is needed from their side, data migration, security review status, and what could go wrong |
| 35–50 | Questions | Real time for the committee; nothing planted |
| 50–60 | The ask | One specific next step with a date, and a draft mutual action plan |
Two rules keep it honest. Every section must map to a decision criterion on the brief; a slide that maps to none gets cut. And unless a demo was asked for, show at most one workflow, the one that answers the criterion the buyer is least sure about.
Four days out: give every person one job
Team pitches go wrong when two people answer the same question, or nobody does. Give every attendee one role:
- Lead. Opens, runs the clock and routes each question to its owner. Usually the account executive.
- Technical specialist. Owns security, integration and implementation questions, and nothing else.
- Executive sponsor. Two minutes and one commitment, such as a named escalation path or their personal involvement in the first 90 days. Not a second pitch.
- Timekeeper and note-taker. Tracks the agenda and writes down every question word for word, for the follow-up.
Then list the objections you expect — price against the other shortlisted vendor, implementation effort, switching risk, security, “why now” — and give each one a single owner. Everyone else stays quiet on that question. Anyone without a role should not attend.
Three days out: run a red-team rehearsal
Book 90 minutes and run the whole meeting once, timed, without stopping.
- Cast the committee. Brief a colleague to play each attendee, using the likely question from the brief. Have one of them play a sceptic who says “the other vendor showed us something similar — why are you different?”
- Interrupt at the two pressure points. Push back hard on pricing and on the implementation plan, because that is where the real committee will.
- Record it. Watch the opening, the pricing answer and the implementation section back as a team.
- Pick three fixes, not twenty. A long list of notes three days out produces a new pitch nobody has rehearsed.
For how to structure each practice block, see the 45-minute rehearsal session template.
Two days out: fix, then freeze
- Make the three fixes and rehearse only the sections that changed.
- Freeze the structure at the end of the day. After this, only wording changes.
- Send the agenda to your champion and ask them to confirm it. It gives them a chance to flag a missing topic while you can still add it.
- Prepare the backups: the deck saved offline and on a second laptop, the demo environment reset, and reference customers briefed in case the buyer calls them.
The day before: drill the moments
Do not run the whole meeting again. Drill the parts that decide how the room feels about the team:
- The opening two minutes, three times in a row, standing, without notes.
- The pricing answer, under 30 seconds, three times, with someone interrupting “that’s more than the other vendor”.
- The hand-offs, using the exact sentence each speaker says to pass to the next.
- The executive sponsor’s two minutes, once, timed.
Stop by mid-afternoon and add no new slides. The pitch rehearsal countdown has the full drill for this day.
On the day: 60 minutes, then 5
- 60 minutes before: run the opening once, timed. Say out loud who answers pricing, security and implementation questions. Check the screen share, the demo environment and the backup laptop. Then close the deck file.
- 5 minutes before: the lead says their first sentence aloud once, decides who to look at first, and everyone silences their phone.
The day after: follow up within 24 hours
The follow-up is part of the pitch, and the committee often compares vendors on it. Within 24 hours, send:
- A mutual action plan: the steps to a decision and a signed contract, with dates and owners on both sides.
- Written answers to every question you parked, taken from the note-taker’s list.
- Anything you promised in the room, even if small.
Then ask your champion how the meeting landed with each attendee, and who still has doubts.
If you only have three days
Compress, don’t skip. On the first day, make the champion call, rebuild the agenda and assign roles. On the second, run the red-team rehearsal and make your three fixes. On the third, drill the opening, the pricing answer and the hand-offs, and stop by mid-afternoon.
How to tell you are ready
Before the meeting you should be able to tick off six things: every attendee has a likely question and a named owner for the answer; every agenda section maps to a decision criterion; the implementation plan names first-90-day milestones and the buyer’s people involved; the team has run the full meeting once inside its time; the pricing answer is under 30 seconds and the same from everyone; and the ask names a specific next step with a date. If you rehearse with an AI buyer, watch composure and confidence at the pricing and implementation moments rather than an overall score. See sales rehearsal metrics for what to measure.