Present so it lands
Outcomes
A presentation is not a recap
You already ran the discovery call. You know the gaps, you know what the prospect said mattered, and now you are back in front of them with a plan. The mistake at this stage is treating the presentation like a summary of everything you found. A summary is an audit, and nobody signs an audit. A presentation is four moves, always in the same order: show them you listened, tell them what changes, prove it is worth it, and ask.
Open with what you heard, not what you sell
Start the meeting with the specific things the prospect told you, not with your product. If a landscaping company's owner told you on the discovery call that half her quote requests never get a follow-up, that line opens the presentation:
"You told me last week that quote requests go cold if nobody follows up within a day. That's the first thing we built this plan around."
This is the insight move, and it does one job: it proves you were listening. A generic opener ("Here's what we do for businesses like yours") sounds like every rep before you. A specific callback sounds like a plan built for this prospect, because it is.
Say what changes, not what you install
Once they know you listened, tell them what changes for their business. Keep this at the level of outcomes, not features. "We'll set up automated follow-up on every quote request within one hour" is a deliverable. "We'll configure a CRM automation with a conditional trigger on lead status" is a feature tour, and feature tours are for the appendix, not the main pitch.
A useful test: if the sentence describes a click path, it belongs in the appendix. If it describes a change the owner will notice in their business, it belongs here.
Prove it is worth it before they have to ask
Every owner is running the same math in their head: will this pay for itself. Answer that before they ask instead of after:
"We'll track quote-to-close rate monthly, and I'll show you the before-and-after myself. If follow-up is really costing you jobs, you'll see it move within the first month."
Naming how you will measure it, and when you will show up with the number, turns "trust me" into a plan the owner can check.
Make the ask, out loud, in this section
Here is the part most reps flinch on: you have to actually ask for the business, and you have to do it here, not bury it in a follow-up email. After insights, deliverables, and value, say the plan and ask for the yes:
"That's the plan: automated follow-up, a monthly report on quote-to-close, and I'll be your point of contact the whole way. Can we get you started this week?"
Confidence here is not about volume, it is about not softening the ask into a question about whether you should be asking. You did the discovery, you built the plan around what they told you, and this is the moment it was all leading to.
Everything you are not sure about goes in the appendix
Not every capability belongs in the main story. If a feature might matter to this prospect but you are not certain, do not build the main pitch around a maybe, and do not cut it either. Put it in an appendix and mention that it is there:
"There's a webchat feature that might be a fit for you too. I've put a page on it at the back in case you want to look at it, but I didn't want to build our whole conversation around something you haven't seen yet."
This keeps the main pitch tight and confident, and it still lets a curious owner go looking without you guessing wrong about what they care about.
Take the plan you would present to your next prospect and write one sentence for each move: the insight you heard from them, the deliverable, how you will prove it worked, and the exact words you will use to ask. Say the ask out loud before the meeting. If it sounds like a question about whether you should ask, rewrite it.
What you now have
- A four-part structure that turns a discovery call into a decision: insight, deliverable, value, ask
- A test for what belongs in the main pitch versus the appendix: outcomes here, click paths and maybes there
- Three lines you can adapt word for word: the insight callback, the value proof, and the ask
- The habit of asking out loud, in the room, instead of hoping the follow-up email does it for you
Knowledge Check
Four quick questions on structure, what goes where, and making the ask.