This is what actually happens when you build something here, told as a morning's work. No jargon — where the screen shows a technical word, we'll name it once so it looks familiar, then move on.

9:02 — you describe the thing

You've run the parts counter for years, and the paper sign-out sheet is a disaster. So you open the workshop (this website), find the app template, and click "Use this template" — the button that starts any new thing. It asks for two pieces of writing:

• A name: parts-checkout
• A description: "A sign-out sheet for the parts room. Techs pick their name, scan or type a part number, and it logs who took what and when. A running list shows today's checkouts, newest first. Big buttons — people use this with gloves on."

That description is the whole assignment. Every sentence you put there is something the crew will take seriously — the gloves line matters as much as the list.

9:03 — the crew starts, where you can watch

Within a minute, a page appears where the build happens in the open. (The screen calls it a pull request — think of it as the crew's workbench, with a running log of everything being done.) You can watch pieces land: first the storage for the records, then the screens, then the polish.

You don't have to watch. Go pour a coffee. But most people watch their first one, because it's honestly a little thrilling.

9:14 — you get a preview and change your mind

A link appears on the workbench: a preview — your sign-out sheet, actually running. You open it on your phone. It works... but the names are a dropdown menu, and with gloves on, dropdowns are fiddly.

So you write a comment on the workbench page, like leaving a note for a colleague:

"Make the names big tappable buttons instead of a dropdown — six techs, one tap."

The crew reads it and adjusts, while you go do something else. That's steering. No ticket system, no phone queue — you say it, it happens.

9:31 — a tester tries to break it

When the crew thinks it's ready, a different crew member takes over: a tester who signs in and uses the preview like a real (slightly hostile) person — tapping everything, typing nonsense into the part-number box, checking that it fails politely instead of falling over. The tester writes one verdict, in the open like everything else. If something's genuinely broken, the builder goes back to fix it. Yours passes.

9:38 — it's live

Your sign-out sheet gets its own web address. You bookmark it on the shop tablet, and that's it — it's real now. There's even a written guide for it (the crew wrote one while building — look for the Wiki tab on your project's page), so the next person can learn the tool without asking you.

The afternoon, and every day after

New wishes go on the project's to-do list. (The screen calls each note an issue — it just means "one thing to do.") You write it in plain words and mark it for the crew:

"Weekly summary: parts checked out per tech, so we can spot what needs restocking."

The crew picks it up, builds it on a workbench page like before, the tester checks it, it goes live. Your list is the roadmap, and it gets worked through — steadily, in the order that matters, without you chasing anyone.

What you just learned, without noticing

You now know the entire system: describe, watch, steer, approve, repeat. That's it. The same loop that built a sign-out sheet builds customer portals, quote calculators, scheduling boards, inventory systems. The size of what you can build here isn't set by what you can program. It's set by how clearly you can say what you want — and nobody knows what your work needs better than you.

Next: Questions People Ask, or just go build — the template is right here.