The whole argument, in three lines
Every large company already runs SG&A.
Not one of them can show it to you.
The SG&A Agentic Ops enterprise and platform changes that.
Every company on earth already does this work. What none of them holds is a model of how they do it — one place where the position, the rule that binds it, the station that runs it, the cost it carries and the person who signed it are the same object. That is the thing being built here, and the four questions that prove it are on their own page.
The case
Why a company would move its functions onto a network
Corporate functions have been reorganized twice in thirty years and both times the unit of change was the transaction. This platform argues the third change is different: the unit is the sub-function, and the thing that runs it is an agent that holds a position, writes the rule, watches the outcome, runs the line and drains the repeatable part into one depot. The 14 functions, 154 sub-functions and 2,748 stations behind this screen exist so that argument can be checked rather than believed.
14
functions
run end to end
154
sub-functions
the unit of change
2,748
stations
508 of them gates
143
interchanges
function boundaries crossed
$9.08m
depot run cost / wk
21.0% inference
0 of 26
systems connected
nothing is reconciled
Where this is heading
Three eras, and only the third one changes the function
Each era took the same corporate work and moved one thing about it. The first moved the place, the second moved the keystrokes, and both left the judgment exactly where it was. The third moves the judgment, which is why it needs a different operating model rather than a better tool.
Centralize the transaction
Move the same work to a cheaper place.
Invoices, payroll runs and journal entries were lifted out of the countries and put into a handful of centers. The unit cost fell because the labor was cheaper, not because there was less of it. Judgment stayed in the function, and every question that needed a decision traveled back up the line as an email.
Where it stops · The saving is bounded by the wage gap, and the wage gap closes. Nothing about how the work is decided changed.
Automate the keystrokes
Take the typing out of the work that was already moved.
Towers were drawn, service levels were signed, and scripts were pointed at the screens people were filling in. Volume per head improved and the towers got a scorecard. The scripts broke whenever the screen behind them moved, and the exception queue became the real operation.
Where it stops · Automating a step does not remove the step. The exception queue grows in proportion to the automation, and it is staffed by people.
Run the function
Agents hold the position, write the rule, watch the outcome and run the work.
The unit of automation stops being the keystroke and becomes the sub-function. An agent authors the strategy position with its options and its dissent, drafts the policy that binds it, watches whether the outcome moved, runs the workflow station by station, and drains the repeatable part into a depot that runs once for the whole company. A named human ratifies, refuses or overrides, and the refusal is on the record.
Where it stops · This is the era this platform models end to end. Modeling it is not running it, and the pages say so wherever a figure would imply otherwise.
The three eras below are an argument about where corporate functions are going, not a measurement. The platform cannot count an industry. What it can count is what the third era looks like when somebody builds the whole thing, and those counts are the ones shown against it.
The operating metaphor
A function is a transit network, and throughput is the whole point
A subway does not go faster because the trains are faster. It goes faster because every train has a line, every line has a timetable, every station has a dwell it is held to, and the places where passengers change lines are designed rather than improvised. A corporate function has all four of those things and almost never draws them, which is why nobody in it can say where the work is standing right now.
What maps to what
Five pieces, nothing metaphorical about any of them
Line
A workflow inside a sub-function
Station
A stage with an owning agent and a dwell commitment
Gate
A station the train cannot leave until a person signs
Interchange
A station where work crosses into another function
Depot platform
A station whose work runs in the shared transaction depot
Where the throughput goes
Timetable against actual, on the estate as it stands
262 run behind, and the volume they carry turns that into 1,767,391 lost hours a week.
Dwell across the whole network sums to 26,835 hours against 47,623 hours of commitment. Every station is inside its own commitment while 262 lines run behind theirs, which the estate does not reconcile.
Against 1,463,698 items a week entering the network. A function that cannot answer this question is running without a signal box.
Why the metaphor earns its place
Corporate functions do not lose time inside the steps. They lose it between them. A request finishes in procurement and waits for finance to notice, a case finishes in legal and waits for a person to forward it, and none of that waiting appears in any process document because no document owns the gap.
Drawing the estate as a network makes the gap a physical object. It becomes an interchange with an owner, a dwell it is held to, and a signal that goes amber when the work has been standing too long. 143 of those exist here, and every one of them is a place the old operating model had no name for.
The second thing the network buys is arithmetic. Once every line has a timetable you can subtract, and the answer is 1,767,391 hours a week on this estate. That number is only available because somebody drew the line first.
where the work is waitingDwell, timetable and actual hours are stored on the station and line records. The gap between timetable and actual is the platform grading its own estate against its own commitments, which is exactly the kind of self-check the verification page refuses to count as proof.
What the platform actually covers
Strategy, policy, observation, the work, and the depot
This is the part that separates an agentic operation from an automation program. The work sits fourth in the order, not first, and the depot sits fifth. A program that starts at the fourth layer and never reaches the first has bought a faster version of the function it already had.
Agents that take positions, argue them, and get held to the outcome.
209 positions authored
Open the positions registerIt starts here, not at the invoice. An agent researches the options, writes the position with its trade-offs and its dissenting read, attaches the evidence, and puts a named human on the ratification. Most automation programs never touch this layer at all, which is why they only ever produce a cheaper version of the same function.
The written rules every other agent is bound by, with version and owner.
465 policy items under version
Open the policy corpusA position that nobody wrote down binds nobody. The policy layer turns the ratified position into versioned text with an owner, an effective date and an authority behind it, so that every other agent in the estate is executing against a rule somebody signed rather than a habit somebody remembers.
Continuous sensing of the outside world and of the agents themselves.
70 signals on the grid
Open signal intakeThen the function watches. Signals come off the outside world and off the agents themselves, and the question the layer exists to answer is whether the outcome the position predicted actually moved. This is the layer that closes the loop, and it is the one that most often finds that the position was wrong.
Doing the work: lines, stations, and live units moving through them.
475 lines · 2,748 stations
Open the live work floorOnly now does the work run, and it runs sub-function by sub-function rather than function by function. Each sub-function is a set of lines, each line is a set of stations, and each station has an owning agent, a dwell commitment and, where the risk warrants it, a gate that stops the train until a person signs.
Repeatable transaction processing run once for the whole enterprise.
12 towers · 900,433 transactions a week
Open the transaction depotThe repeatable part of every line drains into one depot that runs once for the whole company, instead of fourteen functions each keeping their own version of the same posting, matching and settlement work. This is the layer that changes the unit cost, and it is the last one, not the first.
Cost and efficiency
What the depot does to the unit economics
The depot is the fifth layer and the only one that moves the cost line, because it is the only one that stops fourteen functions each running their own version of the same posting, matching and settlement work. Every figure below is read off the twelve depot records, and the before figures were authored rather than observed.
900,433
transactions / wk
across 12 towers
$27.93m
modeled cost before
$31.01 per transaction
$9.08m
run cost now
$10.08 per transaction
$18.85m
weekly difference
67.5% of the before figure
21.0%
of run cost is inference
$1.90m a week
76.3%
touchless, volume weighted
94.5% service level attainment
Read the difference carefully
What the number is, and what it is not
$18.85m a week is the arithmetic difference between two fields on the same twelve records: what the depot costs to run, and what the same volume was authored as costing before it existed. It is a modeled delta, and it is shown here because the shape of it matters, not because anybody has banked it.
The honest way to read it is as a ratio rather than a total. 67.5% of the before cost comes out, and 21.0% of what remains is compute rather than labor. That second figure is the one that behaves differently from every previous era: it scales with volume instead of with headcount, and it is the first thing that moves when an agent is promoted to a higher autonomy level.
Headcount on the depot records moves from 3,642 to 2,219, a difference of 1,423 and 39.1% of the starting figure. Those are authored fields on a modeled estate. No person in any company has been affected by anything on this page.
23 of 655 benefit lines carry a verification, and the verifier is this platform checking baselines it also holds. The benefit ledger is the page that refuses to add the rest into a total.
open the benefit ledgerWhy one depot and not fourteen
851 of the 2,748 stations on the network run their work inside the depot, and 274 of the 475 lines feed one. That is the mechanism: the line stays inside its function, and only the repeatable station drains out.
A function keeps the judgment, the policy and the accountability. It stops keeping its own private copy of matching, posting, settlement and reconciliation, which is the part that is identical in all fourteen and was duplicated fourteen times.
what a tower chargesBefore and after cost per transaction, and headcount before and after, are fields on the twelve depot records. They were authored by the team that built the platform. Treat them as the shape of the economics an MNC would model, not as a saving anybody has banked. Not one currency unit on this page has cleared a general ledger.
The argument for moving
Five things that change, each with the count behind it
These are the reasons a multinational would put its functions on this operating model rather than buy another tool. Each one carries the live figure it rests on and the page that produced it, so the claim can be attacked at the number rather than at the adjective.
The saving stops coming from the wage gap
$31.01 → $10.08 per transaction
Across 12 depot towers carrying 900,433 transactions a week, the modeled cost per transaction moves from $31.01 to $10.08. That is a change in how the transaction is produced, not in where it is produced, so it does not evaporate when a labor market catches up.
Unit costInference is a cost line, and it is on the same page
21.0% of the run cost
$1.90m of the $9.08m weekly run cost is inference. An agentic operation that does not carry its own compute cost on the same statement as its labor is not being honest about its economics, and the ratio is the first thing that moves when volume grows.
Autonomy economicsHandoffs become scheduled interchanges instead of emails
143 interchanges on the network
Work crosses a function boundary at 143 places in this estate. Drawn as a network each of those is a station with an owner, a dwell commitment and a signal. Left as an org chart each of them is an inbox, and an inbox has no timetable.
HandoffsControl stops being an audit and becomes a gate in the line
508 gates standing in 2,748 stations
A gate is a station the train cannot leave until the named approver signs. Because it sits in the line rather than beside it, the control is exercised at the moment the work happens instead of being sampled from a population three months later.
ControlsCapacity is released at the top of the function, not the bottom
209 positions and 465 policy items authored by agents
Authoring a position is most of the labor in a corporate function, and it is the part every previous era left alone. 209 positions and 465 policy items on this estate were drafted by agents for a human to ratify or refuse. That is where the capacity actually is.
Strategy positionsAnd the reason it has to be all five layers
Any one of these on its own produces a tool. A depot without a policy layer is an outsourcing contract with better software. A strategy agent without a workflow layer is a memo generator. The claim is not that agents are good at tasks; it is that a function becomes a different kind of thing once the same estate holds the position, the rule, the observation, the work and the depot, and every one of them is on the record in the same place.
the modeled enterpriseThe other side
What would have to be true before any of this is proof
Four things stand between the argument above and evidence. They are listed here rather than at the bottom of a footnote, because a case that cannot survive its own counter-case is a brochure.
Not one of the 26 source systems is connected
Every figure on this page is read from the modeled estate. 0 systems of record are exchanging data and 0 of 19 write-back routes are open, so no conclusion this platform reaches has ever landed in the system that holds the record.
632 of 655 benefit lines are unproven
The economics section is the weakest part of the case, and it is deliberately placed after the operating model rather than before it. A benefit is only real once it has cleared a close, and none of these has.
62 of 251 checks were signed from outside the authoring team
The rest were signed by the team that wrote the thing being checked, and none by anybody outside the company. A platform that grades itself is a platform with an opinion.
The before figures were authored, not observed
Cost before, headcount before and the timetable each line is graded against are fields on the records, written by the team that built this. They describe the shape of an argument an MNC would have to test against its own baseline, and they are not a measurement of anybody's current operation.
Actions
What is waiting on a person
This page makes a case. The queue below is what the case is missing, ranked by how much of it is outstanding. Every one of these is the difference between an argument and a proof, and not one of them is a feature anybody can ship.
stations reporting inside their dwell while the lines they sit on run late
Every one of the 2,748 stations is recorded inside its own dwell commitment, and 262 of the 475 lines those stations sit on are recorded as running behind their timetable. Both figures are read off the same estate and they cannot both be describing the same week. Nothing on this platform reconciles them, and neither figure has been adjusted to make the other one work.
benefit lines with nothing outside the platform proving it
23 of 655 lines carry a verification, and the verifier is this platform checking its own baselines. The economics argument on this page is only as good as that number, and that number has never been through a close.
lines running behind their timetable
1,767,391 hours a week are lost across them, weighted by the volume each line carries. Those hours are the throughput the network argument is claiming back.
checks signed from inside the team
Of 251 verification checks on the record, 62 were signed by somebody outside the authoring team, which is 24.7%. None was signed by anybody outside the company at all.
source systems described and not one of them connected
19 write-back routes are designed and 0 are live, so nothing this platform decides has ever reached the system that holds the record. Until that changes the migration case is a design, not a migration.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This page starts nothing. It is an argument with live counts attached, and every count is a link to the page that produced it. The only thing it can change is what somebody decides to do next, and the pages it links to are where that gets done.
Live observability
What the record shows right now
The five layers of the operating model, sized by how many records exist behind each one. A function is only agentic when it carries all five, and the bars show that the estate is heaviest where the work is and thinnest where the judgment is.
Current distribution
1,231 records
Is policy and strategy coming to fruition
Whether the written intent is holding here
The model is complete. The migration has not started.
Not holding on the record
The case this page makes is that a corporate function is a network, that the network can be run by agents under a control tower, and that the economics change when the repeatable part drains into one depot instead of fourteen. Everything needed to judge that case is on the record: 14 functions, 154 sub-functions, 1,361 agents, 475 lines and 2,748 stations, with 508 control gates standing in them and 143 interchanges where work crosses a function boundary. What is not on the record is a single connected system. 0 of 26 source systems are exchanging data and 0 of 19 write-back routes are open. 213 of 475 lines hold their timetable and 2,748 of 2,748 stations hold their dwell commitment, which is the platform grading itself against a timetable it also wrote. Those two figures do not agree with each other either, and nothing here reconciles them. So the strategy is coming to fruition as a design and has not begun to as an operation, and no page here will claim otherwise.
What this page is
This page argues a position. The numbers inside it are live counts from the modeled estate, read at page load, and they are evidence of what the operating model looks like when it is drawn in full. They are not evidence that it has run a real quarter for a real company. No source system is connected, so nothing here has been reconciled to anybody.