> ## 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. # Reviewing the plan > The one moment a build deliberately stops: nothing is provisioned until you approve. Before anything is built, the agent turns your idea into a written plan. When it's ready the status pill switches to **Your turn** and the preview area shows the review screen: **"Your plan is ready."** This is the one moment in a build where the platform has deliberately stopped. No cloud services exist yet — approving is what creates them, and what starts their running cost. ## What the review shows **What gets set up.** The centerpiece is the capability table: every cloud service approving will create for this project (a database, sign-in, storage, …). Items that carry a running cost are marked **Costs money**, and when any are present you'll check an acknowledgment box before Approve unlocks. If the plan needs no cloud services at all, the screen says so plainly — "nothing will be created or billed." **The plan itself** lives on the **Plan tab** — the proposal, the architecture document, and the list of promises the build is making. While you're in review, the architecture and proposal are directly editable right there: fix a wrong sentence yourself instead of asking for a rewrite. ## Two buttons, not one Starts your workspace and the build. This is the exact moment infrastructure begins to exist. Type what should be different — "Drop the email notifications for now — I only need the dashboard." — and send it to the agent. Planning reopens, a revised plan comes back, and you review again. The loop is unbounded; only Approve leaves it. Use direct editing for a wrong sentence; use Request changes for anything structural. They're different-sized tools, and both are yours. ## Honesty notes * If the plan changes while you have the review open (for example, you asked for changes in another tab), the screen tells you and asks you to have another look — you can never approve a version you haven't seen. * Planning itself does consume your account's usage — that's the work of reading your idea and writing the plan. What approval controls is **cloud services**: none exist, and nothing runs, until you say go. After you approve, the workspace boots and the build begins — see [the preview](/building/preview) for what the stages look like, and [what "verified" means](/verification/what-verified-means) for how the plan's promises get checked.