Your First Build

One description in, a working product out, while you watch it assemble

Start with one message

Open Projects and tell the Builder what your business is, the way you'd tell a person: “I run a cookware shop in Tel Aviv” is enough. If you have a website, mention it or just include the name, the Builder finds the site on its own, reads it, and comes back knowing your colors, your tone, and what you sell. You don't fill in forms, and you don't pick from templates.

From that first message the Builder works like a colleague sharing their screen: the right-hand panel is a live build theater where the brand board appears first, then your components render one by one, then full screens. Everything you see there is real and already saved, the sidebar tabs (Brand Studio, Screen Builder, Elements) are live views of the same objects, not previews.

It asks little, and asks well

The Builder prefers acting on its best reading and telling you what it assumed. When it does need you, the question arrives with clickable options, where your product data should come from, whether your customers need accounts, whether to add a human contact for escalations. Click an answer or type your own; either way the build continues immediately.

If the Builder ever needs an API key for one of your systems, it opens a secure field in the chat. What you paste there goes directly to an encrypted vault, it never appears in the conversation and is never shown to the AI or to anyone again.

Real data before anything else

The Builder connects data in a strict order of preference:

Your store's live feed first. Shops on Shopify, WooCommerce, or Squarespace are usually connected automatically, prices, stock, and photos stay current because every answer reads the store directly.
Your systems and files next. A booking engine or inventory API can be connected live; a catalog can be attached as CSV, Excel, PDF, or photos right in the chat.
Samples only if you choose them, and they're always marked as samples, so nothing invented ever looks real.

One thing the Builder will not do is copy products off your web pages by eye, a transcribed catalog looks convincing and is quietly wrong. Pages teach it style and structure; data comes from a source that stays true.

The finale, and everything after

A finished build ends in the theater with two tabs: the Playground, where you experience the product as a customer would, answered by the real agent on your real data, and an Overview of what was built. The Agent tab maps everything the agent knows, uses and is served on. From there, publishing is one click.

Nothing about the build is final. Tell the Builder what to change, “make the cards rounder”, “add a sale section”, “here are new prices” with a file attached, and it updates the data, then rethinks whatever presents it. The conversation itself is saved with the project: close the tab, come back next week on another device, and continue where you left off.