Day 12Week 4 · Scale week

Day 12 — Demo day

Twelve days ago you installed an application. Today you present software you specified, built, reviewed, and shipped — to the people who did the same beside you. Then: nominations, certificates, and where to go from here.

Today's goal

Demo your product six times in the two-round fair, try everyone else's with your own hands, and leave with your certificate, three cohort nominations decided — and a concrete next project.

You need: your live URL · your rehearsed 2 minutes · the "demo day" checkpoint from last night (your safety net).

Block A Rehearsal & the last-hour protocol One full run-through in pairs, and the calm procedure for anything that breaks an hour before you present. Nothing new gets built today — today we land the plane.

Pair rehearsal — full dress

Pair up. Present your 2 minutes to your partner exactly as you will on stage — real URL, timer on. Partner's job: note where you rushed, where they got lost, and one sentence worth cutting. Swap. Adjust once. Stop adjusting.

Step done when: both of you fit in 2 minutes and know your opening sentence cold.

If something breaks in the last hour — the triage protocol

Something always breaks for someone on demo day. The professionals' order of operations:

Reproduce it once. What exactly did you do, what exactly happened? One sentence.
Don't debug — restore. Load the "demo day" checkpoint. A missing evening-feature is invisible; a broken demo is not.
If it still breaks: paste the exact error and the one sentence to Codex; apply the smallest fix it offers; verify only the demo path.
If time runs out: demo the parts that work and say “this part is in progress” with a straight face. Every real product demo ever given includes that sentence.

Step done when: you know the protocol well enough to not need it printed.

Block B The demos — and what you're actually taking home Two rounds of the demo fair, three nominations, certificates — and the honest recap of the toolkit you now carry.

The demo fair — two rounds, everyone presents, nobody dozes

Setup (5 min): half the cohort opens their tool at their seat — laptop plus the phone with the installed app. They are round one's presenters; everyone else pairs up as visitors.
Round one (20 min): visitor pairs rotate between stations, about 3 minutes each — the presenter gives the 2-minute demo, then the visitors try the tool themselves. Each visitor leaves one sentence behind: “the thing I'd steal.”
Round two (20 min): swap — presenters become visitors. Same rules.
Close: everyone posts their URL to the cohort Telegram thread — the cohort's collective portfolio — and votes three nominations: Most useful · Most surprising · Best design.

You'll give your demo about six times to real faces instead of once to a tired room. By the last telling you'll sound like someone who's been doing this for years — because by then, you have been. Certificates after the vote.

Twelve days, one card each — click through your own toolkit. This is what walks out of the room with you.

D1 · First agent, first website

D2 · A game and a program

D3 · Software on your phone

D4 · Skills

D5 · Hermes & memory

D6 · Agents in your pocket

D7 · Agentic loops

D8 · Local tools

D9 · Going live properly

D10 · Customer-support bot

D11 · Agents managing agents

D12 · Demo day

What to build next — pick one within a week (momentum is a muscle)

Version 2 of your capstone — give it to one real user and build what they complain about.
The tool for someone else — your colleague's wasted hour, your family's small business. Their spec interview is your Day-3 skill.
Your loop farm — three more standing orders until your mornings feel staffed.
A support bot for a real business — Day 10's pattern is genuinely sellable in this city.
Stay in the cohort Telegram — it stays open, and the “what I'd steal” thread works after the course too.

✦ Certificates are handed out today. The proof, though, is a URL — and yours is already live.

Homework none — one request instead

The only assignment

Give your tool to one real person this week — the person whose problem it solves — and watch them use it.

Time estimate: one coffee

Send your live URL to the one person your spec's USER line describes.
Watch them use it (in person or on a call). Say nothing. Write down the first thing that confuses them.
That confusion is your v2 spec's first line. You know the rest of the pipeline.

Done when:

A real human, not from this cohort, has used your software for its real purpose.

No time this week? Then just don't cancel the Telegram bot and the morning briefing. As long as one loop keeps running, you're still an agentic engineer on the days you forget to be.

Course complete?

Demoed · certified · shipped to a real user

Tick the twelfth checkbox. Look at the dashboard once — all green.

Mark done

What you can do now

Take a problem from your work and turn it into living software — alone.
Run agents on schedules, in Telegram, in teams.
Specify, delegate, verify, ship — as a reflex, not a slogan.

After the course: the portal stays open, the readers stay yours, the cohort chat stays alive. Course 01 — AI Creator — covers the other half of the craft if you want more. Build something this week; that's the whole secret.