Stop editing slides.
Get your time back.
In one live session, you stop hand-polishing decks and documents and start rendering them from a source you own. Change the argument, rebuild the deck. The hours you spend nudging boxes go back on your calendar.
Where the time actually goes.
Nobody edits a compiled binary by hand. You change the source and rebuild. Yet that is exactly what slide editing is: reaching into the rendered output and pushing boxes around, one at a time, while the argument underneath stays frozen.
The deck was never the artifact. The argument is. A slide is a render of it, and so is a proposal, a one-pager, a report. When every change is priced in slides instead of ideas, you stop revving the thinking. You walk into the meeting defending last quarter's reasoning because updating it costs a weekend.
02 · What you buildYour decks and documents, rendered from a source you own.
Two pieces, built live on a real deck of yours. The source file that holds the argument, and the render skill that turns it into finished slides and documents.
The Source File
One markdown file holds the argument: one heading per slide, speaker notes inline, the numbers in one place. It reads like an outline because it is one. This is the only thing you ever edit, and by the end of the session your next deck lives in it.
The Render Skill
A skill in Claude that turns that source into the finished deck or document, in your look, every time. Change a number, rerun, and every slide that touches it updates. Need a version for a different audience? You rebuild it in minutes, and both stay current.
One rule protects the whole system: never edit downstream of the source. Fix the source. Rebuild. Done.
Built hands on in Claude Desktop or Claude Code, on the Claude Pro subscription you likely already have. Results are great in both. Nothing to program, no API to wire up. If you can write an outline, you can do this.
What changes by the end of the session.
| Before | After |
|---|---|
| Every deck change means an evening of nudging boxes. | A change is one edit to the source file, then a rebuild. |
| The numbers live in nine places, and one is always stale. | The numbers live in one place, and every render carries the fresh ones. |
| A second version for a different audience is a second project. | A second version is a rebuild. Two decks, minutes apart, both current. |
| The deck rots because updating it costs too much. | The deck rebuilds cheaply, so the thinking keeps revving. |
| Documents get the same treatment: hand-formatted, hand-fixed. | Proposals and one-pagers render from source, same as the deck. |
Block by block. You build the whole thing.
About 90 minutes, live, no filler. You leave with the system running on a real deck of yours.
| Block | What you build |
|---|---|
| Open | Why slide editing burns time: renders versus source, and the one rule that fixes it. |
| Move the argument | Take a real deck off your plate and pull its argument into a source file: headings, notes, numbers. |
| Build the render | Set up the render skill in Claude and generate your deck from source for the first time. |
| Change and rebuild | Move a number, cut a section, rebuild. Watch every slide follow one edit. |
| Documents too | Point the same pipeline at a document: a proposal, a one-pager, a report. |
| Make it yours | Tune the look, add a rule, break it and fix it, so you can run it alone. |
| Close | How to keep everything downstream of the source as the work evolves. |
The system in your hands, not a someday plan.
- A real deck of yours moved onto source and render, working in Claude.
- The render skill, in your look, yours to keep sculpting.
- The source template: one heading per slide, notes inline, numbers in one place.
- The same pipeline pointed at documents: proposals, one-pagers, reports.
- The templates to keep, plus the replay for as long as you're a member.
- The one rule that keeps it alive: never edit downstream of the source.
The point is the workflow. After this session, edits cost minutes, and the deck is always current.
06 · Why this lastsA rebuilt deck stays honest.
Hand-edited decks drift. The numbers age, the story lags the business, and presenting last month's deck quietly costs you. A rendered deck cannot drift far, because refreshing it is cheap enough to do the morning of the meeting.
We run our own decks this way. One investor deck went through eight versions in three weeks. Two complete 19-slide variants of it, one with acquisitions and one without, were rendered three minutes apart. Hand-editing cannot produce that. A source file can, any morning you need it.
Edit the argument. Render the deck. Ship.
You build the pipeline once, live, and every deck and document after that costs an edit and a rebuild.
Kent Langley. Founder, Founder OS.
Kent runs Founder OS, the skill-based operating system founder-operators install alongside Claude. He stopped hand-editing his own slides: his decks and investor documents render from source files, version after version, some minutes apart. This session installs the same pipeline on your machine, live, on a deck you actually use.
08 · RegisterGet your seat
One workshop. One session. You move a real deck onto source and render, live, and take the system home.
- Tuesday, September 29 · 10:00am to 12:00pm PDT · 90 minutes live
- Replay for as long as you're a member
- The source template and the render skill, built on a real deck of yours
- The same pipeline pointed at documents before you leave
Doors close Monday, September 28 at 11:59pm PDT.
Built for the operator who presents and sends the numbers.
This is for you if
- You present, pitch, or send documents that carry numbers, and the numbers keep moving.
- You have lost evenings to alignment, formatting, and version cleanup.
- You want to be shown how, build it yourself, then run it without help.
- You would rather own a pipeline than rent another slide tool.
- You want something working by the end of the session, on your own deck.
This is not for you if
- You want it done for you instead of built with you.
- You present once a year and never touch the deck again.
- You cannot give one focused session to build it live.
Questions operators ask.
Do I need to be technical?
No. There is nothing to program. If you can write an outline and follow a live screen share, you can build this. The source file reads like the notes you already make before a deck.
What do I need before we start?
A Claude account, Claude Pro recommended. Bring one real deck you present regularly, or a document you keep re-editing. We build on your material, in the room.
Will it match my look?
Yes. The render skill carries your fonts, colors, and layout. You set the look once, and every render after that comes out wearing it. You keep tuning it as you go.
Does this replace my slide tool?
You can keep presenting wherever you present now. The renders are clean HTML and PDF you can present directly or drop into your usual flow. What changes is where the edits happen.
What about documents?
Same pipeline, different render. A proposal, a one-pager, a report: each is a render of a source file. We point the system at one of yours before the session ends.
What if I miss the live session?
You get the replay for as long as you're a member, plus the templates, so you can build alongside the recording.
Is my material kept private?
Yes. You build in your own Claude, on your own files. Nothing you bring leaves your workspace unless you choose to share it.
What happens after the workshop?
You own it. The source template and the render skill are yours, and every deck or document you move onto them gets the same property: one edit, one rebuild, always current.
Stop editing slides. Get your time back.
Tuesday, September 29 · 10:00am to 12:00pm PDT · 90 minutes live · $100
Walk in with a deck that costs an evening per change. Walk out with one that rebuilds in minutes.