One of our clients is a marketing team of one, and he publishes to his Webflow site with Claude all the time. Another client had Claude write custom front-end code for a launch on a site we didn’t build, and it broke the entire site. Same AI both times. One got a faster publishing workflow, the other got six hours of emergency repairs. In this episode, Symon and Marcello dig into what decides which way it goes when you connect AI to a website you already have. This isn’t an anti-AI take. It’s the more useful one: the AI only behaves as well as the site and the guardrails around it. Where they land is that a design system tells the AI what to follow, and governance decides what it’s allowed to touch. Marcello thinks the site does most of the work. Symon thinks you need both. This one is for marketing teams thinking about giving AI publish access, especially if nobody on the team can read the code it writes.
💡 Key Topics:
✦ How normal this already is: 84% of people who build and run company websites use AI for it (Framer State of Sites, 1,900+ respondents, from a company that sells a website builder)
✦ The pressure behind it: 100% of marketing teams that can’t adopt AI fail to deliver projects on time or on budget (Webflow, 1,000 director-level leaders at 50+ person companies, from a company that also sells AI)
✦ What a proper setup gets you: pages going up 10x faster at about 90% design fidelity on client sites with real systems in place (Tennis client work)
✦ The “almost right” problem: 60% of developers have hit AI solutions that are almost right but not quite (Stack Overflow developer survey), and they can read the code. Your marketing team probably can’t.
✦ Rules vs. barriers: a design system tells AI what to follow, while limiting it to approved components stops it from going anywhere else
✦ Why the “CMS is dead” crowd has it backwards, and why the teams using AI well work through the CMS instead of around it
✦ Marketers already check AI writing by hand: 80% review AI content for accuracy (Ahrefs, 879 marketers), because that’s writing they can read. Code is a different story.
✦ The one test to run this week: ask AI to build a single page using only what’s already on your site. If it invents a new button style or font size, fix that before you give it publish access.
📖 Chapters:
0:00 — AI broke the site: six hours
1:03 — Connecting AI to your existing site
2:56 — What happens on real client sites
4:31 — Governance: rules, barriers and design systems
6:26 — Is the CMS dead?
7:58 — Where to start, and the one test
9:48 — Tell us what you’re one-shotting
🌐 Tennis web design & development services: https://www.designtennis.com/services/website-design-and-development
🎧 Spotify: https://open.spotify.com/show/7tufP8mSXC1YrLxrLzw3Ju?si=3839798c83264d9b
📸 Instagram: Tennis.digital
💼 LinkedIn: https://www.linkedin.com/company/designtennis/
🔔 Subscribe for weekly episodes on web design, digital strategy, and building better businesses.
#aiwebsites #webflow #claude #designsystems #aigovernance #cms #framer #marketingops #oneshotting #adigitalstrategypodcast