How to turn your website into a quote request tool for a service business
Short answer: A quote request tool is more than a form: it is a form that asks what changes your price, sends the answers to one named person, replies to the customer with a promise, and tracks the quote until it is won or lost. Pick one of three types by how much your prices vary: a plain request form, a price-range form, or an instant price calculator. Most service businesses should start with the plain request form and add the rest only when the numbers justify it.
You want visitors to ask for a quote from your website without ten phone calls and emails going back and forth first.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Start with the plainest version that works: a short form, a clear promise about when you will reply, and an alert that reaches one person. Add a price range or an instant price only if your jobs are simple enough to price from a few answers. This page is about the whole path from "visitor wants a price" to "quote sent and tracked", not only the form. For form-building steps, see how to make a quote request form that sends details to your team. For calculator tools, see instant quote software for contractors. Here I cover how to choose between them, what to ask, how to route the lead, and when custom software is worth the money.
The three types of quote tool
| Type | What the visitor gets | Pick it when | Main risk |
|---|---|---|---|
| Request a quote | A form, then a human reply with a price | Jobs vary a lot, or you must see the site or photos | Slow replies lose the lead |
| Price range | A "from X to Y" estimate after a few answers, then a human confirms | You can bracket the price but not fix it | The range anchors the customer, so a wide range or a low bottom number causes arguments |
| Instant price | One firm price on screen, often with a booking button | Jobs are standard, such as a gutter clean or a set cleaning package | Wrong rules mean you honour a price that loses money |
A simple rule: if two jobs in the same category can differ in price by more than about 30 percent for reasons the customer cannot describe in a form (access, hidden damage, condition), use request a quote. If you can write the price rules on one page and they rarely need exceptions, an instant price is realistic. In between, use a range and say plainly that the final price is confirmed after review.
Ask what changes the price, and nothing else
There is no official field count. The Nielsen Norman Group (a usability research firm) advises cutting any field you can derive, collect later or leave out. My working range for a service quote form is four to seven fields, and the rule is simple: every question must change the price or change who calls back, otherwise delete it. Dropdowns beat free text because answers can be sorted and priced. Ask for photos only when they help you price, and make the upload optional.
| Trade | Questions that change the price | Optional |
|---|---|---|
| Cleaning | Home size (bedrooms, bathrooms), type of clean, how often, postcode | Pets, parking |
| Plumbing or HVAC (heating and cooling) | Problem type, emergency or not, age of equipment, postcode | Photo of the unit or label |
| Roofing | Repair or replace, roof type, approximate size, number of storeys | Photos, insurance claim yes or no |
| Landscaping | Service type, area size, one-off or regular, access | Photos of the yard |
| Agency or consultant | Type of project, deadline, budget band, how they found you | Link to current site |
Always collect: name, email, and a phone number or a preferred contact method. Add a "best time to reach you" dropdown if you phone back. Address is needed only when travel cost or the service area affects the price, so a postcode is usually enough at this stage. If you need photos, the photo upload guide covers file size and storage.
Send the lead to a person, not an inbox
The tool lives or dies on what happens in the first hour. Set these up in order:
- Name the owner. One person is responsible for every web quote request on each day. If they are away, a named backup takes over.
- Alert them where they look. A text or chat message beats email for a field team. Include the answers in the alert so they can quote from their phone.
- Auto-reply with a promise. "Thanks, we will send your quote by 5pm tomorrow." Then keep it. A promise you cannot keep is worse than none.
- Write it to your system. The request should land as a lead or request in your CRM (customer relationship management tool, the place you keep contacts and jobs) or job software, not only in an email. See building a lead capture flow that writes to your CRM.
- Chase automatically. If the quote is not accepted in three days, a reminder goes out. The steps are in the three-day follow-up guide.
On speed, the best-known source is a Harvard Business Review article, "The Short Life of Online Sales Leads" (March 2011), which concludes that most companies do not respond nearly fast enough to online leads. The full text is paywalled and secondary sources quote different figures, so no single number is repeated here as the finding. A more recent vendor study (Workato, March 2026, 114 business-to-business companies) found an average first email reply of about 12 hours. Measure your own first-reply time for a month and set a target you can hold.
Steps to build it
- Decide the type using the table and rule above.
- Write the questions from the trade table. Test them by pricing five past jobs using only the answers. If you cannot, add the missing question.
- Choose the tool. Options run from your site builder's built-in form, to a form builder, to the quote or booking feature inside field service software. As of November 2026 Tally, a form builder, lists unlimited forms on its Free plan within fair usage. Typeform, another form builder, lists 10 responses a month on its Free plan, and its paid plans carry response caps, so check its pricing page for the current Basic price. Jobber, field service software, lists online booking in its Core plan, which it shows from $29 a month for one user on annual billing and $49 a month on monthly billing, and it describes shareable request forms as a feature, so confirm with Jobber which plan includes them. Check each vendor's page, because plans and limits change.
- Add the spam check (a hidden honeypot field plus a bot check checked on a server). See how to stop spam on your contact form.
- Build the thank-you page. Say what happens next and when, and give a phone number for emergencies.
- Connect the alert and the CRM.
- Test on a phone. Most visitors will use one. Fill it in with thumbs, and time it.
- Go live and read the first 20 submissions yourself. They will show you which questions confuse people.
A worked example with made-up numbers
These figures are invented to show the arithmetic. A gutter cleaning company gets 40 web quote requests a month. At the moment each needs a phone call to learn the house size, and 15 of the 40 never get a callback within two days. Of the 25 who do, 10 accept a quote. The owner changes the form to ask storeys, house type and length of gutter by dropdown, and adds a price range on the thank-you page with "confirmed after a photo check". He also adds a text alert and a two-day follow-up. The next month: 40 requests, 36 get a reply within a day, 16 accept. The difference is 6 more jobs. Those are fictional numbers, and the point is the method: track requests, replies within your target, quotes sent and quotes won, and compare month to month.
Write the first reply before you need it
Speed is not only about alerts. It is also about having the words ready. Draft three short replies once, and save them where the quote owner can paste them:
- Auto-reply (sent at once): thanks, what you received, when they will hear back, and a phone number for urgent jobs.
- Quote ready: the price or range, what it includes, what it does not include, how long it is valid, and one clear next step such as a booking link or "reply YES".
- Need more information: ask for at most two things, with an easy way to answer, for example "reply with a photo of the unit label".
Keep each message short enough to read on a phone without scrolling much. Put the price near the top, not at the end.
If you show a price range, write it carefully
A range anchors the customer, so check these points before you publish it:
- The bottom number must be a price you would actually do the job for. People remember the lowest number.
- Say what moves the price up in plain words, for example "extra storeys, difficult access, or damage found on the day".
- Say who confirms the final price and how, for example "in writing before work starts".
- Test the range on past jobs. If more than one job in five falls outside it, the range is wrong.
Common mistakes
- Asking for everything up front. A long form loses people who would have answered the same questions on a call.
- No owner. A shared inbox is read by everyone and answered by no one.
- A promise nobody checks. If the auto-reply says "by 5pm tomorrow", someone must see a list of requests that are about to miss it.
- Forms that fail quietly. Test the whole path monthly, including the alert. The forms-not-sending checklist gives the order to check.
- Treating a quote as the end. A sent quote with no follow-up is a lead you paid for and then dropped.
What to track
- Requests received, by source page.
- Median time to first reply.
- Quotes sent as a share of requests.
- Quotes won as a share of quotes sent.
- Average job value of quotes won.
Five numbers in a spreadsheet are enough to start. The two that matter most are time to first reply and quotes won, because they show whether your tool fixed a real problem.
Privacy and wording
A quote form collects personal data, and photos of a home can show more than you need. Tell people what you do with the data in one plain sentence near the button, collect only what you need, and delete old requests on a schedule. Rules differ by country and state, so check local law. If a price shown on your site counts as an offer where you operate, check what you promise on the page, and add wording such as "estimate only, final price confirmed in writing". This is information, not legal advice.
When custom is worth it
A ready-made tool is the right first answer, and often the last one. Consider a custom build when:
- your pricing has many rules (by size, material, distance, season) that a form builder cannot express;
- every quote must land in your job software with no retyping, and the ready-made connection does not cover it;
- you want customers to see, accept and pay for a quote in one place (see how to build a quote calculator);
- staff spend more than a few hours a week fixing or retyping quotes.
A rough test: take the hours spent each week on retyping and chasing, multiply by your hourly cost, and compare a year of that with the quote for the build. If the build repays itself inside a year or so and the pricing rules are stable, it is worth a serious look.
Who should skip this
If most of your work is repeat customers or referrals, a phone number and a booking link may beat a quote form. If every job needs a site visit before you can price it, use the form only to book the visit.
How I'd approach this
Start with the plain request form and fix the reply speed before anything else, because a fast reply on a plain form beats a clever calculator that nobody follows up. Week one: write the five to seven questions and test them on five old jobs; build the form and the alert; add the auto-reply with a promise you can keep; and start the five-number tracking sheet. Review after 30 days. If the numbers show you often quote the same standard job, then add a price range. Blur Studio builds the custom version when it is warranted, with quote rules, CRM and calendar connections and ongoing care, described on the business page.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
What should an online quote request form ask?
Only what changes the price or who calls back: the service, the size or scope, the timing, the location (a postcode is often enough) and contact details. Use dropdowns where you can and make photos optional. See making a quote request form.
Should I show prices on my website?
If your jobs are standard, a price or a range lifts trust and filters out poor fits. If jobs vary a lot, a range with "confirmed after review" is safer. Check what the wording commits you to where you operate.
How many fields should a quote form have?
I use four to seven as a working range, and usability research from the Nielsen Norman Group advises removing any field you do not need. Start short and add a question only if you keep having to ask it by phone.
What is the difference between a quote request and an instant quote?
A quote request sends your answers to a person who replies with a price. An instant quote shows a price straight away from rules you set. See instant quote software for tools and costs.
How fast should I reply to a quote request?
As fast as you can reliably hold. Research suggests most firms reply too slowly, but published figures vary, so measure your own first-reply time and set a target. See the speed-to-lead system.
Can the quote request go straight into my CRM or job software?
Often yes, through the tool's own integration, an automation tool, or the software's API. Check which fields the connection fills before you buy. See the lead capture flow guide.
When is a custom quote tool worth building?
When your pricing rules are complex but stable, staff retype quotes every week, or you want customers to accept and pay online. Blur Studio builds these; see the business page.
More in this topic: Websites: custom builds, portals, lead capture and site care (9 guides) →