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 →

Why you keep losing on price — at a glance

The field-note version of our essay on price — where the cheapest bid actually comes from, what it quietly costs, and why we don’t run the race to the bottom.

On price

Getting beaten on price isn’t a pricing problem.

A quote is just a stack of costs with a margin on top. When someone lands far below you, they didn’t bend the laws of math — they took something out of the stack.

Where the low bid comes from
01
They cut the wage.
Junior or rotating contract labor instead of experienced people. The rate drops; so does who’s actually doing the work.
02
They ship it overseas.
Work handed to whoever bills the least, half a world away — oversight and accountability traded for a smaller line item.
03
They shave the margin.
A 4–6% net margin, thin enough that one slow quarter is an emergency — then made back later in change orders.
The lowest bid
4–6%
net margin · the underbidders
Built properly
~8%
net margin · a livable wage, kept

We’re not the cheapest. That’s the point.

We keep wages livable and the work onshore, and run AI and human effort in tandem. We replace the work, not the worker.

Read how we price  →

This is the field-note version of the essay “Why you keep losing on price.”

Why you keep losing on price — and what to do about it

ON PRICE

If you run a small shop, you already know the feeling. You put real care into a proposal, you price it honestly, and then you lose the job to someone who came in thousands of dollars under you. Maybe it’s a prospect who went straight for the cheapest name on the list; maybe it’s work you were genuinely the best fit for. Either way it stings, and the first instinct is almost always to wonder what’s wrong with your number.

Here’s the part worth sitting with: usually, nothing is wrong with your number. To understand why this keeps happening, it helps to look at how the other quote got so low in the first place — because once you see the mechanics, the whole problem starts to look different.

A bid, stripped all the way down, is just a stack of costs with a margin on top. When someone comes in far below you, they didn’t discover a clever way to bend the laws of math. They took something out of the stack. And there are really only a few places it can come from.

The first is wages. It is a lot cheaper to staff a project with junior or rotating contract labor than with experienced people who expect to be paid what they’re worth. The second is location — shipping the work overseas to whoever will bill the fewest dollars per hour, trading day-to-day oversight and accountability for a smaller line item. The third is margin itself: plenty of shops quote at a net margin of just 4 to 6%, thin enough that one slow quarter turns into an emergency, and they make the difference back later through change orders you never saw coming.

None of that shows up on the proposal. What shows up is a smaller number. But the cost didn’t actually vanish — it just moved. It moved onto the worker who’s underpaid, onto the client who discovers the quality gaps three months in, onto the deadline that slips because nobody senior was really watching. Cheap is rarely cheap; most of the time it’s simply deferred.

So when a competitor undercuts you by a wide margin, that gap isn’t evidence that you’re overpriced. It’s a readout of what they decided to remove. A shop that pays a livable wage, keeps the work close to home, and puts senior people on it needs a little more margin to stay healthy — realistically closer to 8% where the underbidders are scraping by on 4 to 6. That isn’t greed. It’s the plain arithmetic of doing the work properly and still being around next year to stand behind it.

Which points to what you should actually do, and it isn’t chasing the bottom. You lose that race even when you win it, because the only way to match the lowest bid is to start removing the same things they removed — and then you’ve just become the vendor you were competing against. The stronger move is to change what’s being compared. Shift the conversation from sticker price to total cost: the rework nobody has to pay for, the institutional memory you don’t lose to turnover, the deadline that gets hit because someone experienced owns it end to end.

That gap is exactly what we built Anchor to close. We keep wages livable and the work onshore, we cut the overhead that quietly inflates everyone’s rate — there’s no trophy headquarters folded into your invoice — and we run AI and human effort in tandem, so you get the speed of automation without paying to feed a swollen org chart. We replace the work, not the worker. The goal was never to be the cheapest name on the list; it’s to make the little bit extra buy you noticeably more — work that’s owned by your team, done end to end, and built to outlast the first invoice.

So if it feels like you can’t win on price, here’s the reframe: you’re right, and that’s actually good news. Price was never the game worth winning. The work is.

→ Read how we price. → Run your real number. → Talk to us for 20 minutes.