Templates
Templates let you start from a working app instead of a blank page. Pick one that's close to what you want, then customize it in the chat — change the content, styling, and features until it's yours.
Why start from a template
- Faster. You begin with real, functioning screens and flows.
- Best-practice structure. Templates are laid out sensibly, so the AI has a solid base to build on.
- It already knows your business. A short intake runs before the project is created, so the first preview shows your real details rather than placeholder copy.
- Easy to customize. Everything in a template is editable through the chat, just like an app you built from scratch.
Template gallery
Berrybell ships ten starters, listed here in the order the gallery shows them:
| Template | Good for |
|---|---|
| Service business | Local and sole-trader sites — cleaners, salons, trades — with an enquiry form and a lightweight admin CRM |
| Landing page | Launch pages, product sites, portfolios, waitlists |
| SaaS dashboard | Apps with sign-in, a database, and billing built in |
| Admin / internal tool | Internal tools to manage records and data |
| AI chat app | Chat interfaces and AI assistants |
| Directory / marketplace | Listings, search, and profiles |
| Blog / content site | Articles, guides, and content-driven sites |
| Form / waitlist | Signup flows, surveys, lead capture |
| E-commerce storefront | Selling products and taking payments online |
| Booking system | Appointments with services, opening hours, a public booking flow and an owner's admin diary |
Opening a card gives you the template's own page: full-page screenshots of the real app, tabs for switching between its screens, a light/dark toggle, a What you get list, and a Platform resources list of what the template will set up for you.
Every template that keeps data in a database — all of them except Landing
page and Blog / content site — includes migrations/0000_baseline.sql,
the starting schema that the AI's later database changes build on. See
Schema changes and migration files.
Starting from a template
Setting up a template takes one dialog with three steps. Its progress bar reads Setup, About, Ready.
- On the home screen, under Or start another way, choose Start from a template. This opens the gallery.
- Open the template closest to your goal (View template) and click Use this template.
- Setup — Choose workspace and confirm what we create. Pick the Workspace the project should land in (see Projects & workspaces), give it a Project name of up to 50 characters, and tick each thing the template will create. Continue stays disabled until every box is ticked.
- About — Tell us about your business. Answer the intake questions, then press Create project.
- Ready — Your project is ready. Check the receipt, then press Open project. The project opens in the Studio with a live preview.
Consent before anything is created
Templates can set things up on your behalf: a database, a test payments account, sign-in for your app's users. The boxes for these are on Setup, before any questions: you tick each one individually, plus an acknowledgement of any integration you'll need to connect yourself (for example, I'll connect Stripe in project settings). You can't move on until every box is ticked, so a project is never created without your consent to everything the template declares.
The intake wizard
The About step puts every question on one screen, with an N of M answered counter at the top. Berrybell asks about your business — what kind it is, its name, where it is, what you offer, what the site is for, the tone you want, and how customers reach you. Most questions offer suggestion chips, and every chip question has an Other free-text box for when none of them fits. Optional questions say Optional — leave blank if unsure.
Create project checks your answers before anything is created. If a required one is missing, the dialog scrolls to it and says what it needs — for example, Pick or type a business type. Back returns you to Setup.
Every template runs the wizard, each with its own question bank. Some questions appear only when they're relevant — the booking template asks about your team only if you said customers choose from a team, and asks for a deposit amount only if you said you take a partial deposit. It also works out your time zone and currency for you to confirm rather than making you type them.
The intake is applied to the template's files directly — deterministically — so the very first preview already shows your real business name, services, prices and contact details. Nothing on that first screen is invented. Your answers are also saved into the project, so the AI can refer back to them later.
The optional AI personalise pass
At the bottom of About is a checkbox, ticked by default: Personalize with AI after opening, with the hint Uses one medium build — your site already shows intake data if you skip this. Leave it on and Ready notes: After you open the project, AI will personalize copy and tone in the background. Preview already shows your intake details.
As soon as the project opens, Berrybell runs one build that rewrites copy, labels and brand colours to match your intake. It runs at the Studio's current effort setting, which is Medium unless you changed it this session.
It's strictly a copy-and-brand pass. It may change display names, headlines, button and nav labels, service names and descriptions, brand colours and page titles. It will not move, add or remove sections, change layout, or add or remove features, routes or form fields.
Untick it and nothing is lost — your site already has your details. See Plans & credits for what a build costs.
The receipt
Ready is a live receipt. It shows the project's name and address, a spinner while the database provisions, and then a tick or a plain-English warning per resource, along with the integrations left for you to connect.
Provisioning is bounded: if the database is still coming up after about a minute and a half, the receipt says "Still provisioning in the background — you can open the project" rather than spinning forever. The Open project button reads Preparing resources… and stays disabled while a resource is still pending.
When a resource is skipped
- A database consumes hosting budget, so a workspace without any is told to enable it later from Database settings instead of failing the create.
- Sign-in for your app's users needs a paid plan. On a free workspace it's skipped with a message pointing at the upgrade, and you can turn it on afterwards.
Either way the project is still created — you just finish the setup yourself.
Templates that come with sign-in
Four templates include sign-in for your app's users, and they differ in who becomes an admin:
- Admin / internal tool and Form / waitlist — the first account created becomes the admin, and every later sign-up is refused.
- SaaS dashboard — sign-up stays open. The first account is
admin, and every later one isuser. - Directory / marketplace — everyone is
user, and the app has no admin screen of its own. Moderation happens in Cloud → Auth → Users. Banning someone ends their sessions but doesn't yet stop them signing in again, so deleting the account is the control that sticks (it also removes their listings).
In Admin / internal tool, Form / waitlist and SaaS dashboard you can
name the admins yourself instead: add an ADMIN_EMAILS variable
(comma-separated addresses) under Cloud → Variables, and from your next
publish those addresses are the admins. The role is then ignored, and in
Admin / internal tool and Form / waitlist only those addresses can sign
in.
To change someone's role, press Make app admin or Remove app admin on
their row in Cloud → Auth → Users (workspace Admin only — see
Who can do what). The change takes
effect on their next request. While ADMIN_EMAILS is set, it decides who is an
admin instead, so these buttons have no effect until you remove it. Directory /
marketplace doesn't read the role at all.
While production is selected, the live preview shares your production database.
In Admin / internal tool, Form / waitlist and SaaS dashboard, that
means the first sign-up anywhere, including on the preview, becomes the admin.
Create your own account, or set ADMIN_EMAILS, before you share either address.
A password shown exactly once
The Booking system template mints a credential for you: an admin password
for its /admin diary, shown on Ready under Save your admin password,
with a Copy button. It's twelve lowercase letters and digits in three groups
of four joined by hyphens, and the hyphens are part of the password. Easily
confused characters (0/O, 1/l/I) are left out. It's stored as the secret
ADMIN_PASSWORD, and Ready is the only time it's displayed.
Service business doesn't mint one. Its admin CRM at /admin/login stays
locked until you add an ADMIN_PASSWORD secret under Cloud → Variables and
publish.
To set a new one, replace or delete ADMIN_PASSWORD in project settings under
Cloud → Variables (the Editor role or higher). It's an ordinary
secret, not a managed one. The new value
reaches your published app the next time you publish.
- Admin sign-ins last 30 days. On a booking site whose Berrybell Cloud database
was set up, changing the password doesn't sign anyone out of
/admin: sign-ins are signed with a separateSESSION_SECRETthat Berrybell creates with the database, so a new password alone won't lock out someone who's already signed in. Without a database, and without aSESSION_SECRETof at least 32 characters of your own, changing the password signs everyone out. - If
ADMIN_PASSWORDis empty or deleted,/adminrefuses every sign-in and shows how to set one.
About the project name
The Project name you type on Setup is carried into the business-name
question on About — unless you left it as the template's own name, in which
case that question starts empty. The business name you end up with becomes the
project's name and its address. If that address is already taken, Berrybell adds
a number to the end (for example, bright-clean-2). The receipt shows the
address you got. The address can't be changed later: renaming the project
changes only its name.
Some templates need integrations you supply
A template can be built around a service you have to connect yourself. The template page lists what it needs, you acknowledge each one on Setup, and the receipt reminds you at the end.
The Booking system template is the main example. It takes deposits through
your own Stripe keys, not Berrybell's
Stripe payments integration under
Cloud → Payments. Add STRIPE_SECRET_KEY and STRIPE_WEBHOOK_SECRET under
Cloud → Variables, and point the Stripe webhook at /api/stripe/webhook on
your site. Without them the site still takes bookings, and a booking with a price
is confirmed unpaid.
Its email no longer needs a key of your own: see the next section.
Templates that send email
Four templates send email through Berrybell, with no email provider of your own. Each kind of email is turned on under Cloud → Email and starts with your next publish.
- Form / waitlist, Landing page and Service business email you each submission, contact message or enquiry, as a notification to you. Notifications work on every plan. Each sets the reply address to the visitor's (on Form / waitlist, when the form has an email field), so you can answer from your inbox.
- Booking system emails customers when a booking is made, moved or cancelled, with a calendar invite that keeps their calendar up to date, and sends a reminder before it. These emails are Booking's four ready-made starter templates: add them from Ready-made, under Your templates in Cloud → Email. They need a Pro or Business plan and a verified sending domain.
- Booking system also emails you a copy of each booking, change and cancellation, as a notification, on every plan. The copies go to the workspace's owners and admins. To have them reach the business's own address too, add it as a notification recipient in Cloud → Email and confirm it.
Until a kind is turned on, nothing of that kind is emailed. Booking system still takes bookings, and its admin says that email is off. Form / waitlist and Service business keep each submission in their admin. Landing page keeps no copy of a contact message, so turn notifications on before you share the site.
Booking's reminders go out 24 hours before the appointment. On Pro and
Business, the published site runs a scheduled job that sends the ones due every
30 minutes, whether or not anyone visits. The free plan arms no schedules. The template still declares its job, so publishing
Booking on the free plan goes live without it and says so: "Your app is live,
but the scheduled job in .berrybell/schedules.json will not run: scheduled jobs
need a paid plan. Upgrade to Pro, then publish to production again to start
them." That is expected. Without the schedule, reminders go out as visitors use
the site, so the calendar invite is the dependable reminder. To send them on time
regardless of traffic, add a CRON_SECRET variable (a random string of at least
16 characters), and have any scheduler call
https://<your-site>/api/cron/drain?secret=<CRON_SECRET> once a minute.
A Booking system project created before this sends through your own Resend API
key, RESEND_API_KEY, and keeps doing so. Ask the AI if you'd like to move it to
Berrybell's email.
From template to launch
Templates are full apps, so the rest of the workflow is the same:
- Add a database or payments if the template doesn't already include them.
- Keep customizing in the chat — "add an About page," "swap the pricing tiers."
- Publish to a live URL.
- Connect a custom domain.
Next steps
- Customize with the AI: Studio & chat
- Write effective requests: Prompting guide