Ask your agent for an argument rather than a look, and build the deck as an HTML page long before you touch PowerPoint. Most decks come out mediocre because of the brief and not the tool, since "make me something beautiful" is a brief you cannot fail, which means you cannot succeed at it either.
My briefs open with a question that comes before all the others: what is the claim. A presentation is a sequence of claims leading to one place, and design is what walks the eye through them in the right order. Hand an agent "make it pretty" and it invents generic prettiness, hand it the claim each slide is making and it suddenly knows what to enlarge, what to push to the margins, and what to cut entirely.
The second piece is the format you work in. We build almost every deck as an HTML page, because it is the only format an agent can edit over and over cheaply: fixing a slide is a line in a file, not dragging a box around a canvas. Only at the end, if someone genuinely needs a PowerPoint file, do we export. The tools that generate a whole deck from a paragraph give you an impressive result in the first minute and start fighting you the moment you want to change one small detail, and in Hebrew that goes double, because text direction breaks fastest exactly there.
Our biggest gain came from something small: every deck the team produces carries an edit mode inside the browser, so Tom fixes a sentence himself without coming back to any agent. It sounds technical, and creatively it changed everything, because a small correction stopped being a request and became a two second action. (From what I see, it saved us more rounds than any design improvement we made that month.)
The practical step: before you ask for a single slide, give your agent two decks you admire and your brand colors, and ask first for the argument skeleton in plain lines, with no design. You approve the skeleton, and only then it builds. That order is the difference between a deck that looks good and a deck that also works. (And if your agent offers you a purple gradient, that is usually its way of hinting you did not give it enough material.)
A prompt, on the house
I am building a presentation, and I am starting from the argument rather than the design.
Topic: [topic]. Audience: [audience]. Goal: [what I want to happen at the end].
1. Before you design anything, give me a skeleton: one line per slide, and that line is the claim that slide is making. No design, no colors.
2. Flag where the argument jumps, repeats itself, or asks the audience to believe something I never established.
3. Wait for my approval on the skeleton.
After approval: build the deck as a single HTML page, using the colors and fonts I am attaching, one idea per slide.
Export to PowerPoint only if I ask, and only at the end.A good deck is built twice: once as an argument, once as a look, and in exactly that order.
