Use Cases

Can Apollo build your board deck? Yes, it's company memory, rendered

A board deck isn't a writing task. It's your company's memory pulled into one view: the metrics, the narrative, and the honest list of what changed since last quarter.

ASR

Apollo Space Research

Apollo Space

· 10 min read

The night before the board meeting always looks the same. Someone has fourteen browser tabs open and a slide template that’s three quarters wrong. They’re copying a number out of one dashboard, a chart out of another, a sentence they wrote last quarter that they now have to figure out whether is still true. It’s eleven at night. The deck is due at nine. And the hardest slide, the one the board actually reads, is still blank, because it’s the one that asks: what changed, and why?

We call that “building the deck.” It’s the wrong name. You’re not building anything. You’re remembering, by hand, under deadline.

A board deck isn’t a writing task. It’s your company’s memory, rendered into one view. That sentence is the whole post, and it’s also the reason the night-before scramble exists: the memory is real, it’s just scattered across ten tools, and assembling it is a job nobody designed for a human to do well at eleven at night.

What a board deck actually is, under the slides

Strip away the template and a board deck is doing three concrete jobs, every quarter, no matter what business you’re in.

It pulls the numbers, revenue, burn, pipeline, retention, headcount, whatever your board grades you on. It drafts the narrative, the paragraph that says what those numbers mean, what you bet on, what worked. And it flags what changed, the deltas since last quarter, the surprises, the thing you said you’d fix that you either fixed or didn’t.

Notice that none of those three jobs is making slides. The slides are the easy part, they’re a template. The hard part is that each job reaches into a different corner of the company, and the company has no single place where all three live. The number is in the finance tool. The narrative is in your head. The “what changed” is the difference between two states of the company three months apart, and nobody is holding both states at once.

So the deck feels like a writing problem and is actually a memory problem. You’re not slow at slides. You’re slow at remembering, accurately, completely, under a deadline, what a quarter of your company actually did.

Job one: pull the numbers, with their lineage

The naive way is the one you live in. You open each tool, you find the metric, you type it into a slide. Revenue from here, pipeline from there, retention from the spreadsheet someone maintains by hand. Twenty minutes of copy-paste, and at the end you have a slide of numbers you mostly trust.

Mostly is the problem. A number on a board slide has to be defensible, a board member will ask “is that net or gross?” and “does that include the deal that closed Friday?”, and the copy-paste version has no answer, because it severed the number from where it came from. You transcribed the digit and left the lineage behind. So the number is right until someone asks one question, and then you’re back in the tab, at eleven at night, in front of the board.

The better way is to never transcribe the number at all. Apollo is built so the metric arrives with its lineage attached, not “revenue: a certain figure,” but the figure and the query that produced it, the period it covers, the definition it used. The deck doesn’t quote the dashboard. It re-derives the number from the same source the dashboard reads, so the slide and the system can never disagree, and when the board asks “net or gross,” the answer is already underneath the slide.

The difference isn’t accuracy, your copy-paste was probably accurate. The difference is that a re-derived number can defend itself, and a transcribed one can only hope nobody asks.

Building a deck by hand means opening four tools and copying a number out of each into slides, the figures arrive stripped of their lineage. The company-brain way re-derives each metric from the same source the dashboards read, so every number on the slide carries the query, period, and definition that produced it.

Job two: draft the narrative the board actually reads

Here’s the slide that takes the longest and looks the shortest: the one paragraph that says what the quarter meant.

The naive version is you, at the keyboard, trying to remember a quarter. You scroll your own Slack. You reread three docs. You try to reconstruct why you made the call you made in week four, and whether the thing you promised in the last deck got done. The narrative is the highest-leverage part of the deck and you’re writing it from the worst possible source: your own tired memory of ninety days, at the end of a long one.

And memory under deadline doesn’t just forget, it flatters. The quarter you remember at eleven at night is smoother than the quarter that happened. The bet that didn’t pay off gets a softer verb. The thing you said you’d fix and didn’t quietly drops off the page. Not because you’re dishonest, but because the only record you’re drawing from is the one in your head, and that record edits itself in your favor.

Apollo drafts the narrative from a different source: the company’s actual record of the quarter. Not your memory of what happened, what happened. The decisions that got made, the work that shipped, the goals that were set and the ones that moved. Because the company brain wrote that record down as the quarter happened, the draft isn’t a reconstruction. It’s a reading. And a reading of the real record says the uncomfortable sentence the flattering memory skips, we said we’d ship this; we didn’t, which is exactly the sentence a board is there to hear.

