The substrate

Two numbers on everything.
Every decision is the difference.

Your operation already knows what things cost. It does not know what they were supposed to cost — not in the same place, not on the same object, not in a form anything can act on. We build the layer that holds both, then act on the gap.

01 · The core property

What is true. What needs to be true.

Every object in the substrate carries two values, and they are never averaged together. This is the whole system, and it is the reason the software can decide rather than report.

Actual

What is true

Derived from an append-only record of everything spent and earned, in order. Never edited, only superseded. This is the number your ERP holds fragments of, across six tables.

Target

What needs to be true

Set by you, or worked backwards from the enterprise value you are building toward. A margin floor, a capacity, an occupancy goal, a valuation. A real object, not a note in a spreadsheet.

The delta

Where the decision lives

Pricing, planning, coverage and capital allocation are one operation: close the gap without breaching the floor. An agent can act on a difference between two numbers. It cannot act on a dashboard.

ONE UNIT · PALLET PROGRAM, RIVE-SUD ACTUAL — WHAT IS TRUE 18.4% contribution margin derived from 41 events append-only · never edited last write 3 days ago TARGET — WHAT NEEDS TO BE TRUE 24.0% required to hit target EV worked back from $40M EV versioned · set 11 Feb by TG floor 18% — not breached 5.6 points THE DELTA where the agent acts
Neither number is interesting alone. The gap is the instruction.
Why this is unusual. Business intelligence holds actuals and calls it insight. Planning software holds targets and calls it a forecast. Neither holds both on the same object — so the gap, the only part that tells you what to do, gets assembled by a person in a spreadsheet every single time. That reconciliation was the most common thing operators described to us, and it is what this removes.
02 · The objects

Nine objects. Not a blank canvas.

A pre-built ontology for asset-heavy operators — the shapes your business already has, named once, so every module, every agent and eventually every lender reads the same thing.

01

Unit

One SKU deployed at one address for one account. Everything else describes, costs or commits to a Unit.
The spine
02

SKU

A productised revenue or cost line — with install time and sales effort attached, not just a price.
03

Address

A physical location where a Unit lives, is serviced, or ships to. Not your offices — your customers'.
04

Account

The customer. One canonical, de-duplicated record that every other object points at.
05

Event

An append-only entry against a Unit: revenue, direct cost, deploy cost, run cost, acquisition cost, capital.
06

Commitment

What you promised. Quote line, contract term, entitlement, billing schedule — bound to what was actually delivered.
07

Target

An object, not a field. Versioned, audited and diffable against the actual — which is what makes section 01 work at all.
08

Attestation

A signed claim over a set of Events, disclosed selectively. Prove a predicate without opening the books.
09

Line

A revenue line, and the business-model shape it runs on. The object that growth changes.
Allometric
01 · THE SPINE Unit 02 SKU 03 Address 04 Account defines 09 Line SKUs belong to a Line 05 Event append-only → ACTUAL 07 Target set against it 06 Commitment what was promised 08 Attestation signs a set of events
Everything defines, measures, promises against or signs over one Unit. That is what makes it a graph rather than a schema.
Nine, and no more. This is not a platform you configure into existence over six months. The objects are already built, for one industry shape — which is why implementation is measured in weeks and priced in thousands rather than hundreds of thousands. A general-purpose ontology is someone else's business model.
03 · The stack

Your systems stay. The layer goes on top.

Forty-nine of the fifty-five operators we spoke to already owned a system of record, and not one of them wanted another. So nothing below the first layer is ours, and nothing above it asks you to migrate.

YoursSystems of recordERP, accounting, CRM, the spreadsheets beside them, the custom database someone built in 2011.
Layer 1ConnectReads what you have — file, database, API, named connectors. Identity, lineage, de-duplication, audit chain. Included at no cost, always.
Layer 2The ontologyNine objects, two numbers each. The part that makes everything above it possible and everything below it legible.
Layer 3ModulesCPQ, Plan & Flow, Cash Ops, Contracts & Renewals, Agentic ABM, Occupancy & ICP. Each acts on the gap in its own domain.
Layer 4Closed LoopEvery module writing to the same Unit. True margin, payback and acquisition cost per deployment — the point at which estimating stops.
Layer 5Adjacent PossibleWhich revenue line to add next, and when. Roadmap
Layer 6CapitalThe attested record, selectively disclosed, priced by a lender. Not a second product — a consequence of layers 1 to 4.
Layers 1–2 are Model. Layers 3–4 are Execute. Layer 6 is Accelerate. The verbs are what you do; the layers are what does it. Model is the operation described as objects rather than tabs. Execute is agents closing the gap those objects expose. Accelerate is what a lender will price once the first two have been running long enough to leave a record.
Read it as a dependency chain, not a menu. Layer 6 is impossible without 4, which is impossible without 2. That is why the capital story is not a pivot or an add-on: it is what an operating layer leaves behind when the operating layer is built correctly.
04 · Why linked beats separate

