One day in the room, four 90-minute blocks. You walk out with a working CRM running live on your own domain. This is the build plan for the Saigon retreat on June 20.
The content is proven, we have run these retreats many times. What makes the day work is how it flows. Four ideas shape every block.
One thing at a time. Each block hands you one thing to do, then you come back ready for the next. A single guided prompt can carry you the whole way, and that is the part that surprises people most.
Nothing on paper. Every step is a real interaction with the AI. No worksheets, no note-taking exercises. You run a prompt, you pick from what it shows you, you set your colors, you build. If it is not happening in the AI, it is not happening.
Fewer choices, faster building. You do not have to choose features, tech, or architecture. It is a set menu, not à la carte. The only choices you make are made once, up front, in the interview. When you are hungry you want to eat, not study twenty options.
Every block ends with something real. The output of each block is an artifact you can point to. A product plan. A live prototype. A working CRM. You leave every block with proof, not notes.
The day runs 9:00 AM to 5:30 PM, with engineers in the room the whole time.
The 100-hour shift. Building used to be 20 hours of planning and 80 hours of building. Now it is 20 hours of planning and about 5 hours of building. The plan is still the hard part, so you still have to do it. But the build runs fast, and your real job becomes review and iterate. That is what you will feel today: most of your time goes into the plan and setup, then the build flies.
The full AIO CRM has four parts. For the one-day format we focus on the spine so you finish with something live. Everyone builds the same core; the only variation is up to three custom attributes you add to your own data model in the interview.
Orders and a newsletter add complexity we leave out so the build stays clean and you finish, the single contact form is enough to prove the flow. You will see the full AIO CRM demoed so you know where this can go, and you take home the full prompt pack, the prompts to build everything you saw, in your own time.
This is the part that matters most. Get the design system and product plan right and everything after is just /goal build it. You run the interview at the end of Block 1, about 20 minutes. It asks a few simple questions, shows you three very different design systems to choose from, takes your brand colors if you have them, lets you add up to three custom attributes, then writes your product plan as two builds.
What you do after running it: save the product plan file on your computer. Create a folder called Code Projects, and inside it a folder called Working Files. Drop the plan there. That is your Block 1 deliverable.
# Product Plan Interview
You are my product partner. Interview me, then write my product plan.
Ask ONE question at a time. Keep it short. Do not move on until I answer.
1. What is your business, and what do you sell?
2. What kinds of inquiries come in to you? (for example: general,
coaching, keynote)
3. Pick your design system. I will show you three. Reply with one:
A) MINIMALIST APPLE: clean, lots of white space, calm and premium.
B) BOLD FERRARI: high contrast, confident, energetic, strong color.
C) ACADEMIC: serious, structured, editorial, trustworthy.
4. Do you have brand colors? If yes, PASTE the hex codes (do not just
describe them). If no, say "use the design system defaults."
5. Your CRM stores People and Contacts by default. Do you want to add
up to THREE custom attributes to a person record? For each one tell
me: the name, and whether it is free text, a dropdown, or a date.
6. What domain will this live on?
When I have answered everything:
- Apply my chosen design system and colors.
- Write my PRODUCT PLAN as a single markdown file with two clearly
labeled sections: "BUILD 1" and "BUILD 2".
- BUILD 1 = data model (People, Contacts, plus my custom attributes),
a verified admin login and password, a contact form on the live
site, and ONE admin page so I can log in and see the leads that
land. Goal: I can run the full flow end to end (submit a lead, log
in, see it).
- BUILD 2 = the rest of the /admin back end (view members, view
inquiries, manage the inquiry pipeline) PLUS a confirmation email
wired through Resend.
- Embed everything you need to execute each build directly inside the
plan, so that later I only have to say "/goal build 1" and "/goal
build 2".
Show me the finished product plan, then tell me to save it in my
Code Projects / Working Files folder.You choose from three design systems, shown as the real .md files so you see the look, not a description. They are deliberately different. This is the only design choice in the whole day, and you make it once.
# Design System: Minimalist Apple
Feel: calm, premium, uncluttered.
Color: near-white background (#FFFFFF / #F5F5F7), near-black text
(#1D1D1F), one restrained accent.
Type: large clean sans-serif, generous line height, few weights.
Space: very generous white space; lots of room around everything.
Components: soft rounded corners, hairline borders, subtle shadows,
flat buttons.
Use when: the brand wants to feel trustworthy, modern, and quiet.# Design System: Bold Ferrari
Feel: confident, energetic, high-performance.
Color: strong dominant brand color, high contrast against dark or
white, decisive accents (no soft pastels).
Type: heavy display headings, tight tracking, strong hierarchy.
Space: dense and purposeful; nothing timid.
Components: sharp or slightly rounded corners, solid fills, bold
buttons, clear active states.
Use when: the brand wants to feel powerful and stand out.# Design System: Academic
Feel: serious, structured, editorial, trustworthy.
Color: navy and ink on warm white, restrained accent, muted palette.
Type: a serif for headings with a clean sans for body; clear,
document-like hierarchy.
Space: structured columns, consistent rhythm, table-friendly.
Components: square corners, ruled lines, understated tables and pills.
Use when: the brand wants to feel established and credible.By the end of this block you have a product plan, and that plan includes your design system. You will pick up a few foundations, then run one prompt with the AI for about 20 minutes. Nothing here happens on paper, it all happens in the AI.
A few foundations you will pick up.
Code Projects, then Working Files inside it, where your plan and working files live.Then you run the interview prompt from Step 0, get your product plan, and save it. The plan also generates a prototype prompt: run it and the AI one-shots a prototype you can see right away. You take it live in Block 2.
This block is hands-on setup. Instead of a single prompt, you install your stack with engineers beside you. Getting your prototype live is the whole job of the block, the payoff for finishing your plan in Block 1.
The goal is simple: get everything wired so you can push to production, then push your prototype live so it has a real URL you can share.
One thing to expect: a couple of steps, like pointing your domain, happen in the Supabase dashboard rather than through the agent. An engineer walks you through these so you do not get stuck.
Your plan is already written, so the build prompt is tiny. You will learn the /goal command, then let it run. It takes 10 to 15 minutes, and you pick up the protocols while it builds.
Why an admin page belongs in Build 1. You cannot review what you cannot see. So Build 1 includes a verified admin login and one admin page, otherwise there is nothing to check. The full flow only works when there is somewhere to log in and watch the lead land.
# /goal build 1
/goal Look at my product plan in Working Files and execute BUILD 1.
Build the data model (People, Contacts, and my custom attributes), a
contact form on my live site, an admin login and password, and ONE
admin page behind that login where I can see the leads that come in.
Set up and verify one admin account so I can actually sign in.
Before you start, confirm I have connected GitHub, Vercel, Supabase,
and provided my API keys; if anything is missing, tell me what to add.
Work until you are done. When finished, give me a short summary of
everything you built and the links I need to test it.While it builds, you will see what is happening behind the scenes: what your login actually does, what gets written to the database, the pull request being created.
When it finishes.
Same rhythm: a little setup, one prompt, then review and iterate while it builds. This is where the rest of the admin back end gets built and where you wire Resend, so you learn email wiring and API keys here.
# /goal build 2
/goal Look at my product plan in Working Files and execute BUILD 2.
Build the rest of the /admin back end behind my login: the full People
directory, all inquiries, and a pipeline to move each inquiry through
its stages. Then wire Resend so that when someone submits the contact
form they get a confirmation email and I get a notification. Keep it
consistent with my design system. Work until you are done, then give
me a short summary and the links to test each screen and the email.Then you merge, review, and test the email flow: submit a lead and confirm the confirmation email arrives. The day ends with an awards moment to celebrate what you shipped.
Email is free to start. Your first domain on Resend is free, so you pay nothing for email. The only thing you pay for is your domain in Vercel.
There is almost nothing to do ahead of time. The day is built so you show up and build.