App builders
Zite consultant: business apps your team can keep running.
Zite builds business apps, portals and internal tools from a prompt, on a shared Postgres database with no per-seat fees. SBD plans the data and permissions, builds the app in your Zite organisation, connects it to your other systems and hands it over documented, for teams of 5 to 1,000 people.
- Tool
- zite.com
- Usually paired with
- Fillout, Airtable, n8n, QuickBooks
- Timeline
- Most builds live in 2 to 8 weeks
- Owned by
- You, with accounts, credentials and code in your name.
What we build on Zite
- Build internal tools and client portals from a written brief
- Move Airtable bases into Zite Database and rebuild the screens
- Connect apps to your CRM, accounting and messaging tools
- Set roles, sign-in and an audit trail before staff depend on it
What we sync
Workflows we are asked for
- Fillout form to a Zite record and an approval queue
- Zite order app to QuickBooks or Xero invoice
- Zite client portal fed from HubSpot or Salesforce
- Zite request tracker with Slack and WhatsApp alerts
Often paired with
Tools Zite usually needs to talk to.
-
Zite and Fillout
Forms with logic, payments and native connections to Airtable and Notion.
-
Zite and Airtable
A relational database with a spreadsheet face, used as the operations base for teams who have outgrown sheets.
-
Zite and n8n
The automation platform we build most systems on: code where needed, visual where not, cloud or self-hosted.
-
Zite and QuickBooks
Intuit's accounting platform for small and mid-size companies, with an API that needs careful handling.
What Zite is
What Zite does, and who is behind it
Zite is a prompt-first builder for business software: apps, workflows, forms, websites and a database in one workspace. It launched in April 2025 from the team behind Fillout. On 9 March 2026 the company renamed itself Zite, and Fillout carried on as a product under it, so a Zite app and a Fillout form can read and write the same tables.
Two things draw operations teams to it. Every plan allows unlimited users, which changes the sums for a tool used by a whole warehouse or a large client base. And the database is included, so there is no separate backend to buy and connect before the first screen works.
What we build
What a Zite project from SBD covers
A prompt gets you a first screen quickly. A system people depend on needs more than that, and most of our work sits in the part a prompt does not settle: which tables exist, who may see which rows, what happens when an integration fails, and who owns the app once it is live.
SBD has no published Zite case study yet, so we will show you comparable internal tools and portals built on other platforms, and we will say plainly where Zite is new to a requirement. We prototype your hardest screen first, so you see what the platform does with your data before you commit to a build.
- Internal tools: order desks, request trackers, approvals and dashboards.
- Client and partner portals with sign-in and per-customer data.
- Airtable moves, using Zite's migration into its database, with the screens and automations rebuilt.
- Rescue work on apps that a team generated and now relies on.
Choosing a platform
When Zite is the right choice, and when it is not
Choose Zite when many people need access, when you want the database included, and when your team is comfortable working from prompts with generated code behind them. Softr is often the safer choice where non-technical staff will edit screens by hand. Lovable has fuller code portability through two-way Git sync, which matters if developers will take the app further. Retool suits engineering teams building on existing databases and APIs.
Zite's own export covers a workspace's apps and table structure. It leaves out database records and chat history, and connections need setting up again, so moving away is a planned job. We document that route at handover.
Plans and limits
Zite pricing and the limits that matter
Zite's pricing page, read in November 2026, lists Free, Pro at $240 a year and Business at $900 a year, with unlimited users on all of them. Pro includes 100 credits, 3 workspaces, 100,000 records and 5,000 workflow runs a month. Business includes 400 credits, 5 workspaces, 250,000 records and 50,000 runs. Single sign-on for app users and audit logs are listed on Enterprise, priced by quote.
Records and workflow runs are the limits we size against in the audit, because they grow with the business. AI credits are spent while building, so we plan the build to avoid regenerating screens that already work.
Ownership
Built in your Zite organisation
Zite's guidance for agencies is to build client systems in the client's organisation, so the workspace, billing and access stay together, with the builder invited as an editor. That is how SBD works on every platform. Editors can reach all the apps and data in a workspace, so we separate workspaces where data must stay apart.
Engagement and cost
How a Zite engagement with SBD works
Every engagement starts with an Automation Audit at $500, credited in full to your build. We map the work, the data and who needs access, and tell you whether Zite fits. Internal tools start at $3,000 and multi-module systems at $5,000, as a fixed price set after the audit, followed by 60 days of hypercare and care plans from $50 a month.
Read next
Sources
- Zite, Pricing page (plans, records, runs, Enterprise features), checked 2 November 2026
- Fillout, The next chapter (company renamed Zite, 9 March 2026)
- Zite Help, Working with clients (where to build, transfer, what exports exclude), checked 2 November 2026
- Zite, Zite vs Lovable (vendor comparison: database, code export, Git)
- Softr, Softr vs Zite (vendor comparison)
In every build
Standards we apply to every build.
Under the hood
- Upserts keyed on the record
Each write is matched on the source ID, so a retry or a re-fired event updates the existing record.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays. If they still fail, they are parked for review.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Each run records the input, the mapping result, the action taken and what triggered it. You can search it by record.
For the team
- Slack or email notifications
Alerts go to a named person on your team, by Slack, email or WhatsApp.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from the start, so the build keeps running if we stop working together.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
Keys and data
- Keys are kept in a vault
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts for connections
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
The offer
Connect Zite to the rest of your stack.
We agree a fixed scope in a discovery call, and most builds go live in three to five business days. The accounts are in your name, and the engineers who built it stay on call for sixty days after.
- ScopeOne call to agree the workflows, the fields and the owner, written up the same day.
- BuildValidation, upserts, retries, reconciliation and an audit log, on n8n, Make or code.
- Go-liveWe test in a sandbox first, then switch over. It takes longer only where a vendor has to approve something.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about Zite.
Is Zite the same company as Fillout?
Yes. The company behind Fillout renamed itself Zite in March 2026, and Fillout is now a product under it. A Zite app and a Fillout form can share one database.
Zite or Softr?
Softr suits teams who want staff to edit screens visually and who already keep data in Airtable or another source. Zite suits teams who want an app generated from a brief, with its database included and generated code they can edit. We test both against your first screen before recommending one.
Zite
Start with the one Zite workflow your team still runs by hand.
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call