Start here
If you’re staring at an empty prompt box, start with whichever of these 5 sounds closest to what you have in mind. Each one is a complete first prompt that builds a working app. Turn a spreadsheet into an appNot sure what you want yet?
Turn on plan mode before your first build. Base44 asks you a few questions, then turns your answers into a structured plan you can adjust before anything gets built.
Starting a business or work app
These prompts build tools for running something: a business, a team, a side hustle. Each one gives you a working app you can put real data into on day one. Invoice trackerStarting a client-facing app
These prompts build things other people use, where the experience they get matters as much as the data you collect. Client portalStarting a knowledge or content app
These prompts organize information so it can be found again, which is most of what internal tools actually do. Team knowledge baseStarting a personal app
These prompts are for your own life. They’re small enough to finish in an evening and useful enough that you’ll keep opening them. Meal plannerStarting something just for fun
These are the ones people build at 11pm and then send to everybody they know. They’re also the fastest way to get a feel for how prompting works, because nothing is at stake. Absurd name generatorAdding what every real app needs
Once your app exists, these are the features it turns out to need. Send them one at a time to an app that’s already running. Add loginsChanging how your app looks
Design prompts work best when you describe the mood, the layout, and what you want left alone. These 4 cover most of what people ask for. Restyle the whole appMaking your app do the work for you
This is where an app stops being a place you type things and starts being something that runs on its own. These prompts set up workflows, emails, AI agents, and connections to the tools you already use. Welcome and follow upGetting your app in front of people
Building it is half of it. These prompts cover the part where other people arrive, understand what they’re looking at, and pay you. Charge for accessFixing and refining
Most of building is not the first prompt, it’s the twentieth. These are the prompts for when something came out wrong, and they’re the ones worth learning by heart. Keep changes where you want themPrompt pathways
The best apps grow one prompt at a time. A pathway is a sequence where each prompt adds one thing, so every change is small enough to check before you move on. Here are 3 you can follow end to end, swapping in your own subject.From a spreadsheet to a tool your team uses
From a spreadsheet to a tool your team uses
Send these in order, checking the result after each one:
- “I track [our job applicants] in a spreadsheet with columns for [name, role, stage, and source]. Build an app that replaces it, with a sortable table and a side panel for adding and editing.”
- “Add accounts. My team logs in with Google, and each person sees every applicant. Give me an admin role that can also delete.”
- “Turn the table into a board with columns for each stage, so I can drag an applicant from one stage to the next.”
- “Let me attach a CV to each applicant, and use AI to pull out the name, current role, and years of experience so I can check them before saving.”
- “Every Monday at 9am, email me everyone who has sat in the same stage for more than 7 days.”
- “Add a dashboard as the home page with 4 cards for applicants per stage and a chart of applications per week.”
From an idea to something people can pay for
From an idea to something people can pay for
Send these in order, checking the result after each one:
- “Build a [meal plan library] where I publish [weekly plans] with a title, description, cover image, and downloadable PDF.”
- “Add a public landing page for people who aren’t logged in: a one-sentence headline, 3 benefit cards, and a sign-up button.”
- “Add accounts. Anyone can sign up free and see the 3 most recent plans. Everything older is locked.”
- “Let people pay [9 dollars a month] to unlock the full library, and upgrade their account automatically once they’ve paid.”
- “When somebody subscribes, email them a welcome message with a link to the library.”
- “Set the public pages up to be found in search, with clear titles and descriptions and a sitemap.”
From a simple tracker to something that runs itself
From a simple tracker to something that runs itself
Send these in order, checking the result after each one:
- “Build a tracker for [my freelance projects] with a client, a rate, hours logged, and a status.”
- “Add a dashboard with cards for hours this week, unbilled hours, and revenue this month.”
- “Every Friday afternoon, email me a summary of the hours I logged this week, grouped by client.”
- “Add an AI assistant I can chat with that logs hours, creates a project, and answers questions about my totals.”
- “When a project is marked complete, generate a draft invoice from the logged hours and email it to me for review.”
- “Make the whole thing work properly on my phone, since that’s where I log hours.”
Micro-prompts for polish
Small refinements take an app from working to finished. Send these to an app that’s already running, or fold a few into your first prompt for a more styled result from the start.Motion and feedback
These add the small reactions that make an app feel alive rather than static.Type and color
These set the visual character of the app in one line each.Overall feel
These describe a whole personality rather than one detail.FAQs
Here are answers to common questions about using the prompts on this page.Do I have to fill in every bracket?
Do I have to fill in every bracket?
No. The brackets mark the parts most worth personalizing, but a prompt still works if you leave some as they are. Base44 treats whatever’s inside them as your description, so
[my client projects] builds an app about client projects. Change the ones that matter to your idea and leave the rest.How long should a prompt be?
How long should a prompt be?
Long enough to describe what you want to see, short enough to be about one thing. The prompts here are roughly the right length: a few sentences covering what it does, how it’s laid out, and anything that shouldn’t change. If your prompt covers several unrelated features, split it and send them one at a time.
Can I use these on an app I've already started?
Can I use these on an app I've already started?
Yes, apart from the ones in the starting sections, which create a new app. Everything from Adding what every real app needs onward is written to be sent into an app that’s already running.
Where else can I find prompts?
Where else can I find prompts?
Many feature pages include example prompts for that specific feature. The most useful ones are on creating workflows, built-in integrations, design foundations and layout, managing your app data, and setting up payments.
Is there a faster way than starting from a prompt?
Is there a faster way than starting from a prompt?
Yes. App templates are complete apps built by the community that you copy into your workspace and change from there. A template gets you further on the first click, and you can carry on with the prompts here from that point.
Want to write your own prompts?
The prompts here all follow the same few habits: describe what should be on the screen, say why you want it, and change one thing at a time. The prompt guide walks through each one.