Fixed-Fee Pricing Calculator

A fixed-fee price is the single number you commit to before the work starts, calculated so that it covers your delivery cost, a buffer for the things that go wrong, and the margin the firm needs to keep the lights on. The math is three layers: blend the cost of the team you intend to staff, add a contingency for risk, then gross that figure up to your target margin. The calculator above runs those three layers in 60 seconds. This page shows the formula it uses, two worked examples, and where the number quietly lies to you.

It does not guarantee you price the engagement correctly. It gives you a number you can defend.

The formula, in three layers

A defensible fixed-fee price is built in three sequential layers: (1) blended cost, which sums each staffing tier’s hours, rate, and duration; (2) risk-adjusted cost, which adds a contingency percentage for scope creep and bench burn; and (3) the fee, which grosses the risk-adjusted cost up to your target margin using fee = cost ÷ (1 − margin). All three layers must be present. Skipping any one of them produces a number you cannot defend after the engagement closes.

Most online “consulting fee calculators” answer a different question than the one you have. They take a desired annual salary and back into an hourly rate for one person. That is useful if you are a solo consultant. It is useless if you are pricing a four-person delivery team against a defined scope, which is what fixed-fee work actually is.

The calculator here runs the real version:

Layer 1: Blended cost. Hours per week, by tier (senior, mid, junior), times each tier’s billable rate, times the engagement duration in weeks. Sum the three tiers. This is your cost-at-rates: what the engagement costs you to staff before any buffer or margin.

blended cost = Σ (tier hours/week × tier rate × weeks)

Layer 2: Risk-adjusted cost. Apply a contingency percentage to the blended cost. This is where bench burn, realization drag, and scope creep live. A 12% contingency on a $200K blended cost adds $24K. Run clean and you keep it. Lose a senior to another account mid-engagement and you have runway.

risk-adjusted cost = blended cost × (1 + contingency)

Layer 3: Margin gross-up. Gross the risk-adjusted cost up to the fee that delivers your target margin. This is the step most people get wrong, so it gets its own section below.

fee = risk-adjusted cost ÷ (1 − target margin)

The output is a suggested fee, the blended hour count, and the full breakdown: cost at rates, buffered cost, and the margin you hit.

The one place people break the math: margin is not markup

Margin and markup measure profit from different denominators. Markup divides profit by cost; margin divides profit by price. Because price is always larger than cost, the same percentage means less actual profit when you label it “margin.” Adding 40% to cost gives a 29% margin, not 40%. The correct formula is fee = cost ÷ (1 − target margin). On $100K of cost at a 50% target, the shortcut prices the work at $150K; the gross-up prices it at $200K.

Here is the error that shows up most often, and it is expensive. Someone wants a 40% margin, so they take their cost and add 40% to it. That is a 40% markup, and it lands you at a 29% margin, not 40. The two words measure from different denominators. Markup divides profit by cost; margin divides profit by price. Because price is always the bigger number, the same percentage means less profit when you call it margin.

The gross-up formula (fee = cost ÷ (1 − margin)) is the only way to hit the margin you actually meant. The gap compounds with every point:

At a 50% target on $100K of cost, the markup shortcut prices the work at $150K and quietly hands you a third of your intended profit. The gross-up prices it at $200K. On a portfolio of engagements, that is the difference between a healthy practice and one that wonders every quarter where the margin went. The calculator uses the gross-up. Most spreadsheets a partner built in a hurry do not.

Two worked examples

Numbers make this concrete. Both use the calculator’s default rates: senior $300/hr, mid $200/hr, junior $125/hr.

Example A: an 8-week implementation, well-scoped, repeat client.

A known client and a scope the team has delivered before justify the lean 12% buffer. The fee clears cost and margin with a little runway for a bad week.

Example B: same shape, new client, undocumented integration target.

Same team, same hours, same rate card. The only thing that changed is the contingency, because the risk changed. The roughly $14K delta between the two fees is what it costs to price an unknown integration surface honestly. If the client will not pay it, that is a signal the work belongs in a different structure, not a signal to drop the buffer.

How to read the output

The suggested fee is not the proposal number. It is the floor you need to clear to hit your margin target at the specified risk level. Move it on purpose, not by accident:

