StainglassCRMExplore demoKeep an RFQ moving with one owner and one clear next action.
An RFQ can stall between the customer, sales and the people preparing a quote. A small set of shared fields and a clear handoff make the work easier to follow, whether you use a CRM or a shared tracker.
1. Capture the request before handing it off
Record the company, primary contact, what is being requested, the latest requirements or revision and the customer’s deadline. Distinguish the deadline for submitting the quote from the date you expect a decision. If requirements are incomplete, make clarification the next action.
2. Give the request a named owner
One person should be accountable for keeping the RFQ current. Other people can prepare pricing, review feasibility or approve terms. Record who owns each handoff and when their input is needed. A stage such as “with engineering” is less useful than a named owner, a deliverable and a due date.
3. Connect quote revisions to the same request
Keep the RFQ and its quote revisions linked. Record which revision was sent, when it was sent, who received it and what changed. This helps the next person follow up using the version the customer actually has.
4. Set the next action when you send the quote
Choose a follow-up date that fits the customer’s buying process. The first check can confirm receipt and identify missing information. A later check can ask about the decision timeline, technical review or a specific obstacle. Use what the customer tells you to set the next date instead of repeating a generic check-in.
A useful follow-up prompt
“Did the quote revision we sent on [date] cover the scope you need? If anything is missing, we can clarify it. What is the next step in your review, and when would a follow-up be useful?”
Replace the placeholders with the actual request and timeline.
A compact RFQ follow-up record
| Field | What it answers |
|---|---|
| Company and contact | Who is requesting the work, and who can clarify it? |
| Owner | Who keeps this request moving? |
| Requirements and revision | What scope are we quoting now? |
| Quote due date | When must the customer receive the quote? |
| Latest quote sent | Which version does the customer have? |
| Next action and due date | What happens next, who does it, and when? |
| Outcome and reason | What was decided, and what can we learn? |
5. Close the loop with an outcome
When the customer decides, record whether the work was won, lost, deferred or withdrawn, along with the reason they shared. If the decision is deferred, set a future review date. Keeping outcomes beside the request makes later reporting and future conversations more useful.
Explore a connected RFQ workflow
StainglassCRM connects RFQs, quote revisions and follow-ups to company and contact context. See the current platform capabilities or explore the example rep workspace.
Explore as a rep Discuss your RFQ process