To brief an AI slide generator well, tell it who the audience is and what they must decide, state the conclusion you want the deck to land, specify the structure and length, point it at the source files your numbers must come from, and name the template and chart treatment you expect. Those five decisions are what separate a draft you edit from one you rebuild. This guide explains why each matters, shows the same deck briefed badly and briefed well, and ends with templates for the deck types advisory teams build most often.
Key takeaways
The brief is where the thinking happens. A generator cannot supply judgment you have not supplied yourself, so an underspecified brief produces a competent-looking summary instead of an argument.
Name the decision, not the topic. "A deck about our pricing analysis" produces a summary. "A deck that gets the client to approve option B" produces a case.
Attach the files rather than retyping the numbers. Your instructions set the angle; the attached material is what makes each figure checkable afterward.
Ask for structure in the language of structure. Action titles, MECE grouping, and a stated slide count are specific requests that a generator will otherwise guess at.
Iterate on the argument first, the slides second. Fixing the storyline after the formatting means doing the formatting twice.
Most people's experience of AI slide tools follows the same arc. The first draft arrives fast, looks polished, and says nothing. The titles are topic labels like "Market Overview." The structure is a list of subjects rather than a line of reasoning. The numbers are either missing or suspiciously round. The natural conclusion is that the tool is not capable of real work.
Sometimes that is true. More often the brief was a sentence long, and the tool did what any system does with an underspecified request: it fell back on the most statistically ordinary version of that deck. It had no way to know who the audience was, what they had to decide, or which of your numbers were load bearing, so it produced the average of every deck with that title. The quality of what comes back is bounded by the quality of what goes in, and the brief is the only place you control that.
Why a weak brief produces a generic deck
A generator fills every gap you leave, and it fills them with the most common pattern rather than the one your situation calls for.
It helps to understand what actually happens when you type "make me a deck about our Q3 results." The tool has to decide roughly forty things you did not specify: how many slides, what order, whether this is informational or persuasive, who is reading it, which metrics matter, what the takeaway is, whether to recommend anything, how formal to be, what the charts should show. Each of those gets resolved toward the most typical answer, because typical is the safest guess in the absence of information.
The result is a deck that is recognizably about your topic and useless for your meeting. It contains an agenda slide nobody asked for, a market overview that states what the audience already knows, and a closing slide reading "Thank you." None of those are failures of writing. They are the predictable output of a brief that specified a subject and nothing else.
This also explains why "make it more executive" rarely helps on the second pass. That instruction does not close any of the forty open decisions. It just asks for a different register on the same unspecified structure. The fix is to close the decisions that matter, which is what the six elements below do.
The six elements of a working brief
Audience and decision, the conclusion, the structure, the evidence, the format, and the constraints. Five sentences is usually enough to carry all six.
1. Audience and decision
Name who is in the room and what they are being asked to do. The same material becomes a different deck depending on the answer. A progress update for a steering committee that must approve additional budget leads with the ask and the justification. The same update for a committee that is merely being informed leads with status against plan. If you do not say which, the tool will write the informational version, because that is the more common one.
Weak: "A deck for the client."
Better: "A deck for the client's CFO and finance director, who must decide whether to fund phase two."
2. The conclusion
State in one sentence what you want the audience to believe or do by the end. This is the hardest element and the most valuable, because it is the one piece of judgment no tool can supply. If you cannot write that sentence, the deck is not ready to be generated, and generating it anyway just defers the thinking to a later, more expensive point.
Weak: "Cover the results of the pricing analysis."
Better: "The deck should land one conclusion: moving to value-based pricing on the top three SKUs recovers margin without material volume loss."
3. The structure
Give a slide count and a section order, and ask explicitly for the structural conventions you want. Two are worth naming every time.
Action titles. An action title is a full-sentence takeaway rather than a topic label. "Margin fell 4 points, driven by input costs" instead of "Margin Analysis." Most generators default to labels, so this has to be requested. It is also the single highest-leverage instruction in a brief, because a deck whose titles read in sequence as a coherent argument is already most of the way to being good.
MECE grouping. Mutually exclusive, collectively exhaustive. Asking for the supporting points to be MECE tells the tool to avoid overlapping categories and obvious gaps, which is the first thing a sharp reviewer probes.
Weak: "Make it well structured."
Better: "12 slides. Recommendation and ask on slide one, then three supporting sections, then risks. Full-sentence action titles throughout. Keep the supporting points MECE."
4. The evidence
Point at the files and say what must come from them. This is where briefs most often fail, and the failure is specific: a number typed into a prompt arrives on the slide with no origin, so three weeks later nobody can reconstruct where it came from. A number drawn from an attached model can be traced back to the cell it came from.
Attach the material rather than summarizing it. An Excel model, a Word memo, a PDF of research, and a prior deck are all more useful than your paraphrase of them, because the tool can work from the detail rather than your compression of it.
Add one more line that does disproportionate work: tell it what to do when the material runs out. "Flag anything the attached files do not cover rather than filling the gap." Without that instruction, a tool facing a missing input will often produce something plausible instead of telling you it is missing.
Weak: "Revenue grew about 12 percent."
Better: "All financials from the attached model. Cite the source for every figure. Flag anything the attached files do not cover rather than filling the gap."
5. The format
Name the template, ask for native editable charts rather than images, and specify the chart type wherever the chart carries the argument. This costs one sentence and saves a rebuild.
Chart type is worth a moment of thought, because the right form is usually determined by the message rather than the data. A movement from one period to another explained by several drivers is a waterfall. A comparison of composition across categories is a stacked bar or a Mekko. A schedule is a Gantt. Asking for the chart that fits the message is faster than regenerating when a pie chart arrives.
Weak: "Add some charts."
Better: "Our template. Native editable PowerPoint charts, not images. Build the margin movement as a waterfall broken out by the four largest drivers."
6. The constraints
Say what to leave out, how long, and what must not appear. Constraints outperform adjectives because they are checkable. "Make it concise" is unactionable; "no more than three bullets per slide, one point per slide" produces the thing you actually wanted and can be verified at a glance.
Useful constraints to keep in your back pocket: no agenda slide, no thank-you slide, no stock imagery, define any acronym on the slide where it first appears, keep each slide to one point.
A worked example
The same deck, briefed two ways.
The weak brief: "Create a presentation about our cost reduction project for the client."
What comes back is predictable: a title slide, an agenda, a background section explaining the client's own business to them, a list of initiatives with no sizing, a generic risks slide, and a thank-you. It is twelve slides, it is formatted competently, and it does not make an argument or ask for anything.
The strong brief: "Build a 12-slide cost reduction case for the client's CFO and COO, who must approve a 2.4 million dollar program. Open with the total opportunity and the ask, not with background. Build the savings as a native editable waterfall from the attached model, broken out by the four largest drivers. One slide per driver covering the initiative, the saving, and the implementation risk. Include phasing over 18 months. Full-sentence action titles. All figures from the attached model, cite the source on each slide, and flag anything the model does not cover. Our template, no agenda slide."
The difference is not length. It is that every one of the forty open decisions that mattered has been closed, and the tool now has both an argument to build and the material to ground it in.
How to iterate when the first draft is close
Fix the argument before the formatting, and change one thing at a time.
The instinct after a first draft is to start correcting slides. That is usually backwards, because restructuring afterward means redoing any formatting work you did in between. Work in this order:
Check the title sequence first. Read only the slide titles, in order. If they do not tell the story on their own, the structure is wrong and nothing below the titles is worth fixing yet.
Fix the structure in one instruction. "Reorder so the recommendation leads, and merge slides 4 and 5, which overlap." Structural edits are cheap at this stage and expensive later.
Then challenge the evidence. Pick the three numbers a reviewer would question and check each against its source. If a figure has no source, that is the problem to fix before polish.
Then formatting and charts. Only once the argument and evidence are settled.
Keep edits single-purpose. Asking for five changes in one instruction tends to produce three of them. One change per pass is faster in practice.
Brief templates you can adapt
Paste one in, replace the bracketed parts, attach the files it names.
Client proposal: "Build a 14-slide proposal for [client], who must decide whether to appoint us for [engagement]. Lead with our reading of their problem before any credentials. Use the attached RFP and our past project summaries, and cite the source file for every result I claim. Action titles throughout. Our template, editable charts, no agenda slide."
Case study deck: "Build a 6-slide case study from the attached project files for [engagement]. Structure as situation, approach, result. Every metric must trace to the attached results file and show its source on the slide. Build the outcome as a native editable waterfall. Our template."
Strategy recommendation: "Build a 15-slide recommendation for [client]'s executive committee, who must choose between [option A] and [option B]. Recommendation and ask on slide one. Structure the case MECE, then handle the main objection to [option A] explicitly. All figures from the attached model. Name the two assumptions that would change the answer."
Due diligence findings: "Build a 16-slide findings deck for [client]'s investment committee, who must decide whether to proceed with [target]. Lead with the recommendation and the three issues that would change it. Structure by workstream using the attached files. Every number must tie to the attached model. Flag anything the material does not cover."
Quarterly business review: "Build a 10-slide QBR for [client] covering [quarter]. Open with the headline result and what we are asking for next quarter, not with an agenda. Use the attached performance file for all metrics and show each against target. Explain the two largest variances rather than listing every KPI. Our template, editable charts."
Board or executive update: "Build an 8-slide board update for [client] on [program]. One slide on status against plan, then the three decisions the board needs to make, each with a recommendation. Figures from the attached tracker. One point per slide, maximum three bullets. Flag risks as risks rather than softening them."
Executive summary or one-pager: "Condense the attached deck into a single slide for [audience], who has five minutes. Lead with the recommendation and the ask. Include only the three figures that carry the argument, each with its source. Everything else goes or becomes an appendix reference. Our template."
If you would rather not write all of this
A well-briefed generic tool and a purpose-built one converge on similar output. The difference is how much of the brief you have to write yourself.
Everything above is a workaround for defaults. You specify action titles because the default is topic labels. You specify MECE grouping because the default is whatever categories come to hand. You ask for sources because the default is unattributed text. You name your template because the default is a house style. You attach the same firm material every time because nothing remembers it between decks.
Perceptis AI is built so those are the defaults rather than the requests. It structures decks top-down with MECE logic and insight-led action titles without being asked, ties each factual claim back to the file it came from with clickable links so a reviewer can open the source behind any figure, and generates a native editable PowerPoint into your own template with editable charts. Its Knowledge Base holds the material that recurs across every deck, including methodology, service descriptions, team bios, and standard language, so you stop re-attaching the same files and re-explaining the same context.
What that leaves you to write is the part only you can know: who the audience is, what they must decide, and what you want them to conclude. That is three sentences rather than twelve, and it is the part worth your time anyway. The case studies show the output on real engagements, and you can run a brief in the app to see how much of the first draft survives review.
Frequently asked questions
How do I brief an AI slide generator?
Cover six things: who the audience is and what they must decide, the single conclusion the deck should land, the slide count and section order, the files the evidence must come from, the template and chart treatment, and constraints such as bullets per slide. Five sentences usually carries all six, and it is the difference between a draft you edit and one you rebuild.
What should an AI presentation prompt include?
At minimum the decision the audience faces and the conclusion you want them to reach, since those two turn a summary into an argument. After that, structure and evidence matter most: state the slide count, ask for full-sentence action titles rather than topic labels, and point at the attached material each figure must come from.
Why does my AI deck come out generic?
Because an underspecified brief leaves dozens of decisions open, and each gets resolved toward the most typical answer. That is where the agenda slide, the background section the audience does not need, and the thank-you slide come from. Naming the audience, the decision, and the conclusion removes most of it in one step.
Should I upload files or just write a prompt?
Both, and they do different jobs. The prompt sets the angle and emphasis; the attached files make the numbers defensible. A figure typed into a prompt has no origin a reviewer can check later, while a figure drawn from an attached model can be traced back to it. Add the instruction to flag gaps rather than fill them, so a missing input surfaces instead of being written around.
How do I get AI to write action titles?
Ask for them by name and define the format in the brief: full-sentence takeaways rather than topic labels, for example "Margin fell 4 points, driven by input costs" instead of "Margin Analysis." Most tools default to labels. A useful check afterward is to read the titles in sequence; if they do not tell the story on their own, the structure needs fixing before anything else.
