What this is
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.
Not a dashboard over the output of the work. A model of the work itself: who holds each position, which rule binds it, which agent runs which station, what it costs a week, and who signed off. Four questions that are a workstream anywhere else resolve here to a query.
Enterprise front door
How SG&A is running, enterprise wide
Five readings sit at the top of the tree: what the run costs, what it moves, how much of it runs without a person, whether what was decided is actually in force, and what any of it has proved. They are five separate readings in five different units, not one score. Each opens on the page that produced it, and the ladder underneath goes down from here into the chairs, the 14 functions, the 475 processes and the explanation of every figure.
What it costs to run
modeledWhat is the enterprise paying a week to run SG&A?
$9.08m
a week, across 900,433 transactions in 12 towers
What it moves, and how well
modeledHow much work goes through, and how much of it lands without a person?
900,433
transactions a week through the shared depot
How much of it runs itself
modeledHow far has the work moved from a person to an agent?
72.9%
mean autonomy across 14 functions, against an 82.7% target
Whether policy and strategy are landing
modeledIs what was decided actually in force in the run?
395 of 465
rules in force; the rest superseded or still under review
What any of it has proved
measuredWhich of these figures has been checked by somebody else?
23 of 655
claimed benefit lines verified by somebody other than the author
Nothing above is added together and nothing is weighted into an index. Four of the five reads are modeled from the estate rather than reconciled to a customer system; the fifth, what has been proved, is the count of checks that actually happened and is the worst number on this page. It is published anyway.
From here, down
Enterprise, then chairs, then functions, then processes, then the explanation
Each rung is the same estate at a smaller grain. Nothing is aggregated on the way up and nothing is invented on the way down: a process belongs to a sub-function, a sub-function to a function, a function to whichever chair is accountable for it, and every figure any of them shows has a page saying where it came from.
Enterprise
5 reads
You are here. The whole of SG&A in five separate readings.
Chairs
9 chairs
The same estate cut by the person accountable for it.
Functions
14 functions
Each opening on 11 views of the one record.
Processes
475 flows
Across 154 sub-functions, station by station.
Explanations
34 figures
Where each number came from, and whether anybody checked it.
Rung two — by chair
9 chairs, each with one question
A chair is a route through the same platform, not a different set of numbers. Each one opens on the four counts that most often answer its question, and the pages behind them.
CEO
23 of 655Chief Executive Officer
Is any of this actually landing?
Benefit lines verified
CFO
$9.08mChief Financial Officer
What does it cost, and what came back?
Run cost a week
CIO
0 of 26Chief Information Officer
Is it actually connected to anything?
Source systems returning records
COO
1,337 of 2,520Chief Operating Officer
Is the work moving?
Work units in flight
CHRO
26 of 154Chief Human Resources Officer
What happens to the people?
Role transitions complete
CPO
291 of 385Chief Procurement Officer
Are we buying and sourcing under control?
Duty conflicts still only detected
CRO
1,750Chief Revenue Officer
Is revenue work actually landing?
Outcome instances tracked
CCO
10 of 24Chief Compliance Officer
Would this survive an examination?
Controls evidenced as effective
CTO / R&D
115Chief Technology and Research Officer
Is the thing safe to change?
Evaluation suites
A chair is a route, not a role. Picking one changes which pages are put in front of you and which numbers are shown first. It grants no access, hides no page, and is never checked against who you signed in as. Every figure on a chair page is the same figure its underlying page shows.
Rung three — by function
14 functions, 154 sub-functions
Each function opens on 11 views of the same record, from its flow of work and five layers through to its agent roster, its governance ledger and its unit economics. The full read of all fourteen together is the functions page.
Sales
11 sub · 2 awaiting
Marketing
11 sub · 2 awaiting
RevOps
11 sub · 2 awaiting
Legal
11 sub · 3 awaiting
Procurement
11 sub · 2 awaiting
Supply Chain
11 sub · 3 awaiting
Engineering
11 sub · 3 awaiting
R&D
11 sub · 2 awaiting
Finance
11 sub · 2 awaiting
HR
11 sub · 2 awaiting
IT
11 sub · 3 awaiting
Admin
11 sub · 3 awaiting
Cust Svc
11 sub · 2 awaiting
AI GBS
11 sub · 2 awaiting
Rung four — by process
475 processes, the six busiest shown
A process is a named flow of work with a line code, a set of stations and a timetable it is supposed to keep. These are the six carrying the most volume this week. Where the actual run time is above the timetable, the flow is running slower than it was designed to, and the figure is shown in amber rather than hidden.
line
process
volume a week
timetable vs actual
touchless
Assignment Change
RevOps · Territory & Comp Ops
Off-catalog Demand
AI GBS · Service Catalog & Intake
Chargeback Run
AI GBS · Cost-to-Serve Management
Talent Pool Nurture
HR · Talent Acquisition
Sample to Coaching Action
Cust Svc · Quality & Coaching
Employee Data Change
AI GBS · H2R Control Tower
Rung five — the explanation
34 figures, 22 of them measured
The last rung is the one most platforms do not have. Every headline figure in this estate has an entry saying what it counts, which records it reads, and whether it was measured from those records or modeled from an assumption. 22 are measured. The other 12 are modeled or asserted, and are labeled that way wherever they appear.
Acting lens
Requester
Nobody is signed in, so this is the lens the platform assumes rather than one anybody chose. Sign in and the persona is read from the session.
What this lens puts first
- Request status
- Time to resolution
- What still needs me
An ordering, not a filter. Every page below stays reachable whichever lens is acting.
Opens on
Work TrackerSigning in under this lens lands on Work Tracker rather than here.
Persona and endpoint coverageThe other way in
The five stages of the run
The ladder above cuts the estate by grain. This one cuts it by the order the work actually happens: see it, run it, govern it, improve it, prove it. Same pages, different route in.
97
stage pages
5
stages
9
chairs
14
functions
154
sub-functions
1,361
agents
Govern
21 pagesAutonomy with a seatbelt
A stage tile carries three counts out of the dozens its pages hold. They were chosen because they are the ones that most often turn out to be the reason something is not finished, not because they summarize the stage.
Start where you left off
What is yours
Four ways in that do not depend on knowing the shape of the platform: your own desk, the items waiting on a person, the views somebody already saved, and a plain question.
Actions
What is waiting on a person
This page is the way in, so the things it puts first are the things that most often turn out to be why nothing finished. Ranked by how many records each one holds up.
benefit lines with nothing proving them
Only 23 of 655 benefit lines are verified, and the verification is the platform checking itself against baselines it also holds. Nothing here has been through a close.
work units stopped until a person does something
Out of 2,520 units. The platform can show who each one is waiting on. It cannot tell them.
duty conflicts found and left where they were found
Detected against the modeled role set. None has been proven changed in a source system, because no source system is accepting a change.
source systems described but not one connected
19 write-back routes are designed and none is live either, so nothing this platform concludes reaches the system that holds the record.
register entries that have never been closed
The register is derived from live queries, so an entry disappears when the underlying gap closes. Not one has.
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 runs a set of live counts at load, one per figure, and caches the result for the life of the server process. It writes nothing and decides nothing. Every tile is a link to the page that produced its number, so a figure that looks wrong can be argued with at source rather than here.
Live observability
What the record shows right now
All 97 pages behind this screen, split by the stage they sit in. The split is the navigation as built, not a judgment about where the weight is.
Current distribution
97 pages
Is policy and strategy coming to fruition
Whether the written intent is holding here
Not yet. The platform can be entered in one click. What it opens onto is still a model of an estate that nothing is connected to.
Not holding on the record
The intent behind a front door is that somebody who has never seen this platform can reach the thing they care about without being taught its shape. That part holds: 97 pages, 14 functions and 9 chairs are now one click from here, each carrying a live count rather than a label. The part that does not hold is what those counts describe. 26 source systems are modeled and none returns a record; 19 write-back routes are designed and none is live. A faster way to the truth does not make the truth better.
What this page is, and what it is not
Every number on this page is a live count from the platform, read at page load. None of it is a forecast, a target or a rounded headline. Where a figure looks bad it is shown as it is, and the page it links to is the page that produced it. The enterprise band at the top is a set of five separate readings in five different units, not a score: there is no composite here and no roll-up across stages, because adding them would produce a number that means nothing. The 97 counted above are the pages that sit in a stage; this screen and the 9 chair pages sit on top of them and are not among the count. Nothing on this page is reconciled to a customer system — not one of the 26 source systems is returning live records.