How to tell a web designer your budget without getting a padded quote back
Say the number, or don't — here's what each choice actually does
You've got a number in your head and you're worried that saying it out loud just tells a builder exactly how high they can price you. That fear is understandable. It also usually points the wrong way. A stated budget doesn't set a ceiling for padding — it gives a builder something concrete to design toward.
Say your number is modest and you're worried that saying it out loud invites a builder to simply quote right up to it regardless of what the project actually needs. In practice, a builder who does that consistently tends to develop a reputation for it, and it's exactly the kind of thing worth asking a past client about before you sign anything.
Asking for a blind quote instead doesn't protect you from a padded number either. It just means the proposal gets built around an assumed scope nobody confirmed with you, minus the chance to shape it before it lands in your inbox.
A range is usually more useful to share than a single exact figure. It gives a builder room to propose something specific while still telling you honestly whether your expectations and their typical pricing are anywhere near each other before real time gets spent on either side.
What a builder actually does with a number you give them
A stated budget lets a builder work backwards: given this number, what's the best version of the project that fits inside it? That's a fundamentally different exercise than pricing an open-ended wishlist and hoping it happens to land close to what you had in mind.
A number also changes the kind of questions you get back. Instead of a generic list of everything a website could possibly include, you're more likely to get specific questions about what matters most to you — which pages are essential, which features can wait — because the builder is actively trying to make the math work.
It also filters out mismatches early. A builder whose typical projects run well above your number can tell you that upfront, before either of you spends time on a proposal that was never going to work.
That early honesty saves everyone the awkward version of this conversation, where a full proposal shows up, the number is far off from what you had in mind, and neither side knows quite how to walk it back gracefully.
Scope a smaller version instead of walking away
A number that feels too small for "everything" can be enough for a smaller, well-chosen version of the project. Fewer custom pages, a lighter feature set, a template-based foundation instead of a from-scratch build — all of these can bring a project back inside a number you already have.
A five-page brochure site with a contact form is a realistic starting point even when the long-term vision includes online booking, a members area, and a blog. Getting the essentials live now, professionally built, often serves a business better than waiting until every feature can be afforded at once.
Some of the same trims show up among the routes that genuinely cost less than a full custom build — a lighter template, a smaller page count, a phased rollout.
What drives the price up is exactly what you'd trim first: custom features, heavy integrations, extensive content work. Naming your budget and asking what this would look like at this number gets you a real answer instead of a guess about what to cut.
Phase the build across more than one budget cycle
Not every website has to launch as one complete project. A phased build ships a solid first version now — the pages and features that matter most — and adds the rest in a later phase, on a separate budget cycle.
This works especially well when the immediate need is narrower than the long-term vision: get a working, professional site live now, then add the booking system or the members-only section once there's budget for it again.
Phasing also gives you a chance to see how the first version actually performs before committing more budget to features you were only guessing you'd need. A booking system built in a later phase can be shaped by real customer behavior from the first phase, instead of by assumptions made before the site existed.
Questions that surface a real answer, not a padded one
Ask what would change about the proposal if your number were meaningfully higher or lower. A builder who can answer specifically — which features would come off, which would get added — is scoping to your actual budget. One who just adjusts the total without explaining what changed is not.
It's also fair to ask what a typical project at your stated number tends to include, in general terms, before you commit to a full conversation. That gives you an early read on whether the number and the vision are in the same neighborhood, without either side having done a full scope yet.
Ask what's driving the number you're comparing it against, too. Two proposals built around the same budget can still look very different once you see what each one included to hit that figure. What actually determines the total is the same set of factors regardless of how the conversation about budget started. The honest version of that conversation just gets you there faster.
There's nothing awkward about naming a number early. The builders worth working with treat it as useful information rather than an opening they can quietly push past. The ones who bristle at the question are telling you something worth hearing before you get any further into the process.
The conversation itself is a small, low-risk step compared to what it buys you: a proposal shaped around what you can actually spend, instead of a guess you have to negotiate down after the fact.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go