AI has made it possible for almost anyone to create almost anything. Tools like ChatGPT and Claude can turn a few sentences into a full-page layout.
That has opened faster ways to prototype and build for web professionals, and it's also put those same tools in the hands of their clients. Where a client might have once sketched on a napkin or sent a link to a site they liked, more of them now arrive with a page design they've built themselves.
It came up during our October 15, 2026 Office Hours with Nathan Ingram, and judging by the chat, plenty of agencies have already been there. For anyone who hasn’t, as Nathan put it, "your time is coming."
The good news is that this isn't a problem to fend off. A client who shows up with an AI design has already done some of the thinking, and they're excited about their site. What they need from you is the experience to turn that design into something that works.
In this post we'll look at how to respond, what AI-made designs tend to miss, and how to bring one into the client's site.
The Office Hours question that started it
The topic came up during the Office Hours when a viewer asked how to work with a design their client had made in ChatGPT:
My client has decided to 'redesign' a page with ChatGPT. I use Claude. What's the easiest way for me to get that info to Claude from ChatGPT? I did try bringing it into Chrome via the link and using Claude in Chrome, but it's not complete.
On the surface, it's a practical question about moving a design from one AI tool to another, which we'll discuss later in this post. Before Nathan got into it, though, he paused to ask the chat how many others had been in the same position. Roughly half of the audience said they've gone through something similar.
Once it was clear how common this has become, he spent most of his answer on a bigger question: how agencies should respond when it happens.
Your client's AI design is a head start, not a threat
It's perfectly natural to feel territorial when a client hands you a finished-looking design, especially when building sites is your job. Nathan's advice was to forget that feeling as early as possible:
Let me urge you not to be offended. This is people getting excited using technology, and I'm all for that.
A client who has spent an evening designing their own homepage is invested in the project. They've thought about what they want the site to say and how it should feel. That in itself is a clearer brief than many projects start with.
Nathan suggested treating the design as exactly that, a starting point: "This is a great start for a design. But maybe there's some tweaks or whatever." Your role shifts from creating everything from scratch to guiding the client through what comes next, which Nathan described as education.
That role matters more as clients gain access to more powerful tools. The design gets the conversation going and your experience is what makes it work. Treating it as a threat only risks discouraging a client who came to you excited about their project.
What AI designs usually miss
Anyone who’s generated something with AI knows the result can look finished at first glance. Look a little closer, though, and you start spotting the extra fingers.
According to Nathan, there are likely things that "neither [the client] nor their AI tool have thought of," and they tend to fall into the same few areas:
Responsive behavior: A layout that looks perfect on a laptop can fall apart on a phone or a tablet, and AI tools rarely get it right on the first pass.
Accessibility: AI tools don't build accessible designs by default. As our viewer pointed out in the chat, you have to specifically tell the AI to make the design accessible. Most clients don't think to do that the first time around.
Borrowed looks: That same viewer also noticed that her client’s design borrowed elements from their competitors’ sites. An AI tool trained on existing websites is likely to echo them more closely than anyone intended.
The parts below the waterline: Sitemaps, social share previews, 404 pages, and form spam protection will not show up in a mockup, so they are easy to forget about.
None of these gaps makes a design inherently bad. However, they are things a client can't see from a screenshot or a mockup. For a useful checklist of those "below the waterline" items, Nathan shared a resource from WebDevStudios earlier in the same session: ItLooksDone.com. It walks through what a site that appears done can be missing on launch day.
Spotting these gaps is exactly where an experienced web design agency comes in, and where you can both educate your client and help them improve their website.
How do you talk the client through the changes?
Once you've reviewed the design, the conversation with the client is what will set the tone for the rest of the project. Nathan's approach is to start positively and constructively: "Sure, we can work with this. Let's massage it a little bit."
From there, you can raise the gaps as part of improving the design, not as a list of mistakes. If the layout resembles a competitor's site, for example, Nathan suggested simply pointing it out: "This is a great design. Did you notice how it's similar?" That opens a discussion instead of a debate, and it's part of the work AI can't do for the client.
As Nathan put it:
It's the human element of walking the client through the decision-making process. That's where we live today. In all this technological change, we're the bridge between the client and the implementation of technology.
There are a few key points worth covering in the conversation:
How the design will look on phones and tablets.
Who needs to be able to use the site, including visitors who rely on screen readers or keyboard navigation.
Whether any part of the design looks too close to another brand's site.
What happens behind the scenes, such as search visibility, forms, and how the page shares on social media.
Handled this way, the client still feels ownership over their design, and you get room to make it production-ready. It also shows them the value of working with someone who knows what to look for.
Moving the AI design to your own tools
Let's go back to our initial viewer's question: how to move the design from their client's ChatGPT session into Claude, the tool they use for their work. They tried opening the link in Chrome and using Claude in Chrome, but that didn't yield the whole design.
Instead of offering some convoluted method of forcing ChatGPT and Claude to work together, Nathan suggested keeping it simple. ChatGPT should be able to export the design as an HTML file. And if the design is loaded in a browser, you can point Claude straight at it. As Nathan explained: "It's just HTML. It'll just digest the HTML."
For this type of job, he'd skip Claude in Chrome and give the URL to the Claude desktop app, which has its own in-app browser. According to him, it will "load the HTML and all the assets simply by virtue of going to the URL and loading the page."
Once you have it in your tool of choice, expect to iterate. Nathan was candid about how this usually goes:
A lot of times these AI agents are pretty good at coding around all of the weird little responsive things. But I've never, not once, had it do it right the first time. So I've always had to iterate.
When he built an event landing page for a client in Claude, it took him around 30-45 minutes of back and forth to get it the way he wanted, even though the first version was "probably 90-plus percent the way there." The final stretch is where the experience counts. "I've been doing this for 30 years, and I know what to look for," he said. Knowing what to look for, and how to fix it, is what gets you from a good first draft to a finished page.
Bringing the design into the client's WordPress website
Before the design goes anywhere near WordPress, make sure it works everywhere. Nathan's advice is to "make sure all of the CSS is built at all of your viewports before you move it into WordPress." That way you're working with a finished design instead of troubleshooting layout issues inside the site.
From there, the design doesn't need to live on a separate platform or replace the site. A WordPress page template can display it on a page of the existing site, just as Nathan's team did with that event landing page. "It's not anything like the rest of their website at all," he said, "but it lives on a page of their website."
Your AI tool can handle the conversion for you, too. As Nathan explained:
If you tell Claude, I want to do what Nathan just said, it'll show you how to do it. It's actually very easy for an AI tool to do. It's a small file.
Where to go from here?
Clients designing their own pages with AI isn't a passing trend. Agencies that respond with curiosity rather than with caution will be in a better position to keep those clients.
Treat the design as a head start, look for the gaps the client couldn't see, and use a page template to bring the result into WordPress. The client gets a site that looks the way they imagined, and you get to deliver one that works.
If you're thinking about how AI fits into the way your agency works with clients more broadly, our Office Hours Q&A on AI in client delivery is a good next read. And if you have a question of your own, you can submit it at WPNathan.com and join us live for Office Hours, every Thursday at 2 p.m. ET.
FAQ
Should a project cost less if the client already made the design?
Not necessarily. A client’s AI design can save time on early layout work, but reviewing it, fixing responsive and accessibility gaps, and making it production-ready still takes expertise.
This is one reason many agencies price by project instead of by the hour: the client pays for the outcome, not for how long each step takes. If the design genuinely reduces the scope, adjust the quote to match. Just don’t assume a finished-looking mockup means the work is mostly done.
Will a custom page template survive theme updates?
Yes, if it lives in a child theme. Parent theme updates don’t overwrite child theme files, so the template stays in place. If the client later switches to a different theme, though, the template goes with the old child theme and will need to be moved or rebuilt.
What if the client keeps redesigning in ChatGPT after launch?
Agree on a process early. Once the design is live, the WordPress page is the version that counts, and changes should go through you so they get the same responsive, accessibility, and launch checks as the original. That way, a quick experiment in ChatGPT doesn’t turn into a live page with the same gaps you just fixed.