You’ve asked a few agencies to quote on your new website, and the proposals don’t line up. One gives a single number for the whole project. Another lists an hourly rate and an estimate of how many hours the work should take. On paper the second one may even look cheaper.
The two can’t be compared side by side, because they promise different things. A fixed price tells you what you’ll pay. An hourly estimate tells you what you might pay if the project goes as expected, and website projects rarely stand still.
We’ve quoted fixed prices for over 15 years, so we have a view. But both models have a place, and the useful question is less about which is better in general and more about what each one asks you to take on.
How the two models work
There are two basic ways to price a website project, plus a middle ground:
| Fixed price | Hourly | Estimate with a range | |
|---|---|---|---|
| How it’s priced | One price for the agreed scope | A rate for every hour worked | Hourly underneath, with a stated tolerance such as 20% either way |
| What the quoted number means | What you pay for the agreed work | An estimate, not a commitment | An estimate with a limit on how far it should move |
| Who carries overruns | The agency | You | You, up to the stated limit |
| Scope changes | Quoted separately | Added to your invoice | Estimated separately |
| Where it fits | A full website project, or anything half a day or more | Small, well-understood work such as edits and content updates | Work where the requirements are still loose |
Neither model changes how much work a website takes. What changes is who carries the cost when the work turns out bigger than anyone expected.
Who carries the risk of the unknown
Every website project has unknowns. Content arrives later than planned, a stakeholder joins halfway through with new opinions, or a feature turns out to be fiddlier than it looked.
With a fixed price, the agency carries that risk. An experienced team builds a contingency into the price, based on what has tripped up similar projects before. If the work runs over, that’s the agency’s problem.
With hourly billing, you carry it. Every extra round of revisions and every unplanned task lands on your invoice.
There’s a second issue, and it’s about incentives.
Jonathan Stark, a consultant who has written about pricing for years, makes the case in The Moral Dilemma of Hourly Billing that billing by the hour quietly rewards working slowly. An agency that has spent a decade making its process faster earns less per project for delivering sooner, which is exactly backwards from what a client would want. We’ve followed his thinking for a long time, and it shaped how we price.

Why we stopped billing by the hour
In our early years, we often sent quotes broken down by hours and rates. It felt fair at the time, because the client only paid for the effort that went in.
Then a string of projects showed us the flaw. Some clients asked for round after round of design revisions, with one even requesting more than 30 rounds of revisions. Others expected help with website-adjacent tasks that were never in the scope. Every one of those hours was billable, and the client wasn’t adding them up as they went.
The trouble arrived with the final invoice. Many clients were surprised by the total, and a project that had gone well turned sour for both sides. Instead of celebrating a new site, everyone was talking about money.
A few years in, we dropped hourly pricing for projects altogether. We didn’t want to watch the clock, and by then we understood what usually trips a project up well enough to quote a contingency for it.
What a fixed price depends on
A fixed price is only as good as the scope behind it. Before we can put a number on a project, we need to know what’s being built, which is a big part of why the discovery call comes first. If you’re sending out a brief, naming your budget helps every agency scope to it.
The other half is the assumptions and exclusions section, which spells out what the price does not cover. In our experience, three items catch clients out more than any others:
- Blog pages. Because so many sites have a blog, clients often assume one is included. We don’t include it by default, especially in our base-level option, because a blog nobody updates for a year leaves what we call digital cobwebs. Whether you need a blog is worth deciding on purpose.
- Copywriting. Once in a while, a client expects us to write every page. We list copywriting and copyediting as optional add-ons in the proposal, so if the question comes up mid-project, we can point back to it and quote the price that was already offered.
- Stock photography. This one comes up most. We can’t know how many images a site needs until the design and copy are final, and we can’t know what they’ll cost. Most images from iStock run $10 to $20 in our experience, but some clients want to swap a few for far more expensive video footage, and others supply their own photography and need none.
Often Assumed, Rarely Included
The most extreme example we’ve seen came from a corporate insurance client. They wanted Getty Images photos of their actual office building in Bermuda’s financial district. Given the remote location and the premium licence, each photo cost about $1,300 USD. They ended up using three of them.
Had stock photos been included in the fixed price, that purchase alone would have turned the project into a loss. (At those prices, sending our own photographer to Bermuda started to look like an option, free vacation included.)
When the scope changes partway through
A fixed price doesn’t mean the scope can never change. About a third of our projects see a change of some kind, and it’s rarely because anyone got the original scope wrong. It usually comes out of working together. A client mentions something about their business in a weekly check-in that they’d love the site to handle, or we spot an obvious win and recommend it.
Here’s how we handle it:
How a Change Request Works
- 1The idea comes up. A new need surfaces in a check-in, or we spot an opportunity and recommend it.
- 2Size it. A small tweak is often absorbed into the existing price.
- 3Quote it. Anything bigger gets its own fixed-price quote, usually within 24 to 48 hours.
- 4Decide promptly. A quick yes or no keeps development moving and the launch date intact.
Small changes often get absorbed. If a client shifts direction on something that adds an hour to a $20,000 project, it’s not something we’re going to sweat.
Anything more involved gets its own fixed-price quote, usually within 24 to 48 hours. It goes to the person we’re working with day to day and to the project owner. We don’t normally ask for another deposit, unless the extra work is being delivered in conjunction with one of our third-party partners.
The one thing we do push for is a prompt answer. Development can’t sit idle for 2 weeks while an enhancement waits for a decision.

