Prompt Kits

Build an Instant Quote Calculator

Most people who want your service want a number before they want a conversation. "Call for pricing" asks them to spend social effort before they know whether you are in their budget at all, and a large share of them simply go back to the search results and click the next name. A quote calculator answers the question on the page — a few questions about the job, then a price range built from rates you set — and hands you the enquiry with the estimate already attached. This kit builds that in five sequenced prompts, and it treats one rule as non-negotiable throughout: what the calculator shows is an estimate that leads to a real quote, never a price you are bound to.

Project type: Instant quote calculator Difficulty: Beginner Time: 1 day Works with: Base44 / Lovable / v0

What you'll have at the end

  • A short set of questions that asks only the things that actually change your price
  • A price range on screen within seconds, calculated from rates you control — not invented by the AI
  • A disclaimer built into the result rather than buried in a footer, so nobody arrives believing they were quoted
  • A request form that captures the person with their estimate attached, so you open the enquiry already knowing what they configured
  • An owner screen where you change your rates yourself, without touching the build or asking anyone
  • A view of what people are pricing — including the ones who got a number and left, which is the most useful thing in here

Before you start

  • Your actual pricing, written down. Base rates, what each variable adds, and any minimum charge. This is the real work of the kit; the build is the easy half. If you do not have it written down, you have been pricing by feel, and the calculator will expose that before a customer does.
  • The three to five things that genuinely change the price. Not everything you ask on the phone — only the factors with real effect. Every extra question costs you people who do not finish.
  • How wide your range honestly is. A range of "$200–$2,000" tells nobody anything and reads as evasion; a range that is too tight becomes a promise you cannot keep. Decide the spread you can stand behind for a typical job.
  • Your minimum job. The number below which the work is not worth doing. The calculator should say so kindly rather than quote it.
  • What you must see before you can give a real quote. A site visit, a survey, a consultation, photos — name it, because it is what the disclaimer will point to.
  • An email address you check quickly. An estimate request is a warm lead with a short half-life.

Which platform suits this

Base44 is the smoothest fit: the calculation, the stored estimates, the notification and the owner screen for rates all stay inside one managed app, which is exactly the shape of this project. Lovable handles the same workflow well through Lovable Cloud or an optional Supabase backend, and gives you code ownership if a developer takes over later. v0 will build the calculator and the lead capture with server actions or API routes and deploy to Vercel, but you choose and secure the data store and the email provider yourself and verify that delivery and permissions actually work. If your pricing is simple enough that the whole thing is one screen and one form, all three are comfortable; the difference shows up at step 4, when you want to change rates without asking anyone.

Start with the first prompt on a free plan. Extra usage and some connected services may cost more as you build out the project.

Build it on

How we make money

The steps

1

Ask only the questions that change the price

When to use this

Start here, either in a brand-new project or on an existing site you already built.

A short, finishable set of inputs — no result yet.

The prompt

Add an instant estimate page to this site for [YOUR BUSINESS AND WHAT YOU PRICE, e.g. a residential cleaning company pricing regular cleans].

The page asks only the things that genuinely change my price: [YOUR 3-5 PRICING FACTORS, e.g. home size, service type, frequency, and optional extras]. Use dropdowns, number steppers and simple choices — as little typing as possible.

Keep it to one screen on a phone where you can, and if it must be longer, show progress so people can see how close they are to the end. Every question must earn its place: if the answer does not change the price, it does not belong here.

Write a plain one-line explanation above the questions saying what the person is about to get: an estimate in a few seconds, and what happens after. Do not promise a final price.

Do not calculate or display any price yet, and do not invent any rates — the pricing comes from me in the next step.

It must work well on a phone with one thumb, because that is where most people will use it.

Check it worked

  • Every question on the page is one that actually changes what you charge
  • Answering the whole thing takes well under a minute on a phone
  • Nothing asks for a name, phone or email yet
  • No price is shown, and no rate has been invented anywhere in the build
  • The explanation above the questions sets an honest expectation before anyone starts

You'll know it worked when:

A short questionnaire you could hand to a stranger, that they would finish without asking you what a question means.

Watch out for

