There is one sentence that runs under everything this studio builds: architecture removes a category of decisions from a person’s day.
Not one decision. A category of them: the kind that recurs, that has an answer someone could write down once, and that nevertheless lands on a person every day, because nobody did. This paper sets out what such a category looks like, what a system takes away, the decisions it must never take, and how a firm can find its own categories in a week.
01The Decisions That Recur
Look at a week inside a firm of any size and the same small decisions come back.
What do we post today? Who answers this request, and has anyone seen it? Which plugin is asking to be renewed, and what breaks if we let it lapse? Which page should a buyer land on for this question? Does the new deck match the brand, or the last deck? Where does the new service go on the site? Did last month’s change do anything?
None of these is hard. Each takes a few minutes and a little attention. Together they take the attention of the people the firm can least spare, every day, for years. They also have a cost that never appears in a budget: each small decision interrupts a larger one, and the larger one is the work the firm is actually paid for.
02The Cost of an Unwritten Rule
The cost of a recurring decision is larger than the minutes it takes. Research on how people switch between tasks has a name for part of it. In a study published in 2009, Sophie Leroy showed that when people move from one task to another before the first is finished, part of their attention stays behind with it, and their performance on the next task suffers. She called it attention residue. A small decision that arrives in the middle of real work does not cost five minutes; it costs five minutes and a share of whatever the person was doing before.
The second cost is inconsistency. A decision made fresh each time is made slightly differently each time. The deck takes the colours of the last deck rather than the brand’s. The new service lands on a page of its own in one month and inside another page the next. One enquiry is answered in an hour and another in a week, because nobody saw it. Each of these is small. Together they are what makes a firm look several sizes smaller than it is, to buyers and to the machines that read it.
The third cost is the one that compounds the wrong way. Every decision left to memory depends on the person who remembers it. When that person is away, busy or gone, the decision is made by whoever is nearest, or not at all.
03What the Architecture Takes Away
A system answers these once, in its structure, so that nobody has to answer them again.
- The schedule decides the posting. Every post has a name, a slot and a channel before it is made; it is booked on the platform’s own schedule and read back from the account. Nobody decides in the morning what to say that day.
- The form decides where a request goes. Each request is routed by product family, market or language, kept on the server before it is mailed, and sent only after a person’s own touch. Nobody sorts the inbox for spam, and no request is lost because a mail server failed.
- The engine decides the plumbing. The cache, the search data, the forms, the languages and the backups are built into the site, in the firm’s name. Nothing is licensed, so nothing has to be renewed.
- The structure decides which page answers. One question, one page, one fact stated plainly. Nobody argues about where a buyer should land.
- The record decides whether it worked. Every change is written with a date and a number it should move, and measured again against the same record. Nobody has to remember what was promised.
Each of these is a rule written once, in the place where the decision used to be made. The rule does not get tired, does not forget on a busy week, and does not need to be explained to the next person who joins.
04Where the Rules Live
A rule removes a decision only if it lives where the decision used to be made. In a firm’s presence, that place is almost always one of five.
| The decision | Where the rule is written | What it frees |
|---|---|---|
| What a new page looks like | The site’s modules: header, opening, services, story, journal, statement, enquiry, footer, on one grid | Every page is built from the same eight parts; nobody designs a page from nothing |
| Where a new offer appears | The entry type: services, programmes, workshops, papers | A new entry reaches the menu, the cards, the footer and the form by itself |
| When something goes out | The schedule: each piece with its date, booked ahead | Nobody decides in the morning what to publish |
| Who answers a request | The form’s routing: by product, market or language | Every request reaches its person, and none is lost |
| Whether a change worked | The record: dated predictions, archived sources | Nobody has to remember what was promised |
A rule kept anywhere else, in a document, a message or someone’s memory, is still a decision someone has to make. That is why the studio builds the rules into the site itself rather than writing a manual about them.
05A Practice That Runs Itself
The clearest small example is a site the studio built for Fulcrum Point, a practice that trains corporate teams in sustainability. Its offer is large for a practice: services, programmes and fifty-two workshops, each with its format, its audience and what it covers.
In most sites of that size, every new workshop is a small project. A page has to be designed, the menu edited, the cards on the home page updated, the footer list changed, the enquiry form given a new option, an outline written and exported as a PDF and attached. Each of those is a decision, and each is a chance to forget one.
On this site a workshop is an entry. When it is published, it appears in the menu, on the cards, in the footer and among the form’s choices by itself, and the site writes its outline as a PDF in the practice’s brand every time the entry is saved. The enquiry form sends only after a person’s own touch, asks how they found the practice, and keeps every enquiry on the site even when the mail fails. An illustrated guide in eight parts shows the practice how to change anything without asking anyone.
The practice decides what its workshops are. It no longer decides how they reach the site, because that category of decisions was removed when the site was built.
06This Site, as an Example
The studio’s own site is built on the same principle, which makes it the easiest example to check. When the studio publishes a paper, nobody decides where it should appear. It takes its place in the archive, on the page of every term it uses, among the related pieces of the papers that share its terms, and in the sitemap the search engines read. The first time it uses a term the studio has defined, the words link to the definition. Its charts carry their own numbers as tables. A paper dated ahead is saved as scheduled and publishes itself on its date, and everything around it updates when it does.
Each of those used to be a decision for someone, every time: update the archive, add the links, remember the sitemap, publish at the right hour. Written once into the structure, they stopped being decisions. What is left for people is the paper itself, which is the only part that ever needed a person. The same holds for the studio’s records: the sources behind every reading are exported and archived on a schedule, so the history a firm will want next year is kept before the search engines drop it, without anyone having to remember to do it.
07Architecture Compounds
The second half of the principle is that architecture compounds. A system built once is reused by every venture after it, and each reuse makes the next one cheaper and better.
The studio’s own portfolio shows it repeatedly. A system of reusable snippets, written to run a large reference network, became the cart-and-archive engine of a later venture. A way of building satellite sites for one firm became the subject sites of another. A page cache written for one network now runs under most of the sites the studio runs. An enquiry gate built to keep one form free of automated messages became the gate every form uses. A way of joining four search sources became the record every reading starts from.
None of these was planned as a product. Each was built to remove a category of decisions from one firm’s day, built well enough to be trusted, and then found to remove the same category everywhere else. That is the practical meaning of compounding: each new site costs less than the one before, not because the work is cheaper, but because most of its decisions were already made.
08Decisions That Must Stay with People
The principle has a limit, and the limit matters as much as the principle. Some decisions recur and should still never be written into a system, because writing them down once would make them wrong.
The position of a firm is one: who it is for, and what it says first. It changes with the market, and a system that repeated last year’s position would repeat it into irrelevance. The words to use and the words to avoid are another; they have to be chosen by people who hear the buyers. The order of the work is a third, set in a room with the people who decide. And the judgement of a finding, whether a number that moved means anything, is a fourth.
There is a simple test for telling the two kinds apart. A decision belongs to the system when its right answer is the same each time it comes up, and when a wrong answer is cheap to notice and to undo: where a page goes, when a post is published, who receives a request. It belongs to people when its right answer depends on the market, the buyer or the moment, or when a wrong answer is expensive and slow to see: what the firm says first, which market to enter, whether a finding is real. Most firms automate too little of the first kind and, once they start, too much of the second.
The studio learned the edge of this the hard way. Its own reference network was built with a great deal of automation, including the writing of its pages at very large scale, and in 2026 Google removed it for exactly that: pages produced in bulk. The part of the network that held its value afterwards was the part that had been decided by people, plain definitions with one job each. Since then the rule is short. Machines produce; people decide; and a system may multiply pages only from data a firm holds that nobody else has.
09How to Find the Category in Your Own Firm
A firm does not need a new site to start. It needs a week and a sheet of paper.
- Write down every small decision for one week. Not the large ones: the ones that take five minutes and come back. The list is always longer than expected.
- Mark the ones that recur with the same answer. Where to post, who answers, where a page goes, what the deck looks like. These are the category.
- Write the answer once, as a rule. In a sentence, the way you would explain it to a new colleague.
- Put the rule where the decision is made. In the site, the form, the template, the schedule, the report. A rule kept in a document is still a decision someone has to remember.
- Measure what came back. Count the decisions a week after, and the hours they used to take. The time returned is the return on the architecture.
Done once, it removes the first of them. Done as a habit, it changes what the firm’s principals spend their days on.
10What It Protects
The point of removing those decisions is not efficiency for its own sake. It is the work that only people can do: the conversation in the room, the decision on the floor, the relationship that takes years to build. When the system holds, the principals of a firm get their attention back for that work. The architecture exists to protect that time.
The studio is built the same way. Its production runs on systems built once and reused: publishing, records, reports, images, translations and documents. That is what lets it carry the work of a much larger firm without the layers of hand-offs a larger firm needs: the people who have the first conversation are the people who decide, and the production behind them runs by itself. AI speeds up the production. It does not decide anything.
11At the Size of a Network
The largest form of this is a System: a main site and a satellite site for each market or question, on one engine, run on a clock written into the agreement: day 30, day 60, day 90, month six. One codebase, one cache, one form: a fix once is a fix everywhere. The channels run on their schedule. One report a month says what each site did.
A director who owns one never decides again whether the sites match, whether the pieces went out, or what the content brought. The architecture has removed that category. What remains is the part of the work that was always theirs.
12Method and Sources
The principle is the founder’s own line, written in his aligned profile and on every surface of the studio.
Attention residue: Sophie Leroy, “Why is it so hard to do my work? The challenge of attention residue when switching between work tasks”, *Organizational Behavior and Human Decision Processes* 109 (2), 2009, pages 168 to 181; it received the Academy of Management’s best paper award in its division (University of Washington Bothell, faculty page of Sophie Leroy).
Fulcrum Point: the site the studio built in September 2026; its workshops, outlines, form and guide are described in the case A Practice, Set Up Once.
This site: its platform (terms, related pieces, the schedule, the archive) as built in October 2026.
The reference network and its removal by Google are set out in the paper Every Engine Keeps Its Own Record.
The portfolio’s systems are described without the ventures’ names.