Building apps for clients

A guide for consultants: get access to a client's business, build and change its apps with AI, publish safely, and hand the work over.

On this page

How partner access works

This guide is for consultants and service companies who build apps for other businesses. In BurrowHub you work as a partner: your own business is given access to your client's business. You never become one of its members, and the client can take the access away at any time.

  1. An owner or admin of your business opens your Members page and copies Your partner code.
  2. Send the code to the client. An owner or admin of the client's business types it under Partners who can work on your apps on their Members page and chooses Give access.
  3. The request appears on your Members page. An owner or admin of your business chooses Accept.
  4. People in your business now find the client in the business switcher, labelled Client: and its name. While you work there, a bar at the top reminds you whose apps you are working on.

The client's side of this is in People, roles and partners.

What you can do, and what stays with the client

  • You can create apps with AI, change them by chat, change an app's look, see the estimate and approve builds, try the preview, publish, discard a preview, put an earlier version's code back live, and make keys for an app's API (at most with the editor role).
  • The client's owners and admins manage members and billing, upload data and connect Google Drive, choose who can open an app and each person's role in it, set an app's own domain, turn on publishing changes automatically, put an app's data back to an earlier version, allow an app to accept Connections from devices and games, and download an app's files for running it elsewhere. Anyone in their business — but not a partner — can download an app's records.
  • You can't see or change the client's members, billing or settings, give anyone else access, or move or delete the business. Their Data screen — uploading, connecting, seeing and changing the data — stays with their owners and admins. That doesn't keep the data from you: when you build, the AI is shown a few sample rows of each source, and previews run on a copy of the client's data (see Connect the client's data).

Everything you do is listed in the client's activity, marked as done by a partner from your business. When the client chooses Remove access, you stop at once and the keys you made for their apps stop working; the apps you built stay theirs.

Before you start: the client's goal and data

A good app starts from a clear job, not from a list of screens. Sit with the client before you build and write down the answers.

  • What job should the app do, and for whom in the business?
  • Who uses it every day, who only reads, and who may change what?
  • Which spreadsheets or files hold the data today, and what do their columns mean?
  • Which languages do the people who use it read?
  • What does "done" look like: one real task the client can try in the preview.

Ask the client's owner or admin to add the data first, so you can pick it when you build: see Getting your data in. Then turn your notes into a request with How to describe your app.

A request written from those notes
A stock app for a bakery with two shops. Shop staff count the stock at closing on a phone; the owner sees each morning what is running low in each shop. Use the "Stock" data source: "item" is the product, "qty" is units on hand, "min" is the level to reorder at. Staff add counts; only the owner changes the "min" levels. English and Japanese. Done when a shop can enter tonight's count in under two minutes and the owner sees the low items for both shops on one screen.

Build an app step by step

  1. Switch to the client in the business switcher, then open Create with AI.
  2. Choose Describe it and paste your request, or From your files to upload what the client gave you — PDFs, photos, Excel, Word, PowerPoint, CSV or text, up to 30 files. Pick the client's data sources the app should read.
  3. Choose See the estimate. Nothing is built yet: BurrowHub plans the request, splits it into phases — phase 1 is the smallest version that does the core job — and shows each phase's cost range, time and what drives it.
  4. Move features between phases or leave some out; the estimate follows. Then choose Approve and build phase 1, or Build everything. Later phases wait in the app's plan until someone estimates and approves them.

While it builds

The build runs in BurrowHub's sandboxed builder and takes minutes. The screen follows it step by step: getting ready, planning it out (a new app only), writing the app, checking it works, finishing it, and ready. When the checks find a problem, the AI goes back and fixes it before anything is shown.

  • A new app's first version goes live when it is built, for the client's business. Every later change waits as a preview.
  • Every app comes with a user guide for the people who use it, written with the app in four languages and updated with every change.
  • A build that doesn't go through changes nothing in the app. If it stops or fails, see When something goes wrong.

Change an app by chat

On the app's page, open Build with AI: the conversation with the app beside it (a tab on a phone). Every message, reply, publish and restore is kept, with who did it — so the client can read later why the app is the way it is.

  1. Write one change per message. Attach a screenshot or files, or choose Use your data to point at a data source.
  2. Choose Send. The plan and estimate appear; approve them to start the build.
  3. When it is ready, the new version is the preview beside the chat. Try it, then publish or discard it.
A change, one at a time
On the stock list, add a filter by shop, and show items below their "min" level in red at the top.

Preview, publish and roll back

A change waits as the app's preview, on a copy of the client's data, seen only by the people who build the app. The client's team keeps using the live version until someone publishes.

  • Publish makes the preview live for everyone who uses the app.
  • Discard preview throws it away; the live app stays as it is.
  • Restore in the app's history puts an earlier version back live. A partner's restore puts back the code only, and the app's data stays as it is now. Choosing Code and data as of …, which puts the data back as well, is for the client's owners and admins.

Connect the client's data and keep it live

The client's owner or admin adds data under Your data: an uploaded spreadsheet (Excel, CSV or TSV, up to 25 MB) or a file followed in Google Drive. Their Data screen, where the data is uploaded, connected, seen and changed, stays with them. As a partner you choose a source by its name when you create an app or with Use your data in the chat.

  • An app reads the latest version of its data every time, so new rows need no rebuild.
  • When columns or sheets are added or removed, the app's page offers Rebuild with the new columns.
  • Tell the AI what each column means in your request; it can't guess the client's abbreviations.

Roles, sharing and the app's user guide

Each app has three roles: admin, editor and viewer. The client's owners and admins become admins of the app and members become editors, unless someone sets a person's role in that app. Rules in the client's own words — "only the owner changes prices" — go into your request and are built on top of these roles.

  • The client decides Who can open it — only their business, specific people, or more — and sets roles in each app. Tell them which setting the app needs.
  • Point the client's team to the app's user guide: the Help button in the app's top bar, or Documentation on its page. See Every app has a user guide.
  • To connect another system to an app, you can make an API key for it with the editor or viewer role. It stops working when the client removes your access, so hand integrations over to a key the client makes.

An app on the client's own domain

A company website or any other app can open at an address the client owns, such as www.yourshop.com. On the app's page, under Your own domain, the client's owner or admin types the address and chooses Use this domain, adds the two records it shows where the domain was bought, and presses Check now.

Help them with the records if they ask — it is often the step that needs a consultant. For a public website, they can also choose to let anyone open the app on that domain without signing in.

Working with your own Claude

You can also build a client's apps from your own Claude, through BurrowHub's connector. When you connect, you sign in and choose the business — pick the client. Claude writes the code on your Claude plan; BurrowHub checks it, builds it, shows the preview and keeps every version, and each preview is one of the client's builds for the day.

How to add the connector and the build loop: Using your own Claude to build.

The code and every version

Every version of an app is kept in BurrowHub, listed in the app's history with what was asked for and who made it, and any of them can be put back live. You don't need to keep your own copy to roll back.

If the client wants to run an app on their own server, their owner or admin uses For developers: run it on your own server on the app's page: Download the setup files, and Save the app image, which is kept for two hours to download. Download your data, which anyone in the client's business can use, gives a copy of the app's records. None of these downloads is open to a partner. Apps built since 20 November 2026 keep their records in a PostgreSQL database, and this download includes those records too.

Handing over to the client

The apps are the client's from the start, so handing over is about making sure they can run them without you. Go through this list with the client's owner or admin.

  • Nothing is left waiting as a preview: each change is published or discarded.
  • The client tried the real daily task in the live app, on a phone and a computer.
  • Who can open each app, and each person's role in it, are set the way the client wants.
  • The data sources are the client's own, and they know how to upload a new version or refresh from Drive.
  • Integrations use API keys the client made, not yours.
  • The client's team knows where the app's user guide is, and how to ask for a change in Build with AI.
  • Later phases still in the app's plan are agreed: to build, or to leave out.
  • If the work is finished, the client chooses Remove access. The apps and their history stay.

When something goes wrong

A build that fails or stops leaves the app exactly as it was, and Try again in the chat starts it again. A published change that turns out wrong is undone with Restore. For messages you see on screen and what to do about each, read When something goes wrong.

All docs

Ready to describe yours?

Write what your business needs, or start from one of six starting points.