Open most sales decks and slide two is the company history. Slide three is the logo wall. Slide four is the mission. The buyer's problem shows up on slide eight, by which point the room has decided this is a pitch about you. The fix isn't better design. It's order: the buyer's situation first, your answer second, proof third, and nothing that doesn't serve one of those.
Here is the seven-slide structure behind our sales deck template, what goes on each slide, what to cut, and how to personalize a deck per deal without rebuilding it every time.
The seven slides
1. Cover
Their name in the title. “Faster claims for Fieldstone” not “Beacon Analytics: Company Overview.” Your logo small, theirs bigger if you can get it. The cover is a promise that the next six slides are about them.
2. Why we're here
One slide of context: what prompted this conversation, in the customer's terms. “You're opening a second site in Q1 and dispatch can't absorb it.” No company history. No founding story. If you've had a discovery call, this slide is a two-sentence summary of it. If you haven't, it's the reason you think you should have one.
3. Their problem
The situation as they described it. This is the slide that makes the room nod before you've pitched anything, and it's the one that gets cut most often in favour of “industry challenges.” Three points at most, each in words they used. The cost of the status quo, if you know it. If they haven't told you their problem yet, this slide is your best guess and you ask them to correct it out loud. Either way it goes before your solution.
4. Your approach
How you solve it, framed against their constraints. Capabilities appear only as answers to the problem on slide three, one for one. The full feature tour does not go here; it doesn't go anywhere. If there are capabilities you're proud of that don't answer a stated problem, they wait for a question.
5. Proof
One strong case study with numbers. A customer like them, an outcome they want. One is better than three: three case studies is a logo wall with captions. Choose for relevance over prestige, and make the number the headline of the slide.
6. What rollout looks like
Kickoff to live, with effort honestly stated. Deals stall on imagined implementation pain. This slide removes the imagination: how many weeks, who on their side does what, what the first milestone is. It's the least glamorous slide and the one that most often moves a deal from “interesting” to “when.”
7. Next steps
The specific ask, with a date attached. A pilot, a technical review, a proposal. “Questions?” is not a next step. “A 45-minute technical review with your IT lead next week, then a proposal by the 30th” is.
The optional slides, and when they earn a place
- Pricing. In a first-meeting deck, usually no: pricing without the value story anchors low. In a second-meeting deck for a buyer who's asked, yes, after proof and before rollout.
- Security and compliance. If IT is in the room, one slide, after rollout. If not, an appendix link.
- Team. Only if the people are the product (services, consulting). Then it goes after approach.
- About us. Last, if at all. One slide. The buyer will Google you anyway.
What to cut
- Company history. Founded in, headquartered in, backed by. Nobody has ever bought because of it.
- The logo wall as slide two. Proof belongs after the problem, and one relevant customer beats forty irrelevant ones.
- The mission statement. It's for your careers page.
- The full product tour. Every feature that doesn't answer slide three is a feature the buyer will wonder if they're paying for.
- The market-size slide. That's an investor deck. Different audience, different structure.
Deck, proposal, or one-pager?
These get confused, and the confusion produces forty-slide decks that are really proposals with page breaks.
- A sales deck supports a live conversation. It's presented, not read. Seven slides, few words, you do the talking.
- A proposal is read alone, by people who weren't in the room. It has the narrative the deck leaves out, and the pricing.
- A one-pager is the thing your champion forwards to their boss. One page, three numbers, one ask.
Considered deals usually need all three, in that order. Trying to make one document do all three jobs produces a document that does none.
Design without a designer
You don't need to be good at design. You need to be consistent. One layout system, three text sizes, one accent colour, your brand but quiet. The buyer notices inconsistency far more than they notice beauty: a deck assembled from four older decks reads as four people who didn't talk to each other. Pick one template and refuse to leave it.
Personalizing per deal without rebuilding
The reason most decks are generic is that personalizing them is expensive. Slides one through three and slide five are the ones that change per deal. Slides four, six, and seven mostly don't. So the real work per deal is: their name, their situation, their problem in their words, and the right case study. Everything else is stable.
That's a job AI does well when it has the right inputs, and badly when it doesn't. Given the CRM deal and the discovery call notes, it can write slides two and three in the buyer's language and choose the case study from your library that matches their segment. Given a prompt that says “make a sales deck for a logistics company,” it writes slide eight of every other deck. Veew takes the first approach: the deal is the brief, the seven slides above are the structure, and the output is a branded deck delivered as a trackable link with a matching PDF. We build it, so weigh that.
Sending it
Send the deck as a link after the meeting, not as an attachment. You'll see whether it was opened, which slides got the time, and whether it went to anyone new. A deck forwarded to three people you haven't met is a committee forming, and that's when the one-pager goes out. The structure is the easy part. Knowing what happened after you presented it is the rest.