Digital labor needs a management layer
Benioff is right that software becomes digital labor. Nobody has specified what managing that labor means.
The digital labor thesis has won the argument. What it has not produced is a management layer: a concrete answer to what supervising a fleet of agents means on a Tuesday afternoon, when an agent wants to act, the action touches three systems, and a regulator will eventually ask why it happened. Every vendor selling the thesis says humans stay at the center. Almost none of them can show you the mechanism that puts a human there. Center is a place on a slide. Management is a mechanism, and regulated enterprises can tell the difference.
What Benioff has been arguing
Marc Benioff has spent two years pressing one idea across earnings calls and this summer's AI for Good push in Geneva. The line he keeps returning to: "Software is about to become digital labor." The claim underneath it is a real break with decades of enterprise software. Tools wait for input; labor does work. Agents that plan and execute multi-step workflows are additions to the workforce rather than additions to the toolbar, which is why he talks about them the way CFOs talk about capacity.
The rest of his argument follows honestly from the premise. If agents are labor, companies scale output without scaling headcount. If agents are labor, humans move up a level, from doing tasks to supervising the entities that do them. The models themselves are becoming interchangeable; what he says compounds is the connection to the proprietary data an enterprise already trusts. And his warning is the sound one: the industry cannot let AI repeat the trust collapse social media went through. Governance first, then deployment.
The thesis is regularly read as a headcount story, and he keeps correcting that reading: the point of digital labor is capacity, the administrative load lifted off people whose judgment is needed elsewhere. That matches what senior people leaders say they want from AI when you ask them directly. The work they want gone is the grunt work. The decisions, they intend to keep.
Take the metaphor as seriously as he does and it becomes demanding. Labor gets interviewed before it is hired. Labor gets managed while it works. Labor gets held accountable afterward, with records. The industry has built evaluation suites for the interview stage and dashboards for the afterward stage. The middle, where an actual manager would live, is mostly empty.
Supervision, specified
Here is what the middle looks like when it is built instead of promised.
Every piece of work an agent wants to do arrives as a proposed workflow, before anything executes. The proposal states what the agent read, what it concluded, what it wants to do across which systems, and what the decision costs: the cost of acting and the cost of declining to act, priced against the business. A human approves the proposal, edits it, or declines it. Nothing acts silently. When the human approves, the system executes across the systems it read from, and the execution is logged in a signed Decision Trace: what was read, from where, why it mattered, and what input the human gave. Workflows in regulated territory take a second signer before anything moves.
That is the whole mechanism, and each clause earns its place. The proposal step makes the agent legible before it is powerful. The two costs attached to every workflow give the supervisor an economic basis for the decision rather than a vibe. The gate makes the human load-bearing: an approver whose decline stops the action is a manager, and an observer watching a feed of completed actions is an auditor arriving after the fact. The trace is what you hand the regulator, and the second signer is what your compliance team already does with wire transfers, applied to algorithmic work.
The gate also gives a manager of digital labor something no dashboard produces: a record of disagreement. The proposals that got edited before approval, and the ones that got declined with a reason, are the most useful management data in the system. They show where the agents' read of the business diverges from the judgment of the people who own the outcomes, which is exactly where a manager of human labor would spend coaching time. A weekly review of declines is to an agent fleet what a one-on-one is to a team.
At Nodes this runs as thirteen agents driving sixteen decisions across three pillars, with one calibrated model underneath. A decision here is a high-stakes recommendation the system surfaces: a hire, a ramp intervention, a retention play. The counts matter less than the ratio they imply. The agents produce; the decisions are where a human signs. In the approval gate piece I argued the human line belongs at approval, not inside every task. This piece raises the same gate to the scale of the enterprise.
The economics follow the labor
If software is labor, seat pricing dies. A seat measures access, and access was the right thing to meter when software was a tool a person operated. Labor is measured by the work, which is why nobody prices a staffing engagement by how many chairs the client owns. Benioff has said the same about where pricing is heading, and the market will follow him there, because CFOs will force it.
What the market has not priced in: outcome pricing has an evidence problem. A vendor who wants to charge for outcomes has to prove which outcomes were theirs, against the customer's own baseline, in a way the customer's finance team accepts. Without that attribution, outcome-based pricing collapses back into negotiated fiction. This is where the management layer and the pricing model turn out to be the same thing. A signed trace on every executed workflow is what makes an outcome attributable: this action, approved by this person, produced this delta. Nodes prices there deliberately, at 2% of validated impact in the outcome-based tier, with a money-back pilot and no per-seat fee. The tier stands on the word validated, and the trace is what validates.
Run the logic in reverse and it becomes a diligence tool. A vendor selling digital labor on per-seat pricing is telling you something about their confidence in attribution. If they cannot bill on the work, ask how they will prove the work happened.
Where the thesis needs one more layer
There is a failure mode waiting inside the supervision story, and buyers should walk in expecting it: approval fatigue. Put a human gate in front of a stream of agent proposals and the gate's quality depends entirely on what the human can see. A supervisor shown a proposal built from one system's slice of reality will approve confidently and wrongly, then learn to stop reading, and the gate degrades into a rubber stamp with an audit trail.
The fix sits below the gate. The agent drafting the proposal has to read across every system of record the company runs, so that what reaches the human is built from the whole picture: the call transcripts and the performance history and the candidate record, resolved to the same person, with the trace showing which system each fact came from. A complete proposal is one a supervisor can evaluate quickly, with grounds to decline. That completeness problem is its own subject, and the fragmentation version of it, why merging five copilots into one interface changes nothing underneath, is in the superagent piece.
The labor framing also clarifies who should hold the gate. Digital labor that executes across the CRM and the HRIS is doing work that used to belong to two departments at once, which is why the approver is whoever owns the outcome, with the trace giving every other stakeholder the means to check the work afterward.
Where the gate already runs
At a Fortune 500 insurance carrier, the loop runs against four years of production data. The cohort: 10,765 agents, with 850,000+ applicants scored, and every recommendation that reached a human carrying its costs and its evidence. The supervision model held up under the carrier's own reviewers and under the adversarial review protocol published in Decision Traces.
Benioff's metaphor is going to organize the next decade of enterprise software, and the companies that benefit will be the ones that took it literally. Labor without management is exposure, whether the labor is human or digital. When the vendors arrive this quarter selling agents as headcount, ask the management question first: show me a proposal one of your agents made that a human declined, and what the record says about why. Digital labor reports to whoever holds the approval gate. Make sure that is you.
Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises. Methodology: Decision Traces.