One change at a time, at first
Six requests in one sentence come back as six half-understood ones. Once you have a feel for it you can ask for more at once, but not on day one.
TUTORIALS / GETTING STARTED
Your first change
The first version is never right, and it is not supposed to be. What matters is the loop that follows it — five steps, four of them the studio's, and it is identical whether the change is a field or a whole new part of the business.
5 minutes
Reading time
A system already created
What you need
The studio
Where you do it
01 Step by step
Learn it on something small
Do not start with the hardest thing your business does. Start with something you can check in ten seconds — a column that should be in the list, a word that is wrong, a field nobody uses.
The point of the first change is not the change. It is that you see the whole loop close, so that when you ask for something that matters you already know what to expect.
01
You describe it
In your own words, the way you would say it out loud to a new member of staff. Not a specification and not technical language — the studio is better at understanding the business than you expect and worse at reading your mind than you hope.
02
It asks what it needs to
Only the questions that change the answer: who else uses this, what happens when two people do it at once, what the message should say. Answer them plainly. A question you skip becomes an assumption you correct later.
03
It builds and puts it live
Screens, database, rules and the address to reach them. This is where the credits go, and you watch it happen rather than waiting for an email in a week.
04
You use the real thing
Not a mock-up. Open it, put a real record in, and try to do the job you actually do. Half of what is wrong only shows up here.
05
You say what is wrong
"The list should show the phone number." "Reminders at six the evening before, not the morning of." Each correction is another sentence and the loop starts again — that is the whole method.
02 In your own words
What a sentence turns into
None of these are settings that happened to exist and none are chosen from a menu. Each one is written for your system in the moment you ask for it.
Which is also why the phrasing matters more than the vocabulary. Say what should happen and when; the studio decides how.
WHAT YOU TYPE, AND WHAT COMES BACK
| I need to see which invoices are unpaid. | A screen listing them, oldest first |
| Add the car's registration number. | The field, in the form and the list, on existing records too |
| Email me a summary every Monday at eight. | A job that runs whether or not anyone is logged in |
| Clients should book their own appointments. | A public booking page and a confirmation email |
03 What to watch for
A
B
Check before you trust it
AI output is occasionally wrong in a way that reads perfectly well. Look at what came back — especially anything that calculates money or sends something to a customer.
C
Say what is wrong, not how to fix it
"The total is missing VAT" gets you further than an instruction about which file to change. Describe the symptom; the studio knows the software.
04 Where to go next
READ NEXT
Describing what you need — the bad sentence beside the good one, and why the difference is everything.
The studio — the whole method on one page, including what it is bad at.