The 47-Slide Demo
Four account executives at a customer-support software company present from a shared 47-slide deck organized by product module: ticketing, knowledge base, automation, reporting, integrations, then pricing. The demo is scheduled for 45 minutes with three people from a 120-seat support team: the support director (internal champion), a CFO, and an IT lead.
The champion has said her goals are to cut first response time from 14 hours to under 4 and to avoid hiring six additional agents this year. The CFO has asked twice, in writing, for 'cost per ticket impact.' The IT lead cares about SSO, data residency, and migration from the incumbent. The AE presenting is on slide 12 at minute 20 when the CFO says she has to leave early; the IT lead follows. The champion stays, asks few questions, and the deal goes quiet for a month.
1. Restructure the 45 minutes around the buyer's context. Give the agenda and say what happens to the 47 slides.
Read the worked answer
Agenda built backward from the three people in the room:
- 0-5 min: confirm goals and agenda. State the three outcomes - faster response without adding headcount, cost-per-ticket impact, and a migration and security path - and ask if anything is missing.
- 5-15 min: cost per ticket and the headcount case, while the CFO is present. Use the champion's numbers: ticket volume, handle time, current cost per agent, deflection assumptions.
- 15-30 min: tailored demo mapped to the champion's goals - automation and knowledge base shown specifically as response-time and deflection levers, not as modules.
- 30-38 min: IT's concerns - SSO, data residency, migration sequence and downtime.
- 38-45 min: next steps, owners, dates.
The 47 slides: the module walkthrough is retired as a presentation. Roughly 10-12 slides become the spine, each tied to a stated goal. Remaining module detail becomes an appendix used only if someone asks. The deck stops being the agenda; the buyer's goals become the agenda.
2. How should the AE handle the CFO's cost-per-ticket question, knowing the CFO may leave at minute 20?
Read the worked answer
Put it early and answer it with their numbers, not a slide of vendor claims.
Preparation: build a one-page model using the champion's figures - ticket volume, current handle time, loaded agent cost, and a conservative deflection range. Show cost per ticket today, cost per ticket at the target response time, and the headcount avoided. Label every assumption and give a range, not a single number.
In the room:
- Raise it in the first 15 minutes, before the CFO's attention window closes.
- Say plainly: 'Here is the model, here is what we assumed, here is what we need from you to tighten it.' CFOs trust stated assumptions more than confident single figures.
- Ask what threshold would make this a yes, and what else she would need to see. That captures her decision criteria even if she leaves.
- Do not defer to 'we'll send a business case later' - that is what produced the silence.
If the CFO leaves early anyway, the AE should book a short follow-up with her specifically on the business case, with the champion present.
3. What should be left behind after the meeting, and what next step should be proposed?
Read the worked answer
Leave behind a one-page mutual action plan, not the deck and not a brochure.
It should contain: the champion's two goals with current and target numbers, the cost-per-ticket model with assumptions flagged, the IT requirements (SSO, data residency, migration approach) marked as open or resolved, named owners for each item, target dates, and the decision criteria each stakeholder has stated.
The purpose is to make the deal legible to people who were not in the room and to expose disagreement early - especially the CFO's threshold and IT's migration concerns, since both left before the end.
Proposed next step: two short, specific sessions rather than another general demo - a 30-minute technical review with the IT lead on migration and SSO, and a 20-minute business-case review with the CFO and champion to validate the model's assumptions.
Then confirm both on the action plan with dates before ending the call. A stalled deal usually means no owned next step, not a bad product.