Straight answers to the questions everyone asks before they build their first thing. No jargon, no hedging.

Is it really building software, or is this a demo?

Really building. Every app gets real storage, real sign-in, and its own web address. A reviewer uses each app in a real browser before it goes live. People run businesses on things built here.

What if it builds the wrong thing?

Then you say so, and the crew fixes it. The first version is the crew's honest best reading of your description. If it misread you, a plain comment redirects it while it works: "no, one form per customer, not one big list." Nothing goes live until a separate reviewer has used it and it holds up. If a change later turns out to be a mistake, the history is kept. Earlier versions are not lost.

Can I break something by asking?

No. Asking is always safe. New work happens on a separate workbench with its own private preview. Your live app keeps running, untouched, until the crew has built, checked, and approved the new version. The worst case of a bad idea is a preview you do not like. That costs nothing.

Do I need to learn the technical pages of this wiki?

No. They exist so the people who run and trust the platform can see exactly how it works. Building things needs only The Big Idea and A Day With Your Crew: describe, watch, steer.

What does it cost to build something?

The crew runs on a shared budget of AI work-hours. The platform's operator sets and meters that budget. The platform paces itself, so the crew works steadily without blowing through it — like a shop that schedules jobs against the hours available. Ask whoever runs your platform how much room there is. Small apps are genuinely small asks.

Who can see what I build?

By default, only the people in your group. Projects here are private unless someone shares them on purpose. You choose who gets the live web address of a finished app — a shop tablet, a team, or the whole world.

How is this different from hiring a developer or buying software?

Off-the-shelf software makes you work its way. A hired developer builds what you meant only if the translation survives meetings, estimates, and months. Here, the person who understands the problem — you — describes it directly to the crew. The crew starts in seconds, shows its work, and takes corrections at once. You are not a client waiting on a project. You are the one holding the pencil.

What is the catch?

Clarity is the price of admission. Vague descriptions produce vague first drafts. The people who do best here treat describing like a skill. They say what the thing is for, who uses it, and what "good" looks like. That skill compounds: your fifth description will be twice as sharp as your first, and your tenth thing will ship in an afternoon.

I am sold. Where do I start?

A Day With Your Crew walks the whole loop once. Then click "Use this template" and describe something small you have always wanted. Small is the right size to start. It can be live before lunch.