A sales presentation that tells a story and makes deciding easier
Organize the problem, proposition, evidence, and next step before designing your slides.
Key takeaways
- Start with the situation of the person you are presenting to.
- Connect every promise to evidence or a clearly identified example.
- Close with a specific decision and the information needed to make it.
A sales presentation should help someone understand a proposal and decide on a next step. If it simply collects everything you know about your business, the person will have to build the story themselves. Organize the argument first, then use design to make important relationships visible.
Define the decision you need to support
Write what the person should be able to decide at the end: request a proposal, agree to a session, or choose a scope. That decision determines what information is needed and which details can go in an appendix.
Also consider how the document will be consumed. A presentation accompanied by a conversation can be more concise than a file sent to be read without explanation. Do not automatically export the same slides for both uses.
Build a sequence of questions
Organize the story around questions: what situation are we addressing, what do we propose, how does it work, what supports it, and what comes next? Each slide should answer one main question and prepare the next.
Hypothetical example: a studio proposes organizing a store's identity. It can show the current inconsistency, explain the proposed system, demonstrate an example application, and describe the scope. The studio's history is useful if it builds relevant confidence, not because it must always open the presentation.
Choose evidence that matches the promise
If you promise ease of use, show how the deliverable is used. If you explain a process, show its stages and decisions. Do not use metrics without context or testimonials you cannot attribute correctly.
Distinguish delivered work, proposals, and hypothetical examples. A mockup can help visualize an idea, but it does not demonstrate a commercial result. The caption and explanation should make that distinction clear.
| Question | Content | Clarity check |
|---|---|---|
| What do we need to solve? | Situation and difficulty | The person recognizes the problem |
| What do you propose? | Approach and scope | They can explain the offer |
| Why trust it? | Relevant evidence | The evidence matches the promise |
| What comes next? | Action and owners | They know how to proceed |
Design hierarchy for reading and conversation
Use headings that express the slide's idea, not just section names. Keep few visual relationships per screen and reserve tables for comparisons that need columns. If the content requires tiny type, split or edit it.
Maintain typography, margins, and image treatment throughout the document. Allow variation when the function changes: visual evidence may occupy more space than a scope summary. Review the presentation on the intended device or projector.
Close with understandable scope and next steps
Explain what the proposal includes, what is needed from the client, and what is excluded if relevant to the decision. Name the next action and who will take it. “Thank you” may provide a visual ending, but it does not explain how to continue.
Before sending, ask another person to summarize the offer, evidence, and next step using only the document. Fix points that depend on information only you know. Save an identifiable version so subsequent conversations refer to the same scope.
Reorder your presentation before decorating it
- Write the decision you want to support.
- Assign one main question to each slide and remove repetition.
- Check evidence, scope, and next step with an outside reader.
Frequently asked questions
How many slides do I need?
Enough to answer the questions behind that decision in the available context. No number guarantees a good proposal. Prioritize understanding and remove content that does not help.
Should I open with the company's history?
Only if it provides necessary context for that audience. In other situations, it may be clearer to start with the problem and introduce experience when evidence is needed.
How do I adapt the version sent by email?
Add the context you would normally explain aloud, review links, and make sure scope and next steps are understandable without a call.
