Brand & Production
Presentation Design
We build the deck for your high-stakes meeting as an argument first, then design it and connect it to a template your team can reuse.
The problem
You walk into your most important meetings with slides stitched together that week, and the point you came to make gets lost.
Presentation problems get mistaken for aesthetic ones. In a weak deck, the argument is what's missing: what will the people in the room decide, what objection are they holding, what evidence would move them? Design applied before those answers exist just makes the confusion tidier.
The second mistake is asking one file to do two jobs. A deck you present and a document you email are different things. Force them together, and slides fill with text while the speaker starts reading from the screen.
You may recognize this
- Slide titles name a topic, such as 'Market Overview', instead of making a claim.
- The deck grows every meeting and nobody ever deletes anything.
- Each salesperson keeps a personal version with outdated figures.
- The template breaks the moment someone pastes in a slide.
How we work
Decision brief
We write down who decides, what they're being asked to do and what objections are on the table. Every later slide answers to this page.
Storyline and ghost deck
Action titles are sequenced before any design happens. Someone who reads only the titles should be able to follow the argument.
Visual system and data
We build the slide master, type scale and color rules, then redraw each chart as a native, editable object that carries one message.
Two versions
The presented version stays spare, a separate reading version carries the detail, and speaker notes get written.
Rehearsal and handover
We run timing and transitions with the speaker, then hand the slide library and template over to your team.
What we deliver
- Decision brief and storyline
- Editable deck in PowerPoint, Keynote or Google Slides
- Speaker notes
- Reading version and PDF
- Slide master and template
- Modular slide library
How we measure
- Decision or next step after the meeting: the real test of a presentation.
- Time to produce a client-ready deck: shows what the template gives back to the team.
- Template and library adoption: shows whether old versions have left circulation.
- Slide-level reading data on shared files: shows where a buyer stopped.
A technical briefing for a public-sector delegation
Illustrative scenario: An engineering firm serving public institutions will brief a senior delegation, and its current deck leads with methodology. The decision brief shows that the delegation mainly cares about risk and timeline. The storyline is rebuilt around those two questions, and technical detail moves to an appendix.
Common questions
We have a designer. Why bring you in?
Your designer may solve the visuals well. We focus on building the argument and telling the data story, and the two roles work well together.
Which software do you work in?
Whichever your team will edit in later: PowerPoint, Keynote or Google Slides. We won't hand over a file only a designer can open.
Can you just fix the visuals?
Yes, though if we see problems in the argument, we'll tell you first. The decision stays yours.
Before we work together, let's think together.
Requests are answered by the founder.