Create an app

Zite starting prompt with App, Database, and Form options

Zite is best for internal tools, business apps, dashboards, portals, and workflows tied to existing data. It is not the best primary stack for launching a full SaaS product, though you can build external apps and add login when needed. Learn more in What can I build?.

Getting started

Choose AppStart from App so Zite builds the user-facing experience. This is the right starting point for dashboards, portals, admin tools, approval queues, onboarding guides, and other business apps.

Select a data source via IntegrationsDecide where the app should store or read data. For most new projects, start with Zite Database. If your team already works from Google Sheets or Airtable, connect that source instead.

Pick a brand or themeIf you have a Brand Kit, select it before building so Zite can match your logo, colors, fonts, and guidelines. You can also create a new Brand Kit at this stage, or choose and change a theme later.

Choose Plan it or Build itUse Plan it when the request is new, broad, or connected to multiple pages, roles, approvals, dashboards, or integrations. Use Build it when your first request is small and specific. Learn more in Agent Modes.

Submit a specific promptInclude the app type, users, workflow, important views, and any login requirements. The more concrete your first prompt is, the better Zite can plan and build the first version.

Popular data sources

Data source	Best for
Zite Database	New apps where Zite should create and manage the data structure.
Google Sheets	Teams that already manage operational data in spreadsheets.
Airtable	Structured business data that already lives in Airtable bases and tables.

If you are not sure, start with Zite Database. You can still connect other tools later through integrations.

Agent modes

Mode	Use it when	What happens
Plan it	You are starting a new app, the scope is unclear, or the app needs multiple pages, roles, approvals, dashboards, portals, or integrations.	Zite creates a plan first so you can review and edit the scope, then see wireframes of the design before building.
Build it	You know exactly what you want and the first version is small or clearly defined.	Zite starts building the app right away, and may ask clarifying questions if it needs more information.

For a first project, Plan it is usually the better choice. It helps turn a broad idea into a clearer build plan before any app changes are made. You can compare all options in Agent Modes, and choose the right model in Model Selection.

Write the starting prompt

A strong starting prompt usually includes the details below. If you are unsure how to scope the project, start with Plan mode so Zite can help clarify the requirements first.

The app type: e.g. a dashboard, portal, or approval workflow
The users: e.g. employees, managers, or clients
The workflow: what users need to view, create, update, approve, assign, export, or submit
Access needs: whether the app is internal, shared externally, or requires login

Example prompts

Employee onboarding guide

Build an employee onboarding guide for new hires and HR managers.
Track employees, onboarding tasks, owners, due dates, and completion
status. Include a new hire view, an HR admin view, and task reminders.

Inventory management template

Build an inventory management app for the operations team. Track items,
suppliers, stock counts, locations, and reorder thresholds. Include a
dashboard, low-stock alerts, item update forms, and manager-only editing.

Dashboard builder tutorial

Build a business dashboard for team leads. Show revenue, pipeline
status, owner performance, and weekly changes. Include filters by region
and owner.

Client portal setup guide

Build a client portal for external clients to view project status,
files, invoices, and next steps. Add login so each client only sees
their own projects.

Approval workflow examples

Build an approval workflow for purchase requests. Track request, vendor,
amount, department, approver, and status fields. Include submitter and
approver views, email notifications, and an approval history.

FAQs

Should I start with App or Database?

Start with App when you want Zite to build an interface first. Start with Database when the first goal is to create or organize the underlying data.

Can I connect existing data after the app is created?

Yes. You can connect or change data sources later, including a Zite Database, Google Sheets, Airtable, or other integrations.

When should I use Plan it?

Use Plan it for new projects, unclear scope, multi-page apps, dashboards, portals, approvals, or integrations.

Can an app be shared outside my team?

Yes. Zite apps can be external and can include login when needed, though Zite is best suited to business apps and internal tools.

Getting Started

How to Build

Features

Access & Sharing

Account

API Reference

Security & Legal

Getting started

Popular data sources

Agent modes

Write the starting prompt

Example prompts

FAQs

​Getting started

​Popular data sources

​Agent modes

​Write the starting prompt

​Example prompts

​FAQs

Getting started

Popular data sources

Agent modes

Write the starting prompt

Example prompts

FAQs