Describe the client app. AI builds it on your CRM.
Your clients get one branded app — their appointments, invoices, courses, community, documents and anything you keep about them. You write what it should do in plain words; the builder designs it, wires it to your CRM data, and shows you a live preview. Nothing to code, nothing to import, nothing reaches a client until you publish.
Build your client appHow it worksExample prompts
AI-built from a descriptionlive preview on real dataone app per sub-accountevery revision keptno data copied out
What you can build
Client portals
Bookings, invoices, contracts, files and messages in one place, each client seeing only their own.
Member & course apps
Redesign courses and communities as an app: continue-where-you-left-off, pinned live calls, certificates.
Booking & rebooking apps
Service menus with a Book button on everything, upcoming visits, one-tap rebook.
Loyalty & offers apps
Points, packages and specials from custom fields and objects, with end dates that actually end.
Agency client apps
Campaign status, approvals, reports and invoices for every client sub-account.
Anything on your data
If it lives in a custom object or field, a screen can show it, filter it, and let the client act on it.
How it works
- Connect your CRM to Claude. One connector, your own CRM user, the CRM's own sign-in. Pick the sub-account the app belongs to. Setup steps
- Describe the app. "A home screen with this month's specials, my service menu with Book on everything, their packages, and a rebook button." The agent plans the screens and asks when something is unclear.
- Preview it live. It builds into a working preview on your real CRM data. Change anything by saying what to change.
- Publish when you choose. Nothing reaches clients until you press Publish. Every revision is kept, so a bad change rolls back in one step.
Web, iOS and Android
Two stacks sit under the builder: a web app on its own domain, and a native app for iOS and Android. Web apps build and preview today; native apps are rolling out across CRM accounts, and 0n3 tells you which your sub-account can build the moment you sign in.
Connected to your CRM, not copied from it
The app reads your CRM directly: contacts and custom fields, custom objects, calendars and appointments, invoices, estimates and subscriptions, contracts and documents, courses, communities, affiliates and forms. Every client sees their own records and nothing else. 0n3 stores none of it — your session is an encrypted cookie in your own browser.
Why build it through 0n3
Plain text, start to finish
Build, change, preview and publish by writing sentences — from the web, from your phone, or from any AI you have installed 0n3 into.
Your AI can write the code
Prefer your own model? 0n3 writes the app's files directly and hands them to the builder to check, build and deploy.
Apps that act
Pages can ask 0n3 to run a sequence or an AI step on the client's behalf, and every call leaves a receipt.
One per sub-account
Agencies sign in once and build a different app for every client, each from its own description.
Client apps by business
Questions
What is a client app builder?
A client app builder makes the app your customers log in to — their bookings, invoices, courses, community, documents and anything else you keep about them — without writing code. This one builds it from a description and runs it on your CRM's own data, so there is nothing to import or sync.
Can I build iOS and Android apps, or only web?
The builder has two stacks: a web app (Nuxt) and a native app (React Native). Web apps build and preview today. Native iOS and Android are rolling out across CRM accounts; when you sign in, 0n3 shows which your sub-account can build.
Do I need to know how to code?
No. You describe the app in sentences and your AI writes it. The CRM checks, builds, hosts and previews what it writes, so there is no server or database to set up.
Which AI builds the app?
The CRM's builder accepts an outside AI as the app's developer, and today that is Claude — claude.ai, Claude Desktop or Claude Code. Claude writes the files; the CRM checks, builds and hosts them. 0n3 runs the same thing from plain text on your own computer.
What CRM data can the app use?
Contacts and their custom fields, custom objects, appointments and calendars, invoices, estimates and subscriptions, contracts and documents, courses, communities, affiliates and forms. Each client only ever sees their own records.
Does it work with a free or entry-level CRM account?
It works wherever your sub-account has the Client App Builder. Sign in and 0n3 checks your account and tells you plainly, before you build anything.
Do you store my client data?
No. 0n3 keeps no copy: you sign in with your own CRM user, the build runs in your CRM sub-account, and the app reads the CRM directly.
I run an agency. Can I build one app per client?
Yes — one app per sub-account, each on its own branding and domain, each built from its own description. Sign in once with your agency user and pick the sub-account each time.
Can my clients' app call AI or automations?
Yes. Pages can ask 0n3 to run a sequence or an AI step — "summarise my last three visits", "rebook my usual" — and every call leaves a receipt.