How to Price Web Design Projects: A Freelancer and Agency Guide
Ask ten web designers how they price a project and you'll get ten different answers, and most of them will admit their pricing is more instinct than system. That's fine when you're getting started. It becomes a real problem once you're busy and still not making the money the workload should justify. Here's a framework that fixes that.
The three pricing models, and why one wins
Hourly. You charge for your time, tracked and billed. Simple to explain, easy for clients to understand, and it caps your income at your available hours. The better you get and the faster you work, the less you earn per project, which is a strange incentive to build a business around.
Fixed project fee. You quote a flat number for defined scope, regardless of how many hours it actually takes. This rewards efficiency: get faster at your craft and your effective hourly rate goes up, because the client is paying for the outcome, not the hours.
Value-based. A variant of fixed pricing where the number is explicitly tied to the business outcome the client is getting, not to your estimated hours at all. A five-page site for a business that will generate meaningful new revenue is priced closer to the value of that revenue than to the hours it took to build.
Fixed and value-based pricing both beat hourly for anyone trying to grow past a certain income ceiling. The rest of this guide assumes you're moving toward one of those two.
Step 1: Define scope before you price anything
Vague scope is the single biggest reason projects go over budget and clients get frustrated. Before quoting, get specific about:
- Number of pages and what's on each one
- Custom functionality, booking, e-commerce, membership logins, integrations
- Who's providing content, copy, photos, versus who's creating it
- Number of revision rounds included
- What's explicitly excluded, ongoing maintenance, additional pages beyond the agreed scope, content beyond the agreed word count
A one-page scope document that both sides sign off on prevents the single most common source of scope creep: assumptions.
Step 2: Price by project type, then adjust for complexity
Start from a baseline for the type of project, then adjust up or down based on the specifics.
| Project type | Baseline range | Adjust up for |
|---|---|---|
| Simple brochure site | $800 to $2,500 | Custom design, more pages, tighter deadline |
| Business site with booking | $2,000 to $4,500 | Complex scheduling logic, multiple staff calendars |
| E-commerce | $4,000 to $12,000 or more | Large product catalog, custom checkout flow, inventory sync |
| Ongoing retainer | $150 to $600 per month | Higher change volume, faster response time expectations |
These are directional starting points based on typical freelancer and small agency rates in 2026, not a rate card to copy exactly. Your market, your portfolio, and your niche all shift these numbers.
Step 3: Build in a buffer, always
Every project takes longer than the initial estimate. Client feedback cycles slip, content arrives late, one small change turns into a redesign of a section. A buffer of roughly fifteen to twenty percent on your time estimate, built quietly into the quoted price rather than announced separately, protects your margin without making the client feel nickel-and-dimed.
Step 4: Cap revisions explicitly
Unlimited revisions is one of the most common and most damaging phrases in web design proposals. It sounds generous and turns into unpaid, unbounded work. Cap it explicitly: two or three structured revision rounds, clearly defined as feedback on the current draft rather than new requests. Anything beyond that is billed as additional work, at your hourly rate or a flat per-round fee.
Step 5: Always propose a retainer alongside the project
A single-project proposal gets a single-project decision: yes or no on this one thing. A project-plus-retainer proposal reframes the conversation around total ongoing value, and the retainer is often the easier part of that conversation to say yes to, because it's a smaller monthly number attached to peace of mind, things get fixed quickly, updates happen without a new invoice each time.
Retainers also solve the feast-or-famine problem that plagues freelance income. A handful of clients on a modest monthly retainer adds up to real predictable recurring revenue before a single new project closes.
Step 6: Use the good-better-best structure
Presenting three tiers, rather than a single number, changes how a prospect evaluates the decision. Instead of deciding yes or no on one price, they're choosing among options, and the middle tier, your actual target price, tends to look reasonable by comparison to the higher option, while the lower tier filters out clients who were never going to be a good fit anyway.
Step 7: Raise your rates on a schedule, not out of desperation
Waiting until you feel overworked and underpaid to raise prices means you're negotiating from a position of frustration, which rarely goes well. Instead:
- For new clients, test a higher minimum on your next set of proposals. If your close rate holds steady, that's your new floor.
- For existing retainer clients, build in an annual increase, communicated a couple of months ahead with a clear percentage and date.
Most clients accept a reasonable, well-communicated increase. The ones who churn over a modest, well-flagged increase were often the clients causing the most friction anyway.
What to do when a prospect pushes back on price
Price objections are rarely actually about the number. More often they signal that the prospect doesn't yet see the connection between the price and a specific outcome. Instead of discounting immediately, it's usually more productive to ask what specifically feels high, then address that directly: if they're comparing you to a much cheaper DIY option, walk through what that option doesn't include, ongoing support, custom design judgment, integration work. If they genuinely can't afford the full scope, offering a smaller, well-defined phase one (a homepage and two key pages now, the rest later) preserves your pricing integrity better than discounting the full scope to win the deal.
A note on lead quality and pricing power
Pricing power depends heavily on how good your leads are. A prospect with genuine, obvious need, strong reviews, no website at all, or a visibly broken one, is far less price-sensitive than a business shopping around because they're bored of their current site. If you're sourcing leads with a tool like LeadX that flags no-website, well-reviewed businesses specifically, you're already talking to prospects where the return on investment case is obvious, which supports pricing at the higher end of your range rather than discounting to compete.
Frequently asked questions
Should I charge hourly or a flat project fee?
A flat project fee, or value-based pricing tied to the outcome, almost always beats hourly for anyone trying to grow revenue past a certain point, because it rewards getting faster and better at your craft instead of penalizing it.
How many revision rounds should be included in a web design project?
Two or three structured rounds is standard. Offering unlimited revisions sounds generous but frequently turns into unpaid, unbounded work that erodes your margin on every project.
Should every project proposal include a retainer option?
Yes, it's worth including on nearly every proposal. A project-plus-retainer proposal reframes the decision around ongoing value, and retainer revenue is what turns unpredictable freelance income into something closer to stable.
How much should I raise my rates each year?
There's no universal number, but many freelancers test increases in the ten to twenty percent range for new clients and communicate smaller, scheduled increases to existing retainer clients well in advance rather than raising rates reactively.