I showed someone an export from PitchShow last year. They opened it in PowerPoint. The chart built itself. The title flew in. The background pulsed. They looked at me and said: "How is that possible?"
I said: "We didn't take the shortcut."
They had no idea what I meant. Most people don't. But that shortcut — the one we refused — is the reason every competitor will eventually hit a wall they can't get past, no matter how much VC money they raise.
The shortcut everyone takes
Here's how 99% of AI presentation tools work under the hood: they design a slide, take a screenshot of it, and paste that screenshot into a PowerPoint shape. The PPTX they hand you is a folder full of PNG images with a .pptx file extension.
Open it in PowerPoint. Click on the "text." Nothing. Try to edit the "chart." Nothing. Try to resize the "logo." It just stretches like a JPEG from 2007.
And forget about animations. You can't animate a screenshot. The slide is dead the moment it leaves the AI's hands.
I get why they do it. It's fast. It's simple. Rendering a visual layout to an image is a solved problem. Writing structured document XML that PowerPoint understands? That's genuinely hard. So teams take the screenshot path, ship something that looks like it works, and move on.
We spent months on the XML path. We're still spending time on it. Some days it feels like we're doing something nobody asked for.
Then someone opens the file and the chart builds itself and they say "how is that possible" and I remember why.
Why we built slides as code
PitchShow generates every slide as a real, running piece of software. Not a design file. Not an image. Actual code — components with logic, data, and animations baked in.
This means when you look at a PitchShow slide in your browser, you're not looking at a picture of a slide. You're running a tiny application. The heading knows it's a heading. The bar chart knows it has three data points. The icon knows it's on the right side of the layout.
That semantic knowledge is everything. When we export to PowerPoint, we don't take a screenshot. We read the structure and translate it: this heading becomes a real text box, this chart becomes a real chart, this animation becomes a native PowerPoint entrance effect. Every element lands in the file as the thing it actually is.
The result: you open the PPTX and the slides animate. You click the revenue number and type a new one. You change the font on the title. Your colleague edits it on a plane with no internet. The deck works like a deck, not like a PDF that opens in PowerPoint.
The part that surprised us
We knew animated export would be a differentiator. What we didn't fully anticipate was how much the architecture would give us for free.
When your output is code, you can do things you simply cannot do with images:
You can click any element on a running slide and tell the AI to change it in plain language — Vibe Mode only works because the slide is live software. You can inspect what the AI generated, read the actual markup, understand every decision. You can hot-swap a completely different visual style without rebuilding anything, because styles are applied as a layer on top of the underlying structure.
None of that exists if you start from "render to image."
The decision we made about output format wasn't just a decision about PPTX export. It was a decision about what kind of product we were allowed to build. And we made it early, almost casually, without fully realizing it was going to define everything that came after.
What this means for the people who use it
Look — most people who use PitchShow don't care about any of this. They care that the presentation looked great and the client called the next morning. That's fine. That's the point.
But occasionally someone pushes it. They send the PPTX to a vendor who needs to add their logo. They export to a conference AV system that requires editable text. They hand it to a designer who wants to adjust the brand colors. And the file just... works. Like it was made in PowerPoint. Because it was actually built as a real document, not an elaborate screenshot.
That's the moment this matters. Not in the demo. In the moment after the demo, when real work is being done with the thing you made.