A consulting deck should be as many slides as the argument needs, and no more — length is a result of what you include, not a target you set in advance. One useful way to decide is to sort every candidate slide into three buckets: the body (slides that advance the argument and that the reader needs to follow your logic and reach the recommendation), the appendix (slides that defend the argument but don't move it forward), and the cut (slides that do neither). Decide those three things well and the slide count takes care of itself. A tool that structures a deck top-down, like Perceptis AI, can help you see which slides carry the argument and which are just support — but the decision rule below works regardless of how you build the deck.
Key takeaways
Slide count is an output, not an input. The right length is however many slides the argument requires; setting a number first leads to padding or cutting the wrong things.
The body advances the argument; the appendix defends it. If a slide is needed to follow the logic, it belongs in the body. If it only backs up a claim under scrutiny, it belongs in the appendix.
Cut anything that neither advances nor defends. Interesting is not the same as load-bearing; if a slide does neither job, it does not belong in the deck at all.
A tighter body tends to read as more focused. When fewer slides carry the argument, it's easier for the reader to see what you think matters most.
This guide is for consultants, strategy teams, and advisory professionals deciding what to put in a client- or board-facing deck — and, by extension, anyone building a business or executive presentation who has more material than the story needs. The same rule applies across the contexts consultants build for — a board or investment committee, a steering committee, a working session with the team — even though each calls for a different amount of detail. It answers the length question by giving you the decision rule that determines it, then works through the body, the appendix, and what to cut.
How many slides should a consulting deck be?
A consulting deck should be exactly as long as its argument requires — the number of slides is set by the logic, not chosen up front.
There is no correct slide count, because the count is downstream of the argument. A tight recommendation with three supporting points needs fewer slides than a complex diagnostic across five workstreams, and both can be exactly the right length. Starting from a target number ("keep it to fifteen") forces you to pad a short argument or amputate a long one, and both hurt the deck.
Context shifts the answer without changing the rule. A board or investment committee reading at altitude needs a shorter body than a working session with the team that has to act on the detail — but in each case the right length is still "as many slides as this audience needs to follow the argument and act on it." So the first question is never "how many slides?" It is "what is the argument, and what does this reader need to accept it?" Answer that, and the length is decided for you.
What belongs in the body versus the appendix?
A slide belongs in the body if it advances the argument, and in the appendix if it only defends a point that isn't in dispute yet.
This is the distinction that governs everything else. The body is the argument: the governing thought, the handful of points that support it, and the evidence each point needs to be believed the first time. If removing a slide breaks the logic — the reader can no longer get from the situation to the recommendation — that slide is body.
The appendix is the defense: the detailed model, the full data table, the methodology, the sensitivity analysis. This material matters, but it does not move the story forward. Its job is to be there when someone asks "how did you get that number?" — not to be walked through in sequence. The clean test: if the reader needs a slide to follow your argument, it belongs in the body; if it only matters when someone challenges a specific point, it belongs in the appendix.
Two failure modes come from getting this line wrong. Put appendix material in the body and the argument drowns in support the reader didn't ask for. Put body material in the appendix and the argument has a hole the reader has to fill themselves. Sorting honestly by "does this advance the story or only defend it?" avoids both. A practical way to build the appendix: anticipate where this audience is most likely to push — the assumption they'll distrust, the number that looks high, the option you rejected — and keep a slide ready for each, rather than treating the appendix as a place to store everything that didn't make the body.
What should you cut entirely?
Cut every slide that neither advances the argument nor defends it under scrutiny — being interesting is not enough to earn a place.
The hardest cuts are the good slides that don't belong. Analysis you're proud of, a chart that took a day to build, context that's genuinely interesting — none of it earns a place unless it advances the argument or defends a point someone will probe. If a slide does neither, it is not appendix material either; it is cut.
Ask of each candidate: what breaks if this is gone? If the honest answer is "nothing — the argument still stands and no likely question goes unanswered," remove it. Cutting is not a loss of rigor; it is what lets the rigor that remains be seen. A deck that includes everything communicates nothing in particular, because the reader can't tell what you think matters most.
How do you decide, slide by slide?
Run every candidate slide through one rule — advance, defend, or neither — and let that place it or remove it.
Name the argument first. Write the governing thought and the two-to-five points that support it in one line each, before you touch a slide. That line is the test everything else is measured against.
Sort each slide: advance, defend, or neither. Advances the argument → body. Only defends a point under likely challenge → appendix. Neither → cut.
Check the body reads on its own. Read the body's titles in order; they should tell the whole story without a single supporting slide. If they don't, something in the appendix is actually body.
Pressure-test the cuts. For each slide you dropped, confirm nothing in the argument breaks and no likely question goes unanswered. If something does, it wasn't a cut — move it back.
Right-size to the audience. Keep the body at the altitude this reader works at; push detail they don't need to follow the logic into backup.
How can AI help you build a tighter deck?
AI helps most when it structures the deck top-down, so the body-versus-appendix line is visible before you start cutting.
The decision rule in this guide is a thinking task, and no tool does the thinking for you. What a tool can do is make the structure visible: when a deck is built top-down — governing thought first, then the points that support it — it is far easier to see which slides advance the argument and which are only support, which is exactly the body-versus-appendix call.
This is the part of the job Perceptis AI is built for: it structures a deck around a top-down, MECE argument with insight-led action titles, and ties each claim to a traceable source, so the load-bearing slides and the supporting detail are distinct from the start. It is one tool among many ways to work, and the honest limitation is the same for all of them — the final call on what advances the argument, what defends it, and what to cut is yours, and a short human pass is always needed before the deck ships.
Frequently asked questions
How many slides should a presentation be?
A presentation should be as many slides as its argument requires and no more — there is no universally correct number. Set the length by the logic: include what the reader needs to follow the argument and reach the recommendation, hold what only defends it in an appendix, and cut the rest. A tighter body tends to read as more focused, because it's easier to see what you think matters most.
What is the difference between the body and the appendix of a deck?
The body contains the slides that advance the argument — the ones the reader needs to follow your logic — while the appendix contains slides that defend the argument, such as detailed models or full data, without moving the story forward. A quick test: if removing a slide breaks the logic, it is body; if it only answers a question that hasn't been asked yet, it is appendix.
Should you cut backup slides from a presentation?
Cut a slide entirely only if it neither advances the argument nor defends a point someone is likely to challenge. Genuine backup — material you can predict a client or board will probe — is worth keeping in the appendix, not cutting. The slides to remove are the ones that are merely interesting: they do neither job, so nothing breaks when they're gone.
How long is too long for a board deck?
A board deck is too long when the body includes slides the board doesn't need to follow the argument — detail that belongs in backup. Boards read at altitude, so the body should carry the recommendation and its core support, with the depth held in an appendix and surfaced only if asked. Length itself isn't the problem; misplaced detail is.
How do you decide what to include in a deck?
Decide by naming the argument first, then sorting every candidate slide into advance, defend, or neither: slides that advance the argument go in the body, slides that only defend it go in the appendix, and slides that do neither are cut. Then read the body's titles in order to confirm they tell the whole story on their own. A tool like Perceptis AI can help by structuring the deck top-down so the load-bearing slides are easy to spot, but the inclusion call is a judgment you make.
Does a longer deck look more thorough?
No — a longer deck usually looks less thorough, because padding hides the argument rather than strengthening it. Thoroughness shows in a tight body backed by a well-organized appendix you can turn to under questioning, not in a high slide count. What persuades is a reader being able to see exactly what you think matters and why.