• Scope uncertainty is high. Raise the contingency, not the rate. A greenfield build with a third-party integration surface deserves 20%+, not 12%.
• Client is rate-sensitive. Shift hours from senior to mid in the mix. The blended cost drops without you touching the rate card or signaling a discount.
• Senior pull-through is a known problem on this account. Enter the senior hours the client will actually get, not what the SOW promises. A senior split across three engagements does not have 40% to give you.
• Realization runs under 85% on this kind of work. The calculator assumes every hour you enter is billable and delivered. The 2025 SPI Professional Services Maturity Benchmark puts average billable utilization across the industry at 68.9% in 2024, well below the 75% threshold considered healthy. Realization risk belongs in the contingency or the hour inputs, not in a surprise after closeout.

When fixed-fee is the wrong structure entirely

Fixed-fee fits when scope is concrete, the team has actuals from comparable work, integrations are documented, and key decisions are made before the SOW is signed. When three or more of those conditions are missing, fixed-fee transfers risk from client to firm with no margin premium for taking it. The right alternative is a short fixed-fee discovery phase to retire the unknowns, followed by a fixed-fee build once the scope is defined. McKinsey research finds that 66% of enterprise software projects still experience cost overruns, and scope ambiguity at the pricing stage is the most common cause.

The calculator will happily price anything you feed it. It has no opinion on whether fixed-fee is the right container for the work. That decision comes first, and it comes down to one question: who should carry the risk of scope moving?

Three or more rows in the right column and you are pricing an unknown as if it were known. That transfers risk from the client to you with no margin premium for taking it. The honest move there is a small fixed-fee discovery phase to retire the unknowns, then a fixed-fee build once the rows flip left. For the deeper version of that argument, see Why Services Businesses Need CPQ.

What the calculator can’t see

The calculator validates none of its three inputs. It accepts whatever hours, rates, and contingency you enter. The three inputs where firms most often lie to themselves are senior availability, risk contingency, and scope realism. Each one can make the fee look correct while the engagement is already set up to underdeliver.

The three inputs above hide most of the risk, and the calculator validates none of them:

• Senior hours. Overcommitting senior availability at the proposal stage is how engagements blow the pyramid. Price in twenty senior hours a week for a person who is realistically pulled across three accounts, and the junior team absorbs the delta in week six.
• Risk contingency. Twelve percent is reasonable for well-scoped repeat work. It is not reasonable for a new client, a new integration target, or any engagement where key technical decisions haven’t been made. Use Phase 0 discovery to retire the unknowns before you set the buffer, not instead of it.
• Scope realism. Enter 40 hours a week where 30 is the historical delivery average and the fee comes out 33% high while your margin looks better than it is. That gap surfaces after the engagement closes, when it is too late to reprice.

A note from Christopher

The common pattern across fixed-fee work is that the math can be exactly right and the engagement still goes sideways. The fee covers the cost. The margin holds on paper. The team does genuinely good work for twelve weeks. Then the engagement underdelivers for a reason a calculator has no field for: sponsor churn, an undisclosed requirement, a client-side dependency that was never in the SOW. The arithmetic was rarely the part that decided the outcome.

That is the thing to internalize before you trust any number this tool gives you. The calculator nails the easiest 60 seconds of fixed-fee pricing. The hard part is the scope, the sponsor relationship, and the assumptions the delivery team hasn’t seen yet, and that is exactly the part Servantium connects to the number. When the quote lives in the same system as the engagement record, the pricing model and the delivery model stop being two disconnected spreadsheets and start answering each other: is the scope real, who is staffed, are they actually available, did the last engagement of this shape land where it was quoted.

What Servantium does that a calculator can’t

This is a starter tool. Inside Servantium, the quote builder runs the same three-layer logic with two additions a static page cannot offer. The margin calculator runs against the firm’s actual resource costs, not self-reported rates. And the AI estimate generator checks your proposed hours against the firm’s own engagement history, so if your last three implementations of this type landed at 110% of quoted hours, the system flags it before the proposal leaves the building.

That link between the quote and the engagement record is where fixed-fee pricing stops being an educated guess and becomes a number you can hold.