Picture the person who is about to send you work. A facilities engineer, 4:40 on a Thursday, standing in a parking lot with a phone. They need three prices by Monday. They have a drawing in their email, a rough scope in their head and about five minutes before they drive home.
Your website is open in one tab. Two competitors are open in the others. Whichever firm makes it easiest to hand over the request gets the first look at the job.
Nobody at your firm will ever see this moment. If the request makes it through, it arrives as an email. If it doesn't, nothing arrives at all. There is no bounce notice for a buyer who gave up on field nine. That is why so many firms underestimate what their website loses: the losses are invisible by design.
So let's follow one request, step by step, and look at where it tends to die.
The request path, in seven steps
Every quote request travels the same path, whether you manage strata buildings or haul out workboats:
- Find the way to ask.
- Fill in the fields.
- Attach the drawing, photo or spec.
- Send it, and get past whatever checks the form runs.
- Confirm that it arrived.
- Route it to someone who can act.
- Reply with something useful.
The first five happen on your website. The last two happen inside your firm. The buyer experiences all seven as one question: do these people want my work?
Step 1: Can they find the door from a phone?
On a desktop, the "Request a quote" button sits in the top corner where everyone looks. On a phone, it often disappears into a menu, drops to the footer, or turns into a "Contact" page with a map, three addresses and a general form at the bottom.
Fix: keep one visible request button in the header on every screen size, and label it with the words your buyers use. "Request a quote", "Request a proposal" or "Book a haul-out" beats "Get in touch". Make your phone number one tap to call, not a picture of a number.
Step 2: The 14-question interrogation
Most quote forms grow one field at a time. The estimator wanted the project number. Accounting wanted the billing address. Someone added "How did you hear about us?" years ago. Each field made sense to someone inside the firm. Together they turn a request into an application.
The buyer's test is simpler: can I answer this right now, standing here? Every field they can't answer on the spot is a reason to close the tab and try the next firm.
Sort your current fields into three groups:
| Keep on the form | Ask on the first call | Drop |
|---|---|---|
| Name, company, email or phone | Billing address and PO details | "How did you hear about us?" as a required field |
| What they need, in their own words | Budget | Fax number |
| Site or location | Exact quantities and specs | Separate first and last name fields |
| Rough timing | Who approves, and how | Company size and industry dropdowns |
| Attachments, optional | Site access and safety requirements | Anything only your accounting team uses |
Then add, at most, one or two fields specific to your work. A strata manager might ask for the number of units. An engineering firm, the project type. An oil and gas service company, the part number or spec, if they have it. A specialty contractor, the bid date. A shipyard, the vessel length and when it needs to come out of the water. Keep them optional unless you truly cannot reply without them.
Then check the small things that quietly block a send: phone fields that reject an extension, required fields that aren't marked, and error messages that wipe everything the buyer typed.
Step 3: The upload that fails on a phone
This is where some of the most valuable requests die, because the buyers with drawings in hand are usually the ones closest to a decision.
Phone uploads fail for ordinary reasons. iPhone photos are often saved as HEIC files, which many forms reject. Four phone photos can add up to more than a form's size limit. Some forms take one file when the buyer has four. And many say none of this until after the buyer has picked a file.
Fix: accept PDF, JPG, PNG and HEIC, plus whatever your trade actually sends, such as DWG files or spreadsheets. Allow several files. State the size limit next to the button, before they choose. And offer a way out: "No file handy? Send the request and reply to our confirmation email with the drawings."
Step 4: The send button that argues back
Spam protection is necessary. A puzzle that asks a site superintendent to find every traffic light on a phone screen is not. Hidden honeypot fields and server-side filtering catch a great deal of automated spam without asking the buyer to prove anything.
Then test the send, from a phone, on mobile data, at least once a month. Forms break silently when a plugin updates, a domain moves or an email password changes. The website still looks fine while it happens.
Step 5: The confirmation nobody designed
After clicking send, many buyers see "Thanks, we'll be in touch" and nothing else. No email, no copy of what they sent, no idea who has it or when they'll hear back. So they send the same request to two more firms, just in case.
A good confirmation does four things, on screen and by email:
- Gives a reference number, such as RFQ-1024-017, that both sides can quote.
- Repeats what they sent, with attachments listed, so they can forward it to their manager.
- Says who will reply and by when, in hours, not "shortly".
- Gives a direct number for anything urgent.
The reference number looks like a small thing. It tells a procurement team they are dealing with a firm that tracks requests. And it gives your own staff a way to find the thread three weeks later, when the purchase order arrives.
Step 6: One inbox, one person, one holiday
In many firms, every form goes to info@ or to one person's inbox. That works until that person is on site, on holiday or off sick. The request sits, and nobody else knows it exists.
Form notifications also have a habit of landing in spam, particularly when they are sent "from" your own domain by a service your email records don't recognize. Ask whoever manages your email to confirm that your SPF and DKIM records cover the service that sends your form emails.
Fix: send every request to two named people, or to a shared mailbox with a clear owner each day. Set the reply-to address to the buyer, so answering takes one click. If you have more than one line of work, route by type: service calls to dispatch, larger projects to estimating.
Step 7: The reply that actually counts
An auto-reply is not a reply. The buyer is waiting for a person who gives a price, books a site visit or asks one sensible question. In work that is won by quote, the first credible answer often sets the frame for every price that follows.
Here is the arithmetic, with illustrative numbers. Say 30 people start a quote request on your site in a month. If 1 in 3 give up at the fields or the upload, 10 requests never arrive. If 4 of the 20 that do arrive sit for two days and go cold, you lose those too. You would see 20 requests, answer 16 of them in time, and reasonably conclude the website "brings in about 20 a month". The 10 that never arrived don't appear in any report.
The 20-minute check you can run today
Take your phone, switch off Wi-Fi and send a request to your own firm the way a buyer would. Then answer these:
- Did you find the request button within five seconds of the home page loading?
- How many fields are there, and how many could a buyer answer standing in a parking lot?
- Could you attach a photo straight from your camera roll, and a PDF?
- Did anything ask you to prove you're human?
- Did a confirmation email arrive, with a reference number and a reply time?
- Who received the request inside the firm, and how long until a person replied?
- Did it land in anyone's spam folder?
Write down the times. If every answer is good, you now have a benchmark to hold the team to.
If you'd rather not test yourself
Testing your own firm is awkward. Your staff know your email address, and people behave differently when the owner is watching. The free Speed-to-Quote Test does it for you, with your permission: one realistic request through your website, timed to the minute, and a one-page report with three fixes in order of impact.
If the report points at the website, that is what LaunchBird Websites builds: request flows designed around your work, from $4,500, fixed price and in writing, with a monthly Inbound Ledger of every request and how fast it was answered.
Either way, send yourself a request this week. It is the cheapest test you will ever run on your website.