Course

AI for Web Studios: Claude Code, Automation and Retainers

Twenty client sites, three people: the build pipeline and the retainer machine.

HardWeb design

0/99 stops · about 2.5 hours · final quiz · certificate

Start course Sign in to save progress

Start with

• AI at Work: FoundationsStart from zero and finish with three things you can actually use.
• AI for Web DesignersDiscovery to launch: the freelancer's site build, with Claude in every step.

Who this is for

Studio owners and lead developers running many client sites at once, with builds, retainers and other people's work to review. Every example follows Dany, who runs a three-person web studio with twenty retainer clients on Wix and a growing set of hand-coded sites on one small host.

You will be able to

• Build a custom site with Claude Code from a Figma file, with tests and a deploy guardrail
• Keep a component library the studio reuses and Claude Code extends
• Run the retainer machine: monthly checks, Search Console digests and content updates on routines
• Check every client site with Claude in Chrome on a schedule and file the fixes
• Report to every client monthly from a pipeline instead of a Friday scramble
• Write the guardrails: what runs unattended, and what only a human ships

Stops

1. 1 The studio Project and the deploy guardrailOne Project above the client Projects: how the studio builds, what never enters a chat, and the rule that no client site changes without a human merging it. Set once
2. 2 A site with Claude CodeA Figma export becomes a repository: the brief, four checks wired to every pull request, the phone pass on the branch preview, and the merge Dany does herself. Weekly
3. 3 The component librarystudio-kit: what earns a place in it, the documentation Claude Code reads before it writes, and how one component changes on six sites without six arguments. Weekly
4. 4 The retainer machineOne client list drives three loops: the monthly site checks, the Search Console digest and the content update queue, all landing on the board as tickets. Weekly
5. 5 Quality checks with Claude in ChromeThe same eleven questions on twenty sites every week, a score per site, and the only output Dany reads: what changed since last week. Weekly
6. 6 Client reporting pipelineTwenty monthly reports built from exports by Claude Code, each with three evidenced fixes, a QA file Dany reads first, and one priced line at the bottom. Weekly
7. 7 Migrations and custom code on buildersMoving a client off a builder without losing their search traffic, the custom code a builder actually allows, and the risk list you quote from. Later
8. 8 Studio operationsProposals and scopes that survive the third week, change requests priced the same day, invoices that go out on time, and a capacity model that says no for you. Daily
9. 9 Dany's quarter and the capstoneThree schedules that carry the quarter, then the graded capstone: one client from Figma to a merged pull request with its retainer routines running. Weekly

Final quiz