Explain why you are asking
For a freelancer, asking about budget before preparing an estimate can feel like asking the client to name a price. Framed well, it is a question about fit. A website, illustration package, or content project can take several forms, each with a different level of work. Knowing the client’s working range helps you propose an approach they can consider, rather than spending time pricing an option they were never prepared to pursue.
Set that context before asking for a figure. You might say, “There are a few ways to approach this, depending on what needs to be included. Do you have a working budget range I should design the estimate around?” The word “working” leaves room for discussion. It also makes clear that the range will guide your recommendation, not automatically become your fee.
Learn what the budget needs to cover
A number alone rarely tells you enough. One client may mean the full cost of a launch, including writing and development; another may mean only the design portion. Before treating a range as a constraint, ask what it covers. Clarify the deliverables, who will supply materials, the desired timeline, and whether other collaborators or expenses need to fit inside the same amount.
Then ask about priorities. “What must be ready for the first release, and what could follow later?” is often more useful than asking whether the client can increase their budget. Their answer may point toward a smaller first phase or a simpler deliverable. It can also reveal work that should be priced separately, such as additional page templates or rounds of revisions. Write down these assumptions so the eventual estimate reflects the same project both parties discussed.
Make it easy to answer without a fixed figure
Some clients do not know what the work typically costs. Others may have an internal limit but need to confirm it. If they cannot share a range, avoid turning the conversation into a standoff. Ask whether they have a ceiling, an approval threshold, or a range they would feel comfortable reviewing. You can also describe two levels of scope in plain terms and ask which is closer to what they had in mind.
If you have enough information to offer a rough starting range from your own practice, label it clearly as preliminary. Explain what it assumes and what might change it. For example: “For a project with the pages and review process we’ve discussed, I would expect the estimate to fall within this range. Additional content creation would be separate.” A preliminary range is a way to check alignment; it is not a substitute for defining the work.
Respond to a mismatch with options
A client’s range may be lower than the cost of the scope they described. That does not require an apology or an immediate discount. Explain the gap in terms of work: “At that range, I could cover the core page designs, but not the additional templates and launch graphics.” This gives the client a concrete choice. They can reduce scope, phase the project, seek a different solution, or revisit the budget.
Be specific about what a smaller version preserves. If the main goal is to test a new offering, a focused landing page may serve that goal better than a partially completed site. If the client needs a full set of assets at once, reducing the work may not be sensible. It is better to say so than to promise a result that the available time or budget cannot support.
Carry the conversation into the estimate
Before drafting, briefly confirm your understanding in writing: the client’s goals, the agreed scope, their budget range if they shared one, and any open questions. This creates a chance to correct misunderstandings while the project is still easy to adjust. If the range was not discussed, you can still state the scope and assumptions you will price, rather than pretending a budget was agreed.
Make the estimate easy to compare with that conversation. List what is included, what is excluded, the expected review process, and any optional additions. If you offer phases, show what each phase delivers instead of presenting a lower total with essential work quietly removed. A good budget discussion does not guarantee acceptance. It gives both sides enough clarity to decide whether the proposed work, cost, and expectations belong together.
