We added a button to Claude Design.
Or: how "Send to Wix" takes a static design and gives it a live business backend in one click.
Until recently, getting a Claude Design project onto a working Wix Headless site meant a detour through your terminal. Export the design, open a coding agent, ask it to scaffold a Wix project, wait while it ran the setup, installed the apps, wired the SDK, and released. It worked, but every step was a place to lose someone.
This week, the whole sequence collapses into a button.
Open any Claude Design project. Hit Share → Send to.... You'll see a new destination - Wix Headless. Click Send. About fifteen seconds later, you have a live hosted site and a dashboard to match.

What happens behind the click
The design is bundled, uploaded, and imported into a fresh Wix Managed Headless project. The project is provisioned with:
Hosting, SSL, global CDN. Your live URL is ready immediately — something like instant-dbfbac896c5f-gonenj.wix-site-host.com, ready to be pointed at a real domain whenever you are.
A managed dashboard at manage.wix.com/dashboard/... — the same Business Manager that runs the rest of Wix, already provisioned for your project.
Business APIs wired into your tenant. Commerce, Bookings, CMS, Members, Identity. Dormant until you activate them, but already pointed at the project you just sent.

You didn't export anything. We didn't write a custom connector. The two products talk directly.
What "Headless" delivers in the click
This is the part worth pausing on, because it's easy to miss what just happened.
A design is a static artifact. HTML, CSS, maybe a sprinkle of JS. The bundle you uploaded knows nothing about authentication, payments, scheduling, or content management. Most "design-to-site" pipelines stop here - they hand you a hosted page and charge a flat monthly fee for it.
Send to Wix doesn't stop there. The project on the other end is a full Wix Headless project: the same backend that runs a yoga studio's bookings, a boutique's storefront, a publication's CMS. Your design is the frontend. The dashboard you just got handed is the rest of the business - waiting until you ask for the parts you need.
The continuation path
Press Visit your site and your design is live on Wix's CDN. Press Open dashboard and the empty Business Manager is waiting - products, services, blog posts, customers, all the surfaces unactivated.
The destination page also hands you a prompt:
Build on what I started with Wix Headless.
Download my project files and build out its features
Using wix-headless.dev
Paste it into Claude Code, Cursor, Codex, or anything else that can read the Wix Headless skill. The agent picks up your project, reads the skill, and starts wiring the dashboard you just provisioned into the design you just sent. A products grid becomes a real catalog. A schedule becomes real bookings. A blog post becomes a rich document served from the same SDK that's serving this post to you.
One click, one direction
The honest version of this integration: Claude Design and Wix Headless are two products that previously talked through a coding agent. Now they talk through a button. The button itself is a small thing. What it unlocks - going from a sketch in a chat to a hosted business backend in fifteen seconds - is not.