Make it plan before it builds

The usual first go at vibe coding is one paragraph typed into the box Base44 opens on. That box starts in Build mode, and Build mode acts at once. One build later there are screens, a login and a table called Customers you never asked for. It looks finished.

Then you want to change what a booking is. Every change touches three screens. The credits go on undoing a decision nobody made.

Planning is not a delay. It is not a document for someone else, not a form to fill in, not a mood board with four colour schemes on it. It is the point where changing your mind costs a fraction of a credit, not a rebuild.

The rules

Nothing gets built from the first message. Plan mode turns a short conversation into a plan you can adjust before anything is built. The Mode dropdown shows Build by default, so you change it on purpose. Once the app exists, Discuss mode does the same job for each change. It proposes. Nothing is built until you approve.

Bring your own sentence and your own tables. The plan panel tracks four things: intent and goal, audience and roles, core flows, and design. Your tables are not one of them. Leave them out and the builder picks them. The sentence comes from Write the one sentence the app has to earn, and the tables from Model your data before you generate a screen, the first two steps of Ship an app without a dev team. If you arrived here first, the prompt below asks for a short version of both.

Every table says who owns its rows. A customer's job belongs to that customer, so it carries their email. Collection times belong to the business, so the plan says admin only. A table left silent on ownership gets a guess. Step three cannot lock a row to an owner nobody wrote down.

Correct the plan in the same conversation. Base44's own guide says to review the plan and keep typing when something is wrong. A correction you only noticed is one the build never hears.

Price the whole track before you spend a credit. On the Free plan in September 2026 you get 25 message credits a month, 5 a day at most. Planning costs a fraction of a credit a message. The first build costs about one. Each Testing Agent run in step five costs one to four. The page "Why is the AI burning my Base44 credits fixing its own mistakes", in the Base44 section of this site, shows where the rest goes.

Do it now

1. Put your sentence, your tables with their fields and owners, your roles, your pages and your refusals on one page.
2. Before you type anything into Base44, click your workspace name at the bottom left, then Settings, then Credit usage under General. Write down the Message credits used figure.
3. Go to Base44. In the prompt box, open the Mode dropdown, which shows Build, and choose Plan.
4. Fill in the prompt below from your page and send it.

Plan this app. Build nothing yet.

Put this sentence at the top of the plan, word for word:
<your one sentence>

Tables, and no others:
<Table>: <field>, <field>, <field>. Owner: <the field naming who each row belongs to>
<Table>: <field>, <field>. Owner: admin only

Fixed lists, never free text:
<field>: <value>, <value>, <value>

Roles: <role> and admin. The only admin is <name>.
Pages: <page>, <page>, <page>. Admin only: <page>.
The app will not: <refusal>, <refusal>, <refusal>.

First build: the tables and one page, <page>. Nothing else until I ask.
Write every table, field, owner, role and page into the plan exactly as above.
Ask me about anything missing. Add no table, field, role or page I have not listed.

5. Answer its questions. When the design question arrives with its four previews, skip it. Base44 lets you skip the question.
6. When the plan appears, check it line by line against your page. Type every correction into the same conversation until it matches.
7. Copy the finished plan into your page, under your sentence. That copy is yours whatever happens to the screen.
8. Do not click Start Building. Open Credit usage again and write down the new Message credits used figure beside the first.

A worked example

Rhys re-covers chairs and sofas on his own. A normal week is 14 jobs, and a quote is turned round in a day. Every one of them starts with a phone call he takes with a staple gun in his hand.

Sentence:   A customer sends a photo, books a collection and sees when the piece is ready, without phoning Rhys.
Job:        photo, description, quote, status, collection slot, mobile, customer email
            Owner: customer email
Status:     new, quoted, booked, in the workshop, ready, delivered. A fixed list
Slot:       collection day and time. Owner: admin only. Customers read it, Rhys changes it
Roles:      customer and admin. Rhys is the only admin
Pages:      Send a photo, Book a collection, My jobs. Admin only: This week
Will not:   take payment, quote from a photo without Rhys, keep a mailing list
First build: Job, Slot and Send a photo. Nothing else
Corrected:  the plan added a Customer table. Removed. The email on Job is the owner
Corrected:  status came back as free text. Changed to the fixed list of six
Credits:    Message credits used read 2.0 before planning and 3.2 after. Planning cost 1.2
Start Building: not clicked

Two tables, two roles, four pages. Nothing built.

The failure you will hit

The design question will pull you in. Four working previews of your main screen, each one refinable up to three times. It feels like the app arriving. Skip it. The look is the cheapest thing to change later.

The quieter failure is a table you did not list, coming back sounding sensible. A Customers table. A Settings table. Delete it in the conversation now, while it costs a sentence.

Not for you if

You want screens tonight. This step ends with none, on purpose. If that feels like wasted time, you will skip it and pay in step two.

Know the cost before you start. Steps one to three run on the Free plan. Step four needs the Builder plan, for backend functions. Step five's own domain needs Starter or higher. That is how Base44's plans page shows it in September 2026. If you will not pay for Builder, stop after step three. Keep every outside service's key out of the app.

In step two you click Start Building on this plan, build one screen, and go back on purpose. The Base44 section of this site answers the questions people ask most about Base44, and the Vault is the paid library, with Operations one of its categories.