ONE IDEA, EVERY ROOM

Stop rebuilding the same
deck for every audience.

Deck Factory takes one idea, writes it once against a framework, and renders a deck for each audience you name. Same structure, language calibrated to the room. Change the idea and every rendition follows.

SIGN IN TO YOUR DECKS ASK FOR AN ACCOUNT

ACCESS IS BY INVITE WHILE WE ARE IN DEVELOPMENT · ASK AND YOU WILL GET ONE

THE IDEA Written once, under a framework THE BOARD THE ENGINEERS THE CUSTOMER THE INVESTOR THE STRUCTURE HOLDS · THE LANGUAGE MOVES
ONE IDEA · FOUR DECKS · EDIT THE IDEA, NOT THE FOUR

THE COST OF COPY, PASTE, REWRITE

The fifth version of a deck
is where the story breaks.

You do not have one deck. You have the board version, the engineering version, the customer version, and whichever one was open last. Each copy costs you the same three things.

COST · YOUR ATTENTION

You spend the thinking time on reformatting

The hour that should go to sharpening the argument goes to retitling slides and resizing a diagram for a different room. The idea gets whatever is left.

COST · THE DRIFT

The versions stop agreeing with each other

You fix a number in the board deck. The customer deck still has the old one. Nobody finds out in the meeting where it would have been harmless.

COST · THE NEXT EDIT

Every change costs four times what it should

One correction to the story means opening four files and hoping you remember all four. So the small improvements never get made and the deck slowly goes stale.

FOUR COPIES OF ONE IDEA · NO COPY KNOWS ABOUT THE OTHERS

WHAT YOU GET

One source of truth,
as many decks as rooms.

AUDIENCES

Name a room, get a deck for it

Add an audience and the idea is rendered again for that audience. The slide structure is the same one you approved; the language is pitched at the people who will be sitting there.

FRAMEWORK

A brief with a shape, not a blank slide

You fill in a brief under a framework rather than staring at an empty deck. StoryBrand is the default, and you can author your own if your team already has one it trusts.

REGENERATION

Fix the idea once and every version follows

Renditions are computed from the idea, so a correction to the canonical brief reaches all of them. There is no version of the deck that quietly keeps the old number.

OVERRIDES

Hand-edit a slide without cutting the cord

When one room needs a different chart, that edit is stored as an override on that rendition. It survives the next regeneration instead of being flattened by it.

REVIEW

Comments land on a slide, not in a thread

Reviewers leave threaded, resolvable comments anchored to the slide they are about, so feedback arrives attached to the thing it refers to.

SHARING

A stable link to publish, a revocable one to review

A published deck gets a clean permanent URL. A deck still in review gets a token link you can regenerate, which cuts off the old one.

WHY WE BUILT IT

We kept presenting
the same idea badly.

The idea was the same every time. The room was not. The board wanted the number, the engineers wanted the mechanism, the customer wanted what changes for them on Monday. So we wrote it four times, and the fourth one was always the worst.

Not because the fourth room mattered least, but because by then we were copy-editing instead of thinking, and the four copies had already started to disagree with each other about things we thought we had settled.

Deck Factory is the fix we wanted: say the thing once, properly, then let the tool recalibrate it per audience. It is the same idea in every room, told in the language of that room, and there is exactly one place to correct it.

The idea is the only source

Every deck is a computed derivation of the brief. There is no edit path that changes a rendition behind the idea's back.

Your manual edits survive a regenerate

Overrides are a structured layer, not a patch applied and forgotten, so recomputing a deck does not silently discard your work.

Your AI key is yours and encrypted at rest

Bring your own key. It is encrypted with AES-256-GCM, never logged, and never returned by any endpoint that reads it back.

A review link you can take back

Review URLs are tokens, not guesses. Regenerating one revokes the link you already sent without touching the published deck.

THE PLAN

Three steps from an idea
to a deck per audience.

No template to fight, no deck software to learn, no second copy to keep in sync.

STEP 01

Write the idea once

Fill in the brief under a framework, in your own words. This is the only place the argument lives, and the only place you will ever correct it.

STEP 02

Name the rooms you present to

Add an audience for each one. You get a deck per audience, built from the same structure with the language moved to fit who is listening.

STEP 03

Send it for review, then publish

Share a revocable token link while it is still moving. When it settles, publish it and the deck gets a permanent URL anyone can open.

SIGN IN AND START ASK FOR AN ACCOUNT

IN PLAIN TERMS

What Deck Factory
actually is

Deck Factory is a deck platform for people who present the same idea to different rooms. You write an idea as a brief under a framework, and the system materialises it as a deck: an ordered sequence of slides, each made of typed content blocks. Then you name your audiences, and each one gets its own rendition of that same deck.

The parts are kept separate on purpose. The idea is one thing, the deck rendered from it is another, the audience calibration is a third, and your hand edits are a fourth. That sounds like an implementation detail, and it is the reason a correction to the idea reaches every audience at once, while an override you made for one room stays put.

Renditions are computed, not typed. A deck is a pure function of the idea, your overrides, the format and the audience, and there is no edit path that bypasses that. It is what lets the system regenerate a deck without asking you whether it is safe, and what stops four copies of an argument from drifting apart.

The slide contents are a registry rather than a fixed list. Markdown, images, video embeds, code and Mermaid diagrams ship today, and a new block type is a registration rather than a database migration. Your deck is a readable structure you can export, not a proprietary blob.

Third-party API credentials are bring-your-own, encrypted with AES-256-GCM at rest, never logged and never returned from a read. Sharing is explicit: a published deck has a stable public URL, a deck in review has a token you can revoke, and everything else needs an account.

Write it once.
Present it everywhere.

If you have ever kept four versions of the same deck alive, you already know what this is for. Access is by invite while we are in development, and asking is the whole process.

SIGN IN TO YOUR DECKS ASK FOR AN ACCOUNT