Skip to main content
Once you’ve determined that people will pay for your idea, you might be tempted to build everything a real business has, like a booking calendar, team logins, online payments, dashboards, and more. However, you won’t know at first whether you need any of that, so start by building an MVP (minimum viable product) before you add more features. Your MVP is the smallest version of your product that provides enough value for someone to pay for it. By starting with a small first version, you can get your product to real customers faster and learn what you need to build next based on how they use it. This article continues with the example of Maya, who wants to launch a move-out cleaning business. In Test your business idea before you build it, Maya tested her idea and her prices with a landing page. Fourteen property managers joined her waitlist, and most of the managers who clicked a price picked the clean with a 24-hour guarantee. Now, Maya needs an app that property managers can use to request a clean. This article also includes examples for two other businesses: a meal-prep subscription and an invoicing app for freelancers. To see each step of Maya’s build, from writing her product brief to sharing her app with her first managers, watch the video. This article covers the same steps, with example prompts you can copy for your own business.

Write a product brief

Before you start building, use the information you gathered during testing to create a five-line product brief with the following information:
  • User: Who it’s for, described as narrowly as you can.
  • Problem: What the problem costs your users today, in time or money.
  • Core job: The main thing your users are trying to get done.
  • Workflow: The steps a user takes from starting the job to knowing it’s done.
  • Success criteria: A result that shows your first version is working.
    Write your success criteria as a number of people taking a specific action within a specific amount of time, like the bar you set when you tested your idea. Write down these criteria before you build anything so you can judge your results objectively.
For example, here are product briefs for three different businesses:

Choose one workflow to build first

The first version of your product should do one job from start to finish. Start with the “happy path,” which is the workflow most people follow when everything works as expected. For most businesses, the happy path is that someone asks for something, you respond, and they see that it’s done. Maya’s happy path is that a manager requests a clean, Maya confirms it, and the manager sees when the unit is ready to rent. When you start, leave out everything that isn’t part of the happy path, like settings, extra dashboards, customization options, and situations most users won’t encounter. Each feature you add is another place where something can break, so build only the happy path until it works well. Most first versions need only three things to support their workflow:
  • Login: A login page lets you limit who can use your app and what they can see. Maya’s managers see only their own requests, and Maya sees every request because she’s the owner. To learn more, see Authentication.
  • Database: A database lets your app store and retrieve information. Maya’s requests are saved in her app instead of in a text thread or an email. To learn more, see Database.
  • Status updates: Status updates keep your customers informed about the progress of their requests. Maya’s requests go from Requested to Confirmed to Rent-ready, so managers don’t have to call to find out if a unit is ready.
Save admin settings, permission levels, and team accounts for when you need them. Maya doesn’t have a team yet, so she doesn’t need team accounts.

Turn your brief into a prompt

Your prompt can follow this structure:
  • Context: Who you are, what you learned from testing your idea, and what you need now.
  • User: Who uses the app. If there’s more than one type of user, like customers and you as the owner, name each one.
  • Core job: The one job the app does, from your product brief.
  • Workflow: The steps of your happy path, including what each screen shows.
  • Who can see what: Which information each type of user can see and change. If you’re the owner, include the email address you’ll sign up with, so Bolt knows which account is yours.
  • Constraints: Requirements like how the app should work on phones and the colors to use. You can describe colors in plain words. If you already have color codes, like #1F8A5B, you can include them.
  • Do not build: Everything you’re tempted to build that isn’t part of your workflow.
The Do not build line tells Bolt what to leave out, so that your first version stays small enough to launch soon. Use the first step of your workflow to describe your start screen. Before someone signs up, they want to know what it costs, how they pay, who’s behind the app, and what happens after they sign up. Your start screen can answer all four questions without any extra features. Maya’s start screen shows her prices, says that she sends an invoice after the clean is done, gives a phone number to text with questions, and promises that she confirms requests within the hour. To build the first version of your app:
  1. From the examples below, copy the one that’s closest to your business, then change the details to match yours.
  2. From the Bolt homepage, paste your prompt in the chatbox and press Enter. Bolt starts a new project and begins building. A new project keeps your app separate from the landing page you built to test your idea, so your waitlist page and its data stay as they are.
  3. In the preview, try your workflow. For example, Maya signs up as a manager with a second email address and requests a clean. Then she logs in with her own email address, which makes her the owner, and changes the status to Confirmed.
For more ways to get the results you want from Bolt, see Prompting effectively.

Make your app intuitive for first-time users

When your app is built, walk through it as if you’d never seen it before. Make a note of anything that might confuse a first-time user, and check for these four things:
  • A clear empty screen: Before someone has used the app, the screen tells them what to do first. Maya’s says, “No cleans yet. Request your first one.”
  • Helpful error messages: Errors explain what went wrong, so people can fix it on their own. If a manager picks a ready-by date that’s earlier than the move-out date, Maya’s app explains the problem so the manager can pick a new date.
  • A welcome message: A short message tells first-time users how the app works, like what each status means. Maya’s explains what Requested, Confirmed, and Rent-ready mean.
  • A layout that works on phones and computers: Buttons and actions are clear on any screen size. To check different screen sizes, use Responsive mode in the preview controls.
To fix something you find, describe the change to Bolt in a prompt. For example:
Your first version needs to work well enough for people to test it. You can add design details and polish later.

Test your app as different kinds of users

When your app has more than one kind of user, check that each one can see and change only what you described in the “Who can see what” part of your prompt before you share the app. For example, Maya signs up with two test manager accounts and checks that each account sees only its own requests and lockbox codes. To learn more, see Security.

Share the product with your first users

When your app works in the preview, publish your project to get a bolt.host URL that you can share with real users. Start by sending your product link to a small group of people who have the problem your product solves and are most likely to use it right away. These can be your best waitlist signups or people you talked to while testing your idea. Send the link to each person yourself instead of posting it publicly. Maya texts the link to the nine managers on her waitlist who turn over two or more units a month. Keep your waitlist page up while you share your MVP so you can keep collecting signups for your next group of users.

What if not enough people use my product?

If fewer people use your app than your success criteria call for, talk to the people you sent it to before you add more features. Ask what kept them from using your product, work their feedback into the app, and send the link again. If fewer than three managers request a clean within two weeks, Maya calls the managers she sent the link to before doing any more work on the app.

Keep a “not yet” list to plan for future features

As you build and talk to users, you’ll think of features you want to add. Write them on a “not yet” list instead of building them right away. That way, you can keep your first version small while you keep track of ideas to build later. For example, Maya thinks online payments would be useful but decides to wait until she has more customers. Other big ideas, like expanding into other cities, can also wait until she establishes herself in her current market. To decide when an item on your list is ready to build, ask yourself:
  • Have users asked for this?
  • Does anyone get stuck without it?
  • Can I handle it manually for now, like sending invoices myself?