Command the Machines
0 / 5
11
BAND III · ADVANTAGE
Week 11 of 12 · JUNGFRAUJOCH · 3,454 m

Build Working Software Without a Developer

The month you go rogue earns its name this week. You're going to build.

The month you go rogue earns its name this week. You're going to build. Ten weeks of commanding machines — this week you build with them. A live page at a real address tonight. Changes shipped in plain English tomorrow. The tool no vendor will ever sell you by Wednesday. Real money by Tuesday — the page, at least; the strangers are the market's exam. And on Friday, worker number four joins The Roll: an engineer that improves your software while you sleep, on staging, always, because the course obeys its own fortress.

Not your desk? This week's moves work on any desk: put something real online tonight · change it with a sentence · build the tool nobody sells you.

Today · one task

Describe the page out loud. Run the prompt above, drag the one file it gives you onto the free host it names — then open the live address on your phone.

Every ceiling you've assumed about building — needs a developer, needs a budget, needs permission — relies on nobody checking. Tonight you check. A real page, at a real address, live before you sleep.

You'll have: a live page on the internet. A real address. Yours. Built by you, tonight.

  1. Describe the page out loud — one page about your business, your offer, or the thing you keep explaining: what it says, who it's for. Run the press below; it builds the whole page as one file, styled by the Brand Vault from week four.
  2. Publish it. A free hosting service takes the file the press hands you — drag, drop, done; the press's output ends with the exact clicks for the one it recommends. Nothing may complicate this day, so nothing does: one file, one drop, one address.
  3. Open it on your phone. Not the preview — the live address. It's real. You built it. (You will refresh it several times tonight. Everyone does. The last refresh is the one where you believe it.)

Build me a complete one-page website as a single file I can publish tonight. It's about: {say it — the business, the offer, the thing}. Apply THE BRAND VAULT — my colours, my fonts, my voice. Structure: a headline that says the thing plainly, three short sections, one clear next step at the bottom. Fast, clean, works on a phone. Then end your answer with the exact steps — click by click, nothing assumed — to put this file live on a free hosting service at a real address, tonight.

COPY

Rescue — Stuck at the publishing step? That's the only place this day can wobble — paste the host's screen back into the chat and say "I'm here, what next." The machine reads screens; you'll be live in minutes.

Did you get this done?

The page is live at a real address — and you opened it on your phone.

Want more — Send the address to one person tonight. "I built this" lands differently when the thing is real — and tomorrow you'll change it in front of them with one sentence.

The ceiling was negotiable. Tomorrow you learn to renovate — in plain English.

Today · one task

Point Claude Code at last night's page. Ask for one real change, in one plain sentence. Approve what it shows you — then open the change, live.

Last night you shipped a page. Today you meet the tool that changes it — and anything else you'll ever build — with a plain English sentence. It's called Claude Code, and the fear of it is the last tax you're paying.

You'll have: one real change to last night's page, asked for in a sentence, live — and the discovery that you were never afraid of code, only of not knowing where it lived.

  1. Open Claude Code and point it at last night's page. The press below is your first conversation with it — paste it, follow its lead. It sees the file; you supply the intent.
  2. Ask for one real change, in one sentence. "Add a contact section with my email." "Make the headline bigger." "Add a second page about pricing." Watch it show you the change before it ships — you approve, it goes live.
  3. Open the live page. The change is there. You asked in English; the machine handled the rest — and the entire skill was knowing what you wanted. That was always the skill.

This folder holds my live one-page website. I'm not a developer and I don't need to become one — you handle the code, I'll handle the intent. First: read the page and tell me in one plain sentence what's there. Then I'll ask for one change in plain English. Show me what you'll do before you do it, in words not code, then make the change and tell me exactly how to see it live. If anything I ask for is ambiguous, ask me one question rather than guessing.

COPY

Rescue — It showed you code and your eyes glazed? Say so: "Words, not code — what will this change do?" It explains in English all day. The code was never your job.

Did you get this done?

One sentence in — one real change live. And you weren't afraid.

Want more — Ask it the question that changes your relationship with every future build: "What else could this page do that I haven't thought to ask for?" Read the answer like a menu.

Plain English is a programming language now — yours. Tomorrow you build the tool nobody will ever sell you.

Today · one task

Name the tool. Describe it in plain English and build it in conversation — one screen, one job. Then load today's real data and use it once, for real.

There's a tool you've wanted for years — the tracker, the register, the calculator shaped exactly like your business. No vendor sells it, because no vendor is you. Today you stop waiting for them.

You'll have: version one of your tool — one screen, one job, running your real data, today.

  1. Name it and describe it in plain English — to Claude Code, using the press below. The discipline that makes today work: v1 is ONE screen doing ONE job. The deluxe version has a name — v2 — and a home — the stretch.
  2. Build it in conversation. It proposes, you correct, it ships. Twenty minutes of "no, the date goes first" and "add a total at the bottom" is you doing software design; nobody needs to tell you the requirements of your own business.
  3. Load today's real data and use it for one real use. Not test data — the actual numbers, the actual list. A tool that's handled one real job is a tool; everything before that is a demo.

Build me version one of an internal tool: {name it, then describe it — what it tracks or calculates, what I type in, what I need to see}. Rules for v1: one screen, one job, no logins, no settings pages, nothing I didn't ask for. Propose the layout in plain words first; I'll correct it; then build it. Make it comfortable on a phone. When it works, tell me exactly how to open it whenever I want it — and keep a list of everything I mention wanting that we're NOT building today, titled V2.