You still edit it. You should. But you’re editing a true draft into your voice, not staring at a blank slide trying to remember a quarter you were too busy living to record.

And the draft can do something your memory can’t: cite itself. Every claim in it points back to the moment it came from, the decision logged in week four, the goal moved in week seven. So when you tighten a sentence, you’re not guessing whether it’s still true. You can see where it came from, the same way the numbers carry their lineage. The narrative and the metrics end up resting on the same foundation, which is the company’s record of itself, rather than two different acts of recall by the same tired person.

Job three: flag what changed since last quarter

This is the job the other two are secretly in service of, and it’s the one humans are worst at, because it isn’t about this quarter at all. It’s about the difference between this quarter and last.

The naive version requires holding two decks in your head at once: the one you’re writing and the one from three months ago. You’d have to remember every number you reported last time to notice which ones moved, every promise you made to notice which you kept, every risk you flagged to notice which came true. Nobody does this. So in practice the “what changed” slide gets written from scratch each quarter, as if the company started in March, and the most valuable thing a board can see, the trajectory, the kept-and-broken promises, the risk you called that landed, never makes it onto the page.

The cost is specific and it compounds. A board’s trust isn’t built on good numbers. It’s built on watching you call your shots and then report honestly against them. Miss that, quarter after quarter, and every meeting starts from zero, because you’ve trained the room that the deck is a snapshot, not a track record.

The reframe is the same one underneath the whole post. A delta is just memory with two timestamps. If the company brain remembers last quarter’s deck, not the slides, the claims, then “what changed” is a comparison, not a feat of recall. Apollo is built to hold both states: it reads the last deck’s numbers and the last deck’s promises, sets them beside this quarter’s, and surfaces the differences nobody had the working memory to spot. The metric that quietly reversed. The goal you set and met. The risk you flagged in March that’s now real and needs a slide of its own.

That’s the slide the board reads first. And it’s the one that’s blank at eleven at night, because it’s the one a human, working from memory, structurally cannot write.

The hand-built way writes 'what changed' from scratch each quarter, so the company appears to start over in March and the trajectory is lost. The memory-rendered way holds last quarter's claims beside this quarter's, and the delta, kept promises, reversed metrics, a risk that came true, surfaces by comparison.

Three jobs, one source

Put the three together and the pattern is the same one under every proactive feature worth building: the work is hard not because any step is hard, but because the inputs live in different places and nobody holds them at once.

The numbers live in the tools. The narrative lives in the record of what the company did. The deltas live in the gap between two quarters. Separately, they’re three scavenger hunts you run by hand the night before. Together, pulled from one company brain that’s been remembering the whole time, they’re a deck that assembles itself from the truth instead of from your recollection of it.

That’s why a board deck is a better test of an AI-native company OS than an investor update is. An update is a message; you can write a good one from a good memory and a calm hour. A deck is the whole company state, rendered, defended, and diffed against its own past, and you cannot fake that from memory, which is exactly why the night before is always a scramble.

The turn: what you’re really doing at eleven at night

Here’s the part that isn’t about slides.

When a founder spends the night before the board meeting assembling the deck by hand, the company is paying twice. Once for the hours, the most expensive person in the building doing copy-paste under fluorescent panic. And once, more quietly, for the version of the deck that comes out of a tired memory instead of the real record: a little smoother, a little kinder to the bets that missed, a little blind to the promise that dropped off the page. The scramble doesn’t just cost time. It costs honesty, in the exact room where honesty is the whole product.

A board deck isn’t a writing task. It’s your company’s memory, rendered into one view, and the reason that view is worth automating is not to save the night. It’s so the founder walks into the room having spent that night on the only thing the board actually hired them for: looking at the true state of the company and deciding what to do about it. Not remembering the quarter. Judging it.

That’s the trade. The assembly is the tax; the judgment is the job. When the deck builds itself from the company’s real memory, the founder stops being the person who reconstructs the quarter and gets to be the person who reads it clearly and calls the next one.


That’s what we’re building at Apollo Space, not a faster slide tool, but a company brain that remembers the quarter as it happens, so the board deck is a render of the truth instead of a reconstruction of it. If you’ve ever rebuilt your own track record from scratch at eleven at night, you already know the deck was never the problem. The forgetting was.

Apollo runs your company's repetitive ops so your team doesn't.

Join the waitlist for early access, founding-user pricing, and a front-row seat as we ship.

Join the waitlist