You Don't Need a Computer to Run a Company
By LumaVista Team
Anya runs a thirty-five-person strategy consultancy out of a converted warehouse in Stockholm. Last month she ran an experiment her COO begged her not to run. For one week, she didn’t open her inbox, the shared drive, or a single spreadsheet, and she didn’t write or read a document. If a thing needed doing, she’d talk to the firm’s substrate about it — the way you’d talk to a chief of staff who already knew everything.
By Thursday she expected the firm to be on fire. It wasn’t. Two partners hadn’t noticed. The pipeline review still happened — the substrate paged her at 9:14am Tuesday with three staffing trade-offs and her preferred answer for each, and she replied in under a minute. The QBR for the Mercer engagement got assembled without her touching a slide.
The things that broke were not what she had braced for. Three conversations — one with a junior who needed reassurance after a bad client call, one with her commercial director about a pricing call that depended on a gut read of the buyer, one with a partner about whether to fire a client. None of those should ever have been documents. They were conversations dressed up as documents because, until now, conversation didn’t scale and documents did.
If you read the previous piece, you saw why the cell stopped being the unit of business thought. The desktop stops being the unit of business work.
The inbox as OS
Your day, right now, is shaped by metaphors a small group of engineers settled on in 1984.
The inbox. The desktop. The folder. The file. The trash can. These were never supposed to be the work. They were visual scaffolding the original Macintosh team picked because the alternative — typing commands at a blinking cursor — was unusable for everyone who wasn’t a hobbyist. The desktop was a kindness. It was also a forty-year compromise.
Notice what’s underneath it. Every one of those metaphors assumes the same thing about you — that you are the one moving data around. You drag the file. You sort the inbox. You file the document. You hand the deliverable to the next person. The OS is built on the premise that the human is the routing layer.
That was correct in 1984. It’s correct in approximately zero professional services firms in 2026. Your associates aren’t paid to route things. Your COO isn’t paid to route things. You aren’t paid to route things. But your day is structured as if you were, because the tools you live inside still assume you are.
This is why your week feels like email triage with strategy work jammed into the gaps. The inbox isn’t a passive container — it’s a queue your firm fills so you, the routing layer, can decide where each item goes. Calendar invites are routing requests. Slack DMs are routing requests. Half the documents in your shared drive exist because someone needed to hand a thing off and the only handoff primitive your firm has is “put it where they can find it later.”
The desktop metaphor outlived its reason for existing about ten years ago. We hadn’t had anything to replace it with.
The new unit is a flow, not a document
A flow is what happens when deciding and moving stop being separate jobs.
Concretely — a flow is a sequence of steps, some deterministic and some judgment-bearing, that runs to completion without anyone dragging a file or forwarding an email. The trigger fires. The substrate gathers what’s needed. Specialized parts of the system do what they’re good at — searching, reconciling, drafting, weighing trade-offs. When a step needs human judgment, the flow pauses, asks the right person the smallest possible question, and resumes the moment they answer.
The flow is the substrate. The document is what falls out of a flow when one is genuinely needed — a client deliverable, a regulatory filing, something outside the firm has to read. Inside the firm, almost every document you generate today is packaging around a handoff the substrate could perform directly.
This is a deeper shift than it sounds. We’ve spent a decade convincing ourselves “automation” meant “the spreadsheet runs faster.” That was a misread. It’s about research workflows that run continuously, accumulate memory across runs, and write back into a knowledge base instead of producing one-off chats — and what that pattern looks like when you apply it to every recurring decision the firm makes.
Once flows are the substrate, the document tier collapses. The WIP report, the pipeline tracker, the staffing rota, the weekly status update, the partner-meeting deck — each exists because somebody needed to coordinate humans and a document was the cheapest way. Coordination artifacts that calcified into the org’s bloodstream because nobody had a better tool.
A flow replaces each without producing the document. The information still exists. It stops being a thing humans have to read, write, format, and circulate.
What flows replace
Walk through your firm and label each tool by the job it actually does.
The inbox is not for messages — it’s a coordination queue. People email you because they need a decision, an approval, an introduction, or a status update. None of those are messages. They’re flow steps dressed up as messages because email was the only universal tool. A flow carries every one of them without producing an email.
The shared drive is not for files — it’s a state machine pretending to be storage. Every document in /clients/Mercer/2026/Q2/ is the current state of something ongoing — states are filenames, transitions are humans manually saving new versions. A flow holds state directly. The drive is what state looks like when your only persistence primitive is “files in folders.”
The ticketing tool is not for tickets — it’s a queue with a UI bolted on. Jira, Linear, Asana, the homegrown thing your ops lead built — workflows expressed as cards because, once again, humans were the routing layer. If the routing layer changes, the board evaporates.
The status meeting is not a meeting — it’s a synchronization barrier. You have it Tuesdays at 10am because it’s the cheapest way to get five people aligned on what’s true right now. Flows are aligned continuously. Synchronization happens by default, not by calendar.
The spreadsheet you keep “just to track” is not tracking — it’s a manual cache. Somewhere in your firm there’s a Google Sheet your commercial director updates every Friday because the source-of-truth system doesn’t have the cut he needs. A senior, expensive professional re-keying numbers from one system into another to look at them differently. That spreadsheet is a flow waiting to happen.
Each of these was the cheapest available coordination primitive at the time. None of them is the work. They’re all forms the work had to take because there was no substrate that could hold the work directly.
What flows leave alone
Be careful here. The temptation when a new substrate arrives is to push it into territory where it doesn’t belong.
Flows do not replace the conversation that builds trust with a client. The thirty-second exchange where your senior partner reads the room and says we’ll eat this overrun, it’s the right thing for the relationship — that is the work, not coordination around the work. A substrate that tries to automate it has misunderstood what your firm is for.
Flows do not replace the strategy session — four senior people locked in a room arguing for two hours about whether to take the firm into a new vertical. The arguing is the deliverable. A system that synthesizes everyone’s positions and proposes a compromise misses the point — the partners are supposed to fight it out and emerge committed.
Flows do not replace the moment in front of the partner where you call it. The Mercer pricing call. The “do we fire this client” call. The “do we promote her this cycle” call. The data is incomplete by definition, taste matters more than analysis, and the act of committing is the value-add. The substrate can lay out the trade-offs. It shouldn’t make the call.
Here’s the test. If the activity is where your firm’s distinctive judgment lives — the thing clients actually pay for, the thing partners spent fifteen years learning — leave it alone. If it’s coordination overhead around that judgment, it belongs in a flow.
Most firms have the ratio backwards. The post-spreadsheet model is not “automate the judgment” — that’s the dystopian version everyone’s afraid of. It’s “evaporate the coordination, so the judgment is what’s left.”
The shift in your day
What does this actually look like? Take Anya’s Tuesday in her experiment week.
She wakes up. No inbox waiting. The substrate filtered overnight — coordination requests routed, status updates folded into the running picture of the firm, anything needing her judgment on a short list, ranked, with the substrate’s recommendation and the receipts attached.
At 9:14am she gets paged. Three staffing trade-offs for the week ahead, each with the substrate’s preferred answer and the second-order effects spelled out. If you pull Erik off the Mercer team, the Volvo engagement starts the week one senior short, but the Mercer close holds. She agrees with two answers, overrides the third with a one-line reason, and the substrate routes the decisions to the partners who need to know. Under two minutes.
Mid-morning, she’s actually doing the work — on a call with a prospective client about a transformation engagement. No laptop screen between them. The substrate is listening, cross-referencing the client’s public filings and the firm’s prior work in their sector. Invisible. It surfaces what matters after the call, not during.
In the afternoon she has the strategy session — whether to open a Berlin office. Four partners, two hours, no laptops. The substrate prepared a brief, but the partners do the arguing. When they decide, the substrate captures it, books follow-ups, and notifies the people who need to know. The decision is the artifact. The meeting notes are a side effect.
She does not look at her email. She does not open a spreadsheet. She does not review a dashboard.
This sounds like a fantasy because the substrate is genuinely new. It isn’t, because each piece is well-understood — research workflows with memory, deterministic gates around judgment-bearing steps, multi-agent coordination, audit trails written in code. What’s new is wiring them together into something that replaces the desktop as the place where work lives.
The title isn’t a stunt. You don’t need a computer to run a company. You need a substrate that runs the company, and a small number of humans — you, your partners, your operators — who decide what it’s for.
What to do now
- Pick the three documents your firm couldn’t survive without. Not “would prefer not to lose” — actually couldn’t run without. The WIP. The pipeline tracker. Whatever your version is.
- For each one, write down the job it does. Coordinate? Calculate? Memorialize a decision? Hold a number until next Tuesday? Most documents do exactly one of those four jobs and could be honest about it.
- For each job, ask whether the document is the right shape. Coordination is a flow. Calculation is a function. Memorialization is a record. “Hold a number until next Tuesday” is a cache. None need to be a document. All of them currently are, because documents were the only primitive your firm had.
- Pick one document this week. Retire it. Replace its job with a flow. Start small — the weekly status email, the meeting prep deck, the spreadsheet your director re-keys every Friday. Watch what happens to the time and attention that opens up.
- Notice who’s running your firm in the gap. When the document goes away, the coordination has to live somewhere — in a flow, or in a person’s head. If you can answer “where,” you’ve found the next thing the substrate should hold. If you can’t, you’ve found the next post in this series — the new org chart — and we’ll pick that thread up there.