COPY

Rescue — Scope swelling mid-build? Say the magic sentence: "V2 list." Everything tempting goes on the list, and v1 ships today. The list is where good ideas wait without killing the tool.

Did you get this done?

Your tool handled one real use, with real data, today.

Want more — Read the V2 list tomorrow with fresh eyes — half of it you won't want, and the other half is Friday's fuel: worker number four improves exactly this build while you sleep.

The tool nobody sells exists now, shaped like you. Tomorrow: real money, by Tuesday.

Today · one task

Write the offer in five lines and wire in the payment link. Test-drive your own checkout end to end, card out — then publish it.

The modern executive tests ideas with a survey, a committee and a feeling. You're going to test yours with a page and a payment link — because evidence that arrives with money attached is the only kind that never argues back.

You'll have: THE PAYMENT PAGE — one offer, one page, one live payment link. A stranger could pay you money right now. Whether they do is the market's exam, not the lesson's.

  1. Pick the idea and write it as one offer: the thing, the price, the promise — the press below sharpens it and builds the page, Brand Vault applied, using everything week eleven taught your hands.
  2. Wire the payment link from your payment provider and put it on the page. Then test-drive your own checkout, right through: the link works, the money path is real, the confirmation lands. You are the first stranger.
  3. Publish, and log it — THE PAYMENT PAGE. The honest scope, printed: the page going live is today's win; paying strangers are the market's verdict, and Tuesday exists so the verdict can start arriving.

Turn this idea into a live offer page: {the thing, the rough price, who it's for}. First sharpen the offer in five lines — what they get, by when, for how much, why now, and the one-line guarantee I can actually honour. Then build the page as one file per THE BRAND VAULT: headline, the offer, three objections answered plainly, and one button — the payment link I'll paste here: {link}. No countdown timers, no fake scarcity, nothing I'd be embarrassed to defend. End with the publish steps, click by click.

COPY

Rescue — Payment provider still verifying your account? Publish with the test-mode link today and swap in the live one the day approval lands — the page doesn't wait for paperwork, and the offer gets sharper while it waits.

Did you get this done?

The page is live, the checkout works — you tested it yourself, end to end.

Want more — Your page can do something you haven't asked of it yet: it can knock — tell another machine the moment money lands. Hold that thought exactly one week. Ideas stop being debates and start being Tuesdays.

A stranger could pay you right now. Tomorrow, worker number four starts improving what you've built — while you sleep.

Today · one task

Paste the prompt above into a scheduled task set for 02:00 and run the first shift now. Approve one proposal on staging — then schedule it nightly and add worker number four to The Roll.

Every builder eventually meets the backlog of small improvements that never make it to the top of any day. Yours gets a night shift: one proposed upgrade, every morning, waiting for your yes.

You'll have: THE NIGHT ENGINEER on The Roll — a nightly worker that studies your build and proposes one improvement as a reviewable change. Staging only. Production never. Your yes is the only door.

The staging law

The Night Engineer works on staging — the copy, never the live thing — and its every proposal arrives as a reviewable change waiting for your approval. This isn't caution for its own sake: an agent with unsupervised access to production violates the fortress you built in week ten, and the course obeys its own fortress. The engineer that can't touch production can never break production. That's not a limitation. That's why you'll sleep.

  1. Open a scheduled task and paste the order below. It points at Wednesday's tool — and its V2 list, which is about to become a workplan instead of a wishlist.
  2. Run it once, live, now (worker law — you watch the first shift). One proposed improvement appears as a reviewable change on staging, with its reasoning. Read it. Good? Approve it, and watch the improvement arrive.
  3. Schedule it nightly, name it, sign The Roll: what it does, what it may touch — staging — and what it may never touch — production, in writing, next to its name. Worker number four. The Roll is complete.

Every night at 02:00, study my tool and its V2 list. Propose exactly ONE improvement — the highest-value item you can complete well — and build it as a reviewable change on the staging copy only. With it, write three lines: what you improved, why this one first, and what to check when I review. You never touch the live version, never deploy, never delete, never send anything anywhere — your entire output is one reviewable proposal waiting for my yes each morning. If the V2 list is empty, propose the improvement you'd want if you had to use this tool all day. Sign off after one.

COPY

Rescue — Morning proposal missed the point? Reject it with one line of why — "speed matters more than features this month" — and the engineer recalibrates. Rejection with a reason is a promotion for tomorrow's proposal.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

One proposed improvement waited this morning, on staging, with its reasoning — and production was untouched.

Want more — When the approvals run clean for two weeks, week twelve's ladder has a rung waiting. Autonomy is earned in writing here — never assumed, never leapt.

Week eleven is in. A live page, changes in plain English, the tool nobody sells, a page that takes real money — and a night shift improving it all, inside the fortress. Four workers. The Roll is fully staffed. Next week you stop building and start commanding.

Week 11

You're a builder now. It took a week.

Five for five. A live page at a real address, changed with plain English sentences, the internal tool no vendor would ever sell you, an offer page a stranger could pay right now — and worker number four proposing one improvement every night, on staging, inside the fortress week ten built. The ceiling was negotiable all along. It relied on nobody checking.

0 of 5 done

The week's quiz · seven questionsNO PASS MARK · IT TEACHES
Continue → Week 12