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, its own web address, and a tester that uses it 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 it fixes it. The first version is the crew's honest best reading of your description — if it misread you, a plain comment ("no, one form per customer, not one big list") redirects it while it works. Nothing goes live until a separate tester has used it and it holds up. And if a change later turns out to be a mistake, everything here is kept as history — earlier versions aren't 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 new version has been built, tested, and approved. The worst case of a bad idea is a preview you don't like, which 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 what's in 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 that the platform's operator sets and meters. The platform paces itself so the crew keeps working 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 deliberately shares them. The live web address of a finished app can be shared with exactly who you choose — a shop tablet, a team, or the whole world if you want.

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 if the translation survives meetings, estimates, and months. Here, the person who understands the problem — you — describes it directly to a crew that starts in seconds, shows its work, and takes corrections instantly. You're not a client waiting on a project. You're the one holding the pencil.

What's 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'm 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've always wanted. Small is the right size to start — it'll be live before lunch.