- 3 days ago
- 5 min read
When Rafal's friend needed an online store, he turned to the stack that wouldn't compromise efficiency or quality, Wix Headless for the business, Google Stitch for the design and Claude Code to build it. He scaffolded a full production storefront by end of day one.
Since then, Solitairec has processed $25,000 in gross payment volume and logged over 217,000 API calls. Here's how it was built, and Rafal's takeaways for developers thinking about their next project.
TL;DR
When Rafal Koziarz's friend needed an online store, he turned to Wix Headless and scaffolded a full production storefront by end of day one.
The stack: Google Stitch for design, Claude Code for implementation, Wix Headless for everything behind it. Since launch, solitairec.com has processed $25,000 in gross payment volume, logged over 217,000 API calls and grown sales by approximately 30% month-over-month.
Keep reading to learn how it was built, and what other developers can take from it.
Learn: what is Wix Headless?
The problem wasn't building a store, it was not wanting to build everything else
"It feels like I don't have any backend to test. I rely a lot on the SDK which makes development a lot smoother." - Rafal Koziarz
In today's AI-first world, where agentic commerce is changing how stores are built and run, the question isn't can this be built from scratch, it's whether it's worth the time, tokens and cognitive load to rebuild something that already exists and works extremely well. For Rafal, the answer was short: no.
Wix's Business Manager and Wix SDK, delivered to his agent via the Wix MCP, wired up his custom frontend fast. solitairec.com was online with a new storefront by the end of the first session.
Learn more:
Why Wix Headless and not another option?
"I found the experience simple... I did actually enjoy working with the product." - Rafal Koziarz
There are alternatives: a custom stack with Stripe and a headless CMS, pure Shopify, a full Next.js build wired to a separate backend. What made Wix Headless different came down to two things.
The backend was already there
Advanced eCommerce platform, auth, CMS, email: all of it on Wix's infrastructure. No database to provision, no auth service to configure, no email provider to integrate. The SDK is the surface; Wix is everything behind it. Build on enterprise-grade infrastructure that keeps any site fast, secure and online with nothing to set up or maintain.
His partner can manage it herself
Product catalog, collections and content all through the Wix Dashboard, no developer required. For a solo dev building for small businesses, a business manager the client actually understands is a genuine force multiplier. Rafal writes code. His partner manages inventory. Neither blocks the other.
The stack: Claude Code + Google Stitch + Wix Headless
This is where it gets interesting for anyone thinking about how AI-assisted development: vibe coding, agentic coding, whatever we're calling it this week, changes what's possible.
Google Stitch handled UX wireframing. The key move: Stitch exports brand guidelines as a DESIGN.md file, an agent-friendly markdown document. That file goes directly into the LLM context, so the agent works within the actual brand's visual system from prompt one, not a generic scaffold.
Claude Code did the heavy lifting on implementation. Scaffold, iterate, test - all through the agent. With the Wix SDK's TypeScript typings, Claude had enough structure to generate reliable, idiomatic code rather than falling back to raw REST calls.
Wix Headless was the platform. The SDK handled commerce, CMS and auth. The frontend was Rafal's to decide, he went with Vercel. Business logic: pricing, inventory, checkout, customer identity, already in Wix, already working.
The Stack Behind a Day-One Storefront:
Layer | Tool | What it did |
Design & Brand | Google Stitch | Exported brand guidelines as DESIGN.md for agent context |
Implementation | Claude Code | Scaffolded, iterated and tested the full frontend |
Backend | Wix Headless + SDK | Commerce, auth, CMS, checkout, all handled |
Hosting | Vercel | Frontend deployment |
Client Management | Wix Business Manager | Product catalog, CRM, inventory |
The combination is the point. Stitch fed brand context to the agent. Claude Code turned it into working components. The last third of the project was wiring, not rebuilding.
What he didn't have to build
"Version one only took a day... it relies a lot on the checkout and the login which is still Wix, and the front end is described by the LLM already."
Rafal didn't build an auth system, Wix handles login, sessions and identity. He didn't build a checkout UI, Wix Payments manages the payment flow. He didn't build a CMS or an admin panel, his partner has a full product management interface in the Wix Dashboard, alongside CRM, coupons and transactional email tools.
Rafal's job was to connect the dots. That's it.
Was it worth it?
solitairec.com wasn’t just a one-off build for Rafal. As his partner scales the business and expands its global footprint, the infrastructure has to keep pace. By choosing Wix Headless, he’s already hit several production milestones:
High performance. Lighthouse scores consistently between 80 and 100.
Efficiency. Running costs are maintained at a lean ~$50 USD per month.
Global reach. Organic traction across Canada, Saudi Arabia, and Asia.
Polished UX. A refined interface with near-zero dead clicks.
Growth. Initial sales increased by approximately 30% month-over-month.
Would Rafal choose the same stack again? The answer is an unambiguous yes. He dives deeper into the technical execution and the results in his post-launch writeup on his personal blog.
Explore more Wix Headless user stories:
Want to try Wix Headless yourself?
Paste wix-headless.dev/skill.md into Claude Code, Cursor or any AI tool you already use, and your project is connected to the full Wix backend instantly, no servers, no backend engineering, no slowing down.
Frequently asked questions about Wix Headless
What is Wix Headless?
Wix Headless is the only headless solution that natively combines a CMS, eCommerce, payments, bookings and events in one place, no stitching, no third-party integrations, no separate vendors. You build your frontend on any AI coding tool or code stack, connect it to the full Wix business backend in one prompt and manage everything from a single Wix Business Manager dashboard. No servers to run, no backend to engineer.
Can you build production eCommerce store with Wix Headless in a day?
Yes, with the right stack. Using the Wix MCP to wire up the Wix SDK, an AI coding agent like Claude Code to scaffold and implement and Google Stitch to generate brand-aligned design context, a developer can connect a fully functional storefront, with checkout, auth, CMS and product management to the Wix backend in a single session. Wix handles all the business logic behind the scenes.
What is the Wix MCP and how does it help developers?
The Wix MCP server exposes all core Wix platform capabilities as structured, callable tools for any MCP-compatible AI client. It gives AI agents direct, accurate knowledge of the Wix APIs without manual documentation lookup, so developers can scaffold, iterate and implement faster. It supports headless development, app building and site management workflows.
