Agent-mediated work

Two Planes of Work: Fewer Steps for the Hands, and for the Head

By Cliff Rosen, Founder & CTO, Orchestrator Studios

July 2026

A business runs on systems that persist data, and the day's work is sequences of operations against those systems — within one system, or across several. Run through each system's native screens, every sequence makes a person do two jobs at once. On the mechanical plane, the person is the operator: launching, navigating, entering, submitting. On the cognitive plane, the person is the processor: between operations, reading what one step produced, deciding, and feeding the next. An agent placed between the person and the systems takes over both. What stays human: stating intent, and confirming what matters.

A person acts The agent acts Mechanical — hands, no judgment Cognitive — the person is the processor Performed by the agent
Example 1 · One system, many steps

Adding a contact to the CRM

The real work is one sentence of information plus one small decision — does this contact already exist? Everything else is the price the interface charges to accept it.

Through the native screens

7 steps · you do all 7

The person is both operator and processor.

Open the CRM and sign inMechanicalCRM
Search contacts for “Dana Whitfield” and “Meridian”MechanicalCRM
Scan the results and decide: new record, or update an existing one?Cognitive · you are the processorCRM
Open “New contact,” enter name, company, roleMechanicalCRM
Enter email, phone, and source on the next screenMechanicalCRM
Tag the deal and set the follow-up ownerMechanicalCRM
Review and submit the recordCRM

Through the agent

1 sentence in · 1 review out

The agent runs the same sequence — operations and decision alike.

“Add Dana Whitfield from the Meridian call — she's their VP Ops, tag her to the Meridian deal, I own follow-up.”Intent
Connects to the CRM and searches for an existing recordCRM
No match on email or account — decides to create, not mergeDecidesCRM
Assembles the record — name, company, role, email, phone, sourceCRM
Tags the deal and sets the follow-up ownerCRM
Review the drafted record — including the create-vs-merge call — and confirm the writeCRM
Notice what did not happen: no step disappeared. Inside one system, the same sequence still runs — the agent simply performs it, absorbing the one cognitive step (the create-vs-merge call) along with the mechanical ones. Only who does the work changes. That alone moves a person from doing seven things to doing two.
Example 2 · Steps across systems

From a CRM segment to an email audience

Cross-system work is worse than long. The seam between two systems belongs to nobody, so the person becomes the integration — exporting, downloading, re-uploading — and in the middle sits real cognitive work: applying the campaign's rules to raw data by hand. Here, some steps don't move to the agent. They disappear.

Through the native screens

10 steps · you do all 10

The person is also the integration layer.

Open the CRM, go to reportsMechanicalCRM
Translate the campaign's criteria into the CRM's filter languageCognitiveCRM
Export the segment to CSVMechanical · exists only for the seamVanishesCRM
Download the file, find it, open itMechanical · exists only for the seamVanishesBetween
Work the list by hand: drop recent unsubscribes, merge duplicates, exclude open support casesCognitive · you are the processorBetween
Open the email platform, sign inMechanical
Go to Audiences, choose “Import,” upload the CSVMechanical · exists only for the seamVanishes
Map columns to audience fields, resolve mismatchesMechanical
Run the importMechanical
Verify the audience count looks right, confirm

Through the agent

1 sentence in · 1 review out

It reads, decides, and writes across both systems — and the seam steps have no reason to exist.

“Build an audience for the spring campaign: active customers, last 90 days, West region — usual exclusions — and load it into the email platform.”Intent
Translates the campaign criteria into a queryDecidesCRM
Pulls the matching records directlyCRM
Applies the rules — drops unsubscribes, merges duplicates, excludes open casesDecidesBetween
Reshapes the fields to the audience schemaBetween
Creates the audience, loads the records, reconciles the count
Review the audience summary and the exclusions applied, confirm before it goes live
Three of the native steps never appear on the right. Export, download, and upload existed only to ferry a file across the seam between two systems. When one agent works on both sides, the seam is gone — and so are the steps. The rest didn't vanish; they changed hands: the mechanical operations and the two cognitive calls all moved to the agent.
The honest part

The “two” is a good day, not a guarantee

When the rules can be stated and the data is clean, it really does run like this: one sentence in, one review out. But the count moves the moment the work gets genuinely ambiguous — a match that's a coin-flip, a rule nobody ever wrote down, a call that deserves a human. Then the agent should stop and ask, and you're back in the loop mid-flow.

That's the design working, not failing. The point was never zero human involvement; it was to move the person off the mechanical and routine-cognitive work and keep them on the calls that carry consequences. Stating intent precisely — and knowing when to distrust a confident-looking answer — is its own skill. The number moves; the principle doesn't.

What to notice across both cases

The comparison is always the same

A sequence of steps against the native screens, versus one sentence of intent. The savings land on two planes at once — and it's worth seeing them as two, because they're different kinds of relief.

Plane 1 · Mechanical

Fewer steps for the hands

Launching, navigating, entering, submitting. The agent performs them without screens — and the ones that existed only to move data between systems disappear entirely.

Plane 2 · Cognitive

Fewer steps for the head

Reading one system's output, deciding, feeding the next. Where the rules can be stated — filter, match, dedupe, reshape — the agent is the processor, not the person.

What stays human

Intent and commitment

The person states the task and confirms consequential writes — including reviewing the decisions the agent made along the way. Direction and accountability don't transfer.

The shift isn't from clicking to chatting.

It's from the person as the workflow engine to the agent as the workflow engine. The person moves up a level — from operating each step to directing and governing the result.

That's the what. The how — how an agent gets the access and the understanding to operate your systems faithfully — is the subject of The Living Workspace.