Skip to main content
Plan mode helps you shape the app before it is built. Instead of sending your prompt straight into Auto, Zite creates an editable plan with wireframes so you can review the direction, request changes, and approve the build when the plan looks right. Use Plan mode when you want to clarify the structure, screens, data, workflows, or user experience before Zite starts making the app.

When to use Plan mode

  • You are starting a new app and want to review the direction first
  • The request is broad, complex, or still partly undecided
  • You want to compare the planned screens and workflows before building
  • You need to align with teammates before Zite creates the app
  • You need to share a proposed app scope with a client or stakeholder
  • You want to avoid rework by catching missing requirements early
Plan mode uses Zite Max and consumes credits, but it can reduce rework by helping you approve the plan before app changes are made.

Create a plan

1

Switch to Plan mode

Open the mode menu and choose Plan.
Mode selector with Plan mode selected
2

Describe what you want to create

Enter your prompt in the chat box. Include the audience, main workflows, data you want to track, and any important constraints. If your data already lives in another tool, name it in your prompt—for example, “build a blog from my Notion”. Send your prompt to create a plan.
Naming the tool helps Zite plan from your real data. See Integrations for the tools you can connect.
3

Review the plan

Zite opens an editable plan that explains the app direction and shows wireframe previews for the planned screens.
Editable Plan mode document with page thumbnails and wireframe previews
4

Review the database tables

Plan mode suggests the tables needed for the app. If the structure is not right, ask Zite to add, remove, rename, or change fields before building.
Plan mode data details showing suggested database tables and fields

Plan with your real data

If your app should use data from another tool, Zite can connect it while planning. You’ll see a connect card in the chat. When you accept, the connection is saved to your workspace right away—the same as connecting from the Integrations tab. Zite then reads your real data before writing the plan, so the planned screens and tables match what you already have. If that account is already connected in the workspace, Zite reuses it instead of creating a duplicate. Stopping Zite does not remove the connection. Disconnect it from the workspace Integrations tab if you no longer want it.

Refine the plan

You can ask Zite to change the plan before building. Each plan screen has a prompt box underneath it, so you can request targeted changes with AI.
  • Use the prompt box under a specific screen when only that part needs changes.
  • Ask for broader changes when the overall app direction, data model, or workflow needs to shift.
  • Review the updated plan and keep prompting until it matches what you want Zite to build.
For example, you might ask Zite to add an approval step, simplify the dashboard, include role-based views, or change which fields are tracked.
Plan mode review prompt with a Build plan button and a message requesting a change

Download a plan PDF

Plans can be downloaded as PDFs, making it easier to send a proposed app scope to a client or stakeholder before build work starts. It is a simple way to align on screens, workflows, data, and assumptions while the project is still easy to refine.

Build the plan

When you are happy with the plan, click Build plan. Zite builds the app in Auto mode, using the approved plan as the direction. Approving the plan already approved the changes, so Auto keeps going without extra Approve clicks. If you had Build selected, that choice comes back after the build.
Use Plan mode to decide what should be built. Clicking Build plan always runs in Auto. For later changes, Auto is the default, or switch to Build mode if you want a checkpoint.
Last modified on October 13, 2026