From idea to launch in an afternoon

You don't need a sprint to ship something real. You need one clear sentence and an afternoon. Here's how that afternoon actually goes - using a running example, a snag-list tracker for a small building firm, though the shape is the same for whatever you're building.

1. Start with one sentence

Describe the app and who it's for: "A snag-list app for a building firm - foremen photograph defects on site and log them against a job, the office manager assigns them to subcontractors and closes them out."

Don't try to write the perfect spec. One or two sentences that name the user and the main flow are enough, because you're about to refine against a live app instead of a document. If you have a mockup or the spreadsheet you currently run this on, attach it - Vorx will build around it.

2. Click through the first build

A few minutes later there's a working app in front of you - and it's been rendered and checked in a real browser before you ever saw it, so you're clicking through something that runs, not a mockup.

Now use it like the person you built it for. Log a snag. Assign it. Close it. The point of this pass isn't admiration, it's a punch list: the field that's missing, the screen that's in the wrong order, the thing you forgot to mention because it was too obvious to say.

3. Refine in small steps

Work through your list one change at a time. "Add a severity field to snags." "The foreman should only see their own jobs." "Sort open snags oldest first."

Small steps aren't just easier to think in - they're safer to apply. Vorx works out what kind of change each request is and scopes the edit to match, so a tweak to the snag form doesn't reorganise your dashboard. Each change lands live, you check it, you move to the next. Twenty minutes of this beats two hours of trying to write the perfect second prompt.

4. Polish the look

When the bones are right, spend a pass on how it feels. Ask for a cleaner layout, tighter spacing, a specific component, a warmer palette - design requests restyle the app without touching the logic you just finished checking. This is also the moment to attach a screenshot of something whose look you admire and say "more like this."

5. Ship it

Deploy to a real URL and send the link. That's the whole step.

Two things about what you just shipped. It's live software, not a frozen demo - you can keep iterating after launch, and changes reach the deployed app the same way they reached the preview. And it's a real app all the way down: its own auth and database, wired up without you asking for them. Local-first sync - instant offline use on site, live updates for the office manager as foremen log snags - is on our roadmap rather than in this build; today the app needs a connection like the rest of the web does.

The honest version

Will every app be done in an afternoon? No - some ideas need days of refining, and some grow into things you work on for months. The claim isn't that software is finished in an afternoon. It's that shipped and in front of real users happens on day one, and everything after that is iteration on a live app instead of speculation about a planned one. That ordering - real thing first, refinement second - is the entire trick.

The best way to check whether the afternoon is real is to spend one. Bring an idea you've been sitting on.