Lucas Gusso: a team of Claude Code agents builds an editable 15-page Webflow site, working around the Webflow MCP
A Webflow designer says a team of Claude Code agents built a native, client-editable Webflow site in three days, and maps where the Webflow MCP fails.
Done withCCClaude CodeWMWebflow (MCP)FMFigma (MCP)
Designer's own portfolio account; figures are his own; no client named
WHAT THEY DID
Lucas Gusso set up Claude Code agents to design and build Agenlab, a 15-page studio site, natively in Webflow, testing the Webflow MCP call by call and adding a converter for what it could not build.
STEP BY STEP
- Test the Webflow MCP call by call against clipboard JSON from hand-built elements; log failures.
- Use a self-built HTML-to-Webflow converter (writes Webflow's clipboard format) for things only a paste can build.
- Agents set up variables and a style guide page first.
- Section 'labs': four agents build four versions on the real page; he picks, fixes, and each fix becomes a rule (21 skills).
- A lighter subagent pushes one approved section at a time; a Figma file is built alongside with the Figma MCP.
HOW IT WENT
By his account the site is native Webflow (classes, variables, components, CMS and interactions) that the client edits in the Designer like a hand-built site, with a matching Figma file made with the Figma MCP.
Reported results: A 15-page Webflow site in three days instead of the 'three weeks or more' such a site usually takes him (his figure: about 85% less time).
WORTH KNOWING
Practical detail on making agent-built sites editable for clients: real classes, variables and components instead of custom code, and a map of where the Webflow MCP fails. A 15-page site was too much for one conversation, so decisions live in skills, a build log and a registry of Webflow IDs. The three-day time and 85% saving are his own figures, the HTML-to-Webflow converter is internal and not shared, and no work dates are given.
TRY IT
- Build one element by hand, copy its clipboard JSON and compare it with what the MCP creates.
- Keep a log of MCP calls you can't trust and have the agent read it before every push.
- Ask for several versions of a section on the real page, pick one and save each fix as a rule.
Rates the entry, not the tool.
Source: Lucas Gusso · XOpen as a page
- Work done: not stated in the source (Not stated. The case study gives the timeline as '3 days, from learning the MCP and setting up the agents to the full site in Webflow' but no dates; he posted it on 27 Oct 2026.)
- Source published: Oct 27, 2026
- On 4TC: added Oct 29, 2026 · checked Oct 29, 2026
About this source
Type: Self-initiated experiment · Firsthand report · Demonstrated workflow
- Post: team of agents in Claude Code builds a full site in Webflow
Lucas Gusso · X · Published Oct 27, 2026 (X post, 27 Oct 2026.) · Checked Oct 29, 2026
Author's own post promoting his case study (self-promotion). No sponsorship disclosed.
Access: open - Teaching AI Agents to build Webflow sites clients can edit
Lucas Gusso · lucasgusso.com · Publication date not stated (Page shows 'Agenlab · 2026' only; linked from his X post of 27 Oct 2026.) · Checked Oct 29, 2026
Author's own portfolio case study (self-promotion: the portfolio says he is open to full-time roles and select freelance). The Agenlab site and a Figma file are linked from it.
Access: open
Source check: Reviewed by a 4TC editor on Oct 29, 2026. Claims, quotes and dates re-checked against the sources by Ella on 29 Oct 2026. Nobody at 4TC has tested this.
Claims and where they come from
- Three days after he started, the whole 15-page site was in Webflow; a site like this usually takes him 'three weeks or more', which he puts at 'about 85% less time'. (reported) [1][2]
- The Webflow MCP 'failed quietly': it would report a style as saved and the page wouldn't change, and some elements it couldn't make at all. (reported) [2]
- He built elements by hand in the Designer, saved the JSON Webflow puts on the clipboard, compared it with what the MCP had made, and put every gap in a log the agents read before they touch the site. (reported) [2]
- For the few things only a paste can build he made an HTML-to-Webflow converter that writes the same JSON format Webflow copies to the clipboard. (reported) [2]
- Every section went through a 'lab': four agents built four versions on the real page, he picked one and fixed what bothered him, and each fix became a rule. (reported) [2]
- Before any section, the agents set up the variables and a style guide page in Webflow. (reported) [2]
- He reports 34 sections, 116 interactions, 7 components, 4 CMS collections and 81 variables, all native and editable in the Designer, plus a Figma file built alongside with the Figma MCP. (reported) [2]
- A lighter subagent pushes one approved section at a time and checks its own work before the next. (reported) [2]
- The Agenlab site linked from the case study was live at agenlab.webflow.io when 4TC checked on 29 Oct 2026; its page title reads 'Agenlab - Webflow HTML website template', and the case study names no client. (checked by 4TC) [2]
4TC interpretation
Our reading, not something the source says.
Agent-built sites often end up as custom code a client can't edit. This shows where the Webflow MCP fails quietly, how he checked it, and how he kept taste and editability in his hands.
Designer impact
Established [2]
Agent tools can report success without changing the page ('failed quietly').
- Check each MCP write in the Designer before trusting it.
- Keep a log of calls that fail and have agents read it.
Established [2]
Cost and speed: he says pushing a whole site through the Webflow MCP is 'slow and expensive'.
- Push one approved section at a time and check it before the next, as he does.
- Estimate model costs before quoting a client a faster timeline.
Established = documented by primary sources or the company’s own statements. Disputed = contested with evidence on both sides. Alleged = reported, not established.
Votes rate whether this entry was useful. They are not an endorsement of the tool, and don’t mean voters agree with the company’s practices.
Report an issue or correction
Share your own experience
4TC does not endorse a tool unless an explicit 4TC endorsement is shown.