The missing layer in your stack finally has a name

Draw your stack on a whiteboard and two layers appear without effort. At the bottom sit the systems of record: the CRM, the warehouse, the ERP, the consent store. At the top sit the systems of engagement: the channels, the portals, the campaign tools, the places where customers and partners actually show up.

Now ask where the work happens. Who approves the claim? Who routes the request? What happens when the file arrives on Monday instead of Friday? Which system knows that a programme changed scope last week and that three downstream teams need to act on it?

The honest answer, in most organisations, is a third layer that never makes it onto the whiteboard. It is made of spreadsheets, inboxes, shared drives, chased approvals and the memory of a handful of long-serving people. It coordinates everything and is owned by no one. It does not scale, it does not audit, and when one of those long-serving people leaves, part of the business leaves with them.

The layer gets a name

The analyst community has started calling this layer a System of Action: the layer that sits above the systems of record and below the systems of engagement, coordinating work, executing operations, surfacing decisions and integrating the stack.

We find the name useful, mostly because we have spent a decade building the thing it describes. In 2019 we wrote about "marketing middleware" and compared running simultaneous campaigns to air traffic control. The language was ours; the category did not exist yet. The problem was exactly this one: the work between systems had no system of its own.

A System of Action is not another database and not another channel. Its job is different in kind:

• It coordinates work. Plans, programmes, budgets, approvals and tasks live in one place, connected to each other, with status that is true rather than reported.
• It executes operations. Registrations, claims, requests, provisioning and routing happen inside governed processes, not inside someone's inbox.
• It surfaces decisions. The person who must act sees the thing that needs acting on, with the context attached, at the time it matters.
• It integrates the stack. It sits above your systems, not instead of them. The CRM remains the record. The channels remain the conversation. The layer in between stops being people.

Why now

Two things changed. First, the coordination load grew past what goodwill can absorb. More channels, more partners, more regulation, more content, smaller teams. The invisible layer was always expensive; now it is breaking.

Second, AI made the layer buildable at reasonable cost. Most of the work in that invisible layer is reading, classifying, drafting, reconciling and routing. These are precisely the tasks that modern models do well, provided they operate inside governed processes with humans holding the decisions. A System of Action is where AI earns its keep in an enterprise: not as a chatbot bolted on top, but as labour inside the layer that coordinates everything else.

What to look for

If you are evaluating this layer, whether you build it or buy it, we would hold it to five tests:

1. It must be configurable, not custom-built. Your operations change monthly. A layer that needs a development cycle for every change recreates the problem it was meant to remove.
2. It must hold the operational truth. If status still lives in a spreadsheet beside the system, the system has failed.
3. It must integrate as a peer, not aspire to replace. Rip-and-replace pitches at this layer are a warning sign. The value is coordination across what you already own.
4. It must carry governance natively. Approvals, audit trails, permissions and consent are the floor, not a module.
5. It must put AI inside the process. Classification, drafting and reconciliation inside governed flows, with people making the calls that matter.

We have views here because this is the work we have done since 2012: bringing data, process, channel programmes and integration architecture together for enterprises, then codifying what kept recurring into platform IP. The whiteboard finally has a name for the layer in the middle. The organisations that treat it as real infrastructure, rather than a heroic effort by tired people, will run faster and break less.