A draft that needs a person to fix it.
And it still doesn't sound like you.
Manifesto
Why we build it the way we do. Why pages, not paragraphs. Why a team of eight, not one clever prompt. Why the document stays itself instead of getting re-spat every time you ask for a change. The arguments, in order.
Why pages, not paragraphs
Most AI tools answer you in a wall of prose. You skim it, half-read it, lose the thread by paragraph three. The engine answers in pages — headings, sections, pull-quotes, the things that have made print readable for four hundred years. Your eye finds the shape before your brain finds the sentence.
There's real research under this — dual coding theory, the picture-superiority effect, the cognitive cost of unbroken prose. Structured, visual layouts get read. Walls of text get scanned and forgotten. We picked a side.
900 words. You'll read the first 80.
Same content. Read in twenty seconds.
The loop
A question, a rumour, a half-formed strategy, a board ask. Type it like you'd say it.
The engine already knows your business. It pushes back, sharpens, asks the questions a smart colleague would.
Not a wall of text — a structured page. Sections, headings, the visual scaffolding your eye is built for.
Throw it away, or promote it into core memory. The next conversation starts smarter than this one ended.
The arithmetic
A page costs about a dollar to make. It does the work of a senior team for half a day. The engine bills you for the page. The value sits in everything the page didn't make you do.
And it still doesn't sound like you.
For the price of a flat white.
The staff list
Every page is the output of eight minds working in sequence — researching, framing, costing, drafting, critiquing, rewriting. They each work in your voice, on your doctrine, against your knowledge.
Reads the prospect's site, filings, news. Returns the facts you'd want.
Frames the opportunity in your business's terms — not theirs.
Designs the solution shape — modules, sequence, scope, dependencies.
Builds the business case — value, cost, payback, who carries the risk.
Drafts every page in your voice, on your doctrine, line by line.
Generates brand-locked imagery — on your palette, in their world.
Reviews every draft against your Company Memory. Names what's weak.
Reads the whole thing end-to-end. Rewrites the parts that won't land.
One bill. One page. Eight people's worth of thinking.
The compounding
Every critique you write trains it. Every rule it learns applies to every future page. The dollar you pay in month twelve buys ten times the thinking the dollar in month one did — and the bill never moves.
Generic-ish. Sounds a bit like you. Useful from day one.
Voice locked. Doctrine sharp. The Critic catches what you used to catch.
Reads like your best architect on her best day. Every time.
Same bill. Sharper engine. Every page worth more than the last.
The whole workshop
Today a single page costs you a Claude tab for research, a ChatGPT tab for writing, a Gamma tab for slides, a PowerPoint window for the fixes, and a half-hour stitching it together. The engine does all of it, in one place, against one source of truth.
Stop relaying. Start running it once.
The living document
Ask ChatGPT for a change and it builds the document again from scratch — losing the bits you liked. The engine edits the page that's already in front of you. Same document. Sharper every pass.
"Tighten the second section." "Re-pitch this for a CFO." "Swap the hero image for something less corporate." It works on the page you're looking at — no export, no round-trip to PowerPoint.
Slides, longform docs, business cases — every solution is a live artefact, not a flat PDF. The bits you liked stay. The bits you didn't get rewritten. No version 47 in your downloads folder.
The fix you made today becomes a rule tomorrow. The Critic learns to catch it before you see it. The engine that drafts your next page already knows what you'd have changed about this one.
No PowerPoint. No re-spitting. No starting over.
A note from the workshop
"Scale the thinking of your best solutions architect — not the documents they happen to send."
— the reason this thing exists
Begin a session