A fixed-price quote is a promise about scope, not a promise about the number of hours you will spend. A project can meet its revenue target and still fall below your sustainable hourly rate. Here is a small planning model for developers who want to catch that problem before signing.

Separate revenue from time

Start with the gross contract amount, the actual service fee, direct project expenses and the total time budget. Include meetings, code review, deployment, revisions and handover, not just development.

Suppose a small integration is quoted at $840 with an illustrative 12% service fee and $35 in direct expenses. The amount remaining after the modeled fee is $739.20. Subtracting those expenses leaves $704.20 before taxes and payout charges.

Activity Planned hours
Discovery 3
Implementation 14
Tests and review 5
Deployment 2
Communication and handover 4
Total 28

The effective hourly rate is $704.20 / 28 = $25.15. If your minimum sustainable rate is $30, the quote already fails your own threshold, even if nothing goes wrong.

Calculate the maximum time you can afford

Instead of asking how long a project might take, also ask how long it can take before the economics break.

Maximum hours = (gross × (1 − fee) − direct expenses) / target hourly rate.

The example gives 23.47 hours at a $30 target. Your estimate is 28 hours, so you need to adjust price, scope or both. This is a planning constraint, not a reason to rush testing.

Price uncertainty explicitly

Try three scenarios: 24, 28 and 36 hours. At the same net amount, the effective rates are about $29.34, $25.15 and $19.56. Notice that the unfavorable case can be materially worse even though the invoice never changes.

A practical response is to spell out the assumptions: one integration endpoint, one deployment environment, two feedback rounds, and client-provided access by a specified date. Additional endpoints or environments require a separately approved change.

A small reproducible model

from decimal import Decimal as D gross = D("840") fee = D("0.12") expenses = D("35") target = D("30") available = gross * (1 - fee) - expenses for hours in (24, 28, 36): print(hours, round(available / hours, 2)) print("Maximum hours:", round(available / target, 2)) 

This deliberately simple model assumes a proportional fee. Flat charges, minimum fees, fee rounding and currency conversion can require different treatment. Use the terms of the actual contract, and reserve separately for applicable tax.

Turn the calculation into a delivery checkpoint

At the end of discovery, compare actual hours with the plan. If access problems consume four extra hours, do not silently assume the remaining work will compensate. Re-estimate the work left and identify what the agreed scope permits. If requirements changed, document the change and agree the revised deliverable before implementing it.

After delivery, record planned and actual hours by activity. Three completed projects can reveal whether meetings, deployments or revisions are consistently underpriced. Use that evidence to refine the next quote.

A worksheet for the next quote

Write down the fee percentage, expected expenses, target rate, planned hours, pessimistic hours and explicit exclusions. Run both the expected and pessimistic scenario before submitting your proposal. For the platform-fee portion, our Freelance Fee Calculator compares modeled deductions using the contract amount. It does not include tax, payout costs or all contract exceptions; add those separately.

A good fixed-price quote is one that can survive an ordinary amount of uncertainty without forcing you to compromise the work.