What a fixed-price contract protects you from (and what it doesn't)

We quote almost every project at a fixed price, and clients sometimes assume that means the number can never change under any circumstances. That's not quite right, and understanding the actual boundary of what a fixed price covers is worth five minutes before signing anything, with us or with anyone else.

A fixed price protects you from paying more because a task took longer than an agency estimated, from hourly billing surprises, and from an incentive structure where the agency benefits financially from a project running long. If our team underestimates how long a feature takes to build correctly within the agreed scope, that's our cost to absorb, not yours. That's the entire point of pricing it fixed in the first place.

It doesn't protect you from scope changes you request after signing. If the original scope was five page templates and you decide midway through that you actually need eight, that's new work outside the fixed price, and any honest fixed-price agreement will say so explicitly rather than absorbing it silently (which usually just means quality erodes elsewhere to compensate).

A fixed price is only as protective as the scope document underneath it is specific. "Website redesign" as the entire scope description leaves enormous room for disagreement about what's included. "Five page templates, three rounds of revisions per template, one round of copy editing, delivered as a responsive Next.js site with CMS integration" leaves much less. Read the scope section more carefully than the price.

Some early-stage projects, especially MVPs, genuinely can't be fully scoped before any work starts, because the client themselves doesn't yet know exactly what they need. For those, we quote a fixed price for a discovery and scoping phase first, delivering a specific, detailed scope document at the end of it, which then gets its own fixed price for the build phase, rather than trying to fix-price an undefined project from day one.

Ask directly: what specifically happens if I ask for something outside this scope partway through? A good answer names a process (a written change order, a quoted add-on) rather than a vague reassurance. If an agency can't answer that question clearly before you've signed anything, it's a reasonable bet they haven't thought it through, and you'll be the one finding out the hard way.

Some clients worry that agreeing to a change order at any point undermines the whole point of fixed pricing. It doesn't. Fixed pricing protects the original scope's price, not the idea that a project can never evolve. A healthy fixed-price relationship handles legitimate scope changes as clearly quoted add-ons, agreed in writing before work starts on them, which preserves the original protection while still allowing the project to adapt to things nobody could have predicted at signing.

What actually erodes trust isn't a change order itself, it's a change order that appears retroactively, after work has already been done, framed as something that should have been included all along. We quote every addition before starting it, specifically so there's never a surprise invoice for work the client didn't explicitly approve in advance.

Even with a well-scoped fixed-price agreement, we tell clients to keep roughly ten to fifteen percent of the project budget unallocated as a personal contingency, not because we expect to need it, but because most real projects surface at least one genuinely worthwhile idea partway through that wasn't part of the original scope and is worth paying for as an addition. Having that room already budgeted means a good idea doesn't get rejected purely because there's no slack left to fund it.

Occasionally a fixed-price project genuinely does turn out to be underestimated on the agency's side, not because of scope changes but because a specific technical challenge was harder than anyone anticipated at quoting time. A well-run agency absorbs this cost rather than renegotiating mid-project, since that's precisely the risk a fixed price is meant to transfer away from the client. We've had projects where a particular integration took nearly twice our original estimate, and we didn't go back to the client asking for more money, because that risk was already priced into how we quote in the first place.

This is also why a fixed-price agency's quotes tend to include some built-in margin for the unexpected, rather than being priced at the absolute minimum estimated hours. A client comparing two fixed-price quotes, one meaningfully cheaper than the other for seemingly the same scope, should ask how the cheaper agency plans to absorb an underestimate, since the honest answer is sometimes that they don't, and quality quietly erodes instead.

Some agencies offer both models and let clients choose. Hourly billing can work well for genuinely open-ended, exploratory work where scoping in advance isn't realistic, but it shifts the estimation risk entirely onto the client, who pays for however long the work actually takes regardless of the original estimate. Fixed pricing works better once scope is knowable, which is most client website and app projects, but poorly for genuinely unscoped, exploratory engineering work.

If an agency offers only hourly billing for a project that's clearly scopeable in advance, that's worth a direct question about why, since it may simply mean they haven't built the internal process needed to price fixed-scope work confidently, which is itself useful information about how mature their delivery process actually is.

On a recent retail client's site rebuild, the original fixed-price scope covered a standard product catalog and checkout flow. Partway through, the client's warehouse team asked for a bulk order form for wholesale buyers, a feature nobody had raised during scoping because the wholesale side of the business hadn't fully launched yet when the contract was signed. We quoted the addition as a separate, clearly priced change order, the client approved it in writing, and it was built and delivered within the original project's overall timeline with no disruption to the rest of the build.

Nobody was upset about the additional cost, because it was explained, quoted, and approved before the work started rather than appearing on a final invoice as a surprise. That's the entire mechanism a good fixed-price relationship depends on, and it's a genuinely simple one once both sides agree to actually follow it consistently.