Design Pattern · September 2026

The Zero Neo reference architecture

Systems of record at the bottom, platform capabilities above them, AI orchestration above that, then workflows, then the mixed workforce, with observable outcomes at the top and purchased software entering only from the side.

Under the pillar Zero Neo

The layers

The architecture is deliberately plain. Its job is to make one thing obvious: where to start.

Start at the bottom with what is already owned, not at the side with what can be bought.

Reading it

At the bottom sit the systems of record and the owned platform: identity, mail, calendar, documents, and data. Above them, the platform capabilities: forms, lists and tables, workflow, messaging, meetings, search, files, approvals, and automation.

Above that sits the AI configuration and orchestration layer, which assembles those capabilities and keeps the assembly working. Above that, the business workflows themselves, then the mixed workforce of people, conventional automation, and AI. At the top, the only thing the business actually wanted: observable outcomes.

Specialized software enters from the side, at whatever layer it is genuinely needed, once a capability gap has been demonstrated. It is a legitimate part of the architecture. It is just not the starting point.

The two questions

Do not start with which application to buy. Start with what outcome is needed and what is already owned that could produce it.

Everything else in this pillar is an attempt to find out how often the second question has a good answer, and how quickly that is changing.

Put this to work

The Zero Neo reference architecture application record

Apply The Zero Neo reference architecture to a real piece of work and record what happened.

For: Technology, operations, finance, security, and procurement leaders.
What you keep: A the zero neo reference architecture application record you can review, revise, and send.
What counts as sound: Names a real setting
Shows the work before and after
Records exceptions
Uses an observable result
Ends with keep, revise, or stop

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.

The caseName the organization, setting, product, or piece of work without including confidential information.The decisionWhat must someone decide, and who owns that decision?Evidence in handList records, observations, measurements, rights, or prior work that can be checked.What is still unknownName missing evidence, disputed assumptions, and practical constraints.

Review the prompt

The Zero Neo reference architecture application record 1.0

PURPOSE
Apply The Zero Neo reference architecture to a real piece of work and record what happened.

CONTEXT
The case: Not provided
The decision: Not provided
Evidence in hand: Not provided
What is still unknown: Not provided

METHOD
1. Name the work and intended result.
2. Apply the pattern as written.
3. Record what changed and what did not.
4. List exceptions and unintended work.
5. Decide whether to keep, revise, or stop.

TASK
Use the method below to produce a The Zero Neo reference architecture application record.

RULES
Separate facts, inferences, assumptions, estimates, hypotheses, and unknowns. Do not invent evidence, performance, rights, customers, economics, or regulatory standing. Quote or link the source for material facts. State uncertainty. Name what would disprove the conclusion. End with the smallest credible test, an owner, a decision date, and a stop condition.

A SOUND ANSWER
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop

CAUTION
A lower license bill does not prove a lower total cost.

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.

Share an implementation Intellectual Frontiers on LinkedIn