The instinct is to ask everything you would ask on the phone. Resist it. Each additional question loses people, and most of what you ask on a call is for scheduling and reassurance, not for pricing — that conversation still happens, just after you have their details instead of before. If you cannot get below six questions, your pricing may genuinely be too situational for a calculator, and an honest "from" price with a short enquiry form will serve you better.

2

Show a range, never a single number

When to use this

Once the questions are right and finishable.

A believable price range calculated from your own rates, with the disclaimer built into the result.

The prompt

Now calculate and show a result on the estimate page, using exactly the pricing I give you here and inventing nothing.

My pricing: [YOUR BASE RATES, WHAT EACH OPTION ADDS OR MULTIPLIES, AND YOUR MINIMUM CHARGE]. Apply them exactly as written. If anything in my pricing is ambiguous, ask me rather than guessing.

Show the result as a range, not a single figure — [YOUR RANGE, e.g. plus or minus 15%, or a low and high band] — and show it as soon as the last question is answered, without a page reload.

Directly beside the number, not in a footer, show this in plain language: this is an estimate based on what was entered, and the final price is confirmed after [WHAT YOU MUST DO FIRST, e.g. a site visit / a short call / a survey]. Make it impossible to see the price without seeing that sentence.

If the answers come in below my minimum of [YOUR MINIMUM], do not show a price. Say kindly that jobs this size are usually better served by [YOUR HONEST ALTERNATIVE, e.g. our call-out rate, or another kind of provider], and offer to talk anyway.

[IF WHAT I ESTIMATE IS A PROFESSIONAL OUTCOME RATHER THAN A JOB PRICE — a fee band, a refund, a valuation, an eligibility or readiness result: call the result an indication only, never advice, a decision or an offer; state that the real answer follows a consultation with me; and do not present any figure with false precision.]

Show the person a short summary of what they selected alongside the result, so the number is clearly tied to their own answers.

Check it worked

  • The range appears immediately when the last question is answered
  • Every figure traces back to a rate you gave — nothing was invented
  • The disclaimer sits beside the number, and cannot be missed by someone who only looks at the price
  • The selections are shown next to the result, so the number is explainable
  • A below-minimum job is handled kindly instead of quoted
  • If yours is a professional estimate, nothing on screen reads as advice, a decision or an offer

You'll know it worked when:

You ran five real past jobs through it and the range covered what you actually charged for each one.

Watch out for

Check the maths yourself before anyone else sees it — run your real jobs through and compare against what you actually billed. An AI will happily produce a formula that is plausible and wrong, and a calculator that underprices is worse than no calculator: you will either eat the difference or start every job by correcting the number your own website gave. This is your pricing; you are the one who has to stand behind it.

3

Turn the estimate into a lead you can answer

When to use this

Once the numbers are right and you have tested them against real jobs.

The person's details captured <strong>with their estimate attached</strong>, stored and emailed to you. This is the step the kit exists for.

The prompt

Add a request step to the estimate page, after the result is shown.

Once someone has their range, offer a clear next action — [YOUR WORDING, e.g. "Get an exact price"] — that collects only [NAME, ONE CONTACT METHOD, AND WHAT YOU NEED TO ARRANGE THE NEXT STEP, e.g. the address area and a preferred day]. Nothing more.

When they submit: store the request together with every answer they gave and the exact estimate they were shown, so I open the enquiry already knowing what they configured. Email me the whole thing immediately, and show the person a confirmation on screen.

Send them a short automatic reply confirming you received it, repeating their estimate and its disclaimer, and saying when I will come back to them: [YOUR RESPONSE PROMISE].

Storing the request and emailing me must both happen. A form that only sends an email will eventually lose a customer to a spam folder with no record they ever existed.

Use a proper email delivery service so these actually arrive, and tell me exactly what to set up for it. Protect the form from automated spam with a hidden field and a submission limit, not with a puzzle a real person has to solve.

Let people get their estimate without submitting anything — the number is not the bait for the form. Anyone who wants to see a price and leave should be able to.

Check it worked

  • A test request arrives in your email within a minute, carrying the answers and the estimate
  • The same request is stored, so it survives a missed or filtered email
  • The sender receives an automatic reply that repeats their estimate and its disclaimer
  • Someone can see their range and close the tab without giving you anything
  • The form asks for nothing you do not need to take the next step

