Anchoring bias means the first number a client hears becomes their reference point for every number that follows, unless you manage it, even when caveats are attached. To reduce the risk of anchoring when you give a ROM, lead with the full range rather than a midpoint, restate the basis of estimate every time the figure is repeated, and put the caveats in writing immediately rather than trusting a verbal disclaimer to survive being retold.
Terms used in this guide. fee: the amount charged to the client; cost: the expense included in the stated project model; margin: revenue left after the included costs; margin percentage = that amount / revenue × 100; ROM: rough order of magnitude: an early estimate for a planning decision.
In plain words
Anchoring means the first number a client hears sticks, and every later number is judged against it. If you say “probably around fifty” on a call, the client keeps fifty in mind even if you later write “seventy-four”. You cannot remove the effect completely, but you can reduce it: give the whole range, say what moves it, and repeat the basis each time the number is mentioned.
Who this helps: Presales consultants and sales managers who talk to clients before a project is scoped.
Questions this guide answers:
- How do you present a ROM estimate to a client?
- What is a business ROM and how should it be worded?
- Why does the first number in a negotiation matter?
- How do you avoid a client holding you to a low early estimate?
Read first: What is a ROM estimate? explains the basics and the lifecycle this guide builds on.
What is anchoring, and why does the first number stick?
An early number can influence later judgments even after better information arrives. Tversky and Kahneman’s research on anchoring is relevant background, but it does not establish that every buyer anchors or that any wording eliminates the effect.
In a services proposal, treat anchoring as a communication risk: a forwarded budget note may preserve the amount while losing the scope assumptions. Present the decision, range and main uncertainty together, and explain revisions using changed evidence. A range can itself anchor attention on either endpoint.
Why is anchoring a commercial risk for IT projects?
For a presales or delivery lead, an anchored client produces two specific, costly outcomes. Either they negotiate the definitive proposal against the wrong number — pushing back on a fee that is objectively fine but subjectively "higher than what you said" — or they hold the anchor against you later, treating a legitimately higher definitive price as evidence you underquoted on purpose. Both outcomes damage the deal and the relationship, and neither is fixed by having technically stated a correct range at the time.
When is the anchoring risk highest, and when can you manage it?
Risk is highest when a ROM is given verbally, off the cuff, under pressure to fill an awkward silence in a first call — exactly the moment a rep is least prepared to phrase it carefully. Risk is lower, though never zero, when a ROM is presented as a written range with an explicit basis of estimate attached, because the full context travels with the number instead of a bare figure traveling alone. The wrong way is blurting a single number to end the silence; the right way treats the range itself, and what would move it, as the actual content of the answer.
How do you present a ROM estimate so it does not anchor?
- Lead with the range, not a midpoint. Say "somewhere between $160,000 and $267,000" — never round that down to "call it $160k" or "around $200k," both of which hand the client a single anchor to fixate on.
- State the basis of estimate every time the number is repeated — verbally and in writing — covering what's included, what's excluded, and what's assumed. A number without its basis is just an anchor; a number with its basis is a starting point for a scoping conversation.
- Steer the conversation to what drives the range, not to either endpoint. Explaining why the range is about $107,000 wide (undefined data volume, unconfirmed integration count) gives the client something more useful to focus on than either endpoint.
- Put the caveat in writing immediately. Do not rely on a verbal disclaimer surviving the retelling — the client will very likely forward just the number to their own boss, stripped of everything you said around it, unless the range and its basis are already in an email or proposal document before that happens.
Example: how one spoken number reshapes a negotiation
Assume a comparable integration cost USD 150,000 to deliver. A scope review identifies a simpler case that removes USD 30,000 of migration work, and a difficult case that adds USD 50,000 of reconciliation work. The provisional internal cost scenarios are USD 120,000 and USD 200,000. These are assumed work changes to investigate, not confidence limits from a standard percentage.
With no other charges and a 25% target margin, the corresponding client fees are 120,000 / 0.75 = USD 160,000 and 200,000 / 0.75 = USD 266,666.67. Share the approved fee range externally and retain the internal cost model. Suppose discovery later supports USD 172,000 cost: the same assumptions require a USD 229,333.33 fee. Explain the confirmed reconciliation work and exclusions instead of comparing that fee with the original internal cost.
The client’s next decision is whether the investigation and scope justify proceeding. Keep both the initial scope hypothesis and the revised estimate so that a changed price has a traceable explanation.
- How to Price a Project to a Target Margin: Formula and Example
- ROM Cost Estimate Examples for IT Projects
- ROM Quote and Estimate Email Examples: 6 Templates
- Cone of Uncertainty in Project Estimation, Explained
How do pricing strategies and rate permissions help in Managed Margin?
Managed Margin lets pre-sales save more than one pricing strategy for the same service order, each with its own team, duration, price and calculated margin, so a leaner option can be compared with a heavier one side by side rather than relying on a single remembered figure. Resource profiles carry role-based planning rates, and individual employee costs are protected by separate permissions, so a pre-sales user can discuss a margin range without exposing what individual people are paid. See project pricing software and the project rate card guide. The software does not remove the need to state the range and its basis out loud; it gives pre-sales real options to anchor the conversation around instead of one guessed number.
Real example: a sales manager says “around fifty” on a call
An illustrative story with invented figures, to show how the idea works in a real office.
Tom, a sales manager, is asked for a number on a first call and answers, “probably around fifty thousand dollars.” Three weeks later the detailed estimate is USD 74,000. The client says, “You told us fifty.”
On the next opportunity Tom changes his habit. He says: “The price could be between fifty and ninety thousand dollars. It depends on two things: how many systems we connect and how clean your data is. We will know more after a short discovery.”
In his follow-up email Tom writes: “Planning range USD 50,000 to USD 90,000, for budgeting only. It depends on how many systems we connect and the quality of your data. Not a quote. We will confirm after a two-day discovery.” The client writes down the range and the two reasons. When the final number is USD 74,000 it falls inside the range, and the conversation is about the two unknowns, not about being misled.
Who presents an early estimate, and at which stage of the deal?
Anchoring does not happen once. A number gets said at four moments in a deal, and each has an owner and a wording checkpoint. A presales lead coaches new teammates on all four.
| Moment | Who is speaking | Wording checkpoint |
|---|---|---|
| The first call | Sales manager or account manager | No single figure. Say the range, the two things that move it and that a short discovery will confirm it. |
| The written ROM | Presales consultant, reviewed by the presales lead | Range, basis, assumptions, “not a quote” and a review point, all in the same message as the number. |
| The budget meeting | The client sponsor, quoting you | Make the written version easy to forward whole: a short note, not a spreadsheet. Ask what they will say if asked the number. |
| The discovery readout | Presales lead | Explain the new number against the earlier range using what discovery found, not against the lowest figure you ever said. |
If the number has already stuck, restate the range and its basis, explain what changed, and agree a review point. Do not simply defend a figure.
Presenting a ROM estimate: frequently asked questions
Should I lead with the low or the high number?
Lead with the range, not either end. State low and high together and say what drives the difference.
What if the client has already anchored?
Restate the range and its basis, explain what has changed, and propose a review point. Do not simply defend a number.
How does this connect to a written ROM?
The email or document should carry the same wording. See the guides on ROM emails and on ROM examples.
Continue the sequence: guides to read next
- What Is a ROM Estimate? Meaning, Cost and Example: the definition of the range you are giving
- How a Discount Affects Project Margin: Formula and Example: what happens when an early low number becomes the anchor
Sources and methodology
The calculations and scenarios are original illustrations, not customer results or market benchmarks. Product guidance was checked against the current pricing and delivery implementation on 13 October 2026.
- GAO Cost Estimating and Assessment Guide: evidence, estimating methods and uncertainty analysis.
- AACE International recommended practice 18R-97 (not linked: the freely available copy is a sample): the process-industry classification of estimates and the limits of generic accuracy ranges.
- Tversky and Kahneman, Judgment under Uncertainty: background on anchoring; this article does not claim that wording eliminates the effect.