The RFQ process looks simple from the supplier's side. A request arrives, you quote it, you win or you don't. What that view misses is everything that happened before the request, and the two or three points where suppliers get eliminated without ever knowing a project existed.
Here's the process as the buyer actually runs it, and where the quiet losses happen.
Step one: the buyer builds a shortlist
Before any RFQ goes out, the buyer decides who to send it to.
If they have a supplier they trust and the job fits, that's the whole list, and you're either on it or this project was never available to you. The interesting case is the other one: the usual supplier is booked, out of scope, or the buyer is new to the seat. Then they build a list from scratch, usually from some combination of a search, a trade directory, a colleague's suggestion, and increasingly an AI they've asked to compare companies that do the work.
This is where most suppliers are lost. Not on price. On not being on the list.
A company whose website only speaks in its own name is invisible to a buyer who doesn't already know the name. Search your company and you rank first. Search what you actually make and you may not appear at all, which we covered in why your website isn't showing up on Google.
There's no notification for this. The project simply happens without you.
Step two: they qualify you in about a minute
Shortlist in hand, the buyer checks each candidate. They're answering a small number of questions:
- Can this company do this kind of work?
- At this size and quantity?
- To this standard, with the certification we need?
- Are they a real, stable operation?
Materials, tolerances, equipment, certifications, industries served. If those are on the page, you clear the bar in seconds. If they're in a downloadable spec sheet, a meaningful share of buyers won't bother, and you're out before you were ever in.
Certifications matter disproportionately here. For a lot of industrial work the cert is a hard filter, not a nice-to-have. A buyer sourcing an aerospace part with an AS9100 requirement isn't weighing your certification against your reputation; they're checking a box, and if they can't find it quickly they assume you don't have it. Burying it in the footer treats a credential you spent months earning like fine print.
The stable-operation question is quieter but real, particularly for a first order. Named customers, real photographs of your floor, current copyright year, a phone number that works. These read as low signals individually and add up to whether someone believes you'll still be there in eighteen months.
Step three: the request itself
Now the buyer sends the RFQ. A well-formed one includes:
- The part or scope, usually with a drawing or model
- Quantity, and whether it's one-off, recurring, or a blanket
- Material and any substitutions allowed
- Tolerances and critical dimensions
- Required certifications or standards
- Finish and secondary operations
- Target date, and whether it's firm
- Where it ships and any packaging requirements
Buyers vary enormously in how complete this is. A good supplier response often includes clarifying what's missing, which is itself a signal of competence.
The friction on your side is the form. A first-contact form asking for fourteen fields, with no file upload, or one that rejects a STEP file or caps uploads below a real assembly size, ends the process right there for a busy engineer. Accept what buyers actually send, ask for the minimum you need to quote, and let the conversation gather the rest. Our RFQ page entry covers what belongs on that page. Where there's no drawing, as with standard or used pallets, the minimum is the handful of answers that set the price; a pallet supplier's quote form shows it.
Step four: the wait, which decides more than people think
The buyer has usually sent the same request to two or three suppliers within the same hour. What happens next matters more than most suppliers realize.
The first response, even an acknowledgment that says "got it, quoting you Thursday," does three things. It confirms the request arrived, which buyers genuinely worry about. It sets an expectation you can be held to. And it becomes the reference point the other quotes get compared against.
It also signals how you'll behave once there's a purchase order. A supplier who takes four days to acknowledge an RFQ has told the buyer something about what a late-delivery conversation will feel like. That inference is unfair sometimes and buyers make it anyway.
A same-day acknowledgment costs almost nothing and is the cheapest competitive advantage available in this process.
How fast should you respond to a quote request?
Acknowledge it the same day, and send the quote by the date you gave in that acknowledgment. Those are two different deadlines. The first is a person confirming the request arrived and saying when the price will follow, which usually takes minutes. The second should come as soon as the work allows, because the buyer is weighing your date against other suppliers', and then it has to land when you said it would.
More of what makes the first deadline easy to hit sits on the website than you'd expect.
The confirmation the form sends. The moment someone submits a request your spam check accepts, they should get an email that says the request and its files arrived, names the person handling it, and says when that person will reply with a date for the quote. That settles the buyer's first worry while your team is still on the floor. It doesn't replace the person. A message from a no-reply address that says "we'll be in touch" gives the buyer nothing to hold you to.
Where the request goes. A form that emails an inbox, shared or personal, can leave a request sitting unread: a shared inbox has no owner, and a personal one has no backup when that person is out. Send each one to a named person, give a second person sight of anything still unanswered, and keep it as a record both of them can see, which is the first thing worth connecting in a CRM integration. If that inbox is mostly junk, deal with that first, because real quote requests get skimmed past when they arrive alongside twenty pitches.
What the form asks for. The acknowledgment can carry a firm date when the estimator has enough to size the job. For most custom work that's the drawing, the quantity and the target date, all of which belong in a short form anyway. When one of them is missing, the same reply can ask for it and give a date that depends on the answer, such as "quoting Thursday once you confirm the quantity."
How you'll know it's working. Your inbox and quoting system hold most of the timestamps, so log the ones they miss, such as a first reply made by phone. For each quote request, note when it was submitted, when a person first replied, and when the quote went out. Look at the slowest few each month rather than the average, since an average hides the request that sat through a long weekend. Every few months, send a test request from a phone with a real drawing attached, under a name and email address your team won't recognize, see what comes back and how long it takes, and tell whoever picks it up once it's acknowledged, so nobody prices it.
Step five: comparison, and it isn't only price
Buyers compare on price, lead time, confidence that you can hold the spec, and how easy you were to deal with in the first exchange.
Price matters most when everything else is equal, and everything else is rarely equal. A quote that arrives quickly, answers the question that was asked, flags a genuine issue with the print, and offers a sensible alternative will often beat a cheaper number from a supplier who was hard to reach.
The quotes that lose avoidably tend to share traits: they arrive late, they quote something slightly different from what was asked without saying so, they omit lead time, or they bury the number in a PDF the buyer has to hunt through to compare.
The ones that win are legible. Clear price, clear lead time, clear assumptions, clear scope, and a named person to reply to.
Step six: the part everyone forgets
If you don't win it, ask why. Not defensively, just once, briefly.
Most buyers will tell you, and the answer is frequently something you can fix: lead time rather than price, a certification you actually have but didn't show, a capability they didn't realize you had. Suppliers who ask this systematically learn more about their win rate in a quarter than most learn in years.
And if you do win it, the RFQ process just became your onboarding. How you handle the first order determines whether the next project is a competitive RFQ at all, or just a phone call to you.
What share of quotes should you expect to win?
Win rate usually means orders won divided by quotes sent. No single figure fits every company: quotes to repeat customers, where you may be the only supplier asked, usually win more often than quotes to first-time buyers, and the mix of jobs you quote moves it too. A very high rate usually means pricing low or quoting only the sure things.
Track the stages separately: requests received, counting any left unanswered as a failure at that stage; requests quoted, with the no-quote rate as its own number, since declining is often the right call; and orders won out of quotes sent. Compare website requests with other first-time sources, such as directories and trade shows, over a few quarters, not month to month. Website requests usually win less than repeat work, because those buyers are comparing several suppliers. If they also win noticeably less than your other new-customer sources, the timestamps from the response-time section in Step four can show whether slow replies are part of it.
What a good quote document contains
Winning is partly about the number and substantially about how readable the response is. Buyers are comparing two or three quotes, often in a hurry, sometimes forwarding them to someone who wasn't part of the original request. That's also why a link to your capabilities page is worth putting in the quote, so whoever it's forwarded to sees what you can do today.
A quote that compares well includes:
- The price, broken out by unit and total, with quantity breaks if they apply
- Lead time, stated in working days from a defined trigger like receipt of purchase order
- Exactly what's included: material, processes, finishing, inspection, packaging
- What's excluded, said plainly rather than buried
- Assumptions you made, particularly where the print was ambiguous
- Validity period for the pricing
- A named person with a direct phone number
Notice how much of that isn't price. Buyers reward quotes that are easy to act on, and a surprising number of suppliers lose on legibility rather than cost.
Red flags buyers notice
Small things carry weight during a first exchange, because it's the only evidence available about what working with you will be like.
Quoting something slightly different from what was asked without flagging the change. Ignoring a question in the request. A quote that arrives as a photo of a printed page. No lead time. A generic email address with no name attached. Terms that appear for the first time on the invoice.
None of those are about capability, and all of them make a buyer wonder what the delivery will be like.
Where to actually improve
If you want more RFQs and a better win rate, the opportunity is not in the quote itself. It's earlier:
- Be on the shortlist. Publish what you make in searchable page text so buyers without a referral can find you.
- Clear qualification in seconds. Specs, tolerances, equipment and certifications on the page rather than in a PDF.
- Remove form friction. Short form, real file uploads, generous size limits.
- Respond first. Same-day acknowledgment, always.
- Quote legibly. Price, lead time, assumptions, scope, and a name.
None of it requires a campaign. Most of it is a week's work on a site you already own, which is where our industrial website design work usually starts.
