Why we don't bill by the hour, and what we do instead

Hourly billing sounds inherently fair: pay for exactly the time worked, nothing more. In practice, we've found it creates a subtle misalignment of incentives that fixed-scope pricing avoids, which is why we've never billed by the hour for project work.

Under hourly billing, the agency's revenue goes up the longer a project takes. Even with the best intentions, that's a structural incentive pointed in the opposite direction from the client's interest in a fast, efficient delivery. We'd rather not ask a client to trust that we're ignoring an incentive that exists; we'd rather remove it.

Pricing a project as a fixed number requires us to actually understand the scope deeply enough to commit to it, which produces a more thorough discovery process than hourly billing typically incentivizes. An hourly arrangement can start with a vague scope and sort out the details as billable hours; a fixed quote can't.

If we underestimate how long something takes under a fixed-price agreement, that's our cost to absorb, not the client's. This asymmetry is deliberate: it puts the estimating risk on the party best positioned to actually improve their estimating over time, which is us, not the client paying for the work.

For genuinely open-ended, ongoing work with no fixed deliverable, an evolving retainer relationship where priorities shift monthly, a fixed scope doesn't fit well either, and we're upfront about recommending a retainer structure with a monthly cap instead, rather than forcing every engagement type into the same pricing model.

Some clients coming from an hourly-billing agency relationship are initially skeptical, expecting fixed pricing to mean corners get cut once the number is locked in. We address this directly by walking through our deliverables list and quality standards as part of the same conversation, so the fixed price is understood as a commitment to a specific outcome, not an excuse to do less.

It means our discovery calls take longer and our proposals are more detailed than a rough hourly estimate would require. We think that upfront cost is worth it for the alignment it creates for the rest of the relationship.

Fixed-price engagements require us to track our own delivery time carefully against the original estimate, project by project, since that's the only real way to know whether we're pricing accurately over time. That internal accounting has become one of our more valuable data sets, and it's fed directly back into how we scope and price the next similar project, which an hourly model would give us far less incentive to build in the first place.

We review this data quarterly across every project type we run, and it's flagged real patterns we wouldn't have otherwise noticed, certain categories of feature that consistently take longer than our estimates assumed, certain client industries where discovery reliably surfaces more complexity than expected. Feeding those patterns back into future pricing is a direct, compounding benefit of fixed-price work that an hourly arrangement simply doesn't generate the same pressure to do well.

Fixed pricing doesn't mean the price never changes, it means changes are named and agreed to explicitly rather than accumulating invisibly in an hourly total. When a client's own requirements shift meaningfully mid-project, we treat that as a scope conversation with a clear, itemized cost, not a silent overrun absorbed by either side without discussion.

Clients coming from a previous agency relationship with an hourly model that spiraled past its original estimate are often the most enthusiastic converts to fixed pricing, since they've directly experienced the anxiety of an open-ended invoice with no ceiling. Being able to tell a client the exact final number before work starts, and meaning it, tends to rebuild a level of trust that a burned client arrives without.

Fixed pricing isn't strictly better in every dimension, it's a different set of trade-offs, and we tell clients that directly rather than pretending it's an unambiguous win. A fixed price means we've priced in a reasonable buffer for the unknowns that always turn up in real project work, so a project that happens to go unusually smoothly costs the same as one that hits a normal amount of friction, whereas a perfectly executed hourly project with zero friction could, in theory, come in cheaper.

We think that trade-off favors the client in the vast majority of real projects, since genuinely friction-free projects are rare and the downside protection fixed pricing offers against the more common, messier outcome is worth more than the theoretical upside of an unusually smooth hourly engagement. But we'd rather state that trade-off plainly than let a client assume fixed pricing is simply free money left on the table for us in every case.

Clients who value predictability and a clear final number tend to be the strongest fit for how we price work, while clients who genuinely want maximum flexibility to change direction constantly throughout a project are often better served by a different pricing model entirely, and we say so honestly in a discovery call rather than trying to force every prospective client into the same structure.

That honesty upfront, about who fits and who doesn't, has actually filtered out engagements that would have been a poor match on both sides, and we consider that a genuine benefit of the model rather than a limitation of it, since a mismatched pricing expectation tends to surface as friction later in a project regardless of how the initial sales conversation went.

It's a filter we're comfortable with even when it costs us a deal, since a client who signs on expecting open-ended flexibility from a fixed-scope agreement is a poor fit for either side, no matter how good the initial rapport was.