Where hourly still makes sense
We haven’t given up hourly billing entirely. Small edits and content updates for existing clients are billed by the hour, and for good reason.
These are the kinds of jobs that take only an hour or two. They’re hard to quote up front without seeing exactly what the client wants and what state their content is in. Preparing a formal quote and waiting for approval would often take longer than actually doing the work. Established clients also know roughly how long these tasks take, so the invoices rarely surprise anyone.
Our rule of thumb is that anything that appears to be a half day or more of effort requires a fixed-price quote in advance. Occasionally, where the requirements are still loose, that quote carries a note saying it’s an estimate that could move by up to 20% either way.
So the honest answer is that hourly suits small, well-understood work, where the client can see what they’re getting for each hour. It suits a full website project far less well.

Comparing a fixed quote with an hourly one
At the price point we work in, we’d expect most agencies to quote a fixed price too. When a client does mention an hourly quote from someone else, we gently point out that the total is only an estimate, not a guarantee of the final invoice. A lower number can be tempting, but we more often see clients who’ve been burned by an hourly project and now want the predictability of a fixed price.
Whichever kind of quote you’re holding, these questions will tell you more than the headline number:
- What exactly is included? A list of pages and features you can check, not a general description.
- What’s excluded or assumed? Look for blog pages, copywriting, stock photography, and anything you’d be upset to find missing. If you don’t see something, don’t assume it is included – ask the vendor.
- How many design revisions are included? This is where hourly projects most often run over.
- How are changes priced and approved? You want to know before the first one comes up.
- For an hourly quote, what happens if the estimate is exceeded? Ask whether there’s a cap, and how much notice you’ll get before it’s reached.
It also helps when a proposal offers more than a single, take-it-or-leave-it scope. We usually offer three solutions at different budgets, and always aim to include at least one or two options that are definitely within your budget. That way a client whose ideal scope runs over budget can still find an option that fits, even if it means giving up something they wanted, rather than setting the whole proposal aside on price.
If the quotes you’re holding are far apart, our articles on why the cheapest website ends up costing the most and what a B2B website costs in Canada cover the other side of the comparison.
Price the work, not the clock
A fixed price makes the agency do the hard thinking up front, and it lets you plan a budget without watching an invoice grow. Hourly billing has its place, but for a full website project it hands you a risk you don’t need to carry.
If you’re weighing quotes for a new site, or you’d like to see what a fixed-price proposal looks like for your project, book a discovery call. It’s a useful conversation about your site and your budget, with no pitch, and no pressure.



