Design and build a professional ecommerce site. In 4 days.

A little. If you've opened up Claude Code or Cursor and tinkered — even if you never finished what you started — you'll be fine. You don't need to write code unaided, and you don't need to have shipped anything.

What the sprint doesn't do is start from zero. Day 1 begins with the brief and project setup rather than with tool installation, and a short setup video handles tools and environment beforehand. If you've genuinely never heard of Claude Code, you'd spend the week catching up instead of building — join the waitlist for the next AI site building sprint, and this one will make far more sense afterwards.

It's also not a sprint for expert developers. Most of the room will be designers who've dabbled and want to go further.

Normally Shopify runs both halves of a store: the shop front customers see, and the admin the owner logs into. A theme controls the first half.

Headless splits the two. You build the front end yourself, so it looks and behaves exactly as you designed it. Shopify keeps doing the parts you don't want to be responsible for — products, inventory, payments, checkout, tax — and your client still gets the standard admin they'd have had anyway.

In practice that means you can take on a store without taking on the risk that usually comes with one.

Day 1, and it takes the whole day. You'll work from a client brief — Julian designs a storefront live from a mock one, then hands you the prompt to write your own — and turn it into a direction specific enough for an agent to build against.

That's the real skill here. Agents rarely fail because they can't write the code; they fail because nobody told them what good looks like. Day 2 is where the brief becomes working, responsive code, and you're directing it the whole way.

The main cost is a Claude Pro subscription (~$20/m), which is required to use Claude Code.

Shopify is free for the sprint: a Shopify Partners development store costs nothing and has no time limit. You only need a paid Shopify plan when a store starts taking real orders. Everything else (Node, GitHub, Vercel) is free on the tiers we use.

No. Day 1 is design, but it happens as a brief and a direction rather than as artboards — and Day 2 turns that straight into code. If you'd rather start from something you've already drawn in Figma, bring it and build from that instead.

Neither. Day 1 gives you a mock client brief to work from — or you can swap in a real project if you have one waiting. Then on Day 3 you'll spin up a fresh development store through the Shopify CLI and stock it with sample products, so everyone builds something real without needing a live business behind it, and the agent handles the setup work rather than you clicking through settings screens.

If you do have a client project in mind, you can use their products instead — and a Partners development store can be transferred to the client later when they're ready to go live.

All sessions are recorded and available right after they end. The chat platform runs Monday through Sunday, so if you need to catch up over the weekend, support will still be there.

1 to 3 hours per day covers the lesson, the build and the live session. The sprint runs four consecutive days, Monday September 7 through Thursday September 10, and support continues through the weekend if you need to catch up.

A working headless storefront: a front end you designed in code, pulling products, prices and inventory from Shopify, with a functioning cart and Shopify's own checkout handling payment.

It's a demo store with sample products — you don't need a client to take part — but it's built exactly the way a client project would be, and deployed live by the end. Use it as a portfolio piece, or as the template for the first one you sell.

That's the point of building it this way. Products, prices, inventory, orders, discounts and shipping all live in the standard Shopify admin, so anything a store owner normally does day to day, they do without touching code or calling you.

What still needs you is design and layout changes to the front end — which is the work you'd want to be paid for anyway. Day 4 covers what to document and hand over so the line between the two is clear from the start.

The workflow we teach works with other providers like Codex or Gemini, but all demos use Claude Code. If you prefer a different tool, you can still use the same framework but will have to install the CLI on your own (we will include links to 3rd party tutorials)

Yes. Lifetime access to all lessons and office hour recordings is included.

If you're not satisfied by the end of Day 2, reach out and we'll refund you in full. No questions asked.