{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Fsurvive-and-thrive.simplecast.com%2Fepisodes%2Fai-broke-our-clients-website-heres-why-5MVo40lb","width":444,"version":"1.0","type":"rich","title":"AI Broke Our Client's Website. Here's Why","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/e5e37d85-25a3-4f11-a7e5-abcc974a9c31/af8b39f3-b366-412b-8fe3-1f89da83c03e/cropped_1791509138038.jpg","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/f59ca4e7-a4ad-4c4e-8af8-eec8a44581ff\" height=\"200\" width=\"100%\" title=\"AI Broke Our Client&apos;s Website. Here&apos;s Why\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"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.\n\nIn 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.\n\nThis one is for marketing teams thinking about giving AI publish access, especially if nobody on the team can read the code it writes."}