A quote calculator for your website that turns estimates into enquiries
An online quote calculator gives a visitor a believable price range from a handful of answers, then asks whether they'd like a firm quote. Done well, a quote calculator for website visitors filters out people who can't afford you and hands you warm enquiries that already contain the job details. Here's how to design the questions and the maths, and how Anticode delivers each estimate to you.
When an instant estimate helps, and when it doesn't
Instant quote calculators work for services where price follows a few measurable inputs: square metres of flooring, rooms to clean, hours of filming, number of guests. They work badly where the price depends on a site visit or judgement you can't encode, such as structural repairs or bespoke design. If you'd refuse to name a range over the phone, a calculator shouldn't name one either. In that case, a quote request page with good questions is the honest choice.
Choosing the questions
Each question should move the price or qualify the lead. If it does neither, cut it. A good set is short and concrete:
- The size of the job in a unit the visitor knows: rooms, not square feet, if most people don't know their square footage.
- The main option that changes cost most, shown as two to four choices with a short description each.
- Extras as checkboxes, each with its own price shown, so people see why the total moves.
- Timing, if rush jobs cost more.
- Postcode or area, only if travel changes the price or you don't cover some places.
Put the contact fields after the estimate, not before. Asking for an email to reveal a number feels like a trap and many people leave; showing the number first and offering a firm quote earns more of the enquiries worth having.
Getting the maths right
Write your pricing down as a formula before you ask for the app, because you'll need to check the output against jobs you've already quoted. Most service pricing fits a pattern like base fee plus quantity times rate, plus extras, times a multiplier for urgency or difficulty, with a minimum charge.
| Rule | Value |
|---|---|
| Call-out fee | Fixed amount per visit |
| Per room | Rate times number of rooms |
| Stain treatment | Optional, flat add-on |
| Next-day service | Total times 1.25 |
| Minimum charge | Never quote below this |
Show a range rather than one figure (for example the formula's result to 15% above it) unless your prices really are fixed. Print the assumptions under the result: "Based on average-sized rooms with standard carpet. Final price confirmed after we see the job." That one sentence prevents most disputes.
What Anticode builds
Give the Architect your questions, your formula and the wording of your disclaimer, for example: "A quote calculator for a carpet cleaning business. Ask number of rooms, carpet or rug, stain treatment yes or no, next-day or standard. Use these rates. Show a range and a breakdown, then a form for name, email, phone and preferred date." Check every rate in the plan it shows before you build. The model writes the calculator as one app that runs in the visitor's browser, so the total updates instantly as they change answers, with no page reloads.
The enquiry step uses Anticode's form pipeline: when the visitor sends their details, the app posts them as a contact submission, with the answers and the estimate added to the message. You get it by email and in the dashboard, and connectors can pass it on to Slack, Google Sheets, Airtable, Notion, HubSpot or any webhook so it lands wherever you already track jobs.
Keeping the price check on the server
The calculator's maths runs in the visitor's browser, which means a determined visitor could edit the figure before sending it. For a ballpark that rarely matters; if you'll honour the number, recalculate it from the answers before you confirm. A site function attached to the built-in contact form also runs when the app sends the enquiry; the answers arrive as lines in the message, so checking them takes a signed call to your own endpoint, and whether the app shows the function's message depends on the app (ask for it and test it). The other route is a custom form on a design-engine page instead of an app: its site function runs on the server when the form is sent, as a small formula over the submitted numbers (rooms times rate plus extras; formulas work on numbers only) or as a signed HTTPS call to your own endpoint, and the total is shown on the thank-you page. Nothing updates as the visitor types, because those pages run no scripts. The site functions page explains both.
Limits worth knowing
- Rates are what you enter. The app can't fetch material prices, fuel costs or anything else live from the web; update the rates by asking for a change.
- No payment or deposit. The calculator can't take money. Link a Stripe Payment Link or similar checkout from the thank-you message if you want a deposit.
- No saved quotes for the visitor. There are no customer accounts; if they want a copy, it comes from your reply.
- Submission allowance. Free sites have a monthly number of visible submissions; see pricing for plans.
Questions people ask
Will the visitor see the same estimate I receive?
Yes, the estimate and the answers behind it are included in the enquiry, so you can recalculate it from the answers before you confirm.
Can I change my prices later?
Ask for the change in a sentence, such as "raise the per-room rate to 40", and the app updates. Recent versions stay in version history.
Can it book the job as well?
An app form can be a booking request with a service, a day and a time, which reaches you through the same pipeline. It can't take a deposit.