Core onboarding · 3 of 6

Review your first build.

The first preview is a working draft, not a promise to keep every detail. Check the customer path first, then use the result summary to decide the next focused change.

5 minutes · Updated September 2026

Check the path a customer will take

Open the preview and act like the first customer. Can you find the offer, complete the main action, and reach a saved result? On a mobile screen, check that the primary button and the next step remain visible without guessing.

PreviewSee the customer and operator surfaces.

Completion summaryRead what was included and what remains a test boundary.

One focused requestDescribe the next improvement in everyday language.

Check againKeep the core path intact after each change.

Use the completion summary

After creation, the conversation explains the scope, points to the preview, and reminds you that login is needed to save and publish. It also identifies where live payments, personal data, and permissions require approval and verification rather than an assumption.

Ask for a focused change

Say what should be different and where it belongs: “Add a capacity indicator to each workshop card,” “show the booking status in My Bookings,” or “make the operator queue show pending requests first.” You do not need to name components or files.