Quote requests close before a proposal process can start.
A request for quotation is a different animal from a formal solicitation: days rather than weeks, line items rather than a narrative, and an award decided on price, lead time and whether you answered at all. RFQ discovery tracks them in the same feed and treats them as what they are.
- Produces
- Opportunity records, typed as quote requests
- Typical window
- Days — the clock is the feature
- Needs
- A catalogue or capability list to match against
A ten-day window found on day seven is not an opportunity.
Quote requests are the volume business of public procurement. They are smaller, they are frequent, and they are how a buyer keeps a fleet running and a laboratory stocked. They are also posted with the least ceremony: no pre-bid conference, no question period worth the name, and a closing date that arrives before a weekly review does.
Because they are small, nobody staffs them. They arrive in a shared inbox, get forwarded, and are answered by whoever has time — which means the ones that get answered are the ones from buyers who remembered to email, and the published ones go to whoever was watching that portal that week.
Treating them as small RFPs makes it worse. A response project built around volumes and evaluation criteria is a heavyweight process wrapped around a spreadsheet with four line items in it, and the process is why the deadline gets missed.
- Repeat business quietly lostAn annual supply quote missed once is a competitor’s incumbency for a year, and their relationship for the renewal.
- Answered too late to matterQuotes arriving after the window closes are not evaluated, however good the price is.
- Mis-filed as proposalsA quote request routed into a proposal workflow gets a kickoff meeting it does not need and a deadline nobody flagged.
Classified as a quote, and put on a clock.
The pipeline is the one discovery already runs. What differs is the classification, what is extracted, and how hard the deadline is pushed at the person who has to answer it.
Classify by what is being asked for
A package asking for unit prices against a drawing and a delivery term is a quote request, whatever the title says.
A record typed as a quote request, so everything downstream treats it as one.
Read the schedule of items
Line items, quantities, specifications and delivery terms are extracted from the workbook or table the buyer published.
A structured item list to price against, rather than a spreadsheet somebody retypes.
Put the window on a clock
Posting, question deadline, quote deadline and any site visit are lifted onto one timeline with the time zone resolved.
A countdown with the next milestone named, and alerts pinned to the deadlines rather than to a digest.
Match against what you supply
Items are compared with your catalogue or capability list, including the ones you would have to source.
A coverage figure — how much of the schedule you can actually quote — before anybody starts pricing.
Open a pricing response, not a proposal
The response project for a quote is the item schedule, the certifications required and the forms, and nothing else.
A response that can be finished in an afternoon, because it is not carrying a proposal’s furniture.
Eleven days from posting to close, and what is being asked for.
The ring is the share of the quote window still open. Beside it is the schedule of items as published — quantities, specifications and lead times — and under it the three other quotes in the same feed, sorted by how little time is left.
Hydraulic hose assemblies and fittings — annual supply
Eleven days from posting to quotes due, and the specification package landed on day two.
A listener that runs daily is a listener that finds this on day five.
- Posted
- Specification package released
- Questions close
- Quotes due
- Award target
| Item | Specification | Quantity | Lead time |
|---|---|---|---|
| Hydraulic hose assembly, 3/8 in. | SAE 100R2AT, crimped ends | 640 ea | ≤ 21 days |
| Hose assembly, 1/2 in., abrasion sleeve | SAE 100R2AT + sleeve | 310 ea | ≤ 21 days |
| JIC fittings, assorted | Drawing 44-118 rev. C | 2,400 ea | ≤ 30 days |
| Emergency replacement service | On-call, county garage | As ordered | ≤ 24 hours |
Why this is filed as a quote request, not a proposal
The package asks for unit prices against a drawing and a delivery term, and it evaluates on price and lead time. There is no technical volume, no page limit and no evaluation criteria section, so the record is classified as a quote request and the response project it opens is a pricing workbook rather than a proposal outline. The distinction is in the data model, not in the wording of the title — three of the four line items here were published under a heading that says “RFP”.
- Shop consumables — annual supplyTransit authority
- Precision machined brackets, 12 drawingsPublic utility
- Laboratory glassware replacementUniversity procurement
No prices appear here. Quantities, specifications and lead times are the buyer’s; the price would be yours, and inventing one would demonstrate a number rather than the feature.
Nothing above is a live query or another customer’s pipeline. Every record in it was written for this page, and no buying organization named in it is real.
What a quote request needs that a proposal does not.
Everything here exists because a quote is decided on responsiveness and price, and both are lost in the first two days.
Line-item extraction
The schedule of items is read out of the published workbook, including quantities, units and delivery terms, and kept in a table you can price against.
Deadline-first alerting
Alerts are pinned to the question deadline and the close, not to a daily digest that arrives after both.
Coverage before pricing
How much of the schedule you can supply directly, how much needs a distributor, and how much you cannot quote at all.
Specification packages attached
Drawings, revision numbers and specification references come with the record, and a revision that changes mid-window is flagged.
Repeat-buyer memory
A quote from a buyer you have quoted before shows what was asked for last time and what happened, so a renewal is not answered from scratch.
Registration and form requirements
Vendor registration, certificates of insurance and the forms a buyer requires are surfaced early, because they are what actually stops a quote going out.
Where quote volume is the business.
These are the shapes of company for which the quote feed matters more than the proposal one.
A parts and supply distributor
- Hundreds of small public buyers, each running quotes on their own schedule, most of them never emailing anybody.
- Category listeners across local and district portals, with item extraction and a coverage check before anybody prices.
- Quoting becomes a daily routine on a short list instead of a scramble whenever somebody notices a portal.
A fabrication shop
- Wins on lead time and capacity, and needs to know quickly whether a drawing package is work it can take.
- Quote records with the drawing package attached and the delivery terms on the face of the record.
- A go or no-go on a quote in the time it takes to open the drawings, rather than a day of chasing the package.
A services firm with a supply line
- Bids formal solicitations and also supplies consumables to the same buyers under separate quotes.
- One feed carrying both, with quotes typed separately so they route to the desk that answers them.
- The two kinds of work stop competing for the same process, and neither is answered by the wrong team.
Quote requests are not a separate line on the price list.
Quote discovery is part of discovery, on every plan, and it consumes the same listener and match allowances. What tends to decide the plan is volume: a distributor watching a thousand jurisdictions needs more listeners than a firm watching four states.
- Included wherever discovery is included, which is every plan.
- Listener and saved-search allowances are what scale with the plan, and quote-heavy work uses more of both.
- Document page and OCR allowances cover reading specification packages, and rise with each plan.
- Custom connectors for a credentialed supplier portal are an Agency capability.
Plan names and allowances are mirrored from the billing catalog. Amounts are on the pricing page, which reads them from Stripe rather than from a number typed into a marketing page.
What people ask about quote requests.
How do you tell an RFQ from an RFP?
By what the package asks for rather than by its title. A request for unit prices against a specification, with no technical volume, no page limit and no evaluation criteria section, is classified as a quote request even when the buyer has headed it “RFP”. The classification is on the record and can be corrected by hand.
Does it read the pricing workbook?
The schedule of items is extracted — descriptions, quantities, units, delivery terms and any specification reference — into a table you can price against. Your prices stay yours: nothing fills in an amount for you, and no price is ever suggested from another organization’s data.
What about quotes that only ever arrive by email?
Discovery covers published sources. A quote a buyer emails you directly is not published anywhere, so it is not something a listener can find — though the response side of the product will still open a project for it, price it and export the answer.
Can we be alerted only for quotes we can actually fill?
Coverage against your catalogue or capability list is calculated before an alert is sent, so the threshold can be set on that as well as on score — for example, only quotes where you can supply most of the schedule directly.
What happens if the specification is revised mid-window?
The revision is attached to the same record, the change is flagged against the items it touches, and anything already quoted against the superseded revision is marked. A revised drawing that nobody noticed is the classic way a quote is disqualified.
Watch a week of quotes in your categories.
Set a listener on the buyers you supply and see what comes back with a real clock on it — including the ones that would have closed before anybody forwarded the email.