The case for boring pricing

Hourly billing for web design creates a weird incentive: the slower I work, the more I make. Nobody behaves badly on purpose, but incentives leak. So I do fixed price web design instead, a number, in writing, with the scope written down next to it. This is the case for why that's better, not just tidier.

The problem with hourly billing

It isn't that hourly designers are dishonest. Most aren't. It's that the meter rewards the wrong things. Efficiency costs you money. Experience, the reason a senior designer solves in two hours what takes a beginner ten, shows up on your invoice as a smaller bill, which is backwards. And you can't budget. You sign up for "we'll see," and "we'll see" is a terrible line item for a small business trying to plan a year.

The deeper issue is that hourly puts you and me on opposite sides of every minute. I want the project to take longer; you want it to take less. That's a bad way to start a relationship that depends on trust.

Why fixed price web design is better

So I quote fixed. You get a number, in writing, with the scope written down next to it. If I estimate badly, that's my problem to absorb, not yours to discover on an invoice. That single move flips the incentives: now I'm rewarded for working well, because the faster and cleaner I work, the better the deal is for me too. We're finally on the same side.

It also forces a better conversation up front. To quote fixed, I have to actually understand what you need, which means we figure out the hard questions before the work starts, not three weeks in when the budget's already half gone.

What's in the written scope

"Fixed price" is only as good as the scope it's pinned to, so the scope is written down in plain language:

• Every page, listed.
• Every feature and integration, named.
• The number of revision rounds, so "can we try the header in the other font?" is already paid for.
• Who provides what, you bring copy and photos, or we scope help for those too, but it's decided, not assumed.
• The timeline, with milestones tied to payments.

Written scope is also what protects both of us from scope creep. If you want something that isn't on the list, that's completely fine, it's just a small, separate conversation with its own number, instead of a silent argument that ends in a tense invoice.

What this means for you

You can budget. Your bookkeeping is clean, one number, maybe split across milestones, no monthly mystery. There's no anxiety about asking questions or requesting the revisions you're entitled to, because they're already in the price. And you never get the email that starts "so, we went a bit over." Predictability is boring. Boring is exactly what you want from the people you pay.

a quote should be a promise, not an opening bid ✿

When hourly actually makes sense

I'm not religious about it. There's one situation where hourly is the honest choice: open-ended ongoing work where neither of us can define the scope, because there isn't one. A monthly block of "whatever the site needs this month", small tweaks, a new section, a quick fix, is genuinely hard to fix-price, and pretending otherwise would just mean padding the number to cover my uncertainty. For that I bill time, transparently, with a cap we agree on. But for a defined project with a defined outcome, a new site, a redesign, a store, there's no excuse for hourly. The scope exists, so the price should too.

A few questions I get

What if the project changes halfway through? Then we write a quick change order, a small, named scope with its own fixed number, and you decide. The original price holds for the original scope. Nothing changes silently.

Isn't fixed price riskier for you? A little, and that's the point. I'm taking the estimation risk instead of handing it to you. That's only fair, because I'm the one who can actually estimate the work.

Does fixed price mean rigid? No. It means decided. Revisions are built in, and real changes are welcome, they just get priced honestly instead of absorbed into a meter you can't see.