Somebody on the other side of a deal is waiting for a proposal. What they want first is not a beautiful document. What they want is to stop waiting. A rough thing today changes a conversation. A polished thing in nine days arrives after the conversation moved on.
At Digitech that gap is where most of my week used to go. Research would be finished on Tuesday and the piece that carried it would go out the following Monday, because between those two points sat a deck, a design queue and three rounds of comments in a file nobody could open at the same time.
The first question is when
I started building those pieces as web pages, and the delay collapsed. Not because a web page is a clever format, but because it removed every step that was about production rather than about thinking. One file. No template to fight. No export step until the very end.
It is an odd thing to say out loud. The fastest way I have found to make a presentation is to not make a presentation.
A rough thing today changes a conversation. A polished thing in nine days arrives after it.
A report is not a deck
Once the format stopped being slides, the reports got better, and the reason is structural. A slide flattens. Everything on it has roughly the same weight, and anything that does not fit gets cut or pushed to an appendix nobody opens.
A page has real hierarchy, and it can hold depth without spending it on everyone.
Headings that are the argument. Read them alone and you have the summary. Nobody has to build a separate summary slide that drifts out of sync.
Detail on demand. The methodology, the caveats, the full table. Present in the file, folded away from the person who does not need it.
Sources attached to claims. A link sits next to the number it supports, in the same line, where it can be checked.
Tables that stay tables. Forty rows of account data live as forty rows, instead of being cropped into a screenshot of a spreadsheet.
One artifact, always current. There is no v3-final-final. The link is the document and the document is the link.
Showing beats describing
The strongest case for this is the mockup. Describing an idea to someone costs a page of writing and still leaves them imagining a different thing than you are. Showing them the thing costs about the same and ends the ambiguity.
A landing page, a campaign concept, the layout of a report we might build. In the old workflow that meant a designer, a queue and a week. Now the first version exists before the meeting, which changes what the meeting is for. It stops being about whether the idea is clear and becomes about whether the idea is right.
Sometimes those mockups become the real thing without a rewrite, which is a nice accident of the format. Most of the time they die, and they should. A thing that costs an afternoon is a thing you can throw away.
Notes, hierarchy, mind maps
The same format is where my notes live. A page is a good place to take them because it holds a hierarchy, links to its own sources, and grows without turning into a scroll of undifferentiated text.
Put a few months of those pages in one folder and something changes. That folder is a knowledge base, and a model reading it can generate instruments instead of summaries: a brief that already knows what was decided in March, a mind map of a topic with every source still attached, a comparison that assembles itself.
The closest reference most people have is one of the hosted notebook products that ingest your documents and answer questions about them. This is that, with one difference that matters to me. I decide the shape. What it emphasizes, what it hides, what it looks like, and where it lives.
The folder is worth more than any single page in it.
The export is the easy part
The objection is always the same. People want a file. Fine. Print to PDF and the page is a PDF, with the page breaks and the print styles set once and reused forever.
And when a different format is genuinely required, that conversion is now trivial in a way it never was before. HTML is the format models handle best, so going from a page to a deck, a doc or a set of slides is a request, not a project. The page is the source of truth and every other format is a render of it.
That ordering is the whole trick. For years the deck was the original and everything else was a degraded copy of it. Now the structured file is the original and the deck is one of its outputs.
Where this is the wrong tool
I want to be straight about the boundaries, because this is a working method and not a belief system.
Anything with real scale belongs in a system. APIs and proper integrations do this job completely and durably. If a report has to run every Monday for forty people, build the integration.
Live data wants a dashboard. A page is a snapshot. When the number has to be current at the moment someone looks, that is a different tool.
Collaborative editing is not this. If four people need to be typing in the same document, use the document.
A beautiful page still hides bad thinking. The models make polished output cheap, which means polish stopped being evidence of care. That is on me to check.
What is left after those exceptions is most of my actual week at Digitech: the proposals, the research, the briefs, the internal explainers, the one-off analysis the team needs by Thursday. For all of that, this path gets there first.