Why fixed-scope pricing is 10x better.

What "fixed scope" actually means here.

When we quote a fixed price we are quoting against a specific deliverable list: a handbook, a pentest report, a positioning brief, a SaaS starter. The price holds for the list as specified. If the list changes, the price changes.

This is the model that has been standard in creative agencies for decades. The twist is that we apply it to work that consulting firms have historically billed hourly, because they were buying unpredictability into the middle of their engagements and passing it along.

In Claude-accelerated delivery the unpredictability shrinks. A week of research becomes a day. A report draft becomes a two-hour edit pass. The underlying cost structure that made hourly billing the default has changed. Fixed scope now matches how the work actually behaves.

The hourly-billing conflict, briefly.

We have a separate essay on this, but the core idea is short: when you bill by the hour, you are paid more for being slower and for creating more work.

Under Claude, the team that uses tooling well can finish a traditional hourly engagement in a third of the time. Under hourly billing, that efficiency reduces revenue. Under fixed scope, it increases margin. The incentive flips.

This is not an argument about ethics. It is an argument about which pricing model does not punish good operating discipline. Hourly billing, under Claude, penalizes it. Fixed scope rewards it.

The four things it changes.

Fixed scope is 10x better because it changes four distinct operating variables at once.

Change 1: the engagement ends. Hourly retainers drift. Someone is always billing something. Under fixed scope, delivery is the event that closes the engagement. The team ships, gets paid, and moves on. The client gets their deliverable. Nobody is optimized for keeping a meter running.

Change 2: scope conversations happen up front. Under hourly, scope creep is priced in. Under fixed, scope is the thing the contract is about. The pre-sales conversation is longer, more detailed, more honest about what is in and what is out. That conversation, by itself, prevents roughly half of the project failures we used to see.

Change 3: the operator thinks about leverage. A fixed-price engagement that takes twice as long as planned costs the operator. This creates a direct incentive to use Claude, use templates, use the right tool, and stop doing things by hand. Under hourly, the same behavior reduces revenue. Fixed scope turns operational improvement into direct margin.

Change 4: the client sleeps at night. Clients buying hourly are signing up for a meter they cannot predict. Clients buying fixed scope know the total cost before they start. The CFO objection shrinks. The legal objection shrinks. The budgeting fight shrinks. The sales cycle gets shorter.

How we scope without underpricing.

The fear operators have about fixed scope is that you underprice a hard engagement and eat the cost. We have done this. We now have a few practices that make it rare.

Practice 1: a discovery week. For anything above $25k, the first week is a scoped, paid discovery phase with its own deliverable. We learn the system, write a scope of work, and quote the full engagement at the end. If the client doesn't like the quote they have a scope-of-work document to shop elsewhere. We have not lost the full engagement yet after discovery; the quote is informed enough that it is usually accepted.

Practice 2: reference classes. We keep a list of the last 20 engagements with their hours spent, their quoted price, their scope, and their outcomes. When we quote a new engagement, we pick the three most similar and use them as a reference class for estimation. This beats estimating from scratch.

Practice 3: a standing buffer. Quotes include a 20 percent buffer for the unexpected. It is not a line item on the invoice. It is embedded in the fixed price. If the engagement runs smooth, the buffer is margin. If it runs hot, the buffer absorbs it. Over a year this averages out to healthy margin.

Practice 4: firm change-request terms. See next section. The point here is that "fixed" is only fixed against the agreed scope. Anything beyond that is repriced.

Handling change requests.

Fixed scope breaks down when the client adds work without adding payment. The terms have to be clear and enforced from the first week.

Our template has three clauses that do the heavy lifting.

Clause 1: a change-request form. Any ask that expands scope goes through a one-page form: what is being added, what effect it has on timeline, what the new price is. The form is filed, signed, and the scope gets updated. Informal Slack requests do not expand scope. This feels bureaucratic for about two weeks; after that the client adapts.

Clause 2: a budget for minor adjustments. Every engagement has a stated allowance for small iterations. For a handbook engagement it might be 8 hours of revision. For a SaaS build it might be 20 hours of design tweaks. Inside that allowance, the client asks and we do. Beyond it, we file a change request. This prevents the constant back-and-forth on tiny asks.

Clause 3: a "done" definition. Every scope includes explicit "done when" criteria. Handoff is the event the contract is written around. Without an explicit done-when, engagements drift. With one, drift ends.

These three clauses together are what makes fixed scope survive contact with real clients. Without them, fixed scope becomes open-ended work at a capped price, which is the worst of both worlds.

When fixed scope fails.

Fixed scope is the right default for 80 percent of the work we do. It is the wrong default for about 20 percent. Knowing which is which matters.

It fails when the problem is genuinely unknown. Research engagements, exploratory threat modeling on novel systems, early-stage discovery for a product that has not been specified. The team cannot quote what they cannot bound. In these cases we use a time-and-materials frame with a weekly cap and a clear reset point.

It fails when the client wants to pay for thinking, not output. Advisory retainers are a different product. The client is paying for brain availability, not for a deliverable. A monthly advisory retainer is closer to a board seat than to a project.

It fails when the scope is a moving target by design. SEO and content retainers, for example, are a steady monthly output against evolving goals. We price these as a monthly retainer with a specific minimum output per month, not as a fixed-scope sprint.

For the 80 percent where it fits, fixed scope is the pricing model we will default to until we see evidence that something else works better. So far, three years in, we have not.