“Can you give me a ballpark?” is something clients ask before they have a detailed scope. “Here’s our exact budget” is something clients say after they’ve got one. Between those two points, there are actually four distinct types of estimates — each appropriate at a different stage and with a different level of accuracy expectation. Using the right type at the right time protects you from under-pricing and protects the client from surprise costs.
Why estimate types matter
The problem with giving a number too early is that it anchors the client’s expectation. If you say “$5,000” in a casual early conversation without qualification, and the project later comes in at $12,000 after proper scoping, the client feels misled — even though you told them at a higher level of scope.
Naming the type of estimate you’re giving sets the right expectation. “This is a ballpark based on what I know so far — I’ll give you a proper quote after we define the scope” is a sentence that saves future disputes.
Type 1: Ballpark estimate
What it is: A rough range based on your experience with comparable work. Not based on analysis of this specific project.
Accuracy: Wide range — could be off by 50–100% in either direction.
When to give it: When a client asks for an idea of cost before you’ve done any discovery. In early conversations, before a scope of work exists.
How to communicate it: Always qualify it. “For something like what you’re describing, projects typically run between $X and $Y — that’s based on similar work I’ve done. Once I understand your full scope, I can give you a real number.”
Never commit to a ballpark. It’s a starting point for conversation, not a price.
Type 2: Rough Order of Magnitude (ROM)
What it is: More structured than a ballpark but still approximate. Often used in project management and construction but applicable to any complex freelance work.
Accuracy: Typically +50%/-25% — meaning the actual cost could be 50% higher or the project could come in at 25% under.
When to give it: Early in a project after some initial scoping but before detailed discovery. Useful when a client needs to build an internal budget or get approval for a project before you’ve done the full work to produce a definitive estimate.
How to communicate it: “Based on our initial conversation, I’d estimate this project in the range of $15,000–$30,000. This is a rough order of magnitude — the final number will depend on scope decisions we haven’t made yet.”
Type 3: Budget estimate
What it is: Based on defined project parameters. You have enough information to estimate reasonably accurately, but some scope elements are still being refined.
Accuracy: Typically +/-10–15%.
When to give it: After preliminary discovery, when the main parameters are known (project type, approximate scope, key deliverables, timeline constraints) but detailed specifications haven’t been finalized.
How to communicate it: “Based on what we’ve discussed, my budget estimate for this project is $22,000–$26,000. This will tighten up once we finalize the feature list and decide on the third-party integrations.”
Type 4: Definitive estimate
What it is: A precise figure based on full project scope. This is what appears in your proposal or quote.
Accuracy: Within +/-5% — essentially, this is your price.
When to give it: After completing discovery. You understand the full scope, deliverables, timeline, technical requirements, and any dependencies. You’ve asked the questions you need to answer.
A definitive estimate is only as accurate as the scope it’s based on. If the scope isn’t fully defined, you’re actually giving a budget estimate calling it definitive — and scope changes will prove it.
How the four types work together in a client engagement
A typical project might move through all four types:
- First call: Client asks for a ballpark. You give a range: “$10,000–$25,000 depending on scope.”
- Post-discovery call: You provide an ROM: “$15,000–$20,000 for what we discussed — pending final tech decisions.”
- Mid-scoping: Budget estimate in writing: “$17,000–$19,000.”
- Proposal: Definitive estimate: “$18,400.”
Each step narrows the range as you learn more. The client’s expectations evolve with the numbers, rather than being shocked by the final price after expecting the early ballpark.
Communicating estimates in proposals
When you send a formal proposal with a definitive estimate, you’re turning that number into a commitment. Once the client signs, that’s the price. Make sure the scope that generated the estimate is clearly stated — and include a clause about how scope changes are handled (typically, changes to scope require a change order with revised pricing).
Waco3 makes it straightforward to turn a definitive estimate into a trackable proposal with line-item pricing — and you’ll know when the client opens it and reviews the price section.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
