Most CRM reports stop at won, lost and a reason such as price. That record cannot tell you whether the buyer compared the same scope, whether the project went ahead, which competitor won or what happened after your own order entered engineering and production.
A disciplined review follows the quote in both directions. It reconstructs the customer’s decision from evidence, then follows won work through order review, manufacturing, shipment and early service. The result should change a qualification rule, cost assumption, product choice, price approval or proposal. If it changes nothing, the reason code is too broad to help.
Classify the outcome before you assign a reason
Separate competitive losses from projects that never reached a purchase. A cancelled capital project says little about the strength of the offer. A budgetary request that never received funding says even less. Mixing these outcomes lowers the reported win rate and sends product, sales and pricing teams after a problem they did not cause.
Record the customer outcome and your own pursuit outcome. A manufacturer may withdraw because the RFQ changed, the delivery window became impossible or new contract terms exceeded its risk limit. That is useful evidence, but it is not a competitor win.
| Outcome | What it means | Evidence to retain |
|---|---|---|
| Won | The customer placed the order with your company | Purchase order, final negotiated terms and accepted scope |
| Lost to competitor | The customer bought a competing offer | Winner, comparable scope, decision criteria and customer statement |
| No decision | The customer delayed, cancelled or did not fund the project | Customer confirmation, revised date and next review point |
| Customer changed the requirement | The final need no longer matched the submitted quote | Changed quantity, scope, site, schedule or procurement route |
| Withdrawn or no-bid | Your company chose not to submit or left the competition | Decision owner, date and the rule that caused the exit |
| Budgetary or test request | The customer did not run a live purchase process | Stated purpose and evidence that no award was made |
Freeze the quote the customer actually evaluated
Save the final submitted revision before anyone explains the outcome. The baseline needs enough detail to recreate the commercial offer without opening an old mailbox: the supplied equipment, exclusions, options, quantity, net price, discount, delivery promise, payment terms, warranty, validity, risk allowance and every customer requirement that remained an assumption or deviation.
Also save the estimate that supported the price. Include the material and labor basis, engineering hours, bought-out quotes, freight, commissioning, contingency and approved margin. Later cost data has value only when the business can compare it with the same scope and cost structure used at approval.
| Baseline item | Record at submission | Why it matters later |
|---|---|---|
| Scope | Equipment, quantity, deliverables, options, exclusions and customer revision | Shows whether offers and actual costs cover the same work |
| Commercial offer | Gross and net price, discount, currency, terms, warranty and validity | Explains the approved trade between price, cash and risk |
| Schedule | Quoted ship date, milestones and customer dependencies | Separates an uncompetitive lead time from a later execution miss |
| Cost basis | Material, labor, engineering, suppliers, freight, site work and contingency | Supports quoted-versus-actual review by cost family |
| Bid effort | Internal hours, supplier requests, tests and travel | Shows the cost of pursuing and revising the opportunity |
| Open position | Assumptions, deviations, unresolved questions and approval exceptions | Preserves the risks that the final price accepted |
Ask the buyer while the decision is fresh
Request the review after the customer has made the decision and before the team forgets the details. For a material bid, use someone who can listen without defending the proposal. The account manager can introduce the discussion and supply context, but the interviewer should not turn the call into another sales meeting.
Ask how the customer made the decision. Which criteria mattered? Who took part? Which offers reached the final comparison? Did the customer normalize scope, delivery, warranty and terms? What gave the winning supplier technical credibility? Which concern made your offer harder to accept? What should your team have done earlier or explained better?
Save the buyer’s words separately from your team’s interpretation. “Your delivery was four weeks later” is customer evidence. “We lost because operations would not reserve capacity” is an internal diagnosis that still needs support. Both may be useful, but they carry different confidence.
- Record who supplied the evidence and when.
- Quote or summarize the specific customer statement without turning it into a broader claim.
- Mark competitor scope and price as confirmed, reported by the customer or inferred.
- Allow one primary reason and several contributing reasons.
- Leave the reason unresolved when the evidence does not support a conclusion.
Treat “price” as the start of the review
Buyers often say price because it is easy to report and hard to argue with. Find out what the number included. A competing offer may omit commissioning, use a shorter warranty, accept a later payment milestone or assume a different test standard. Normalize those differences before changing a price rule.
The remaining gap can still be real. The customer may not value the added scope, may distrust the technical approach or may simply have a lower-cost option. Record that result plainly. Do not relabel every price loss as “value communication” to protect the estimate.
Discounting deserves the same arithmetic. The NIST MEP manufacturing finance guide shows that a company with a 35% gross margin needs just under 17% more unit volume to recover a 5% discount, and 40% more volume to recover a 10% discount. The exact effect depends on the job’s cost base, so show the approved discount and the contribution it removed on that quote.
| What “price” may hide | Check | Action if confirmed |
|---|---|---|
| Different scope | Normalize equipment, documentation, testing, installation, spares and exclusions | Fix the comparison and make scope differences obvious in the proposal |
| Different risk transfer | Compare warranty, penalties, payment, bonds, escalation and validity | Price the exposure or change the approved position |
| Different delivery | Compare ship date, site date and customer dependencies | Change the capacity promise, supplier plan or qualification rule |
| Unconvincing premium | Ask which benefit justified a higher price and whether the buyer believed it | Change the offer or supply proof the customer will use |
| Higher comparable price | Compare the normalized net price for the same obligation | Review cost, margin target, discount authority and market position |
Code the reason with its evidence and owner
Use a short reason family, then write the specific cause. “Delivery” is a family. “Our quoted ship date missed the planned outage by three weeks because the approved motor lead time was 26 weeks” is a cause that sourcing and planning can test. “Product fit” becomes useful when it names the missing certification, duty range or interface.
Separate external and internal findings. The PMI paper on risk in the early project phase treats customer, market, competitor and strategic position as external risk, while product, process, resource and cost deviations belong to internal risk. It also recommends comparing successful work with its expected cost, time and performance, while comparing unsuccessful bids with the winning offer where evidence exists.
| Field | Example | Rule |
|---|---|---|
| Primary reason | Delivery window | The factor with the strongest evidence and greatest effect on the decision |
| Contributing reason | Technical clarification finished late | A factor that weakened the offer without deciding the outcome alone |
| Evidence | Buyer debrief on 18 May; award notice; competitor schedule supplied by buyer | Name the source and date |
| Confidence | Confirmed, supported, weak or unknown | Do not turn a guess into a fact when reporting across bids |
| Owner | Supply chain director | The person who can change the relevant rule or input |
| Action | Qualify alternate motor at RFQ intake | A dated change with a testable result |
Review won work at order release and after delivery
The first review happens when the purchase order arrives. Compare the order with the accepted proposal. Record negotiated concessions, changed quantities, new documentation, revised delivery, retained scope and any customer term that moved after the “win.” A deal can enter the backlog with less margin and more risk than the quote that sales marked won.
The second review happens when the business has enough actual cost and schedule data to judge the order. Compare the estimate with material receipts, booked labor, engineering hours, subcontract cost, freight, rework, expedite, warranty and service. Include approved and unbilled changes. A profitable base order can still lose money when the team absorbs customer changes that should have become a change order.
The GAO Cost Estimating and Assessment Guide calls for teams to update estimates with actual costs and document why cost or schedule changed. Crowe’s manufacturing analysis of pricing leakage lists material overruns, labor variance, expedited freight, rework, warranty and subcontracting among the costs that can erode margin after an order is won. Those categories belong in the win review because they test the assumptions behind the next quote.
| Compare | Quoted baseline | Delivered result |
|---|---|---|
| Scope | Accepted equipment, deliverables and exclusions | Delivered scope, concessions and absorbed changes |
| Cost | Material, labor, engineering, supplier, freight and contingency | Actual cost by the same families, with variance reason |
| Schedule | Customer and internal milestones | Actual dates, delays and accountable cause |
| Margin | Approved gross profit and contribution | Realized margin after concessions and execution variance |
| Quality and service | Inspection, acceptance and warranty basis | Rework, claims, field time and customer acceptance |
Worked example: the customer said price
Consider a hypothetical quote for four engineered dosing skids. The OEM submits $780,000 with witnessed factory testing, commissioning and a 24-month warranty. The customer buys a competitor’s $690,000 offer and tells the account manager that price decided the award.
The review finds that the competitor excluded the $18,000 witnessed test and $25,000 commissioning scope, and offered an 18-month warranty that the OEM values at a $12,000 difference. The comparable competing offer is about $745,000. The remaining $35,000 gap is 4.7% of that normalized price, far less than the headline 11.5%. The buyer also confirms that the winning supplier promised shipment four weeks earlier.
The primary reason becomes delivery. Comparable price remains a contributing reason. The team also records that a motor clarification sat with engineering for six days and pushed supplier selection past the capacity reservation date. The response is specific: qualify a second approved motor for this product family, request motor data at intake and show optional test and commissioning scope separately. “Reduce price” would have missed all three changes.
| Comparison | Your offer | Winning offer | Review result |
|---|---|---|---|
| Submitted price | $780,000 | $690,000 | $90,000 headline gap |
| Witnessed factory test | Included | Excluded: $18,000 | Add to competing scope |
| Commissioning | Included | Excluded: $25,000 | Add to competing scope |
| Warranty | 24 months | 18 months | Add $12,000 risk-adjusted difference |
| Comparable price | $780,000 | $745,000 | $35,000, or 4.7%, remaining gap |
| Shipment | 24 weeks | 20 weeks | Customer confirms four-week difference mattered |
Segment the data before you compare rates
A repeat spare, a configured machine and a first-of-kind engineered package do not have the same sales cycle, bid effort, cost risk or expected win rate. Compare similar work: product family, quote type, region, channel, customer relationship, deal size, incumbent position and technical novelty. Keep the sample size beside every rate.
Use distributions as well as averages. A median response time can hide a group of engineered bids that consistently miss the customer deadline. A higher win rate can hide a fall in realized contribution if the business discounts the segment with the most execution risk.
The RFQ scoring method supplies another useful segment. Compare the predicted win band with the result, then compare the internal risk score with delivered margin and schedule. A score that predicts awards but misses bad orders needs better cost or execution factors.
Turn each repeated finding into a dated change
Review individual bids first, then look for a repeated cause. Give each theme an owner, a change and a date. Check later bids from the same segment to see whether the result moved. A quarterly deck full of reason percentages does not improve the next quotation by itself.
| Repeated finding | Change the team can make | Test on later work |
|---|---|---|
| No-decision rate is high in unfunded projects | Require budget source and decision date before full bid funding | Bid hours and no-decision rate for qualified projects |
| Late technical questions weaken delivery | Move product-specific checks into RFQ intake and name a response owner | Clarification age and on-time submission by product family |
| Comparable price remains high | Review cost drivers, margin rules and modular scope options | Normalized price gap and realized margin |
| Won orders overrun engineering | Update engineering-hour standards and identify first-of-kind work during qualification | Quoted versus actual engineering hours |
| Changes are delivered without payment | Tie changed requirements to a commercial change review before work starts | Approved, rejected and unbilled change value |
How Bourne supports win-loss review
Bourne can assemble the final submitted quote, estimate, approvals, customer messages and award evidence in one review. For a loss, it keeps the buyer’s statement separate from the team’s diagnosis and shows which scope, price, delivery and terms changed the comparison. For a win, it connects the accepted commercial baseline to the purchase order, actual costs, schedule events and change records.
When a similar RFQ arrives, Bourne can surface the earlier case during bid/no-bid review and costing. The reviewer sees why the case is similar, which facts came from the buyer and which assumptions failed during delivery. Your commercial and operational owners decide which lesson applies to the new quote.
Measure whether the reviews improve later bids
| Measure | Question it answers |
|---|---|
| Outcome coverage | How many submitted quotes have a confirmed outcome instead of an expired CRM stage? |
| Evidence coverage | How many reasons cite a buyer, award record or comparable commercial fact? |
| No-decision rate | How much bid effort goes to projects that do not reach a purchase? |
| Win rate by comparable segment | Where does the company win when the work and buying situation are similar? |
| Quoted versus realized margin | Which assumptions or concessions make won work less profitable? |
| Estimate variance by cost family | Where do material, labor, engineering, suppliers or freight miss the baseline? |
| Action follow-through | Did the owner make the agreed change, and did the next comparable bids improve? |
Set review timing by value and risk. A standard spare may need a short reason and margin check. A large engineered order may need an award review, an order-release review and a final cost review after delivery. Use the detail that can change a later decision. Skip fields that nobody will act on.
Bourne for manufacturing
See what Bourne could do for your quoting team.
Bring a customer request and the steps your team takes to quote it. We’ll discuss the application, integrations and approvals you need.