News
The work you can't automate is usually in somebody else's system
By Jay Waters

An owner who runs about a hundred units around the Bay Area is walking me through his work orders, and halfway through he lands on the actual problem without meaning to.
"Maybe you have 20 or 30 work orders in a day, and that carry on next because they weren't, the process was unfollowed appropriately by an external party."
External party. Meaning the vendor. The plumber went out, did the job, submitted the invoice, got paid, and never went back in to close the ticket. So 20 or 30 of them roll into tomorrow, and somebody in that office spends part of every morning chasing people who have already been paid and have no reason left to care.
Nothing inside his business is broken. His staff did their bit. The dispatch went out, the vendor got the job, the invoice got processed. The one step that didn't happen was the one step he has no authority over.
You can't route around the thing everybody hates
Everything in that company runs through one property platform. Tenant complaints, work orders, vendor dispatch, vendor payment, all of it sits in the same system. Here's how he described it:
"It's kind of a neural hub for us, but the systems within it currently suck."
Both halves of that are true at the same time. It's the neural hub, so you can't route around it. The systems in it suck, so nobody wants to build on top of it. And replacing it means a migration that eats a year and puts every tenant record at risk, which he is not doing and shouldn't.
I've been in this room a lot this year. A surgeon told me his practice won't request insurance authorisation until the month of the surgery, because the authorisations expire, and the hospital pushes back on the paperwork more than about seven days out. Everyone in that chain is behaving sensibly. Three separate organisations are each protecting themselves, and the patient sits in the middle of it for months.
Same shape. The constraint is outside the walls.
And my honest answer to that was always: that one I can't touch. If there's no integration, no API, no way in except a person typing into a login screen, then it stays manual and I go automate something else. I said it to owners' faces. It was the truthful answer and it was also the reason half the real work in a service business stayed exactly where it was.
What changed last week
On August 25 OpenAI's work browser learned to log into websites and finish tasks behind the login. Their own examples were utility signups, DMV appointments and insurance portals. The user puts the credentials in, OpenAI says the model never sees the password.
The next day, August 26, Anthropic moved Claude in Chrome out of preview and onto every paid plan. It reads the page, types, clicks and fills out forms using the logins your browser already has. And Anthropic pointed it directly at internal dashboards, legacy systems and vendor portals. The stuff with no API. The stuff that was always the reason it stayed manual.
Two labs shipped the same capability inside 48 hours, which usually means it's about to be in everything.
Nothing about the model got smarter last week. It just got into rooms it couldn't get into before. Nobody ever doubted the thing could write a vendor follow up. The doubt was whether anything could get inside the platform to see which vendors needed following up in the first place.
The person who already uses it is stuck too
That owner isn't behind. He's ahead of nearly everyone I meet. He already has Claude connected to his property software and his email, he's built instruction sets, he's got some of his operations reporting running on its own. He's a daily user. And when I asked him where he wanted to start, he couldn't answer.
"You're just kind of hit with a fire hose of information."
The owner who has never opened any of this and the owner who lives in it every day are stuck on exactly the same step. And it's almost never a question of which tool either of them should buy.
He also killed one of his own ideas in front of me, which I liked him for. He wanted the scheduling automated, then worked out in the same breath that it needs the whole team keeping their calendars properly first.
"That's just such a large ask. People just don't do that."
He's right. There's nothing to automate there, because nothing is feeding it. Before anyone builds you anything, ask what has to be true for it to run. Then ask honestly whether that thing is true in your office today.
Where it actually went
I asked him where the time goes and he designed the fix himself, out loud, in one breath. Set a threshold. Auto clear the low risk invoices. Anything outside the band goes to a human to look at. Then he set his own target before I could offer one.
"So you cut that down from 100 a day to 50 a day."
Fifty invoices a day that nobody has to open. I didn't pitch that. He's the one who knows which fifty are boring, and no consultant walking in cold was ever going to know that.
So if you're running property, or any business where the work sits inside one platform you're stuck with and half the delays are caused by companies that don't work for you, the questions are these. Where does the day actually go? Which of those steps happen inside a system you don't control? Which ones are just somebody logging in and retyping? Who is the external party that keeps dropping the last step? And what would have to be true before any of it could run without you?
None of those are technology questions. Answer them and the build is usually small and boring.
I do this in person and I'm 30 minutes from most of Marin. Write down every system somebody in your office has to log into by hand. Just the names, back of an envelope is fine. Send me that list and I'll tell you which ones a browser agent can handle now, which ones still need a person, and which ones you should be deleting rather than automating. No charge for that, and I'd rather do it standing in your office than on a call, because I want to watch somebody actually do the task before I say a word about it.
Book 30 minutes, or email jay@jaimate.com with the list.
