A good first prompt for an AI app builder describes your business the way you would explain it to a new office hire: what you do, who works for you, what you keep track of, and what goes wrong today. You do not need technical words. Concrete details about your real day (crews, recurring visits, gate codes, quotes per window) matter far more than feature names.
Below are examples of weak and strong descriptions, plus a template you can copy.
Why the first description matters
An AI app builder takes your words and turns them into screens, lists and buttons. The more it understands about how your business actually runs, the closer the first version will be to what you need.
The good news: you do not have to get it perfect. With Alori, if something is unclear, it asks a couple of simple multiple-choice questions instead of guessing. And you can change anything later by asking in a sentence. But a clear start saves you a few rounds of changes.
Talk like an owner, not like a software person
You do not need to know words like "database," "fields" or "dashboard." In fact, owner language usually works better, because it carries the details that matter.
| Software language | Owner language |
|---|---|
| "I need a CRM module with custom fields" | "I need to keep track of customers, their addresses and the gate code" |
| "Scheduling with resource allocation" | "I need to see which crew goes where each day" |
| "Recurring event support" | "Most of my customers are every two weeks" |
| "Invoice status tracking" | "I need to know who hasn't paid" |
The owner version is shorter, clearer and tells the builder more.
Weak vs strong descriptions
Example 1: Cleaning company
Weak:
I need an app for my cleaning business.
This tells the builder almost nothing. What do you track? How many people? Homes or offices?
Strong:
We clean houses, 6 cleaners in 3 teams. Most customers are weekly or every two weeks. I need to track customers, which team goes where each day, and who hasn't paid. Cleaners need to see their day on their phone, with entry instructions.
Example 2: Plumbing company
Weak:
Plumbing software with everything.
"Everything" means something different to every plumber. The builder will have to guess.
Strong:
Residential plumbing, 4 techs plus me. Customers call, we go quote, then book the job. A lot of our work is emergencies the same day. I need customers, quotes that turn into jobs, a schedule by tech, and invoices. Techs should be able to add photos and extra parts from their phone.
Example 3: Salon
Weak:
Booking app.
Strong:
Hair salon, 5 stylists. I need clients with their color formulas and notes, appointments by stylist, and a list of clients who haven't been back in 3 months.
Notice how the strong versions use the business's own words: "teams," "techs," "stylists," "color formulas." Alori uses your words in the app, so a salon sees clients and appointments and a plumber sees customers and jobs.
What to include
You do not need all of these. Even three or four make a big difference.
- What you do. The trade and the type of customer (homes, businesses, property managers).
- Your team. How many people, and whether they work alone, in pairs or in crews.
- How work flows. Do you quote first? Is work one-time or recurring? Are there emergencies?
- What you keep track of. Customers, properties, equipment, quotes, jobs, invoices.
- Special details for your trade. Gate codes, roof type, square footage, vehicle make and model, color formulas.
- Who uses it where. Office only, or crews on phones too?
- What goes wrong today. "Jobs get done and never invoiced." "Techs call the office for addresses." This tells the builder what matters most.
What to leave out
- Feature wish lists from other tools. Describe the problem, not another product's screen.
- Every exception. Start with how 90% of your work goes. Add the odd cases later.
- Things you do not need yet. It is easier to add than to remove.
A template you can copy
Fill in the blanks and paste it in:
We are a [trade] company serving [homes / businesses / both]. We have [number] people, working [alone / in pairs / in crews]. Most of our work is [one-time / recurring every ___ / emergencies]. Customers usually [call us / fill out a form / are repeat], then we [quote / book directly]. I need to keep track of [customers, properties, quotes, jobs, schedule, invoices]. For each customer or property we need [special details]. [The office / techs on their phones] will use it. The biggest problem today is [what goes wrong].
You can also paste your website. Alori reads it to pick up your business name, colors and what you do, so the app looks like yours from the first screen.
After the first version
Your first app is a starting point. Look at it with your real day in mind and ask for changes one at a time:
- "Add a gate code to each customer."
- "Show unassigned jobs at the top of the schedule."
- "Add a list of quotes that haven't been answered in a week."
Changes are tried on a copy first. Your team keeps using the live app until you publish, and you can go back to an earlier version if a change does not work out.
To see what happens behind the scenes, read how Alori builds your app. For ideas on what to track, see build your own CRM.
Frequently asked questions
How long should my first description be?
A few sentences to a short paragraph is usually right. Long enough to cover what you do, who works for you and what you track. Short enough that you would say it out loud.
What if I forget something important?
Add it afterward by asking in a sentence. Nothing is locked in, and changes are tried on a copy before your team sees them.
Can I write my description in French?
Yes. Alori works in English and French.
Do I need to describe how the screens should look?
No. Describe your business and your problems. Alori picks up your business name and colors if you paste your website, and you can ask for changes to how things look later.
Write yours now
The best way to learn is to try it with your own business. Alori is free to start, needs no credit card, and you can try it without an account. Describe your business.
