A little while ago, I lost a client I'd worked with for over a year. They were happy with my work, paid on time, and had no problems. Then, one month, they told me they were going to try handling it in-house with an AI tool instead. It stung more than I expected, partly because there was nothing I could point to as the reason. I hadn't done anything wrong. They just found a way to get something close enough for a fraction of what I charged.The work they replaced was the simple, repeatable stuff I'd been doing on autopilot. It was easy money for me, so I never questioned it. AI was always going to take that piece first. What I learned is that the safe work was the boring work, and the boring work was the most replaceable. The clients who stayed are the ones where I do the messy, judgment-heavy parts that a tool can't reason through on its own.Have you lost a client to AI? What was the work they replaced, and did it change how you position yourself now?
Top comments (1)
The point about AI replacing the repetitive parts of client work is interesting.
I’m working on Tweak around another part of that workflow: keeping the client’s original request and exact website context connected all the way to the developer.
The developer can then pull the request into Cursor/Claude through MCP instead of manually translating feedback.
Do you currently use AI tools when handling client revisions as well?