An RFQ is ready for pricing when the estimator has the inputs required for the agreed type of response. A firm quotation, an indicative range and a feasibility discussion need different evidence. State which one the team is preparing before deciding whether the request is complete.
Completeness is therefore a business rule, not a document-length test. A two-line repeat order can be sufficient if it references an approved specification. A detailed PDF can remain unpriceable if the quantity or delivery scope is unclear.
A fictional display order
Request RQ-62 asks for “counter displays like last time, needed in November”. It includes a photograph but no product reference. The previous order contained 40 units in one finish and 20 in another. The new request does not identify quantity, finish, delivery sites or whether the artwork is unchanged.
A useful intake result lists those gaps and links the previous order as context. It should not silently repeat the old quantities. The customer may mean the same design while changing the volume completely.
| Input | Current evidence | Next action |
|---|---|---|
| Product or specification | Photograph and historic order | Confirm the intended reference |
| Quantity | Not stated | Ask for units by variant |
| Finish or artwork | “Like last time” | Confirm approved version |
| Delivery scope | November only | Confirm sites and required date |
Define the minimum for each quote type
Work with estimators to identify which fields actually change their decision. Avoid adding questions simply because a form builder supports them. A requirement should have an owner who can explain what happens when it is absent.
- What is being supplied or performed?
- How much, in which units and variants?
- Where and when is it required?
- Which source specification or reference governs the request?
- What is included, excluded or supplied by another party?
- What response is the customer asking for?
For a preliminary discussion, some unknowns can remain visible. For a price the business is prepared to issue, the reviewer may require clarification or an explicit assumption. Keep those states separate so an indicative draft does not become a commitment by accident.
Use tools to assemble the evidence
Pipedrive Smart Docs supports templates populated from CRM records. Existing quote tools may already cover the document-generation step. The first improvement might be better intake fields and a readiness check, rather than a new quoting application.
Where requests arrive in mixed emails and attachments, a custom assistant could propose the brief and identify missing fields. Each proposed value should point back to its source. Staff should confirm interpretations before the request moves into pricing.
Handle contradictory detail as well as absence
Suppose RQ-62’s email asks for 80 units while an attached schedule totals 60. The quantity is not missing; it conflicts. Show both values and ask which governs. Similarly, a filename containing “approved” does not prove that its contents were authorised for this order.
Do not let an urgent deadline bypass unknowns without a recorded decision. The estimator may choose to prepare a bounded estimate, but the assumptions should remain visible in both the internal brief and the approved response.
Assign one person to decide when an unanswered question can become an explicit assumption. Otherwise sales may consider the brief complete while estimating waits for information that nobody has actually requested from the customer.
Test readiness with past requests
Choose authorised past RFQs and ask estimators what information they needed before pricing. Compare that with the proposed checklist. Count unnecessary questions as well as missed essentials; a form that demands irrelevant detail can obstruct a simple enquiry.
Clear Anvil’s synthetic intake demonstration shows a guided brief using fictional entries. Use it as a conversation about the handoff, then define the specific fields and decisions that make your own request ready for an estimator.
Sources and further reading
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.