Existing platform capability
The thing may already be there and switched off. Check before designing anything.
Operating Theory · September 2026
The Zero Neo principle
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
The proposition
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.
How the ladder is used in practice
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.
Configure what exists
Settings, templates, permissions, and structure, with no new code and no new vendor.
Connect existing capabilities
Wire owned pieces together so a record entered once is not entered again.
Let AI orchestrate
Have AI handle the sequencing, the drafting, the routing, and the watching.
Lightweight automation or code
A small script or flow, owned and documented, where the platform stops short.
Integrate systems of record
The record system stays authoritative. Nothing above it is allowed to become a second source of truth.
Another application
Justified in writing, with the gap named and the alternative rungs shown to have failed.
The burden of proof
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.
Put this to work
The Zero Neo principle challenge record
Test the claim behind The Zero Neo principle against a real case and look for where it fails.
- For
- Technology, operations, finance, security, and procurement leaders.
- What you keep
- A the zero neo principle challenge record you can review, revise, and send.
- What counts as sound
- Makes the claim testable
- Includes contrary evidence
- Preserves competing explanations
- States uncertainty
- Names what would change the conclusion
A lower license bill does not prove a lower total cost.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.