Won the RFQ, Lost the Margin: The 7 Traps in Project Sales
Project Sales · 3. Februar 2026 · Klaus Müller
The customer sends an RFQ, your team invests weeks, and the winning bid becomes a loss-making project. Discover the 7 most common traps in project sales and how to defuse them effectively to protect your margins.
You know the scenario: The customer sends an RFQ, your team invests weeks in engineering, calculation, and quoting, and in the end you win the bid. Yet a bitter aftertaste remains: the margin is gone, the project is stressful, there are escalations, addendums, and bad morale. In the worst case, the won order is a loss-making business.
This is not an isolated case, but a common pattern in project sales: An RFQ is often not the beginning of the buying process, but a late step in it. You frequently receive a request when the playing field has already been defined.
The 7 Traps in Project Sales
Trap 1: You react to the RFQ instead of setting the framework beforehand
Symptom: You only enter the game when the specification is already set. Consequence: You become a price taker. Differentiation is difficult, comparability is high.
Countermeasure:
- Treat the RFQ as a late signal, not as a starting gun
- Be present early on through content, preliminary work, reference cases, and expert dialogue
Trap 2: Bid or No-Bid is decided based on gut feeling
Symptom: You submit an offer because you have to or because the customer is important. Consequence: Effort explodes, the win rate remains average, and margins are sacrificed.
Countermeasure with clear criteria:
- Strategic fit
- Feasibility and capacity
- Risk and payment or delivery terms
- Hard termination rules: If X, then no offer.
Trap 3: Lack of capacity leads to silent risks
Procurement or the project team decides too late that parts need to be purchased externally, or they underestimate delivery times. A supply risk check should be a mandatory part of the quoting phase.
Trap 4: Pricing like a calculation, not like a risk decision
We calculate cleanly, so it fits. Even small deviations can destroy the margin. Pricing logic must be separated: target costs vs. risk costs vs. contract costs.
Trap 5: Lack of stakeholder alignment
Engineering says A, procurement asks B, finance wants C, production expects D. In the project business, a network of operations, engineering, procurement, quality, finance, and possibly IT makes the decision.
| Stakeholder | Focus |
|---|---|
| Procurement | Price, terms, contract clarity |
| Finance | Total cost, payment terms, budget |
| Operations/Production | Schedule reliability, downtime avoidance |
| Engineering | Feasibility, integration, risk |
| Quality | Acceptability, documentation and proof |
Trap 6: Scope is not watertight
Unclear boundaries or missing assumptions lead to addendums, disputes, and unpaid additional effort. A lack of clarity regarding the scope and weak stakeholder involvement are among the most common reasons for contract value erosion.
Trap 7: Poor handover from the deal team to execution
Sales wins, the project team inherits. Promises get lost, expectation gaps arise. The handover must be a fixed milestone covering scope, assumptions, risks, open items, and a stakeholder map.
Practice Test: Spotting RFQ losses early
How Amplifa helps you win RFQs more profitably
- Enter the right accounts earlier: Amplifa identifies suitable target customers via signals and fit so you are not just a price taker.
- Free up capacity: When lead generation and appointment setting run semi-automatically, sales and sales engineering gain time for scope clarity and risk checks.
- Systematically map buying committees: Structurally address multiple roles per account rather than just serving procurement.
Conclusion
In project sales, it is not the cheapest provider who wins, but the cleanest process.
If you consciously manage these 7 traps, something crucial happens: You do not just win orders, you win orders that are worthwhile.