How we price a project without hourly billing

Hourly billing has a structural problem that's easy to overlook: it pays the agency more for working slowly and pays the client less for a fast, efficient team. That's a genuine misalignment of incentives, even between two parties acting in good faith, and it's a big part of why we default to fixed-scope pricing on nearly every engagement instead.

This isn't a criticism of any particular agency or client relying on hourly billing today, it's a structural observation about the model itself. Even a genuinely honest team billing hourly is working inside an incentive structure that quietly rewards the wrong thing, and it's worth naming that plainly rather than pretending hourly billing is a neutral, purely administrative choice.

A detailed scope document, reviewed and agreed before a number is quoted, lets us price based on the value and complexity of the defined deliverable rather than an estimate of hours that then has to be tracked, justified, and occasionally disputed. It removes the awkward dynamic of a client scrutinizing a timesheet, and removes our incentive to work less efficiently than we're capable of.

Building that scope document well is genuinely the harder, more valuable half of the pricing process, and it's where we spend the most deliberation before any number gets attached to a project. A vague scope document produces a vague, poorly calibrated price regardless of the pricing model layered on top of it, so the actual discipline lives upstream of the pricing conversation, not within it.

Under fixed-scope pricing, if our team finds a faster way to deliver the same scope, that efficiency is ours to keep, which is exactly the incentive you want a vendor to have. Under hourly billing, the same efficiency gain reduces the invoice, which quietly discourages the vendor from ever getting faster.

We've watched this incentive shift genuinely change how our own team approaches process improvement. A reusable component library or a better internal workflow pays for itself directly under fixed-scope pricing, since the time saved becomes margin rather than lost revenue, which gives the team a real, ongoing reason to keep investing in getting faster rather than treating efficiency gains as something to quietly avoid.

Genuinely open-ended work, ongoing retainer-style support where the exact monthly scope varies, is priced as a capacity commitment (a defined number of hours or a defined set of recurring deliverables available per month) rather than pure hourly billing, which keeps most of the same incentive alignment while accommodating work that doesn't fit neatly into a fixed, one-time scope document.

The distinction that matters here is between billing for hours worked and billing for capacity reserved. A capacity commitment still gives a client a predictable number to budget against, and it still doesn't reward us for working slowly, since the price is fixed regardless of how efficiently that capacity gets used within a given month.

Most clients have experienced the frustrating side of hourly billing firsthand at some point, an invoice that felt padded, a vendor who seemed to take longer than necessary once time became the billing unit, and explaining the structural reason behind that experience tends to land immediately, without much persuasion required. It's one of the easier pricing conversations we have, precisely because the client already has a real, specific memory of the problem it's solving.

The one pushback we do occasionally get is from a client who assumes fixed-scope pricing must be padded to protect us against the risk of underestimating the work. We answer that directly with our own estimation track record, showing how often projects land within the quoted scope, since a defensible history is far more convincing on this point than any explanation of the pricing philosophy alone.

We still track internal time carefully on every project, even though the client is never billed by the hour, because that data is what lets us price the next similar project accurately. Time tracking under fixed-scope pricing serves a completely different purpose than it does under hourly billing: it's an internal calibration tool, not a client-facing justification for an invoice.

This distinction turns out to matter a lot for team morale as well. Engineers and designers report feeling less scrutinized and more trusted under a model where their internal time tracking never becomes a line item a client can question, even though the underlying discipline of tracking time accurately hasn't gone away at all.

Every completed project's actual time against its original estimate gets logged into an internal reference we consult before quoting anything similar in the future, which is what makes our fixed-scope quotes get more accurate over time rather than staying anchored to a single founder's early gut-feel estimates. A pricing model built on genuinely improving internal data beats one built on static assumptions that never get corrected against reality.

Fixed-scope pricing does mean a client can't casually ask for small additions along the way without a conversation about scope, the way an hourly arrangement sometimes allows informally. We treat that as a genuine tradeoff worth naming rather than a hidden cost, since a client who understands it upfront handles a mid-project scope request calmly, through the change process built for exactly that purpose, rather than being caught off guard by it later.

We keep that change process itself deliberately lightweight, a short written note describing the addition and its price impact, agreed over email in a day or two, rather than a heavy formal amendment process. A tradeoff worth naming honestly is still worth making painless in practice, and a fast, low-friction change process is what keeps fixed-scope pricing from feeling rigid even when a genuinely new request comes up mid-project.