A field report on the operational layer nobody is doing for the time-poor founder — and the builder who sells the role rather than the software, hands it over, and is writing the book about what that displaces.
Consider Monday at seven in the morning, as the founder actually meets it. Forty-seven emails arrived overnight, and there is no telling which three matter. The 09:30 needs preparing, and whatever was promised in the last meeting is scattered across sent items and three different apps. A client asked about contract amendments four days ago; the reply exists only as a weight behind the sternum. Four back-to-back meetings are coming, every one about to be walked into cold. The homepage this transmission is about keeps score in a storyboard: zero hours of admin done before the first meeting starts. Then the caption underneath lands the diagnosis: “Not because you are disorganised. Because nobody is doing the operational layer for you.”
The operational layer has a job title. Every founder knows the hire — the junior operations person who would prep meetings, triage the inbox, chase follow-ups, keep the CRM honest — and why it sits unfilled; the same site compresses the reasons into one line: the hire “you cannot find, afford, train or keep.” So the role is absorbed by the most expensive person in the company. The market’s answer is a drawer of point tools — a scheduler, a triage plugin, a note-taker, a drafting model — each solving its slice, none speaking to the rest. The founder becomes the integration layer: coordination work between the coordination tools.
This transmission is about the builder who filled the role for himself first — fifteen years of running operations poured into an AI that reads everything he works in, prepares his day, then does the work. Other founders asked for it, so he now hands the finished role over, one executive at a time. Readers will know the shape this series documents — decades of judgment, encoded into a system. This is the ninth time we have filed the story, and the first in which the operator is also writing the book about what such systems displace.
Chris — first names are policy here; he can introduce himself properly — has spent fifteen years in digital marketing and agency leadership, and the CV reads like one move practised at increasing altitude. He built a digital agency with offices in London and Manchester, ran it, and exited it. He co-founded Skills Hub, an EdTech platform now used by teachers across the UK, and designed the eight-capability framework behind its Human Skills Index. His own summary of that chapter is the tell: “I built it, I ran it, I handed it on.”
The judgment was earned operationally, and he is precise about that: “Everything I know about AI, I learned by building with it under real operational pressure.” Not a lab, not a keynote — four businesses run simultaneously with AI wired through their operations, one of them, for the avoidance of Silicon Valley romance, an actual car garage in Hampshire. He delivered the Raleigh Lecture on AI and the future of work, and is a Liveryman and Chair of the Communications Committee at the Worshipful Company of Entrepreneurs, the City livery company of founders and investors. His advisory page condenses it into a line no consultancy deck would dare: “I know the room you are in.”
And then there is the book. The Next Rung, on AI and the knowledge economy to 2040, is publishing early 2027 with Practical Inspiration Publishing. Its author’s profile states the position in full: “Building the AI that displaces knowledge workers. Writing the book about it.” He does not flinch: “I’m openly complicit in this. I build the tools that displace knowledge workers and I write about that displacement honestly.” Nine systems profiled in this series automate somebody’s working day; Chris is the first subject publishing the disclosure himself.
Orca is the main thing, and its origin is the series’ own: he built it for himself first, because nothing available did what he needed. Every tool he tried required him to change how he worked to fit the software; so he connected the actual systems instead — Microsoft 365, meeting transcription, contact intelligence, CRM, task management — into one orchestration layer. His homepage leads with three words that double as a market correction — “An actual agent.” — and draws the line just as tersely: “An AI that talks. An agent that works.” Chat boxes wait to be asked. Orca picks the day’s three priorities before its owner sits down, preps each meeting with relationship history attached, drafts follow-ups in the owner’s voice, triages the inbox — and pauses for sign-off before anything leaves the building.
The commercial design inverts the SaaS playbook. Each instance is built, configured and maintained by Chris personally, and distributed through Microsoft service providers and IT services partners rather than a self-serve funnel. “Not a product you learn. A role you hand over.” The client gets not an onboarding sequence but a working member of staff who happens to be software. And the upkeep is no abstraction: “I wrote the integrations. I own the infrastructure. I maintain it every week. When something breaks, I fix it. When a client’s workflow changes, I reconfigure it. That is what a managed service means.” Alongside the flagship sit the bespoke builds — lead generation pipelines, diary booking, reporting automation — each, in his words, “not a template, not a SaaS retrofit,” but a system designed around how one particular business actually works.
The advisory practice runs on the same refusal to pad. One focused session, your operations on the table, honest output by the end — his page opens with the industry diagnosis (“Most businesses are using AI badly. Some are not using it at all. Both are a problem.”) and reserves its driest contempt for the consultant’s roadmap: potential use cases described, nothing built, nothing changed six months on. The session starts with operations, not AI, and the engagement is designed to shrink: build rapport, build the system, build the process, support adoption, step back. “Clients should need me less every quarter, not more.” The same instincts now advise Reakt, an AI platform rebuilding private credit and debt execution — but the sentence to keep is the one about being needed less.
Notice, for the ninth time in this series, the shape. In our last transmission, ten years of safety education became a curriculum with an honest grading rule. Here, fifteen years of operations became a colleague. The encoding is unusually literal: the judgment about which three emails matter, what the 09:30 needs, which silence has gone four days too long — lifted from the operator’s own habits and installed as infrastructure. The through-line has not moved an inch: find the gap between how a thing is done and how it should be done, and build the system that closes it. What is new is the candour about the other side of the ledger: the system that does the role is, unavoidably, the system that displaces the person who would have held it.
Strip away the AI and the rules travel to anyone encoding expertise into a product:
Build it for yourself first. A system built under your own operational pressure takes its spec from reality; one built from user interviews takes its spec from politeness. “Nothing available did what I needed” is where durable products come from.
Sell the role, not the software. Time-poor people do not want another tool to learn; they want the work done. Position the system as capacity — a hire, not an app — and the comparison stops being SaaS pricing and starts being a salary.
Own the maintenance. “When something breaks, I fix it” is the whole moat. Software that merely ships is a commodity; software that stays fitted to one business’s changing workflow is a role nobody casually churns out of.
Design the engagement to shrink. Needing you less every quarter is a strange promise with compound interest: it filters for clients who trust you. Dependency is a billing model, not a service.
Say the quiet part in print. If your product displaces work, the honest sentence about it is coming eventually — from you or about you. Publishing it yourself is both the ethical move and the credible one. Nobody trusts a keynote that claims nothing is lost.
What changes when the operational layer is finally staffed is measured in mornings. The 09:30 arrives pre-prepped, context attached. The four-day silence never happens, because the follow-up was drafted while the meeting was still ending. None of it is spectacular; it is just the junior operations hire, finally found, afforded, trained and kept — made of software, paused for sign-off, on duty before seven.
The displacement question does not go away; it goes into the book. The Next Rung asks what the knowledge economy stands on by 2040 — asked by someone building a piece of the answer with his own hands and declining to pretend otherwise. That is the position this publication finds worth documenting: not the evangelist’s claim that nothing will be lost, nor the pundit’s claim that everything will be, but the operator’s — here is what the machine now does, and here is the honest account of the difference.
So: if your Monday looks like the storyboard — forty-seven emails, four cold meetings, zero hours of margin — the system that staffs the operational layer is at simmance.ai, and the single honest session about where AI fits your business is a page away. The pattern of Chris’s career has held for fifteen years: build the thing, run the thing, hand the thing on, climb. The agency, handed on. The EdTech platform, handed on. The operational layer of his own days — and now of other founders’ — handed to a system he maintains personally. The book will say what all that handing-over does to the knowledge economy. But the pattern was set long before the book: every rung Chris has ever stood on, he has handed to somebody else on the way up. The only difference now is that the somebody is a something — and he is the one writing that down.
— END TRANSMISSION 05R
We publish roughly once a month. One email when it lands, if you ask for it.
Ask for the one email →