Each module works alone. Together they stop guessing.

Any vendor can say their products are better together. Here is the mechanical reason, which you can check: the cost of a Unit is written by one module and read by another.

ModuleWhat it writes to the UnitWhich means
CPQthe price, and the floor it was held againstWhat you sold it for
Contracts & Renewalsterms, entitlements, what recursWhat you committed to
Plan & Flowhardware, freight, install hours, travel, service visitsWhat it cost to deliver
Cash Opscash landed, days outstandingWhat actually arrived, and when
Agentic ABMsales hours, time to close, commissionThe half of acquisition cost nobody books
All of themone closed record per UnitTrue margin, payback, LTV and acquisition cost per deployment

Run CPQ alone and it prices against standard cost — a target, not a fact. It cannot tell you whether the last hundred quotes at that price made money. Add Plan & Flow and delivered margin becomes real, but acquisition cost is still zero, so every unit looks better than it is. Close the loop and the chain runs all the way up: unit, address, account, business unit, enterprise value.

Which is why the whole operation is priced as one thing rather than sold as a discount on six. See how Closed Loop is priced →
05 · Authority

Agentic execution. Human authority.

Nearly every operator who told us what they wanted also told us what they did not want: software that acts on the business without asking. It came up as a condition of buying, not a preference.

The agent does the labour. You keep the decision.

Every recommendation arrives with its reasoning and a number attached. Every consequential write — a posted invoice, a repriced quote, a released order — is gated on your approval. And no recommendation that breaches a floor you set is ever shown as an option; it escalates instead.

Agentic is about who does the work. Augmented is about who holds authority. Different questions, which is why we answer both. What operators asked for was nimble, augmented operations and then speed — not a system that runs the company while they watch.

Enforced, not promised. Floor-never-breached and no-unapproved-write are invariants with tests behind them, the same way tenant isolation is. They are not settings, and there is no administrator who can switch them off.
06 · The allometric layer

When a business grows, its shape has to change.

Allometry is the study of how proportions must change with size. A mouse scaled up to elephant proportions collapses, because strength grows as the square while weight grows as the cube. Growth is not magnification — past a threshold the structure has to change. Operating businesses work the same way, and nobody names it.

A restaurant at $2M is a restaurant. At $10M it is not five restaurants — it needs a commissary, central purchasing and a brand function, or it breaks. Every operator eventually asks “we are doing well, when do we add the next thing?” and answers on instinct, because no system anywhere answers it with numbers.

The line it addsWhat it reusesWhat it does to the valuation
A second locationbrand, playbook, suppliersMore of the same multiple
Cateringkitchen capacity in off-peak hoursSlightly better — utilisation
Retail pasta saucerecipe, brand, supplier relationshipsA consumer-goods multiple — roughly double
A boutique hotellocation, brand, hospitality operationsAsset-backed — higher, and financeable

The rerate is worth more than the revenue. A restaurant group trading on restaurant economics that becomes a consumer brand earns consumer-brand economics on the whole entity. This is the sharpest form of pricing backwards from enterprise value, because sometimes the honest answer is not raise your prices — it is you are the wrong shape for the valuation you want.

Answering it needs every layer below. Spare capacity comes from Plan & Flow. The margin that funds it comes from the unit ledger. Whether your customers would buy it comes from the book model in Occupancy. Proof you can operate it comes from the attested record. Which makes this the payoff for closing the loop — and unreachable from any single module.

Roadmap, deliberately. We will not ship a recommendation to add a revenue line until the loop is closed on real data at more than one operator, because the advice is only as good as the utilisation and margin underneath it. It is published here because it is the clearest statement of what the substrate is for.
07 · Oracle

Ask the operation anything.

Once the objects exist, a question is just a query. Which addresses lost money last quarter, and why. Every unit trading below floor. What the install actually costs on the configuration you keep quoting.

What Oracle does
ReadsThe whole graph, in your own words. No report builder, no ticket to an analyst.
WritesNothing without your approval. The authority rule above applies unchanged.
ExtendsDefine a SKU, set a target, save a recurring question, build a view. You personalise the system without us shipping a bespoke feature.
CostsMetered in credits — work actually done, not logins. An allowance is included.
Also roadmap, and in this order for a reason. A chat interface over an incoherent object model is a demo. The ontology comes first — which is the whole argument of this page.

Start with the gap. Not a migration.

A free Margin Scan reads what you already have and returns one number: what your pricing is leaking. No implementation, no commitment, and your data stays yours.