Existing platform capability
The thing may already be there and switched off. Check before designing anything.
Operating Theory · September 2026
New business-operations software should be the last resort. Start with the capabilities already owned and move outward only when evidence shows a real gap.
Under the pillar Zero Neo
Begin with what the business already owns. Move outward one step at a time, and only when evidence shows the current step cannot produce the required outcome safely and economically.
This is not frugality for its own sake. Every application added to an environment brings an identity, a data store, a permission model, an integration surface, a training obligation, and a vendor relationship. Those costs are real whether or not anyone lists them.
A rung is not skipped because it looks tedious. It is skipped when someone can state, in a sentence a colleague could check, why it cannot produce the outcome.
The thing may already be there and switched off. Check before designing anything.
Settings, templates, permissions, and structure, with no new code and no new vendor.
Wire owned pieces together so a record entered once is not entered again.
Have AI handle the sequencing, the drafting, the routing, and the watching.
A small script or flow, owned and documented, where the platform stops short.
The record system stays authoritative. Nothing above it is allowed to become a second source of truth.
Justified in writing, with the gap named and the alternative rungs shown to have failed.
The old question is why we should not buy this. The Zero Neo question is why we cannot achieve the outcome with what we already own.
The reversal matters because it changes who has to do the work of thinking. Under the old question, the sceptic has to argue. Under this one, the proposer does, which is the right way round: the proposal is what alters the environment.