RFQ or lead: what does an industrial buyer actually send?
How to tell an early lead from a specific RFQ, ask only for details that change the next action, and leave unknown or sensitive information for the right follow-up.
Updated
A buyer can be worth answering before they are ready to send an RFQ.
A business may call every new contact a lead. The buyer is usually trying to do something more specific: ask for a sample, confirm a standard, check supply for a destination, share a drawing or request a quotation.
The first enquiry should help the receiving team choose what happens next without making the buyer invent or overshare details.
Lead is an internal label
Calling every contact a lead may help a pipeline, but it does not explain what the buyer needs. A sample request, technical question and defined quotation request belong to different moments in the buying process.
Start by naming the buyer's job. Then ask for enough context to route and answer it, instead of forcing every visitor through the same form.
RFQ is specific, but not universal
An RFQ makes sense when the buyer can define the requirement and ask for commercial terms. Earlier enquiries may still deserve a useful response.
- 01
Early enquiry
Can you help with this?
The buyer may need application advice, a certificate, a sample or confirmation that the supplier is relevant.
- 02
Requirement to clarify
Can we discuss this job?
The need is recognizable, but the buyer or supplier still has important questions before commercial terms make sense.
- 03
Specific RFQ
What would it cost, and when can you deliver?
The product, service or scope is defined well enough for the supplier to prepare or clarify a quotation.
Put fit information the buyer can safely assess on the public page. Use the first enquiry for the context needed to respond. Move sensitive drawings, maintenance histories and exact site details to a suitable private follow-up.
Ask only what changes the next action
A short form can leave sales to rediscover the requirement. A long form can demand certainty the buyer does not yet have. A question earns its place when the answer changes what the receiving team does next.
Hypothetical teaching example
“Planned maintenance for two packaging conveyors in Nashik. The model and dates are not fixed. Maintenance history is available once we agree how to share it privately.”
Add one named contact and their chosen reply method. This is enough to recognize and route the request; it does not prove fit or make the enquiry quote-ready.
What this first enquiry should ask
- How can we reply?
Why it helpsLets the right person continue the conversation
Make room forOne supported reply method; no automatic marketing opt-in
- What equipment or service do you need help with?
Why it helpsRoutes the request without forcing a catalogue match
Make room forAn equipment type or plain-language description
- What needs attention?
Why it helpsExplains the reason for the enquiry
Make room forA short description without sensitive detail
- Where is the work needed?
Why it helpsSupports an initial coverage conversation
Make room forCity or region first; exact site details can follow privately
- When are you planning the work?
Why it helpsSurfaces a genuine timing need
Make room forIndicative timing or ‘dates not fixed’
- Do you know the model or reference?
Why it helpsRemoves ambiguity when the buyer has it
Make room for‘Not yet known’ without blocking the enquiry
- Do you have documents to share?
Why it helpsShows that useful detail exists
Make room forA request for a suitable private sharing route; no pretend upload
The right questions vary by buying situation. A known component, custom part and industrial service need different details. The separate examples in the Thomas RFQ tip sheets show why one industrial form cannot fit every request.
The service team still decides what happens next
An exact shutdown date may matter later, but requiring one too early makes the buyer invent certainty. Detailed documents may matter to technical review, but a general form should not pressure the buyer into an unsuitable upload. Annual turnover adds nothing when it does not change the first response.
The GOV.UK form guidance recommends knowing why each question is needed, who needs to answer it and how the information will be used. Before release, ask the colleague receiving the enquiry: can you choose a sensible next step? If not, another required field may not fix the real problem.
Ask a clarifying question
Arrange technical review
Prepare a quote later
Decline the request
A detailed enquiry can still be outside capability. An early enquiry can still be worth clarifying. The form starts the conversation; it does not award a qualified label.
Make it easy to answer and safe to continue
Use clear labels, explain unfamiliar questions, show what is required and let buyers say “not yet known” when that is honest. Confirm what happened after submission without promising a response time or qualification decision the business has not agreed. The W3C forms tutorial covers understandable labels, instructions, validation and completion feedback.
Keep contact details, requirements, free text and document names out of general analytics. Google Analytics warns that URLs, page titles and user-entered fields can expose personally identifiable information. See the provider's privacy guidance. If a suitable private sharing route does not exist, let the buyer request one instead of displaying an upload control that cannot support the promise.
Search to Enquiry
Where Plact fits
Plact studies the buying situation, identifies the smallest useful first request and improves the connected page and enquiry path. Your team confirms the service facts, who receives the enquiry and how private documents can be shared. Sales and technical teams still decide whether to clarify, review, quote or decline.
Improve one real enquiry path.
Share your website and the product, service or capability you want buyers to enquire about. Plact will identify where the path breaks and prepare the smallest useful improvement.
Primary sources
First-party guidance checked 4 September 2026. The planned-maintenance example and question choices are Plact editorial guidance, not a customer result or universal field set.
- RFQ Tip Sheets
Thomas
- Structuring forms
GOV.UK Service Manual
- Forms Tutorial
W3C Web Accessibility Initiative
- Avoid sending personally identifiable information
Google Analytics Help