Fixed price vs. retainer: how to choose per project

The pricing model matters more than the price. Quote a well-defined website build on a retainer and you'll spend the project negotiating hours instead of building. Quote an open-ended ongoing engagement at a fixed price and you'll either underprice your time every month or fight scope creep constantly. Most agencies default to whichever model they're used to rather than the one the project actually calls for — and that mismatch is where margin quietly disappears. Here's how to tell which model fits before you send the proposal.

When fixed price makes sense

Fixed price works when scope is genuinely knowable in advance: a defined set of pages, features, or deliverables with a clear finish line. It gives the client budget certainty, which is often the deciding factor in a competitive pitch, and it rewards you for working efficiently rather than billing more hours. The risk sits entirely on your side of the table — if the estimate was wrong, you absorb it — so fixed price only works when your estimation is genuinely reliable, built from a real breakdown of hours by phase rather than a gut-feel number. Projects with a lot of undefined discovery work baked in, like a new product with unclear requirements, are the wrong candidates for this model.

When retainer makes sense

Retainers fit ongoing, variable work where the deliverable isn't a fixed thing but a fixed amount of capacity — marketing management, ongoing development support, a consultant embedded in a client's process month over month. The client is buying access to your time and expertise, not a specific output, so trying to force a deliverables list onto a retainer usually backfires: either you overpromise output for the retainer amount, or the client feels like they're not getting enough for what they're paying. State clearly what capacity the retainer buys — hours per month, or a defined set of recurring activities — so both sides can tell if the retainer is being fulfilled.

Hybrid models worth considering

Many projects are actually two projects wearing one contract: a fixed-price build phase followed by an ongoing retainer for support and iteration. Pricing them as one blended number usually shortchanges one side of the work. Quoting them separately — a fixed price for the defined build, a retainer starting the month after launch — is clearer for the client to evaluate and protects your margin on both halves. Milestone-based pricing, where a large fixed-price project is broken into priced phases with separate sign-off, is another hybrid worth using when scope is mostly known but likely to shift after the first phase ships.

When a client asks to switch models mid-project

Occasionally a fixed-price client will ask, mid-project, to shift toward hourly billing for extra work, or a retainer client will ask for a fixed quote on a large one-off feature. Both are reasonable requests — but they should be treated as amending the contract, not absorbed silently into the existing terms. Quote the new work under the model that fits it, even if it means running two pricing structures in parallel for a while: hourly for the exploratory piece, fixed for the well-defined one. Resist the temptation to just fold new asks into an existing retainer's hours "since we're already working together" — that's exactly how a fairly priced retainer quietly turns into an underpriced one, three or four small favors at a time.

Signals from the discovery call that predict which model fits

• The client can describe a finish line clearly → fixed price
• The client says "we're not sure yet, we want to figure it out together" → retainer
• The project has a clear build phase and an open-ended maintenance need → hybrid
• The client's budget is fixed but the scope keeps expanding in conversation → milestone-based fixed price, to contain the risk

Getting the model right the first time avoids the awkward mid-project conversation where you try to renegotiate structure, not just price. Dealora's pricing engine recommends fixed, hourly, retainer, milestone, or hybrid based on the scope and discovery answers already captured — so the proposal reflects the model that actually fits, not just the one you reached for out of habit. Getting this one decision right tends to matter more for long-term profitability than any individual rate negotiation, because it determines whether every future scope conversation works in your favor or against it.