> ## Documentation Index
> Fetch the complete documentation index at: https://docs.convonexai.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> From sign-up to a live, working app — the whole path, honestly described.

## 1. Get access

Creator is in closed beta. Create an account with **email + password** or
**Google** on the sign-in page. If your email isn't on the invite list yet, you'll
land on a short access-request form — tell us what you want to build and we'll
review it. Once you're approved you can sign straight in.

After your first sign-in you'll be asked for a display name and, optionally, what
you're hoping to build. Then you're on your dashboard.

## 2. Describe your app

The dashboard opens on a single prompt box — that box is the product. Type what
you want in plain English:

> A booking page for my studio where clients pick a slot and get a confirmation
> email.

One sentence is enough; the agent will ask when it genuinely needs a decision from
you. If you have a detailed brief, paste the whole thing — it adapts to either.
You can also attach **images** (a sketch, a screenshot of a design you like) and
they'll reach the agent.

Press **Enter** and you'll land on the build configurator.

## 3. Configure the build

Five choices, all changeable later:

| Choice       | What it means                                                                                                                                                           |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Model**    | Which AI model does the building. The default is a sensible pick.                                                                                                       |
| **Stack**    | *Frontend* (Next.js + Tailwind, the default), *Full-stack* (adds Postgres + auth), or *Supabase*.                                                                       |
| **Approach** | *Quick build* starts building right away. *Guided design* designs each screen with you first and waits for your approval before any code.                               |
| **Fidelity** | *Production* — strictly verified, with a scorecard, safe to hand to a client. *Prototype* — faster, verification gates off, may include mocked pieces. Not for handoff. |
| **Tier**     | *Builder* — "I want it built, keep it simple." *Developer* — full control: code view, memory and skills tools, everything on.                                           |

You can also tag the project to a **client** if you're building for someone else.

Press **Start building**.

## 4. Review the plan — nothing runs until you approve

The agent reads your idea and writes it down properly: what the app must do, what
it must not do, and how it will be built. While this happens **no infrastructure
exists** — planning draws only on your usage allowance, and nothing is provisioned
until you approve. You'll see the status pill turn to **Your turn** when the plan
is ready.

The plan review shows:

* the proposal and architecture (both editable right there if you want to change them),
* the list of **promises** — the specific things the finished app commits to doing,
* a table of the **capabilities** approving will create (database, sign-in, …).

Two buttons: **Approve & start building** creates the workspace and starts the
build (this is the moment real resources — and real spend — begin, and the button
asks you to acknowledge that). **Request changes** sends your feedback back to the
agent and reopens planning — as many rounds as you need.

## 5. Watch it build

After approval the preview pane comes alive. The build moves through visible
stages — **Building → Testing → Polishing → Ready** — and the panel next to the
preview tracks each story of the plan as it's implemented and verified. The
preview hot-reloads as files land, so you see the app take shape without
refreshing anything.

If the agent needs a decision, it asks in the chat and the status shows
**Needs your input** — it won't silently guess on things that matter.

## 6. Try it, then publish

When the build is **Ready**, click around your app in the preview (or open it in
its own tab). Ask for changes in the chat — every change goes through the same
build-and-verify loop.

When you're happy, press **Publish**. You'll see the ledger of promises and their
verification status before confirming; publishing promotes the app to a permanent
production URL you can share.

<Note>
  Your project preview goes to sleep after about 30 minutes of inactivity and wakes
  in seconds when you come back — your work is always preserved. The published
  production app is separate and stays up.
</Note>

## Next

* [Core concepts](/concepts) — the vocabulary the product uses.
* [The workspace](/building/workspace) — what every panel and tab does.
* [What "verified" means](/verification/what-verified-means) — how to read the proof.