The list just got shorter

A field note on the work AI used to be told it couldn’t do — and why most of that list is now a 60-day build.

Field note · May 2026

— The list you stopped trying to automate

The list of work AI couldn’t do just got shorter.

Every leadership team has it — the workflows they decided, quietly, can’t be fixed. Three shifts in the last 18 months mean most of that list is now a 60-day build.

01 · The list

The work you wrote off as un-automatable.

It isn’t written down anywhere, but everyone on the leadership team knows what’s on it. The senior, expensive work that vendors kept promising to automate — then came back asking your systems to talk to each other. They don’t. So the work stayed on people.

01
Monthly close
Eats your finance lead’s last week
Now buildable
02
Dunning & collections calls
Pulls AR out of every meeting
Now buildable
03
Pipeline hygiene
Work your best AE shouldn’t be doing
Now buildable
04
Compliance checks
Lives in one person’s head
Now buildable
05
The judgment calls only your best people should be making
Stays with the team — always
Off-limits
02 · What changed in 18 months

Three shifts — stacked.

Each one alone would be incremental. Together they redraw the line between ‘we’ll have to hire someone’ and ‘we’ll ship an Operator.’

01
Agents that use a computer the same way your team does.

Not chatbots that answer questions — agents that take an objective and carry it out. A real cursor moving across the page. Real clicks on the buttons your AR manager clicks. The legacy portal nobody could connect to isn’t a wall anymore; it’s just another screen.

portal.legacy-claims-system.gov / submit
● OPERATOR · LIVE
Claim IDCLM-2026-04471
ProviderSt. Mary’s Regional · NPI 1487263901
Service date2026-05-12
Amount$4,820.00
Submit claim →

Real cursor · Real clicks · Real typing

02
They hold the whole workflow, not just one step.

Old automation pulled one number and sent one email. Useful, brittle — and the hard part stayed with your team: deciding what to do next, chasing the exception, knowing when to hand off. A crew of agents now runs the sequence end to end and escalates only the judgment calls.

Step 01
Research the account
Step 02
Draft the outreach
Step 03
Log the activity
Step 04
Chase silent replies
Step 05
Hand judgment back to a human

End to end · Owned by you · Hand-off where it matters

03
Safe to run where the work actually lives.

Finance, healthcare, legal — the teams that were told ‘no AI near this for compliance reasons.’ The agent runs read-only first: looking, not touching. Every action is logged. Sign-off gates sit at the points where money moves or records change. Auditors get a clean trail.

02:14:08 Read Fetched 47 open invoices from NetSuite sha · 8c4f…
02:14:32 Read Matched 41 to remittance lines in lockbox sha · 1a90…
02:15:01 Gate Sign-off requested · 6 unmatched · > $10K threshold @finance-lead
07:42:11 Write Applied 41 cash receipts · audit trail attached approved · sha · 4e22…

Read-only first · Logged · Sign-off where money moves

03 · The new math

The role you were about to post is a stack of recurring workflows wearing a salary.

Eighteen months ago, this workflow was a hire. Today it’s a build. The economics didn’t move a little — they moved by an order of magnitude.

— Yesterday’s answer
Hire someone to absorb it.
$189K
fully-loaded · annual
  • 90-day search, 3-month ramp
  • Works 40 hours a week
  • Median tenure: 18 months
  • Headcount on the org chart forever
— Today’s answer
Ship an Operator that runs it.
60 days
kickoff → in production
  • Outcome-priced, no retainer lock-in
  • Runs at 2am, every night
  • Doesn’t quit in eight months
  • On the P&L, not the org chart
04 · The point

Not every workflow should be automated. Most of the list is.

Some items are exactly what your best people were hired to do — keep those. The rest are still on the list out of habit. The ‘it’s not technically possible’ reasons mostly aren’t true anymore.

60d

From kickoff to a working Operator — in your environment.

2am

When the work gets done. Every night. No retainer lock-in.

0

80-page deliverables. No platform to learn. The work just starts getting done.

Where Anchor sits

The job you’re about to write a description for is probably already a workflow we can run.

We sit with the workflow, build the AI Operator that runs it, ship it in your environment, and run it. No platform to learn. No year-long integrations project.

Tell us the one on top of your list →

⚓ One next step

Don't miss the next essay.

One piece a week on the real cost of busywork — and what changes when you clear it. Founder-written. No fluff.

Discover more from Anchor

Subscribe now to keep reading and get access to the full archive.

Continue reading