How the work actually gets split, by Marcus Li
you decide → [ claude builds ] → you review
THE LOOP THAT ACTUALLY WORKS
People ask me some version of the same question a lot lately: does Claude actually replace the work I used to do by hand, or is it just a faster typist? The honest answer is neither. It's closer to having a very fast, very literal junior developer and copywriter who never gets tired, but who still needs someone deciding what "good" looks like. Here's what that division of labor actually looks like day to day.
What I hand to Claude
- First drafts of copy. Not final copy, a starting point. It's much easier to edit something than to stare at a blank page, and that's true whether the something came from Claude or an intern.
- The actual HTML, CSS, and JavaScript. Once I know what a page needs to do, describing it and reviewing the result is faster than hand-typing every div and selector myself, especially for something like a full redesign touching a dozen pages.
- Repetitive changes across many files. Updating the same footer link or navigation item across every page on a site is exactly the kind of tedious, error-prone task worth automating, as long as you check the result.
- Explaining unfamiliar code. When I inherit a client's messy old theme or plugin, having something read through it and explain what it's actually doing saves hours versus tracing it by hand.
What stays mine
- What the site is actually for. Strategy, positioning, what a visitor needs to see first, none of that is a prompt-engineering problem. It's understanding the business.
- Whether the output is actually good. AI-generated code runs. That's not the same as it being right, secure, or a good fit for the rest of the codebase. Every meaningful change gets reviewed before it goes live, the same as I'd review a junior developer's pull request.
- Client relationships and judgment calls. Knowing when a client's request is actually a symptom of a different problem, that's not something you hand off.
The failure mode to watch for
The mistake I see people make isn't using AI tools, it's stopping reading the output. It's easy to get lulled into approving things you haven't actually checked because the last ten were fine. Treat every change the same way you'd treat a contractor's work: you don't have to do it yourself, but you do have to look at it before it ships. That's not a knock on the tools. It's just what "still being the one responsible for the site" actually requires.
This describes my own workflow running client and personal sites with Claude. It's a description of a process, not a guarantee of results for any particular project.
WRITTEN BY
Marcus Li
Vancouver web designer and online operations consultant, building websites and running online businesses since 2013, now with Claude and OpenClaw. Full background & credentials →
If you're weighing whether AI tools actually fit into how your business runs its website, that's a genuinely useful question to talk through. Ask it here, for free, or if it's a bigger project, reach out directly.
GET IN TOUCH →