Bubble Setup for Small Business: Build an Enquiry Tracker
Compare Bubble’s current web costs, plan a simple enquiry tracker and check its records, workflows and access before launching.

In this guide
- Is Bubble the right starting point?
- Understand Bubble's current costs
- Step 1: define the smallest useful app
- Step 2: start in the development version
- Step 3: decide what records to store
- Step 4: build the screens around the task
- Step 5: connect buttons to actions
- Step 6: check who can read and change data
- Step 7: test the tracker on different screens
- Step 8: launch only after the process works
- Add integrations when they earn their place
- Common questions
- Your next step
Bubble is a visual app builder for projects that need screens, stored records and actions. It can suit a small customer portal or internal work tracker, but it takes more planning than publishing a basic business website.
This guide walks through a fictional enquiry tracker: a team member signs in, adds a request and moves it from new to quoted to completed. It is a planning and build example based on Bubble's documentation, not a tested customer deployment.
Is Bubble the right starting point?
Choose an app builder when your project needs people to interact with records and a repeatable process. Choose a simpler website tool when you mainly need service pages, a blog or a contact form.
Swipe the table sideways to see all columns.
| Your project | A sensible first option |
|---|---|
| Business information and enquiry form | A website builder or existing site |
| Shared contact records and sales follow-up | An existing customer record tool |
| A custom tracker with its own screens and actions | Consider Bubble and compare existing apps |
| A complex business-critical system | Get experienced help before relying on a prototype |
Our website builder comparison covers simpler sites. If you mainly need customer records, compare HubSpot before building your own.
Understand Bubble's current costs
Bubble's pricing separates app plans, AI credits and workload units. Workload units measure server activity such as database operations and workflows. They are not simply a visitor count.
On November 5, 2026, the selected Web pricing view showed these options:
Swipe the table sideways to see all columns.
| Web plan | Displayed price | What matters for this example |
|---|---|---|
| Free | $0 | Development version, 50,000 workload units/month and 500 AI credits/month |
| Starter | $32/month equivalent, billed annually | Live website, custom domain, 175,000 workload units/month and 1,000 AI credits/month |
The Starter figure is an annual-billing equivalent, not a $32 monthly-billed subscription. Check the selected billing period, taxes and current checkout price before purchasing.
Mobile and combined Web & Mobile plans differ. Extra workload, AI usage, plugins and outside services can add costs. Do not budget for your app from the headline subscription alone.
Bubble's current FAQ says app generation does not require AI credits. Other AI features, including its AI Agent, page generation and image generation, can use them. These allowances can change.
Sources: Bubble pricing and what contributes to workload.
Step 1: define the smallest useful app
Write down who will use it, the information they need and the one process it should support. For our fictional tracker, only signed-in team members should see and update enquiries.
Keep the first version to three tasks:
- Add a new enquiry.
- See the team's current enquiries.
- Change the status and record the next action.
Leave customer portals, payment collection and AI-generated quotes for later. Each extra feature creates more behavior to build and test.
Step 2: start in the development version
Use the Free plan to learn and prepare a prototype before buying a launch plan. Use fictional records while building so mistakes do not expose real customer information.
You can begin from a blank app, a relevant template or an AI-generated starting point. Inspect what was created instead of assuming every screen and permission is ready for use.
Copy this app-planning prompt
Plan a small internal enquiry tracker for a service business.
Only signed-in team members may access enquiries.
Each enquiry has a customer name, contact email, service,
status, next action and assigned team member.
Statuses: New, Quoted, Completed, Closed.
Screens: sign-in, enquiry list, add enquiry, enquiry detail.
Use fictional sample records. Explain missing decisions.
Do not add payment, public customer access or automatic emails.
Treat the result as a starting plan. Check that each record, screen and action matches the process you actually want.
Step 3: decide what records to store
A database is the app's organized storage. In Bubble, a data type describes a kind of record, and fields describe the information each record holds.
Create an Enquiry data type with a small, clear set of fields:
Swipe the table sideways to see all columns.
| Field | Example value | Purpose |
|---|---|---|
| Customer name | Example Customer | Identify the request |
| Contact email | A fictional test address | Keep the reply destination |
| Service requested | Regular cleaning | Describe the need |
| Status | New | Track progress |
| Next action | Review service area | Make the next step clear |
| Assigned team member | An app user | Show who is responsible |
Use a fixed set of status options rather than allowing "New," "new" and "Needs reply" to mean the same thing. Do not add sensitive notes just because a text field is available.
Step 4: build the screens around the task
Create a short add-enquiry form. Label each input clearly, explain required fields and show a confirmation after a successful save.
Use a list display, often called a repeating group in Bubble, to show enquiry records. Let a team member open one record to see details and change its status.
Keep the assigned person and next action visible. A tracker should make work easier to find, not just collect a larger pile of records.
Step 5: connect buttons to actions
A workflow tells the app what to do when something happens. For example, clicking "Save enquiry" can create an Enquiry record using the values entered in the form.
Plan that first workflow in plain language:
- Check that required information is present.
- Create one enquiry with status New.
- Assign the responsible team member.
- Show a success message and the saved record.
- Explain a failure without pretending the record was saved.
Test repeated clicks so a slow connection does not create duplicate requests. Test an empty required field too; a happy-path demo will miss that problem.
Step 6: check who can read and change data
Hiding a button or page does not, by itself, protect the records behind it. Set data privacy rules and action conditions that match who is allowed to see or change each record.
For the tracker, start by denying access to signed-out visitors. Decide whether all team members can see every enquiry or only the records assigned to them, then implement that decision consistently.
Test access using the roles your app will actually have:
- A signed-out visitor opening a saved record's direct address.
- A team member reading an allowed record.
- A team member trying to read or change a record they should not access.
- A user attempting an action without the required information.
Consult the Bubble Manual for the current privacy and workflow instructions. Get experienced help if you cannot confidently verify that private records stay private.
Step 7: test the tracker on different screens
Try the form, record list and status update on a phone and a computer. Check that labels are readable, buttons are usable and important fields do not disappear on a narrow screen.
Use a realistic sample of fictional records. One record may look fine while a longer list or a long customer name reveals a layout problem.
Make a short acceptance list: "A team member can add an enquiry, find it again, update its status and see the next action." Complete each task before calling the first version usable.
Step 8: launch only after the process works
Free is for development; a live web app and custom domain require the appropriate paid plan. Before upgrading, check access, sample records, error handling and your estimated ongoing costs.
Separate test data from live work. Document who owns the app, who maintains it and how the business will keep working if the app is unavailable.
Monitor workload after launch. A design with unnecessary searches or repeated actions may consume more than expected. Review the bill and the process before adding features.
Add integrations when they earn their place
An existing app may already handle the work you are trying to build. Compare the complete setup before adding connectors, plugins or more subscriptions.
Our Make introduction explains connections between apps. The AI return-on-investment guide helps compare costs with the benefit.
Common questions
Can Bubble build my app without any work from me?
It can help create a starting point. You still need to define the process, check the records and actions, test permissions and maintain the result. Generated screens do not prove that an app is ready for customers.
Can I publish the enquiry tracker on the Free plan?
Bubble's current Web Free plan provides a development version. The pricing page lists a live website and custom domain under Starter. Check the current plan before promising a launch date or budget.
Should I build a custom customer record system?
Only when an existing tool cannot reasonably meet your needs. A custom app gives flexibility but also creates maintenance work. Compare the smallest working version with an existing tool first.
Your next step
Write the three tasks your first version must handle. Build them with fictional data, then test every task and access rule. Decide whether to launch based on that result and the complete ongoing cost.
Pricing and documentation checked November 5, 2026. Some linked tool pages contain affiliate links, which may earn us a commission if you purchase.



