The first deck should probably be ugly

Two weeks on a font

A founder I talked to spent eleven days on her first deck before a single investor saw it. She picked a typeface, then a second one because the first felt cheap. She found a muted palette, aligned every icon to an 8-pixel grid, and animated the market-size slide so the bubbles grew on click. The deck looked like a Series B company's deck. It was beautiful.

Then she rehearsed it out loud for the first time and the whole thing fell apart in ninety seconds. The problem slide described a pain nobody had asked her to solve. The "how it works" slide was three sentences of nouns. When she got to traction she realized she had designed a slick container around a story she had never argued. The beauty had done something worse than waste time. It had let her feel finished before she had thought.

This is the trap of the first deck. You treat it like a sales asset, something to be made impressive, when at this stage it is a thinking tool, something to be made true. Design polish and narrative clarity feel like the same kind of progress. They are not. One makes the deck look done. The other makes the argument hold. And polish actively hides the gaps, because a clean slide reads as a finished thought even when the thought is missing.

Why the ugly version is more honest

A rough deck has nowhere to hide. When a slide is one sentence in the default font on a white background, the only thing on it is the claim. If the claim is weak, you see it immediately, because there is no design carrying it. You read "We help teams collaborate better" sitting alone on a slide and you feel the emptiness of it. Put that same sentence under a custom illustration with a soft gradient and your eye forgives it. The picture vouches for the words. That is exactly the favor you do not want this early.

Polishing first also inverts the order of the work. The expensive, irreversible decisions in a deck are about sequence and substance: which problem you lead with, what claim each slide has to earn, where the argument is load-bearing and where it is decoration. The cheap, reversible decisions are visual: font, color, spacing, icons. When you start with the visual layer you spend your freshest hours on the part that does not matter yet, and by the time you discover the story is wrong, you are emotionally attached to the version you spent two weeks making pretty. Founders rewrite words. They rarely throw out a beautiful deck.

There is a second cost that is easy to miss. A polished deck invites the wrong feedback. Show people a designed deck and they comment on the design. They tell you the green is nice, or the third slide is busy. Show them a deck that is plainly nine ugly slides with one claim each and they have nothing to react to except the argument. The ugliness is what forces the conversation you need.

What the first deck has to do

Strip away the idea that the deck is for investors and ask a narrower question: what does this artifact need to make you confront? A first deck has one job, which is to force you to make every load-bearing claim explicit and in order, so you can find the one that does not hold. Investors come later. Right now the deck is an argument you are running against yourself.

That reframes what a slide is. A slide is not a surface to fill. A slide is a question you have to answer in one breath. If you cannot answer the question on a slide cleanly, out loud, without the design helping you, that slide is not done, and no amount of layout will finish it. So build the deck as a list of questions first and answer them in plain text. The visual deck is a rendering of a story that already works. If you do it in the other order you are decorating a draft.

Before and after: one slide

Here is the kind of slide that two weeks of design produces, and what it looks like once you make it answer its question instead of look good.

Before (beautiful, empty). A full-bleed photo of a city at night. Centered over it, in a thin elegant font: "The future of work is here." A small animated logo in the corner. It looks like a keynote. It says nothing. The question this slide is supposed to answer, which is what specific, expensive problem exists today, is nowhere on it.

After (ugly, true). White background, default font, left-aligned: "Series A+ recruiters run 40+ open roles in spreadsheets and email. They lose 1 in 5 candidates to slow follow-up. The follow-up is slow because there is no shared status anyone trusts." No image. No animation. Three sentences. It is ugly and you cannot look away from whether it is true. If a recruiter would argue with it, you found that out in the time it took to read it, not after a designer rendered it.

The after slide is the one that does work. It names a buyer, a number, and a cause. It can be wrong, which means it can be tested, which means it can be fixed before you have built an hour of animation on top of it.

The artifact: a two-hour rough-deck sprint

You do not need design time to make a first deck. You need two focused hours and a constraint: nine slides, one question each, answered in plain text, no images, no color, no fonts. If a slide cannot answer its question in one or two clear sentences, that is the signal of where your story is actually weak. Mark it and move on. The gaps are the output.

Set a timer. Roughly ten minutes per slide leaves you twenty minutes at the end to read all nine aloud in sequence and hear where the argument breaks.

Rough-deck checklist: 9 slides, one question each

Rules for the sprint. Answer every question in plain sentences, not bullets of nouns. If you write a buzzword ("AI-powered," "next-generation," "seamless"), delete it and write what literally happens instead. If a slide needs a chart to be true, write the one sentence the chart would prove and move on; you can draw it later. When the timer ends, read all nine aloud as one story. The slide where you hesitate, hedge, or reach for adjectives is your weakest link. That slide, not the font, is what to fix first.

Run this sprint, fix the broken slides by changing the answers, and only then, once the nine plain answers hold together when spoken, open a design tool. By that point the deck is cheap to make beautiful, because there is finally something true to make beautiful.

Where RoundOS fits

The rough-deck sprint sharpens the story. It does not give you the raw material the story stands on. Slides 6 and 7, traction and market, are where founders stall, because the evidence is scattered across pilot emails, call notes, a half-updated metrics doc, and memory. You end up writing the proof slide from a vague sense of how things are going, which is exactly the kind of soft claim a rough deck is supposed to expose.

RoundOS pulls that context into one place. It connects the sources where your round and your traction already live, email, calendar, meeting notes, and your own uploaded numbers, so when you sit down to answer "what evidence exists that this is real," you are reading actual usage and actual conversations instead of guessing. The deck is still yours to argue. RoundOS makes sure the proof slide is built on what happened, not on what you hope happened.