How to describe your app to the AI
Write requests BurrowHub's AI builds well: start from your business and the job, name your people, screens, data and rules, then change it in small steps.
On this page
How the AI reads your request
When you press Build my app, BurrowHub's AI first writes a plan from your words: who uses the app, the things they do in it, its screens, what it stores, where AI helps inside it, and what it deliberately leaves out. Then it builds the app from that plan and checks it before you see it.
Wherever you say nothing, it chooses the most ordinary thing and writes that down as a decision. So the more of the plan you give it, the closer the first version gets. You can write in English, Japanese, Traditional Chinese or Indonesian, up to 2,000 characters.
Start from your business and the job
Say what kind of business you are, how the work is done today, what goes wrong, and the one job this app should take off your hands. A picture of your work tells the AI far more than a list of features.
Features versus the job
An app with a table, a form, a search box and export.
We are a print shop with 6 staff. Customers order by phone and we write jobs on paper, so jobs get lost and nobody knows what is due today. I want one place where we record each print job, who it is for and when it is due, and see today's jobs first.
Why: The second one gives the AI the business, the problem, what each record holds and what the first screen should show.
Say who uses it and what each may do
Name each kind of person and what they are trying to get done: the owner who checks numbers at night, the staff who record sales at the counter, the manager who approves. Then say who may see or change what — "staff see only their own leave; managers see everyone".
You don't need to build sign-in. BurrowHub signs people in, and inside every app a person is an admin, an editor or a viewer: your business's owners and admins are admins of its apps and members are editors. Rules in your words are built on top of that. See People, roles and partners.
Describe the screens and the main daily task
Walk through the task people do most, step by step, from where they start to what they end up with. Say what the first screen should show, what is at the top, and what happens when there is nothing yet.
Apps are planned for a phone first and work on a computer too. If the work happens at a counter, on a shop floor or in a van, say so; if it is mostly at a desk, say that.
Every morning the driver opens the app on their phone and sees today's deliveries in route order. They tap a delivery, see the address and what to drop off, and mark it delivered with a photo. The office sees which deliveries are done, live.
Give it your data, and name the columns that matter
The AI builds much closer to your business from your own data than from a description of it. There are two ways in:
- Build it on your data: pick a spreadsheet you have added under Your data. The app reads its latest version live, so new rows appear without a rebuild.
- From your files: upload what you already use — spreadsheets, forms, receipts, photos of paper notebooks, price lists. Up to 30 files, 50 MB each; scans and handwriting are fine. The AI reads them, writes down how your work runs, and shows it to you to correct before it builds.
Then say which columns matter and what they mean: "In the Products sheet, Qty is stock on hand and Min is when to reorder." Column names are often short or old; one sentence saves a wrong guess. More in Getting your data in.
Write down your rules
Rules are what make an app yours, and the AI cannot guess them. Write each as one plain sentence, with numbers where there are numbers.
- An order can't be marked shipped until it is paid.
- Leave needs at least 3 days' notice, except sick leave.
- Warn when a product falls below its Min column.
- Only managers can change prices.
Say which languages and words your team uses
Every app is made in English, Japanese, Traditional Chinese and Indonesian, and each person sees it in their own language — you don't need to ask. Write in the language you are most comfortable with: the AI writes that one first and best.
Do say the words your business uses: "we call orders *jobs*", product names, how you write dates or money. Those are what make the app read like yours.
Say where AI should help inside the app
Every BurrowHub app uses AI for something real, where it saves typing or reading: reading a photo of a receipt or delivery note into the form, sorting a free-text note into the right fields, answering questions about your own records, drafting a message. If you know where that is, say it.
AI proposes and a person confirms before anything is saved, and the same job can always be done by hand. When people use it, that AI counts against your business's AI credits.
Say what "done" looks like
End with how you will know it works: one or two things a real person can do in it. It gives the AI a target and gives you something to try in the preview.
It's done when a manager can approve a leave request from their phone in two taps, and the staff member sees it approved straight away.
Make one app for each job
An app that does one job well beats one that does five things halfway. The AI keeps an app to what one app can be and cuts what is too big. Leave, stock and the company website are three apps — they can read the same data.
Ask for changes in small steps
After the first version, open the app's Build with AI and chat. Each message makes a new version you can try before anyone else sees it. Ask for one thing at a time: a small change is easy to check, and if it isn't right you know exactly which message to undo.
One message, one change
Make it better, add reports, change the colours and fix the bugs.
On the Orders screen, add a filter for status (new, packed, sent, paid) above the list, and remember the last one chosen.
Why: It names the screen, the change and how it should behave — and nothing else.
The AI reads the conversation so far, so you don't have to repeat what was decided; if something you say now conflicts with an older message, the newest wins. Each message that changes the app is one of your business's builds for the day, and the screen shows how many are left.
Attach a screenshot of what's wrong
A picture of the problem beats a paragraph about it. In the chat, use Attach files to add a screenshot — or a spreadsheet of what a screen should hold — and say in words what is wrong and what you expected. The AI reads the files only to understand the change; nothing in them is copied into the app unless you ask.
On the phone, the Total column is cut off on the Orders screen (screenshot attached). Show the total under each order's name on narrow screens instead.
Preview, then publish — and go back if you need to
A new app's first version is live straight away. After that, every change waits as a preview on a copy of your data, seen only by the people who build the app. Try it, then Publish when you are happy. Every version is kept, and Restore puts an earlier one back live. See Preview, publish and versions.
What the AI can't do — and how to check
The AI builds with what BurrowHub has. Ask only for that, and check the result rather than trusting a description of it.
- An app can't reach other websites or services on its own: no outside APIs, fonts, images or payment providers. It reaches AI, your data sources and maps only through BurrowHub.
- Some features need switching on by whoever runs your BurrowHub first — maps, Google Drive, your own web address. The app says so and keeps a way to do the job by hand.
- Anything you asked for that it couldn't build is listed on the app's page and in its user guide as needing setup or not supported — never quietly left out.
- AI inside an app reads what it is given and answers. It doesn't learn from your data, remember between visits, or get better over time.
Examples: before and after
A bakery dashboard
A dashboard for my bakery.
A dashboard for our bakery, built on the "Daily sales" sheet I've added (columns Date, Item, Qty, Price, Shop). Two shops. Each morning I want to see yesterday's sales per shop compared with the same day last week, the 5 best-selling items this week, and which items sold out before noon. Only the owner and the two shop managers can see it. Done means I can check yesterday from my phone before 7am in under a minute.
Why: It names the data and its columns, the comparison that matters, who may see it, and a test you can try.
Stock and orders
Inventory system with orders.
We sell kitchen supplies to about 40 restaurants. Build a stock and orders app on our "Products" sheet (SKU, Name, Qty, Min, Cost, Price). Deliveries from suppliers add to Qty; customer orders take from it. An order goes new → packed → sent → paid, and can't be marked sent until it is packed. Warn on the first screen when Qty is below Min. Warehouse staff (on phones) pack and send; only the office can change prices.
Why: Data with column meanings, the order of statuses, a rule, a warning, and who does what on which device.
HR: leave requests
HR app.
A leave app for our clinic's 25 staff. Each person has 12 days of paid leave a year and unlimited sick leave. Staff request leave from their phone (dates, type, a note); their team lead approves or declines. Paid leave needs 3 days' notice. Staff see only their own requests and days left; team leads see their team; the owner sees everyone and a month calendar of who is away. Uploading our current "Leave 2026" spreadsheet as the starting balances.
Why: Numbers, three roles with what each sees, a notice rule and starting data.
A company website
Make us a nice website.
A website for Green Leaf Cleaning, a home and office cleaning company in Osaka. Pages: Home (what we do, three services with starting prices, a call-to-action to ask for a quote), Services, About us (our story and 4 team members), and Contact (a quote request form: name, phone, address, service, preferred date; our phone and opening hours). Friendly and plain, mostly read on phones. We want to change prices and text ourselves. Use our brand kit for the logo and colours.
Why: Each page and what is on it, the one action you want visitors to take, the tone, who edits it and where the look comes from.
A consultant building for a client
Build the client's CRM.
I'm a consultant working in my client's business, Sato Auto Parts. They track customers in the "Customers" sheet they added (Company, Contact, Phone, Area, Last order) and follow-ups on paper. Build a customer app for their 3 sales reps: today's follow-ups first, each customer's calls and quotes, a next-follow-up date on every customer, and search by company or area. Reps see all customers; only the sales manager can delete one. Write it in Japanese first — the client's staff read Japanese.
Why: It says whose business it is for, uses the client's own data and words, and names the language the client's staff read.
Checklist before you press Build
- What business this is, and the one job the app does.
- Who uses it, and who may see or change what.
- The main daily task, step by step, and the first screen.
- Your data attached or picked, with the columns that matter explained.
- Your rules, with numbers.
- The words your business uses, and the language you write best in.
- What "done" looks like.
- After it's built: one change per message, try the preview, then publish.