You'll know it worked when:

A test estimate that arrived by email, appeared in your stored requests with its answers attached, and triggered an automatic reply — all three, tested from a phone on mobile data.

Watch out for

Do not hide the price behind the form. Gating the number converts a few more addresses and loses the people who would have trusted you precisely because you answered the question — and those are the ones who arrive ready to buy. The estimate is what earns the enquiry; taking it hostage undoes the reason you built this.

4

Put your rates under your own control

When to use this

Before you launch, and certainly before your first price change.

You change your prices yourself, in a minute, without touching the build.

The prompt

Give me a private owner screen for the pricing behind the estimate calculator.

Show every rate, every option's effect on the price, my minimum charge and my range width as editable fields. Changing one and saving it must change what the public calculator shows, immediately, with no rebuild.

Before a change is saved, show me what it does to a typical job so I can see the effect of the edit rather than discovering it from a customer.

Only I can reach this screen. Make sure it is properly protected, not just hidden behind an unlinked address.

Keep a dated record of past rate changes, so an estimate someone was shown last month can still be explained.

Keep the public calculator, the request form and all the notifications working exactly as they are.

Check it worked

  • You can change a rate and see the public calculator reflect it straight away
  • The preview shows what the change does before you commit it
  • The screen is genuinely protected — signed out, the address goes nowhere
  • Old estimates remain explainable after a price change
  • Nothing on the public side broke

You'll know it worked when:

You raised one rate, checked the preview, saved it, and confirmed the public calculator changed — without a single message to a builder.

Watch out for

This is the step people skip, and it is the one that decides whether the calculator survives contact with real life. Prices change, and a calculator you cannot edit yourself becomes a calculator quietly showing last year's rates — which is worse than no calculator at all, because now your website is undercutting you. Test the protection by opening the owner address in a private browser window while signed out.

5

Read what your estimates are telling you

When to use this

Once real estimates are running through it.

See what people price, what they ask for, and where they stop.

The prompt

Add a private results view for my estimate calculator.

List every submitted request newest first, with the person's details, their answers, the estimate they were shown, when it came in, and a status I can set: new, quoted, won, lost. Let me add a private note to each one.

Also count the estimates where someone saw a price and did not submit a request. Show me how many, and what they had selected — anonymously, with no attempt to identify anyone. This is the most useful number on the screen.

Show me a simple monthly summary: estimates run, requests submitted, which options are chosen most often, and the typical range people land in.

Flag any request I have not answered after [YOUR THRESHOLD, e.g. 24 hours].

Let me export my requests so I always have my own copy.

Keep the public calculator, the form and all notifications working exactly as they are.

Check it worked

  • Every request appears newest first with its answers, its estimate and your notes
  • You can see how many people got a price and left, and what they had selected
  • The monthly summary shows real counts you recognise
  • Unanswered requests are flagged before they go cold
  • You can export your own leads

You'll know it worked when:

You looked at a month of estimates and learned one thing you did not know — the option people pick most, or the configuration that makes them leave.

Watch out for

The people who saw a price and left are the point of this screen, not a failure to fix. If most of them stop at the same configuration, your price for that job is out of step with what your market expects — and you would rather learn that from your own data than from a slow month. Do not try to identify those visitors; count them and read the pattern.

Going live

  • Run at least five real past jobs through the live calculator and confirm each fell inside the range you actually charged
  • Confirm the disclaimer is visible beside the price on a phone, without scrolling
  • Send one real test request from a phone on mobile data and confirm all three: your email, the stored record, the automatic reply
  • Check the estimate email does not land in spam on an ordinary email account
  • Open the owner rates screen in a private window while signed out and confirm it is properly closed
  • Test a below-minimum job and confirm it is handled kindly rather than quoted
  • If your estimate is a professional one, have the wording checked against what you are permitted to say in your field
  • Add a privacy note covering what you do with estimate details (see the legal pages prompt)
  • Connect your custom domain and check the padlock appears

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

  1. Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
  2. Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
  3. Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
  4. One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
  5. Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
  6. Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Last reviewed: 2026-09-14

FAQ

We use cookies to analyze traffic and track affiliate clicks. By continuing, you agree to our Privacy Policy.