Pitch Deck Design Brief: Story, Evidence and Presentation
TL;DR
In this guide
- Define the decision. Name the audience and the specific next step you want.
- Shape the story. Select the information that supports the argument instead of importing an entire document.
- Plan delivery. A live presentation, emailed deck and editable sales tool have different needs.
A useful pitch deck design brief explains who will see the presentation, what decision they need to make and which evidence supports your argument. Agree the story before turning the content into slides.
At a glance
Three decisions behind a useful pitch deck
01
Audience and ask
Identify the decision maker, their questions and the action the deck should support.
02
Story and evidence
Build a clear argument using approved facts, relevant examples and a deliberate slide order.
03
Presentation and reuse
Agree the live, screen, PDF and editable versions, including who will update them.
Pitch deck or company profile?
A company profile introduces the business and its capabilities. A pitch deck develops a particular argument: why an opportunity matters, why an approach is suitable and what should happen next. It may support a sales meeting, partnership conversation, internal proposal or investment discussion.
Those audiences need different evidence. A prospective customer may want relevant work, scope and next steps; an internal team may need options and dependencies. Do not use a generic investor outline for every presentation. The company profile design guide covers the broader business introduction.
Write the story before designing the slides
Describe the presentation in a few plain sentences: the situation, the issue or opportunity, the proposed response, the supporting evidence and the request. If those sentences do not connect, more visual polish will not resolve the missing logic.
Then give each slide one useful job. A slide may establish context, explain an option, show a relevant example or make the next step clear. Its heading should communicate the point rather than label a vague topic such as “Solutions”. Separate the main argument from background information that can sit in an appendix.
A flexible slide outline
Use this as a starting point rather than a required slide count. Combine or expand sections according to the audience and the actual evidence.
- Context: Why this conversation matters to the audience.
- Need: The problem, task or opportunity being addressed.
- Approach: What you propose and how it relates to that need.
- Evidence: Relevant work, approved data or a clear demonstration.
- Practicalities: Scope, dependencies, responsibilities or options.
- Next step: The specific decision or action you are requesting.
Keep unverified projections and unfinished numbers marked for review. The designer should know which information is approved and who can validate the rest.
A worked presentation example
Fictional example: A consultancy is presenting a proposed website project to a client’s management team. The deck starts with the customer journey problem, shows the proposed page structure, explains the content and integration dependencies, and compares a complete first release with later enhancements.
A permitted project example demonstrates a relevant design approach. The final slide asks the client to confirm the scope and nominate a content owner. It does not invent a conversion increase or make a mockup appear to be a completed client result. This is a story example, not a Simply Graphic case study.
Design for the way the deck will be used
A speaker-led deck can use concise prompts because the presenter supplies the explanation. An emailed version often needs more context to stand on its own. Decide whether both are needed and keep their content coordinated.
Discuss screen size, meeting software, aspect ratio and PDF distribution before layout begins. If a sales team needs to edit the deck, agree the tool, master layouts, fonts and elements it can change. Do not assume a PDF will be an editable presentation or that every layout will work unchanged in another application.
Review the argument and the exported file
Review the story separately from spelling and visual consistency. Can a reader identify the point of each slide? Does every chart state its source, period and units? Are qualifications and important assumptions visible?
Then rehearse the actual presentation and check the exported version. Test links, page order, missing assets and readable text. Keep an approved version and remove older files from the routine sales handover. Changes to facts should go back to the responsible content owner rather than being introduced casually during design review.
Choose references that help the brief
When you browse presentation design work, explain what is relevant: information hierarchy, visual tone, a diagram approach or a clear evidence page. References should guide the discussion, not become a request to copy another business’s presentation.
If the identity also needs attention, start with the branding guide. Explore our profile and pitch deck design services with the story, approved content and required formats in mind.
Put it into practice
Prepare these inputs for a pitch deck
- Audience, meeting context and the decision requested.
- A working story and proposed slide order.
- Approved facts, data sources and project permissions.
- Current brand assets and relevant references.
- Required live, PDF and editable formats.
- Content owner, review process and delivery dependencies.
Keep in mind
One deck does not fit every audience
Reuse approved facts and visual assets, but adapt the story and level of detail to the actual reader. An investor discussion and a client sales meeting are different tasks.
Mistakes to avoid
- Starting slide design before agreeing the argument.
- Putting every detail on the main slides instead of using an appendix.
- Presenting unsupported projections or mockups as established results.
- Assuming print, PDF and editable versions require no additional planning.
Useful answers
Common questions
How many slides should the deck contain?
Enough to support the conversation without repeating the same point. Start with the story and available time, then decide what belongs in the main presentation and what belongs in the appendix.
Can you design from an existing presentation?
An existing deck is a useful input. Identify which content is current, which facts need checking and whether the task is a visual refresh or a restructuring of the story. Agree the required work in the brief.
Can the team edit it afterwards?
Specify the editing application, who will use it and which elements need to remain editable. Source files, fonts and templates should be included only as agreed in the scope.






