Claude design conversion
Your Claude design, built as a real website.
You made something good in Claude. We rebuild it in WordPress or Next.js with a database, a CMS, a responsive layout and hosting, so it stops being a prototype and starts being a website.
What we can convert.
If you can send it to us, we can usually build it.
A Claude artifact
The working prototype you built in a conversation. It runs, people can click it, and it stops at the edge of the page it lives in.
A Claude design
A generated page or interface you are happy with, in code or as a mockup, that needs to become a site anyone can visit.
A ChatGPT image mockup
A homepage generated as a picture. There is no layout underneath it, so it gets redrawn as one.
A v0, Lovable or Bolt project
A build that started fast and became hard to change. We take it off the generated scaffolding and make it maintainable.
A Figma file
Approved designs, AI-assisted or not, built as responsive front ends that keep the detail the designer intended.
A screenshot of something you like
A reference rather than a file. We design the gap between it and your brand, then build the result.
Why the artifact is not a website yet.
It looks finished, which is the problem. Here is what is missing underneath, and what each one costs you.
It has no database
State lives in the page. Close the tab and whatever anyone typed is gone, and two people never see the same thing.
Nobody can log in
There are no accounts, no permissions and no way to tell one person from another, so there is nothing to keep private.
The content is hard-coded
Changing a price or a headline means changing the code. You wanted a site you could edit without calling a developer.
It was built at one width
Generated layouts are tested at the size they were generated in. On a phone, where most of your traffic is, it usually falls apart.
Search engines cannot read it
No titles, no descriptions, no headings in a sensible order, no structured data and often nothing in the HTML until JavaScript runs.
It cannot take real traffic
No hosting, no domain, no backups, no error tracking, no security and nothing watching it at three in the morning.
What you get back.
A real codebase or CMS
WordPress when the client wants to edit everything themselves, Next.js when the product needs to do something a CMS cannot.
Content you can change
Text, images and pages editable without a developer, in an admin your team can be shown in ten minutes.
A responsive, accessible build
Tested at phone, tablet and desktop widths, with keyboard focus, contrast and semantics handled rather than assumed.
Technical SEO in place
Titles, descriptions, headings, canonical URLs, sitemap, Open Graph cards and structured data, so the pages can actually rank.
Live, on your domain
Deployed with SSL, backups, analytics and error tracking, on hosting that fits the build rather than whatever was cheapest.
Handover and documentation
Repository, accounts and credentials are yours, with notes on how it works. Nothing is locked to us.
WordPress or Next.js.
The right answer depends on what the thing has to do, not on which is newer.
WordPress
When the point is content you change yourself: a business site, a blog, a brochure, a shop on WooCommerce. You get an admin anyone on your team can use, and a theme built from your design rather than a page builder bolted on top.
WordPress and storesNext.js
When the product has to do something a CMS cannot: accounts, dashboards, calculations, an API, AI features. Most artifacts worth converting land here, because they were already an application pretending to be a page.
React websitesHow a conversion runs.
- 1
Send us the artifact
A link, a file or a screenshot is enough. We look at what is really in it and what it is pretending to do.
- 2
A written plan
What gets kept, what gets rebuilt, which stack and why, what it costs and how long it takes. Before you commit.
- 3
The build
Rebuilt properly, with a staging link you can open at any point and show to whoever needs to see it.
- 4
Launch and handover
Domain, hosting, SSL, analytics and backups, then the keys and a walkthrough of how to run it.
For agencies
Your client built it in Claude and now expects a website.
We do these conversions white label, under your brand, with the terms agreed before anything is shared.
Agency partnershipsQuestions.
Can you turn a Claude artifact into a real website?
Yes. An artifact is a working sketch: one page, no database, no accounts, no CMS. We rebuild it as a deployed site or application with the parts a real product needs, keeping the design and the behaviour you already approved.
Do you keep the design, or start again?
We keep what you liked. The layout, type and behaviour carry over; what gets replaced is the generated markup underneath, so the result stands up to real browsers, real devices and real traffic.
WordPress or Next.js, which should I choose?
WordPress when the point is content you edit yourself: a business site, a blog, a shop on WooCommerce. Next.js when the product has to do something a CMS cannot, such as accounts, dashboards, calculations or an API. We recommend one after seeing the artifact, and we will tell you if the cheaper option is the right one.
How long does a conversion take?
A single generated page is typically a few days. A multi-page site is usually one to three weeks. An artifact that becomes a real application with accounts and a database takes longer, and we give you a written estimate after looking at the file rather than a number before.
What does it cost?
It depends on what is in the artifact and how much of it has to become real. You get a written, fixed quote after we have looked, and we will say plainly when a rebuild is cheaper than a conversion.
Can you add a database, logins and payments?
Yes. Accounts and permissions, a database, payments through Stripe or similar, admin views, email and third-party integrations are the usual things a prototype is missing.
Will it be fast and good for SEO?
That is a large part of the job. Generated pages tend to ship heavy markup, no metadata and nothing for a crawler to read. We rebuild for Core Web Vitals, add titles, descriptions, headings, sitemaps and structured data, and test the result.
Who owns the finished site?
You do. The repository, hosting, domain and accounts are in your name, with credentials and documentation handed over at the end.
Do you work with agencies on this?
Yes, white label. Your client never has to know we exist. The terms are set out on our agency partnerships page.
Send us the artifact.
A link or a screenshot is enough to start. You get a written plan and a fixed quote before anything is built.