Most freelancers leave discovery knowing what the buyer wants but not what it’s worth to them. Opportunity sizing closes that gap. It’s the question that turns “here’s what we’re trying to achieve” into “here’s why the investment makes financial sense”, and it takes about thirty seconds to ask.
The Question Most Freelancers Are Too Polite to Ask
Here’s the scenario: you’ve done a solid discovery call. You know the goals, you’ve heard about past pain, you understand the timeline. You’re about to say “great, I’ll put together a proposal.” And then you don’t ask the question that would make the proposal better, justify the price, and qualify the buyer’s seriousness all at once.
“If we hit those goals, what’s that worth to the business?”
Most freelancers skip it. The reasons are understandable: it feels presumptuous, it sounds like a price justification tactic, it might put the buyer on the spot. But every one of these concerns dissolves when you understand what the question is actually doing.
It’s not a manipulation move. It’s a diagnostic. You’re helping both parties understand whether the investment of time, money, and organizational energy is justified by the outcome. That’s not sales technique, that’s basic business logic.
How to Ask It Without Awkwardness
Framing determines whether this question lands as strategic or presumptuous. The transition that works: “You mentioned the main goals are [restate ranked goals from earlier in the call]. Before we talk about scope, I want to make sure I understand the stakes, if we actually hit those, what’s that worth to the business over the next 12 months?”
Three elements make this framing work:
First, you recap the goals before asking. This signals you’ve been listening and positions the question as a natural extension of what they just said, not a pivot to pricing.
Second, you specify a time window, “over the next 12 months” grounds the estimate in something calculable. “What’s better marketing worth?” is unanswerable. “What would a 15% increase in qualified leads be worth over the next year?” is not.
Third, you say “to the business” rather than “to you.” This keeps it objective and operational rather than personal, which lowers the defensiveness some buyers feel about sharing financial information.
The opportunity sizing question doesn’t just anchor your price, it tells you whether the engagement is worth pursuing at all. A buyer who can’t articulate the value of their own goals either hasn’t thought through the project seriously or is running a price-shopping exercise. Both are useful things to know before spending six hours writing a proposal.
Building the Number Together When the Buyer Doesn’t Have One
“I’m not sure” or “we haven’t really quantified it” is a common first response. Don’t interpret this as a signal to move on. It’s an invitation to do a joint calculation.
Walk them through it step by step. “Let’s rough it out. What does the problem cost you right now, in time, rework, missed revenue, whatever applies?” That usually produces a number. Then: “What would hitting Goal 1 be worth, if the conversion rate went up by X, what does that mean in monthly revenue?”
The arithmetic is usually simple. You’re not building a financial model, you’re anchoring both parties in a shared understanding of the stakes. Even a rough number, “somewhere between $50K and $100K over the year”, is infinitely more useful than no number.
If the buyer genuinely cannot estimate, ask them to calibrate on magnitude: “Are we solving a $10K problem or a $200K problem?” Most buyers can place themselves on that scale even when they can’t give exact figures.
The Number as Proposal Architecture
Once you have the opportunity size number, it performs two functions in your proposal.
Function 1: ROI framing. Your proposal now has a natural headline calculation. “The outcomes we’ve defined in this engagement represent an estimated $80–120K in [revenue impact / cost reduction / efficiency gain] over the next 12 months. Our investment for this engagement is $14,500.” The buyer doesn’t have to do the math, you’ve done it for them.
Function 2: Scope calibration. If the opportunity is $15K and the buyer is thinking about a $12K proposal, you have a scope problem to solve before submitting. Either the scope needs to shrink to leave meaningful ROI on the table, or the opportunity needs to be reframed as larger than they currently see it. The opportunity sizing number gives you the data to have that conversation before it becomes an objection.
When the Number Is Smaller Than Your Price
This is the scenario freelancers worry about, the one where the honest application of the question creates a pricing problem.
It happens. A buyer names an opportunity size of $20K and your proposal is going to be $17K. That’s a 15% ROI on their investment, which is weak. You have two options:
Rescope the engagement to deliver specific outcomes at $7–8K, a leaner version that leaves clear ROI headroom.
Or help the buyer see that their opportunity sizing is incomplete. “You mentioned Goal 1 is worth about $20K in annual revenue impact. But Goal 2, the operational efficiency piece, that wasn’t included in that estimate. What’s the time cost of the current process per week, multiplied out?” Often the real number is two or three times what the buyer initially named, and your full proposal becomes clearly reasonable.
Qualifying Intent With the Size Question
The opportunity sizing question is also an intent qualifier. Buyers who are serious about solving a problem engage with the calculation. They have a rough sense of what the outcome would mean. They’re willing to do the math with you.
Buyers who are running a price-shopping exercise, collecting proposals to justify an internal decision they’ve already made, or not actually empowered to move forward tend to shut down when asked about value. “I don’t know, we just need someone to do the work” is a soft red flag worth noting.
Not a disqualifier on its own, but paired with other signals, it tells you where to put your proposal-writing energy.
Ask the question. Count the awkward pause as a feature, not a bug. The answer you get is the most important number in your discovery call.
