Why we quote fixed fees

Ask an agency for a price and you’ll usually get a rate instead — $150 an hour, $185 an hour, some hours, who can say how many. Ask us and you get a number. A whole one, in writing, that doesn’t move. People assume this is a marketing preference. It’s actually a philosophical position about who should carry risk, and it changes everything about how a project runs.

What hourly billing actually sells

Strip the convention away and look at the deal. Hourly billing sells you effort, not outcomes. The meter starts, and every risk in the project — unclear scope, wrong estimates, rabbit holes, the developer’s learning curve on a tool they’ve never used — lands on your invoice. The provider is structurally fine either way; you’re the only person at the table with money at stake on efficiency.

Worse are the incentives nobody acts on consciously but everybody marinates in. Under hourly billing, slow work earns more than fast work. Experience gets punished: the developer who solves your problem in two hours because they’ve solved it fifty times bills a quarter of the one Googling as they go. And every mid-project conversation carries a small conflict of interest — is this suggestion good for the project, or good for the invoice? Honest people resist the pull. The pull is still there, every day, on every decision.

What a fixed fee forces — on us

A fixed quote moves the estimation risk to our side of the table, which means we can’t afford to be sloppy about scope. So we aren’t. Before a number leaves this building, we’ve done the unglamorous discovery work — what exists today, what “done” means, where the bodies are likely buried. The quote is the output of that work, not a guess dressed up in confidence.

That discipline is the hidden gift of fixed fees: the scoping conversation happens before the money conversation ends, instead of erupting in month two as a change-order fight. The number includes a buffer for the surprises experience says to expect — and when we estimate wrong anyway, we eat it. That’s not generosity; it’s the deal. We priced the risk, we own the risk. You’d be amazed how accurate estimates get when the estimator pays for the misses.

“But what about scope creep?”

The standard objection, and it has a clean answer: a fixed fee covers a fixed scope, written down in plain English. Want something genuinely new mid-project? Great — it gets its own plain number, and you decide with full information. Compare that to hourly, where scope creeps silently because nothing forces anyone to notice it creeping — the invoice just gets taller. Fixed fees don’t prevent change; they make change visible and chosen instead of ambient and billed.

Where each model honestly belongs

• Defined builds and fixes — a site, a platform, a rescue with a known endpoint: fixed fee, every time. The outcome is specifiable, so the price should be too.
• Ongoing operation — care, monitoring, steady improvement: flat monthly, which is the fixed-fee philosophy applied to time. (We’ve written about why flat-rate beats hourly for care work specifically — the incentive math is even starker there.)
• Genuine exploration — “we don’t know what we need yet”: that’s consulting, scoped as a short fixed-fee discovery engagement whose deliverable is the plan. Even our hourly-shaped work gets a fixed wrapper.

Notice there’s no row where open-ended hourly wins for the client. There’s a reason the model persists anyway: it’s easier for providers. No estimation risk, no scoping discipline required, revenue scales with inefficiency. Persistent and convenient-for-the-seller is not the same as good.

“Don’t you just pad the quote, then?”

The sharp version of the objection deserves an answer: if we carry the risk, isn’t the buffer just hidden hourly billing? Two honest responses. First — the buffer is priced against scoped, named risks, not vibes, and fifteen years of estimating the same kinds of projects makes it small; experience is precisely the ability to price uncertainty tightly. Second — competition disciplines it. A padded fixed quote loses to an accurate fixed quote, so the market punishes lazy estimating in a way it never punishes a meter that simply runs longer.

And when reality beats the buffer anyway — it happens a few times a year — we finish the job at the quoted price and update our model. That feedback loop is the entire reason fixed-fee shops get more accurate over time while hourly shops never have to. The system isn’t pad-proof because we’re saints; it’s pad-resistant because the incentives finally point the right way.

What this buys you in practice

Budget certainty, obviously — the number you approve is the number you pay, which your cash flow planning will appreciate. But the quieter benefit is alignment: once the price is fixed, every incentive we have points at finishing well and efficiently. Faster is better for us and you. Experience is rewarded. Suggestions carry no meter behind them. The entire project runs without the low-grade adversarial hum that hourly arrangements normalize so thoroughly that most people stop noticing it.

It’s also why we publish our starting prices instead of hiding them behind a sales call, and why the qualifier on our start page gives you an honest starting range before anyone’s “circled back” to anything. Guessing games help nobody. If you’ve got a project and you’d like a whole number with your name on it, tell us what you’re building — the quote is free, and it stays put.