Bolt.new is worth paying for if you can describe one narrow tool clearly and will test it carefully, and a small project usually fits within Pro's $25 month. It is poor value if you cannot check the result. In the illustrative project below, the first build takes about a quarter of the tokens and the fixes take the rest.
Bolt sells tokens, not projects, so no one can give you a fixed price for yours. What you can do is price a single project in stages, count the fixes honestly, and compare the total against the Free plan, Pro and simply hiring someone. That is what the rest of this tutorial does, with figures that are illustrative and labelled as such.
What Bolt charges for, and what it does not
On Bolt's pricing page the Free plan costs $0 and gives 1 million tokens a month, with a daily cap of 300,000 and no rollover. Pro lists at $25 a month on monthly billing, starts at 10 million tokens a month, has no daily cap, and unused tokens roll over (the page says they stay in the balance for up to two months while the subscription is active). Teams lists at $30 per member a month, and each paid member gets their own allowance. Yearly billing saves up to 28 percent, according to the page. Free-plan sites carry Bolt branding, and Pro removes it and allows custom domains. Check Bolt's pricing page for the current numbers.
The page does not say how many tokens a typical project uses. Top-ups exist but are narrower than you might expect: Bolt's help centre says token reloads can be bought only on the highest monthly Pro tier or on an annual Pro plan, the price depends on the plan and shows at the reload screen, and reloaded tokens do not expire. That is why every figure below is a worked illustration. The one reliable rule from Bolt's own FAQ is that tokens are spent when the AI reads your prompts and project files, plans, or writes code. So a project gets more expensive to change as it grows. If you want a different business tool measured in this way, Bolt.new pricing: how many tokens a business tool really uses walks through one.
The project: an instant-estimate page for a removals firm
For a worked example, take a small removals firm that wants a web page where a customer picks the number of bedrooms, the distance band and whether they need packing, and sees a price range plus a "request a booking" button. The owner cannot code. She writes a plain-English brief of about 250 words and gives it to Bolt.
The brief matters more than most people expect. Here is the shape of one that works, with the figures filled in.
Build a single-page removals estimate tool.
Inputs: bedrooms (1 to 5), distance band (under 25 miles, 25 to 100 miles,
over 100 miles), packing service (yes or no).
Prices: base by bedrooms 350, 520, 700, 880, 1050.
Distance adds 0, 180 or 420. Packing adds 40 per bedroom.
Show a range of plus or minus 10 percent, not a single figure.
Button: "Request this booking" opens a form with name, phone, email, date.
Style: white background, one accent colour, works on phones.
Do not add anything not listed here.
The last line stops the model adding invented features, each of which would cost tokens to build and again to check. That is a practical saving worth more than any plan choice.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe token bill, step by step
These figures are invented to show the shape of a real project. Yours will differ, and the balance on Bolt's Subscription & Tokens settings page shows the real numbers as you go.
| Step | What happens | Illustrative tokens |
|---|---|---|
| 1. First build | The brief becomes a working page | 220,000 |
| 2. Fix the price maths | 3 bedrooms with packing shows the wrong total | 85,000 |
| 3. Phone layout | Buttons overflow on a narrow screen | 70,000 |
| 4. Validate the form | Empty phone number accepted; email not checked | 90,000 |
| 5. Send enquiries somewhere | Form submits to nowhere; needs a destination | 140,000 |
| 6. Wording changes | Three small text and colour tweaks | 60,000 |
| 7. Regression fix | The step-5 change broke the date field | 110,000 |
| 8. Final polish | Spacing and error messages | 75,000 |
| Total | 850,000 |
Two things stand out. The first build is only about a quarter of the total, so a budget based on "one prompt" is wrong by a factor of four. And the regression fix in step 7 exists because every change can break something that worked, which is the most underrated cost of building by prompt.
Where that lands on each plan
On Free, 850,000 tokens fits inside the 1 million monthly allowance, but not in one sitting: the 300,000 daily cap means steps 1 and 2 (305,000) already hit it on day one, and you wait until the next day for step 3 and onward. Spread over three to four days, the project completes for $0. If the owner makes two more mistakes or changes her mind about the layout, she goes over the monthly million and stops until the next month.
On Pro, the same project uses about 8.5 percent of the 10 million allowance, and there is no daily cap, so it can be finished in one afternoon. The cost is $25 for the month, plus nothing else if she cancels afterwards: Bolt keeps the plan and unused tokens until the billing period ends, then moves the account to Free. If she keeps paying instead, unused tokens roll over for up to two months, so a second small project the following month draws on the leftover as well.
So for a single tool like this, the arithmetic is: Free if you can wait and your brief is tight, Pro if you want it done in a day or expect to keep changing it. Paying $25 to finish a task that would otherwise take a week of evenings is a cheap trade when the tool brings in even one booking.
The costs that are not tokens
The token meter measures only the building. Other things need to be on the sum before you call a project "free".
- Your time. Writing the brief took an hour, testing took another hour per round of fixes, and eight steps with testing is perhaps 8 to 12 hours. At $25 an hour that is $200 to $300, which dwarfs the subscription.
- A domain. Pro allows a custom domain, but registering one is a separate cost that depends on the registrar and the name. Check a registrar's current price rather than relying on a figure from a tutorial.
- Where the enquiries go. Step 5 above sends form data somewhere. Using an email destination is simple; connecting a database or an outside service can bring its own plan and limits, so read those pages before you rely on them.
- Maintenance. If the price list changes, someone must update the prompt, rerun it and test again. Put the prices at the top of your saved brief so the change is one line. Bolt's help centre also notes that direct edits in Code view use no tokens, so a single changed figure can be typed straight into the code if you can find it.
A realistic all-in figure for the removals page is therefore a month of Pro ($25), a domain, and about ten hours of the owner's time, against the alternative of paying a freelancer to build a quote form. If you are weighing that, Is paying for AI help worth it? sets out your time against an expert's fee.
Testing like a customer when you cannot read the code
The skill a non-coder actually needs is testing. A page that looks right can hide arithmetic errors, and the price is the one thing you cannot get wrong. Use a test sheet like this one, filled in for the removals page.
| Test input | Expected result | Passed? |
|---|---|---|
| 1 bed, under 25 miles, no packing | 350, range 315 to 385 | Yes |
| 3 bed, 25 to 100 miles, packing | 700 + 180 + 120 = 1,000, range 900 to 1,100 | No, showed 1,060 (fix needed) |
| 5 bed, over 100 miles, packing | 1,050 + 420 + 200 = 1,670, range 1,503 to 1,837 | Yes |
| Form with phone left blank | Error message, no submit | No (fix needed) |
| Phone screen, 360 pixels wide | No sideways scrolling | No (fix needed) |
Work out expected answers on paper before you look at the page. If you check the page first, you tend to agree with whatever it shows. After every fix, run the whole sheet again, not just the failing row, because regressions are how step 7 appeared.
Writing the fix prompts so they cost less
Fixes are the expensive part, and the way you word them changes both the tokens used and the chance of breaking something. Here is a weak and a strong version of the step-2 fix.
Weak: "The price is wrong, please fix it."
Strong: "For 3 bedrooms, 25 to 100 miles, with packing, the total shows 1,060. It should be 1,000 (700 base + 180 distance + 120 packing at 40 per bedroom). Fix only this calculation. Do not change layout or wording. Show me the formula you used."
The strong version names the exact case, the expected figure and the working, and it fences the change. The model has less to guess, so it is less likely to rewrite unrelated parts. Asking to see the formula also lets you check it against your brief, since you can read a sum even if you cannot read code.
The mistake of letting the tool keep going
One failure shows up again and again. A fix does not work, the owner asks again, the model tries a different approach, and four prompts later the page is worse than it was and 400,000 tokens have gone. The pattern is a loop, and more prompts feed it.
The way out has three parts. Restore the last version that worked through Version history, which Bolt's help centre says restores a project without consuming tokens. Rewrite the request from scratch with the exact failing case. And set a stop rule in advance: no more than two attempts at one problem before you step back. If a single bug has cost more than 150,000 tokens, it is time to change how you ask or bring in a person, not to ask again.
Four other projects, quickly priced
The removals page is a mid-sized example. Here is how the same approach looks for other small businesses, with the same caveat that all numbers are illustrative.
- A florist's event enquiry form: mostly a form with five fields and an email destination. Perhaps 300,000 to 450,000 tokens including fixes, and a good fit for Free over a weekend.
- A landscaping company's before-and-after gallery: image-heavy, so the work is layout rather than logic. Cheaper in tokens but more fiddly to test on phones; allow two or three layout fix rounds.
- A bookshop's reading-group sign-up: a form plus a list page of members. The list page needs storage, which is where outside services come in and the risk of surprise costs rises.
- A staff holiday planner: several users, logins, dates and rules. This is the type where prompts alone struggle, and where a spreadsheet or an existing planner is usually the better choice than a build.
The pattern: forms and calculators fit Bolt well, anything with logins, payments or shared data does not. If your idea sits in the second group, read No-code AI tools vs a custom build before you spend a token.
Three ways the same project can go
Because a build is a string of small decisions, the same removals page can cost very different amounts. Here are three runs of it, all illustrative.
The tight run. The owner writes the full brief above, tests the first build against her paper sheet, and sends one combined fix covering the price maths and the phone layout. Total: about 550,000 tokens in five prompts. Free covers it across two days.
The wandering run. She starts with "make me a quote page for my removals firm" and lets the model choose the inputs. She then adds a gallery, a testimonials block and a map over the next dozen prompts. Each addition reads a larger project, so the later prompts cost more. Total: 2.4 million tokens, over Free's monthly allowance, and a page with features she did not want to maintain. Pro handles it, but she has paid $25 for tokens spent on decoration.
The stuck run. The form needs to send enquiries to a booking system she already uses. Nothing in the brief says which, and the model builds a generic form that posts nowhere. Three prompts try to fix it and each makes it slightly worse. Total: 1.3 million tokens and no working submit button. The fix turns out to be an email destination or a link to the booking system's own form, neither of which needed a build.
The lesson is that the brief, not the plan, sets the bill. A paid plan removes the daily wall, but it does not stop a vague project from consuming a lot of tokens.
A brief checklist to fill in before the first prompt
Copy this and answer each line in a sentence. If you cannot answer one, that is the thing to decide before you spend any tokens.
- The one job. "A customer gets a price range in under a minute." If you need two sentences, you probably have two tools.
- Every input and its allowed values. Bedrooms 1 to 5, three distance bands, packing yes or no.
- Every figure and rule, written out, so the model does not invent any.
- What happens at the end. Who receives the enquiry, in what form, and what the customer sees afterwards.
- What you will not build. No logins, no payments, no gallery.
- Three test cases with answers worked out on paper.
- A stop rule. Two attempts per problem, then restore and rewrite.
The same brief, before and after
A first-draft brief for the florist's enquiry form read: "A nice form for wedding flowers with all the details I need." After the checklist it became: "One page, five fields (name, email, event date, venue, budget band of under 500, 500 to 1,500 or over 1,500), a 'send enquiry' button that emails the florist, a thank-you message, white background, one accent colour, nothing else." The second version leaves the model almost nothing to guess, and it makes the result testable: there are five fields, one button and one message to check.
Choosing Free or Pro with one question
Ask: "Can I finish within the daily cap and the month's million tokens if I follow the brief?" Use these quick tests.
- If your first build plus two fixes would exceed 300,000 tokens in a day and you cannot wait, take Pro for one month.
- If you will show the page to customers and want your own domain and no Bolt branding, you need Pro anyway.
- If you are still learning and might abandon the idea, start on Free; you lose nothing but time.
- If you expect to change the page every month, remember paid tokens roll over for up to two months, so a light month is not wasted.
Whichever you choose, record the token counter before and after each prompt in a notes file. After three prompts you will know what your own projects cost, and that is more reliable than any figure here.
When the answer is no
Bolt is not worth it if the job is already done by something you own. A quote form is a feature of many website builders and a form tool plus a spreadsheet does most of what the removals page does without any prompting. It is also a poor choice if the tool will handle card payments, health information or other sensitive data, because you cannot review the code yourself. In that case, a developer should build or at least review it. A half-built app is a common reason owners seek help, and Hiring a Lovable expert to finish a half-built app shows what a brief and a budget for that look like.
A short rule to finish: if you can describe the tool in one page, test it on your phone with five odd inputs, and the data is not sensitive, a month of Pro is a cheap experiment. If you cannot meet all three, spend the $25 on a conversation instead.
What non-coders ask about Bolt.new
Can I finish a small project on Bolt's free plan?
Sometimes. Free gives 1 million tokens a month but no more than 300,000 a day, and tokens do not roll over. A simple tool with a handful of fixes can fit, but you will spread it over several days. If the first build and two fixes already use the daily cap, expect to pause.
Do tokens run out faster as the project grows?
Yes. Bolt spends tokens reading your project files as well as your prompt, so the same short instruction costs more on a large project than on an empty one. Fixes at the end of a build tend to cost more than the first prompts did.
Do I need to know any code to use Bolt.new?
No, but you need to test like a customer. You describe changes in plain English and check the result. You cannot judge the code, so you must judge the behaviour: try odd inputs, a phone screen and the empty state before anyone else sees it.
What if the tool breaks after I publish it?
Keep a list of the prompts that built it and test it again after every change. For anything handling money or customer data, have a developer review it. Fixing a live bug with more prompts can spend tokens and still miss the cause.
Further reads
- Are AI Tools Built for Coaches Worth Paying For Over ChatGPT? — Another worth-it test, for tools built for one profession.
- Are AI Lifetime Deals Worth Buying for a Small Business? — Why cheap one-off tool deals can cost more later.
- Free vs Paid AI Marketing Tools: What Is Worth Paying For — A rule for deciding which subscriptions earn their fee.
- How Much Does It Cost to Automate Social Media With AI? — Price another automation before you build it.
- How Much Does It Cost to Automate Lead Follow-Up With AI? — What the enquiries from your new form need next.
- Is AI Worth It for a Small Business? How to Work Out Your Answer — Work out whether any AI spend pays off for you.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Bolt.new pricing page and FAQ, Bolt help centre articles on tokens and on maximising token efficiency, checked 5 November 2026. Token figures in the worked example are illustrative.