Software should demand less attention.And leave more room for judgment.
I start at the outcome and work back to the system that produces it: what must never be probabilistic, who is accountable, what may leave the building. The code is the last decision, not the first.
Every decision teaches the system, so it asks less each month. Nobody is trained and nothing is rolled out. The work simply stops arriving.
We have been measuring software incorrectly.
For thirty years, more interaction has been treated as more value.
- Daily active users.
- Time in application.
- Feature adoption.
- Prompt count.
I think the better question is:
How often does it still need a person?
There is no front door.
The best software you have ever used still waits for you to open it. Shazam comes closest: you open it, it is already listening, and five seconds later you have your answer.
For consumer software that is the ceiling. For professional work it is the floor.
You do not open this. It opens you.
Work arrives through the channels that already exist. The system reads it, assembles it, and completes the deterministic parts in full.
Then it reaches you in the inbox, the thread, or the channel you were already working in, carrying one decision, everything required to make it, and nothing else.
No application to learn. No context to supply. No prompt to write.
It prepares and proves. It does not sign.
Every decision teaches it.
You are not filling in a form. You are not writing a prompt. You are ruling on a case.
The system keeps the case, the context, and the call you made. Its confidence grows where you have been consistent. Its questions narrow to where you have not.
Nobody runs a training project. The work is the training.
So it asks less every month.
Almost every product asks more of you the longer you own it. More features, more surface, more maintenance. This is the one property I want to get right, and it runs the other way.
Month one.It asks about most things, because it has learned almost nothing about how this organisation decides.
Month six.It asks about the exceptions. The routine has become settled practice.
Month twelve.It asks about the things that genuinely deserve a person, and handles the rest without mentioning it.
The ask decays. The accountability does not.
What that feels like.
You are in a conversation that matters, or thinking hard about something, or not working at all.
A message arrives where you already are. One decision. Everything you need to make it. Nothing else.
You decide, and you go back to what you were doing.
Fewer emails. Fewer bookings. Fewer meetings. Less documentation. Not because anyone launched anything.
This is not a faster tool. It is the absence of one.
Before anything is built.
The system is decided before it is built. I start at the outcome the organisation is accountable for and work back until I reach the first thing that has to exist. What survives that walk gets built. Nothing else does.
Almost everything that determines whether this works is not a coding decision. It is a decision about where liability sits.
The clock.Runs from the earliest event across every channel, not from the date printed on the document. The post arrives after the clock already started, and a register keyed to the document is confidently wrong.
The wall.Deterministic at the number, not at the draft. A person can review prose. Nobody can review a figure they did not compute.
The signature.Binds the exact artefact, not a summary of it. What was approved has to be what left the building.
Three decisions. Not one of them is code.
The decision everything follows from.
Language models are probabilistic. That makes them good at reading, classifying, extracting, and bounded drafting. It makes them the wrong authority for a number somebody is accountable for.
Work with me.
If your people spend their days on paperwork a system should have prepared, that is the work I want.
I am not selling a tool to add to your stack. I design the capability, build it inside the organisation, prove it against the work you already do, and then make myself unnecessary.
Start with one painful workflow.
Less attention demanded.
More room for judgment.