How to Structure a Consulting Deck
A consulting deck has one job: to make an executive audience act on your recommendation. The firms that do this best follow a defining rule — lead with the answer — and a repeatable slide sequence built on the pyramid principle, action titles, and one idea per slide. Here is that structure, slide by slide, plus how to build it fast in Gixo Lumen.
The three rules that define a consulting deck
Answer first. Barbara Minto's pyramid principle is the backbone of every great consulting deck: state your recommendation up front, then support it with grouped, MECE arguments, then back those with evidence. Executives do not want a mystery novel that builds to a reveal — they want the conclusion, then the reasons. If a partner read only your executive summary, they should already know what you are recommending and why.
Action titles. Every slide's headline should state the takeaway as a full sentence — "Two accounts drive 60% of churn; concentrate retention there" — not a label like "Churn analysis." Read the titles top to bottom and they should tell the whole story on their own. This is the single biggest difference between an amateur deck and a firm-quality one.
One idea per slide. Each slide makes exactly one point, and the body proves the title. When a slide tries to say three things, the audience remembers none of them. The sequence below applies these rules from the cover through the appendix — adapt the number of slides per section to your engagement, but keep the order.
One more discipline separates firm-quality work: a consulting deck usually has to work in two modes at once. It has to support a live read-out, where you talk over lean slides and the room follows your voice, and it has to stand alone as a leave-behind — the document a sponsor forwards to people who were never in the room. Those two jobs pull in opposite directions, and the action title is what reconciles them. When every headline states its takeaway as a sentence, the argument survives without a presenter: a reader who only skims the titles still gets the whole story, while the live audience gets the detail beneath each one. Write the deck for the skim-reader first, and the presented version takes care of itself.
The consulting deck, slide by slide
Nine sections from framing to roadmap. Each is one to a few slides, with an action title.
Client, engagement, audience, and date, with a one-line statement of what this readout delivers. Orient the room on whose decision this informs and what stage of the engagement they are seeing. Keep it clean — the cover sets the tone for whether this reads as a credible, firm-quality document.
State your recommendation in the first content slide, with the two or three reasons that support it. This is the pyramid principle in practice: conclusion at the top, governing arguments beneath. A time-pressed executive should be able to act on this slide alone; everything that follows is proof for those who want it.
Frame why the client is here using the SCQA pattern — the stable situation, the complication that disrupted it, and therefore the question that must be answered. This builds shared context and earns agreement on the problem before you propose a solution. Done well, the audience is nodding before you reach a single finding.
State the central question the work answers and the boundaries of scope — what is in, what is out, and the success criteria. A crisp question keeps the deck disciplined and pre-empts the "but what about…" tangents. It also signals rigor: you defined the problem before you went looking for answers.
Show how you got to the answer: the framework, the MECE workstreams, the data sources, and the analyses run. Keep it to the logic, not the project plan. The point is to give the recommendation credibility — the audience should trust the answer because they trust the method behind it.
The evidence, one insight per slide, each with an action title that states the so-what. Resist the urge to dump every analysis — show the findings that drive the recommendation and move the rest to the appendix. Each chart exists to prove its title; if it does not, cut it.
Translate findings into a prioritized set of recommendations, each with its rationale and the trade-offs you considered. Sequence them by impact and feasibility so the client sees where to start. This is the heart of the deck — make the recommendations specific enough to act on, not platitudes.
A phased plan: workstreams, owners, milestones, dependencies, and the quick wins that build momentum in the first 90 days. Recommendations without a path to execution rarely survive contact with the organization. Showing the "how" and "when" is what turns a strategy deck into a mandate.
Quantify the expected value, the investment required, and the payback, then name the key risks and mitigations. Put the detailed models, methodology, and supporting analyses in an appendix so the core deck stays tight. The appendix is your credibility reserve — it answers the deep-dive question without cluttering the argument.
Common consulting-deck mistakes to avoid
- Building up to the answer. Saving the recommendation for the end is the most common error. Lead with it — this is not a thriller.
- Descriptive titles. "Revenue analysis" says nothing. The title must state the insight as a sentence.
- Framework theatre. A 2x2 or a five-force chart for its own sake adds no value. Use a framework only when it sharpens the argument.
- Data without a so-what. Every chart needs a conclusion. If you cannot write the action title, the slide does not belong.
- Recommendations with no roadmap. "What" without "how and when" rarely gets executed.
Build the consulting deck in Gixo Lumen
Lumen's consulting workflow shapes the deck around answer-first structure — so you spend your time on the thinking, not the formatting.
Keep decks grounded to source material and approved web research when needed. Gixo extracts key claims, highlights what needs verification, and surfaces citations, attribution, and trust status inside the deck viewer.
7 workflow profiles across consulting, finance, startup, sales, executive, product, and general business decks. The consulting workflow drafts the situation-to-recommendation arc above, not a generic slide template.
Build from a topic, notes, briefs, articles, and uploaded reference material. Bring your findings and Lumen drafts the framing, findings, and recommendation slides for you to sharpen.
Create a finished presentation in one workspace, with outline planning, workflow-specific structure, slide editing, citations, presenter tools, and export attached to the same deck.
present mode, speaker notes, timer, and shareable delivery. Export to PPTX, PDF, HTML, and slide images for the client read-out and the leave-behind.
Why consultants use Lumen for client-ready decks
The job is not to generate slides once. The job is to finish a deck you can actually present.
Workflow fit
The deck starts from a consulting, finance, fundraising, sales, executive, product, or general-business workflow instead of generic slide filler.
Outline first
Structure stays reviewable before full generation, so the first pass is shaped like a real deck instead of a prompt experiment.
Editability
Theme switches, layout swaps, slide edits, and regeneration all happen after the deck exists without forcing a rebuild.
Evidence
Evidence trust checks, citations, and fact-check details stay attached to the deck instead of being bolted on after generation.
Delivery
Speaker notes, present mode, shareable delivery, and exports stay on the same finished deck when it is time to ship.
From analysis to client-ready in four steps
Add your analysis, the question you answered, and your headline recommendation. Lumen uses it to draft the deck in answer-first order.
Get a draft with executive summary, situation, approach, findings, recommendations, and roadmap — in a clean, professional theme.
Sharpen each title into a takeaway, drop in your charts, and attach citations so claims are traceable for a skeptical client.
Present with speaker notes, then export the deck as the client leave-behind in the format they expect.