Build the Site Around Your App

You have a working app at a real address. Someone arrives. They see… the app. No explanation of what it is, who it is for, or why they should care.

Most people leave. Not because the app is bad — because nobody told them what it was.

What the page has to do

A first site needs five things, and genuinely not much else:

• What it is, in one sentence, at the top, in plain words. Not clever. Clear.
• Who it is for — so the right person recognizes themselves.
• What it actually does — three or four concrete things, not adjectives.
• One obvious next step — try it, download it, join the list. One.
• Proof it is real — a screenshot beats any paragraph.

That is a single page. Resist building a nine-page site for an app with four users.

Do not invent things

The temptation is enormous and it is a trap. No made-up testimonials, no "trusted by thousands" when it is eleven, no logos of companies that have never heard of you.

Beyond the honesty problem, it is fragile: the first person who asks a follow-up question finds out. "Built this to solve my own problem, here is exactly what it does" is a perfectly good pitch, and it is true.

Keep the facts checkable

If your site states a number, it should come from somewhere you can point at. This site does that — the audit numbers on its own pages are read from a published record rather than typed in by hand, so they cannot quietly go stale.

You do not need that machinery for a first site. The habit — every number has a source — is worth copying at any size.

Building it without starting a second project

You can hand-write one page, use a site builder, or generate it the same way you built the app.

Vibe Coder Playground includes a template-based site builder for this: you edit the words next to a live preview, it generates the search and sharing tags from stage 17 for you, and it produces plain static files you can host anywhere. Unverified facts you leave marked show up as a bright yellow box on the built page, so you notice them before publishing rather than after. It runs on Python, which most machines already have.

Whatever you use, the page is not the project. Keep it to an afternoon.