Decided RFQ win-rate calculator
Separate resolved outcomes from open quotes in one quoted-request cohort.
Use the interactive tool without signing up. It runs in your browser: enter your numbers, save a comparison, download results or print a working copy. Your numbers are not sent to BlueFinch.
Illustrative example inputs
These starting values show how the math works. They are not industry averages, customer results or a quote.
| Input | Example value |
|---|---|
Quoted RFQs in the cohort Distinct quoted requests from one defined intake group. | 50 |
Won RFQs from this cohort Requests meeting your documented won definition. | 18 |
Lost RFQs from this cohort Requests meeting your documented lost definition. | 12 |
Example results
| Measure | Result |
|---|---|
Decided-quote win rate Wins divided by resolved wins plus losses. | 60% |
Won share of all quoted RFQs Wins divided by the entire quoted cohort. | 36% |
Open RFQs Quoted requests with no recorded final outcome. | 20 |
Calculation detail
| Measure | Result |
|---|---|
| Decided RFQs | 30 |
| Open share of cohort | 40% |
Model assumptions
- One quoted-request cohort and one observation date.
- Won and lost are disjoint subsets of that cohort.
- Open quotes are not automatic losses.
- Revisions do not create extra requests.
- Zero denominators produce unavailable rates.
Read alongside these results
- These descriptive rates forecast neither orders nor revenue.
- Changing the outcome definition or observation window changes the comparison.
Download this worked example (CSV). Use the interactive version to export your own inputs and results.
Your shop won several RFQs while other buyers still have quotes under review. Dividing wins by all quoted requests gives a different answer from dividing wins by decided quotes. Label your denominator before comparing estimators or changing prices.
The calculator above starts with 50 quoted RFQs, 18 wins and 12 losses. Those illustrative inputs leave 20 open quotes. The decided-quote win rate is 60%, while 36% of the entire quoted cohort has been won by the observation date. These are arithmetic examples, not machine-shop benchmarks or customer results.
Use with this guide
Record the reason behind a lost quote
Separate buyer evidence from guesses about pricing.
Build a current RFQ pipeline
Keep pending questions and owners visible alongside outcome rates.
Review the BlueFinch dashboard
See the available owner workspace without assuming a machining ERP or drawing archive.
Compare machine-shop customer concentration before chasing one account
A large account deserves a clear denominator. Separate its share of sales from a forecast about whether the customer will leave.
Create a weekly machine-shop sales pipeline report from recorded stages
An old quote with no next task does not become a forecast because the CRM displays a dollar amount. Review the decision and its owner.
Machine-shop RFQ aging: find quotes needing a decision
Track machine-shop RFQ aging by its current decision stage. Use the quote register to assign follow-up without counting unresolved quotes as lost work.
Browse the complete machine shop guides and worksheets.
Choose one group of quoted requests
Define the intake period and observation date before counting. Count distinct quoted RFQs from the selected intake period. New messages and quote revisions are not additional opportunities. Keep out-of-scope requests separate. A revised price for the same project does not create another possible win. Apply the same rules to another estimator’s list before comparing the two.
Record the current status of each quoted request in your CRM or quoting system. HubSpot’s pipeline guidance describes stages representing steps in a process. Use your actual decision record for won and lost rather than copying a software probability into the outcome. A buyer opening the quote email is not an accepted order.
Sources for this section: HubSpot: Set up and manage pipelines
Calculate the decided-quote rate
Add won and lost requests to get the decided count. Divide wins by that count and multiply by 100. In the illustrative example, 18 wins plus 12 losses gives 30 decisions. Eighteen divided by 30 produces a 60% win rate among decided quotes. The remaining 20 requests stay open. A zero decided count produces an unavailable rate.
The overall won share uses all 50 quoted RFQs instead, producing 36%. The open share is 40%. All three figures describe the same snapshot with different questions. None predicts how the open quotes will resolve. The tool rejects wins and losses exceeding the cohort rather than displaying an impossible negative open count.
Keep the reason behind the outcome
Use a documented rule for when a request becomes won or lost. Record the accepted order reference for a win. For a loss, retain the buyer’s actual answer where available. No response is not proof your price was too high. Keep withdrawals, duplicates and out-of-scope requests visible under your counting policy instead of silently mixing them into losses.
Connect the buyer and the project in the customer system. HubSpot’s association guidance describes linking records representing those relationships. Check your platform and plan rather than assuming labels or automation are available. The calculator receives counts only. It does not inspect your CRM, identify a buyer or determine which orders your shop should classify as won.
Sources for this section: HubSpot: Associate records
Compare similar work and observation periods
A prototype RFQ and a recurring production request have different decisions under discussion. Review quantity, scope and buyer type before interpreting a changed percentage. An early observation date leaves more unresolved quotes than a later one. Report the pending share beside the win rate so staff understand how much of the cohort is undecided.
Do not assign a cause from one rate. A smaller quote group or changed customer mix might explain the difference. The calculator provides no significance test, revenue forecast or pricing recommendation. Use the saved scenario comparison to document two sets of counts, then inspect the underlying request outcomes before attributing the change to an employee or follow-up message.
Use the report to find the next question
Open a few unresolved quotes and check the next action, owner and current scope. A buyer awaiting a drawing answer needs a different task from one postponing the project. The report should help identify the decision your team still owes, not encourage repeated generic contact. Review resolved loss reasons before changing the rate quoted on unrelated work.
BlueFinch’s business dashboard has the scope shown on its product page. It is not an RFQ outcome database or machining ERP. Keep the actual quote history in your chosen business system. Download this free report with its inputs and counting assumptions for the next review. Browser scenarios clear on reload, and no entered counts are sent to BlueFinch.
Sources for this section: BlueFinch: Business dashboard scope and demo
Primary sources
BlueFinch last reviewed these sources on October 3, 2026. Payment rules and state requirements can change.
- HubSpot: Set up and manage pipelines
- HubSpot: Associate records
- BlueFinch: Business dashboard scope and demo
Use this page for general business information. It is not legal, tax, or accounting advice.
Related resources
- 2026 Credit Card Processing Cost Report
- Auto Repair Shop Payment Guide
- Auto Repair Shop Credit Card Processing Calculator
- Compare machine-shop customer concentration before chasing one account
- Record why a machining quote was lost before revising your pricing
- Keep machine-shop RFQs from disappearing in a shared email inbox