A small business can build a quote calculator in Bolt.new by describing its price table, calculation rules and customer form in plain language, then testing the generated page against hand-calculated quotes. Publish the checked version through Bolt hosting, and link to it or test an embed on your existing website.
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 nowBolt.new here means the AI app builder at bolt.new, made by StackBlitz, not Bolt, the ride-hailing and delivery app. Start with an estimate that needs no customer account, payment or saved personal information. That keeps the first version focused on one question: does the customer see the same price your team would calculate from the approved rate sheet?
Why write your rate sheet down before opening Bolt?
Write the rate sheet as a calculation contract first, because Bolt can only build a correct calculator from prices and rules you have stated exactly. Consider an illustrative cleaning company that prices routine visits by bedrooms and bathrooms, with two optional extras. The owner wants customers to understand the likely charge before requesting a visit. The calculator must describe an estimate, because unusual access, condition or scope still requires staff review. Every amount below is an invented teaching figure, not a recommended market rate.
| Item | Illustrative rule | Customer explanation |
|---|---|---|
| Base visit | $45 | Included once per visit |
| Bedroom | $18 each | Whole numbers from zero to six |
| Bathroom | $25 each | Whole numbers from one to four |
| Oven cleaning | $35 | Optional, once |
| Interior windows | $20 | Optional, once |
| Minimum estimate | $95 | Applied after the items are added |
A three-bedroom, two-bathroom property with oven cleaning gives $45 + $54 + $50 + $35 = $184. With no extras, a zero-bedroom, one-bathroom property gives $70 before the minimum, so the customer sees $95. Write both calculations on paper before opening the builder. These become acceptance tests: known inputs with agreed outputs.
Decide what the numbers mean. Does a bedroom used as an office count? Does the window option cover every window or only an agreed set? In this illustration the answer is one room counts once regardless of use, and windows cover the standard package described alongside the checkbox. If the actual business cannot define an extra clearly, replace that extra with “ask for a tailored quote”.
Keep commercial exceptions visible. The calculator should route properties above six bedrooms or four bathrooms to staff rather than silently cap their quantities. A customer entering seven bedrooms must not receive a six-bedroom estimate. Record those boundaries in the same document as the price table, so a future price edit does not erase the rules that make it safe.
What should you ask Bolt to build first?
Ask Bolt for the smallest useful estimate page: one screen with named inputs, an exact formula and an itemised result. Open Bolt.new, paste the build request into the chatbox and select Build now; Bolt then asks you to sign in or sign up (Google, GitHub or email, with no card needed for Free) and shows the result in a Preview window, as its QuickStart describes. Describe the desired behaviour before styling details: labels, allowed inputs, formula, output wording and exclusions. An instruction such as “make a professional cleaning calculator” leaves the builder guessing the most important business decisions.
Build a single-page cleaning estimate calculator.
No account, database, payments, AI answering or personal data collection.
Inputs: bedrooms 0–6, bathrooms 1–4, oven yes/no, windows yes/no.
All room quantities must be whole numbers. Do not silently correct invalid inputs.
Estimate = maximum of 95 and (45 + 18*bedrooms + 25*bathrooms
+ 35 if oven selected + 20 if windows selected).
Use USD. Show the itemised calculation and minimum adjustment.
Label the result "Estimated visit price", with scope subject to staff review.
For quantities outside the range, show "Request a tailored quote".
Include clear labels, keyboard access and a visible contact alternative.
Keep the pricing constants together so future changes are easy to review.
Do not invent discounts or add integrations.
The prompt is a specification, not proof the app obeys it. When the preview appears, enter the $184 case and read the line items. An illustrative acceptable output is “Base $45; bedrooms $54; bathrooms $50; oven $35; estimated visit price $184”. If the screen shows only a large total, ask for the breakdown before making any cosmetic changes.
Give corrections one at a time. For example: “The minimum is missing. For zero bedrooms and one bathroom without extras, show subtotal $70, minimum adjustment $25 and total $95. Preserve the other rules.” That request supplies the failure, the expected result and the boundary of the change. Asking Bolt to “fix the maths everywhere” makes a later regression harder to trace.
Do not let convenience widen the project. If the generated draft offers a customer login, a chat assistant or an online payment button, remove it from scope. Those features create new responsibilities without helping the first arithmetic test. Read the Bolt.new versus Replit business-tool comparison if you are still deciding where this calculator should live.
How many tokens does a quote calculator use?
A calculator with no login or database is a smaller job than a full app, but your token use will differ, so keep a ledger of each request instead of guessing. Bolt measures its building work in tokens, small pieces of text it processes as it reads, thinks about and builds your project. Its token page says most usage comes from reading and syncing the project files, so a bigger project costs more per message. At the time of writing, the pricing page lists Free at $0 with one million tokens a month and a 300,000-token daily limit, and Pro from $25 a month billed monthly with ten million monthly tokens and no daily limit. Free tokens reset on the 1st of each month; unused Pro tokens stay in your balance for up to two months.
The number of form fields does not fix the token bill. For scale, Bolt's QuickStart builds a pet-name app with sign-up, login and a database: its first build used 204,000 tokens, a one-line title change used about 70,000, and the whole walkthrough uses just under the 300,000 daily limit. A calculator with no login or database is a smaller job, but your figures will differ, so the ledger below is an illustration, not a measurement.
| Stage | Illustrative balance change | Tokens used |
|---|---|---|
| Initial form and formula | 1,000,000 to 830,000 | 170,000 |
| Minimum-price correction | 830,000 to 795,000 | 35,000 |
| Input error messages | 795,000 to 755,000 | 40,000 |
| Small-screen refinement | 755,000 to 725,000 | 30,000 |
| Total | Four assumed requests | 275,000 |
In that invented ledger, 275,000 tokens use 91.7% of the Free daily allowance and 27.5% of its monthly allowance. Another assumed 40,000-token repair on the same day would take the total to 315,000, beyond the daily ceiling. It is a planning example, not a promise that your build fits Free. If you do hit the daily ceiling, Bolt's token page says you can still edit the existing code directly in Code view, which uses no tokens, or wait for the next daily reset.
To measure your own run, open Billing & usage before starting (select your account or workspace name in the sidebar, then Subscription), and switch on Display token usage in chat under Account settings, as the QuickStart describes. The remaining balance then appears above the chatbox. Record it after each request. Do not run other projects during the experiment if you want a clean comparison. Save the request wording next to each reading so you can identify expensive, avoidable rework.
The subscription cost belongs to building and maintaining the tool; it is not a fee per quote in this deliberately arithmetic-only design. Customer calculations should not call an AI model. Ask the builder to confirm that architecture and have it reviewed if you cannot tell. The separate Bolt token-pricing tutorial covers budgeting beyond this single calculator.
How do you catch price errors that a polished preview hides?
Catch price errors by running a written test sheet and marking each case pass or fail, with expected totals the owner worked out independently of the AI. Include ordinary enquiries, boundary values and deliberate mistakes. Do not ask the same AI that created the calculator to invent all expected totals: the owner should calculate those independently. Otherwise a misunderstood pricing rule can appear in both the code and the generated test answer.
- Three bedrooms, two bathrooms and oven: expect $184.
- Zero bedrooms, one bathroom, no extras: expect $95 with a $25 minimum adjustment.
- Two bedrooms, one bathroom, both extras: expect $161.
- Six bedrooms, four bathrooms, both extras: expect $308.
- A blank bathroom field, a negative bedroom number or 1.5 bedrooms: expect an explanation, not a quote.
- Seven bedrooms: expect the tailored-quote route, with no misleading total.
The third example is useful because it tests two independent checkboxes. Its arithmetic is $45 + $36 + $25 + $35 + $20 = $161. Untick the oven and the price should become $126, not $141 or $96. An illustrative faulty draft applied the window charge only when the oven was selected; toggling each option in both orders exposes that dependency.
Also test what happens after an invalid entry. Suppose a visitor first sees $184, then deletes the bathroom number. The old estimate must disappear or clearly become invalid. A red error message under the input is insufficient if a large, plausible price remains below it. Ask Bolt to prevent stale totals being presented as current estimates until the inputs are valid again.
Use keyboard navigation from the top of the page. Every input needs a visible label, and error messages must identify the field that needs attention. Check the page on a narrow phone screen and with enlarged text. A two-column rate table that forces horizontal scrolling may be tolerable for staff but awkward for someone comparing services while holding a phone.
Preserve a plain-text rate summary and contact route outside the interactive area. A generated calculator may rely on JavaScript for arithmetic; the surrounding service page should still explain the offer when scripting fails. Test that failure explicitly. The customer should see “Contact us for an estimate” and the pricing basis, rather than an empty rectangle that suggests the business has disappeared.
If you keep your rate sheet and test cases in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.
How do you publish a quote calculator from Bolt?
You publish a Bolt calculator with the Publish button in the top-right corner, then Publish again in the menu that opens; deployment takes about a minute and the live link appears in the chat. Use those buttons rather than typing “publish this” into the chat: Bolt's publishing page says the Publish and Update buttons use no tokens, while prompting Bolt to publish does. The first publish gets a random address ending in bolt.host, which you can rename with the pencil icon in the Publish menu.
Later edits do not reach the live calculator until you select Update in the same menu. That is useful: you can change a rate in the editor, run the test sheet in Preview and only then update the public page. Open the live address in a separate browser tab. Treat that as a new test environment: a preview working inside an editor does not establish that the public page, contact link and small-screen layout all work after publishing.
Repeat the $184 and $95 cases on the public address before adding it to your website. Ask a colleague who is not signed into your Bolt account to try it too. Record the published address, the rate-sheet version and the date of your own check in the business's maintenance record. That record describes your release, not a vendor release date.
Hosting has its own ceiling, separate from tokens. Bolt's hosting-plans page lists Free sites at up to 10 GB of bandwidth and 333,333 requests a month with a hard limit: a Free site that reaches it stops serving until the next cycle, and it shows a Made in Bolt badge. Paid plans include Pro hosting, with up to 30 GB and one million requests a month, a custom domain, no badge and optional pay-as-you-go traffic up to a spending cap you set. Bolt estimates that Free typically supports around 10,000 to 15,000 visits a month, depending on the site.
For the cleaning company, a calculator linked from one service page sits comfortably inside that estimate during a pilot. The risk is a campaign. If an email to past customers is expected to send several thousand people to the page in a single week, check the hosting usage in Bolt beforehand and decide whether that month justifies a paid plan, rather than discovering an offline estimate page halfway through the promotion.
The simplest installation is an ordinary link from the existing service page labelled “Calculate an estimated cleaning price”. A link keeps the calculator on its own page, gives it enough room and provides a useful fallback when an embedded version fails. You can test demand this way before paying someone to adjust the existing site's layout.
An embed places another page inside your website, normally using an iframe. It is a website configuration step, not a special Bolt token feature. Bolt's publishing documentation does not cover embedding, so ask your website maintainer to test whether both the published calculator and your site's security settings permit framing. Do not assume every hosting configuration accepts it, and do not weaken security headers just to remove an error message. On Free, the Made in Bolt badge is part of the published page, so expect it inside the frame as well.
If your website provides an HTML embed block, the maintainer can start from the following markup, replace the placeholder with the real public address and adjust its layout in the site's own styles. The title describes the frame for assistive technology. Keep the normal calculator link alongside it, and test the completed estimate rather than judging the empty form alone.
<iframe
src="YOUR_REAL_PUBLISHED_CALCULATOR_URL"
title="Cleaning visit estimate calculator"
width="100%"
height="760">
</iframe>
<a href="YOUR_REAL_PUBLISHED_CALCULATOR_URL">
Open the estimate calculator
</a>
Website handover request:
Please test the published calculator in an iframe on a private draft page.
Use the real published URL, a descriptive frame title and responsive width.
Give it enough height for the longest valid estimate and validation messages.
Keep an ordinary "Open the estimate calculator" link beside the frame.
Test phone scrolling, keyboard focus, enlarged text and blocked scripts.
If framing is refused, keep the link version and report the exact browser error.
The MDN iframe reference explains the web element and its title attribute. Use it with your site's own editing instructions. The sample height is only a starting value: the correct published address, usable frame height and site restrictions must come from your actual installation.
For example, an illustrative draft embed looks fine with no extras but clips the itemised total when both extras are selected. The repair is to allow the full result and error state to fit, then check scrolling on the parent page and inside the frame. It is not to shrink all text until the form becomes difficult to read. Keep the independent link available after the embed passes.
If you want help choosing a sensible first calculator and the checks around it, I offer one-to-one AI consultations for small businesses.
How do you change a price without rebuilding the calculator?
Change a price by editing the pricing constants in Code view, which uses no tokens, then re-run every test case before you select Update.
Bolt's Version history (the clock icon in the top menu) lists automatic backups. Select one to preview it, then choose Restore this version and confirm with Restore version; restoring uses no tokens. Hover over a version to rename it with the pencil icon or bookmark it. Name the last tested one “Rates A, six cases passed” rather than leaving “latest good version” to memory, and keep a separate copy of the approved rates and acceptance sheet, because version history is a recovery aid, not a record of your pricing policy.
Imagine the cleaning company increases the illustrative bedroom rate from $18 to $20. The three-bedroom, two-bathroom oven case should move from $184 to $190, while the minimum case remains $95. A one-number change like this does not need a prompt at all: open Code view, search for the pricing constants, change 18 to 20 and save, which uses no tokens. Bolt's QuickStart warns that version history does not cover code-view edits, so log the change yourself, then re-run every acceptance case before selecting Update, because a small edit can still alter wording, bounds or how checkboxes behave.
Specify the customer-facing explanation too. “Bedroom rate updated to $20” is clearer than leaving an old rate in the visible table while changing the total. Test the printed or copied estimate if you later add one. A correct calculation with an outdated explanation creates the same customer argument as an incorrect price, because staff and customer appear to be using different promises.
A furniture maker could adapt the approach to a different illustrative job: $120 base preparation, $40 per shelf and $30 for finishing. Three shelves with finishing total $270. However, timber species, fitting complexity and measurements may make a fixed calculator unsuitable. Offer a narrow standard product first, and route bespoke work to a discussion rather than inventing a universal formula.
A pest-control firm has a different boundary: an estimate for a standard inspection should not become a promise about treatment success or an automatic treatment recommendation. An illustrative $60 inspection plus a $15 access option gives $75, but uncertainty about the job should trigger staff review. The lesson is to encode priced scope, not let the generated interface create new service commitments.
Does the calculator earn a place on your website?
A calculator earns its place when a customer can move from the estimate to an enquiry without retyping their choices, so test that handoff as a separate task. In the cleaning illustration, the customer may calculate $184, then contact the office saying only “I want the cleaning”. Ask them to include the selected rooms and extras, or provide a clearly labelled selection summary they can copy. Do not imply the estimate has been sent to staff unless you have actually built and tested a sending mechanism.
A filled-in sample handoff would read: “Estimated visit price $184; three bedrooms; two bathrooms; oven included; windows excluded; standard access assumed; request subject to scope review.” Staff can now reproduce the figure. If the customer later changes to four bedrooms, the original summary remains an estimate of the earlier selection, rather than evidence that the larger job was agreed for the same amount.
Keep confidential costs out of the specification you intend to expose in the finished page. The customer needs selling rates and scope, not staff pay, supplier discounts or internal margin targets. A browser-side calculator is a poor place to hide commercially sensitive pricing logic. If the estimate depends on private account-specific agreements, pause the public version and get help designing a controlled quoting process instead.
Finally, distinguish a reset from a return visit. After pressing a reset control, all extras should be cleared and the result should match the new default inputs. An illustrative fault leaves the oven checkbox unticked but still adds $35. Test reset after the most expensive case, then enter the minimum case again. That sequence catches hidden state, meaning old selections that continue affecting a new calculation even though the screen no longer displays them.
Set aside an owner-selected trial budget, such as two hours for the specification and manual checks, plus another hour for publication and handover. Those are suggested planning allowances, not measured build times. Stop if the formula cannot be explained clearly or if a helper cannot reproduce the expected results. More design prompts will not resolve an unsettled pricing policy.
During a small trial, keep a simple tally of estimate starts, requests received and cases staff had to correct, using whatever measurement you have deliberately installed. Do not assume a published page automatically records all of those events. An illustrative review of 20 submitted enquiries might find 16 within scope and four requiring a tailored quote; read the four before expanding the calculator's boundaries.
Give one person responsibility for rate changes and one other person responsibility for checking the totals. Write down how to take the calculator down if a fault appears: remove the link from your site, or select Unpublish in Bolt's Publish menu and confirm (a custom domain has to be disconnected first). If it starts collecting customer details, taking payments or saving quotes later, revisit the security checks for an AI-built customer tool before making that broader version public.
A useful launch record contains the formula, the approved rate table, six test inputs with expected totals, actual token readings, the public address and the person who owns updates. With that record, the next change becomes a controlled edit. Without it, even a neat no-code calculator can become an unexplained price source that nobody on the team feels able to correct.
Further reads
- Is Bolt.new Worth It for a Non-Coder? What One Project Costs — Decide whether maintaining the calculator suits you.
- How to Build a Quote Calculator With Claude Artifacts — Consider a smaller calculator experiment.
- Is Replit Worth It for a Non-Coder Building a Business Tool? — Replit for an owner who cannot code: what a simple internal tool costs, where it gets risky, and when a freelancer is cheaper.
Browse all AI-for-business tutorials
Sources: Bolt pricing page; Bolt QuickStart guide; Bolt tokens, publishing, hosting plans, and backups and version history help pages; MDN iframe reference.
