The short version
- Every form needs the name, phone, email, job address, the service, the timeline, and a short description of the job.
- Add two or three questions for your trade, and give each one a not sure option so nobody gets stuck.
- Leave out anything you will ask on the callback anyway, and test that each request arrives in your email with every answer on it.
A quote form has one job, to get you a request you can call back on with a plan. You want to know what the job is, where it is, and when they want it done, before you dial. You do not need the square footage to the inch or the brand of the old water heater. That comes on the call or at the site visit.
Every question you add costs something. Each one is another chance for a homeowner on a phone at 9pm to give up and call the next contractor on the list. So the work is picking the few questions that matter for your trade and cutting the rest.
What the form is for
The form is the start of a conversation, not the estimate. When a request lands, you should be able to answer three questions without calling anyone.
- Is this my kind of job? A roofer who does not do flat roofs wants to know before driving out.
- Is it in my area? A Kent address is a yes for a Kent crew. A Bellingham address might be a no.
- How soon? A leak today and a remodel next spring get different callbacks.
If the form answers those three, the callback is short and the homeowner hears a contractor who read what they wrote.
The questions every trade needs
Here is the set I start from, in this order. The easy questions go first, so the homeowner is invested before the form asks for contact details.
- The service. Tap one or more from your list, like roof replacement, roof repair, or gutters. Tapping a choice beats typing on a phone.
- The timeline. As soon as possible, within a month, one to three months, or just planning.
- The job address and ZIP. This tells you whether the job is in your area and which town it is in.
- A short description. One box, with an example in it, like "Leak over the garage after the last storm, about 1,800 square feet."
- Photos, optional. A photo of the leak or the old panel saves a trip for some jobs. Make it optional, never required.
- Name. One field for the whole name.
- Phone and email. Both, because some homeowners answer one and ignore the other.
- The best way to reach them. Call, text, or email. Then use the one they picked.
Some contractors add a budget question. If you do, use ranges and a "not sure yet" option. A homeowner who picks a range like $10,000 to $25,000 for a bathroom remodel tells you something useful before the visit, and one who picks "not sure yet" is not stuck.
Questions by trade
On top of the basics, add two or three questions for your trade. Pick the ones that change what you say on the callback. Everything else waits.
| Trade | Add to the form | Leave for the callback |
|---|---|---|
| Roofing | Roof type (asphalt, metal, flat, not sure), number of stories, leaking now (yes or no) | Pitch, square count, layers of old roofing |
| Remodeling | Which room, full remodel or update, budget range | Material picks, layout changes, permits |
| HVAC | Current system (furnace, heat pump, AC, none), fuel (gas, electric, oil, not sure), working now (yes or no) | Tonnage, duct condition, equipment brands |
| Plumbing | The problem or fixture (water heater, leak, drain, sewer), water leaking now (yes or no) | Pipe material, water heater size, access |
| Electrical | Job type (panel, EV charger, lighting, rewire), panel size (100 amp, 200 amp, not sure) | Load calculation, service upgrade details |
| Landscaping | Job type (cleanup, lawn, patio, wall, irrigation), one time or ongoing | Plant choices, yard measurements, drainage |
| Moving | Move date, from ZIP and to ZIP, home size, stairs or elevator at each end | Item by item inventory, packing supplies |
| Concrete | Job type (driveway, patio, slab, walkway), rough size in feet, old concrete to tear out (yes or no) | Thickness, reinforcement, finish |
Give every trade question a "not sure" answer. A homeowner who does not know the amps on their panel should still be able to send the form. You will find out on the call.
The "leaking now" question on roofing, HVAC, and plumbing forms does extra work. A yes means the request should jump the line, and you can call back first.
What to leave out
Every one of these makes the form longer without making the callback better.
- Anything you will measure anyway. Square footage, roof pitch, room dimensions. The homeowner guesses, you measure, and the guess helps nobody.
- How did you hear about us. Homeowners guess at it, and on the sites I build, the stats dashboard already tags every quote request by source.
- Separate first and last name fields. One name field is faster on a phone.
- An exact budget in dollars. Ask for a range or skip it.
- Required photos. Some homeowners are at work when they fill out the form. Let them send photos later.
- Long dropdowns. A list of forty services is a list nobody reads on a phone. Show your six main services and an "other" box.
- Questions only a contractor could answer. "What R value do you want?" belongs on the call, where you can explain it.
Look at your current form and cross out every question you have never used on a callback. What is left is the form.
Make it easy on a phone
Picture the homeowner filling out your form with one hand, standing in the kitchen with the other hand on a leaking faucet. A few small details decide whether they finish.
Google's guidance on form design at web.dev (opens in a new tab) covers the ones that matter most.
- A phone number field should bring up the number pad, not the full keyboard.
- Fields should be set up so the browser can fill in the name, email, phone, and address for them.
- One name field works better than separate first and last name fields.
- Each field needs a real label. Gray placeholder text inside the box disappears as soon as the homeowner starts typing.
Then break a long form into short steps. The quote form I build asks the job questions first, then the address and ZIP, then the description and photos, then the contact details. Each step fits on one screen.
Where the request goes
A request is only as good as where it lands. On every site I build, each request arrives in your email with every answer on it, the moment the homeowner sends it. You see it on your phone and on your computer at the same time.
Test it before you trust it. Fill out the form from your phone with a made up job, then check your inbox and your spam folder. If it takes more than a minute, lands in spam, or goes to an address you do not check, fix that before anything else on the site. A form that goes nowhere was the second mistake in my list of contractor website mistakes, and it costs you the homeowners who were ready to hire.
Put your license number right under the form, too. A homeowner typing their address into a form on a site they found ten minutes ago wants one more reason to trust you, and the number is that reason.
Call back with the answers in hand
The form did its job when your callback sounds like you read it. Open the request before you dial and say back what they told you. The roof over the garage, the leak after the last storm, the house in Renton. A homeowner who hears their own words knows you paid attention.
Use the contact method they picked. A homeowner who chose email at 9pm may not want a call at 7am, and one who chose call wants to hear a voice. If they sent photos, say what you saw in them. If a question came back as not sure, that is your first question on the call.
After hours, the intake chat on a Site with Tools takes the same details in a conversation. It asks for the name, the phone number, the address, the job, and the timeline, and they arrive in your email the same way a form request does.
The quote form on my builds
The form on every site I build asks the questions you pick for your trade. Send me your services and the three questions you ask on every callback, and those become the form. You can fill out a sample quote form and watch the email arrive before you decide.
Each request is counted on the stats dashboard, tagged with where the homeowner came from, next to visits, phone taps, and review clicks. A Site is $1,500, with $750 to start and $750 at launch, and it has a page for each service and 20 town pages.




