ZAMBO.

Direct answer

A fixed price puts the clock risk on you. A changed job puts it back on the table.

You priced the job at a number that felt safe, and the work quietly ate twice the hours. Now there are two bad options on the table: swallow it and resent the client, or send a bigger invoice and dare them to argue. There is a third, and it starts with an honest sort. Some of those extra hours are your underestimate, and a fixed price means exactly what it says about those. Some came from things nobody could see at quote time. And some the client added, in changes, in waiting, in extra rounds, without ever calling them changes. This page walks the sort, shows you how to raise the changed part mid job while agreement is still cheap, and ends with the quoting habits that stop one surprise from doubling the next job.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 13, 2026. First published November 13, 2026. The records quoted below are real and public, read back from the live service on November 13, 2026.

Step 1. Sort the extra hours into three piles before you think about money

Pile one is your underestimate: the work was the work described, it just took longer in your hands than you priced. On a fixed price, that pile is yours. The client bought certainty, and the certainty is what they paid for; billing them for your learning curve breaks the deal you sold. Pile two is hidden conditions: facts about the job that were not visible, not stated, and not reasonably checkable when you quoted, which changed the work itself once opened up. That pile is arguable, in the fair sense: the quote priced the job as described, and the job turned out to be a different job in that named respect. Pile three is client-caused growth: extra revisions beyond the agreed rounds, new requirements, late or changed inputs that forced rework, approvals that arrived as redesigns. That pile was never in the fixed price, because the fixed price covered an agreed scope, not whatever the scope later became. Write the three piles down with hours against each, from your time record or your job history, before any conversation. The sort is the whole strategy: it tells you what to absorb without a word, what to raise as a fair question, and what to invoice as change.

Step 2. Absorb pile one visibly, once, and learn the number it taught you

Absorbing your own underestimate is not weakness; it is the price of the information. You now know what this kind of job actually costs in your hands, which is the single most valuable number in a freelance practice, and most people pay for it exactly this way. Two disciplines make the absorption worth it. First, do not let pile one leak into the conversation as a grievance; a client who hears that the job took you longer than hoped hears a request coming, and every fair claim in piles two and three gets discounted as part of the same complaint. Second, write the real hours into your quoting notes against this job type, with the reason your estimate was half the truth: the stage you forgot, the revision rounds you assumed away, the setup you did not count. An underestimate you record becomes a corrected rate card. An underestimate you only suffer becomes the same surprise on the next similar job.

Step 3. Put piles two and three on the record as changes, priced as their own stages

A change claim lives or dies on whether the change is visible as an event, with a date and a decider, or only as a feeling that the job grew. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the per step, decision-carrying structure a change is priced against:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the structure for what it gives a mid job conversation: steps as separate items, each checkable, and one acceptance decision over them. Your piles two and three want the same shape in miniature. Each hidden condition becomes a named item: what was found, when, what extra work it forces, what it costs, decided before the extra work runs where that is humanly possible. Each client change becomes a stage of its own with its own small price and its own yes. The pending record is the warning case: work that sits checked but undecided, release on hold, is how extra hours pile up unpriced. A change the client has not decided on is work you have not been asked to do yet, and treating it that way, kindly and out loud, is what keeps a fixed price fixed in both directions.

Step 4. Have the conversation in the middle of the job, not on the final invoice

Timing is most of the ethics here. Extra cost raised while the work is still running is a decision the client can actually make: proceed at the new figure, cut scope to hold the old one, or stop at a clean boundary. The same figure first appearing on the final invoice is an ambush, and clients fight ambushes on principle even when the underlying claim is fair. So as soon as piles two and three are real and sized, send the short version: the job as quoted is on track at the agreed price; these two things have changed it, named in one line each; here is what each adds, priced; here is the scope cut that holds the original price if you prefer it. That last door matters. A client offered a genuine choice between paying for growth and trimming back to the number rarely feels billed unfairly, because the fixed price is still standing there, honoured, attached to the job it was quoted for. What you should not do is finish everything and present the difference as a fait accompli; at that point even a reasonable client is only deciding whether to reward a surprise.

Step 5. Quote the next job so one surprise cannot double it

Four habits, all cheap at quote time. First, split discovery from delivery on any job whose insides you cannot see: a small fixed price to open it up and report, then the real fixed price quoted against known facts. Second, name the revision rounds and the input assumptions in the quote itself, so pile three has a written boundary to be measured against. Third, add one change line to every fixed price: work beyond the described scope is priced and agreed in writing before it runs. Fourth, keep a stage boundary in the middle of longer jobs, a point where both sides look at actual progress against the price and can re-agree with most of the work still ahead. None of these make you harder to hire. They make the price mean something specific, which is what a good client is buying with a fixed price in the first place.

What this page cannot settle

This page cannot rewrite a fixed price you already agreed; if the job was the job described and it simply took longer, the honest answer is that the extra time is yours, and no framing changes that. It also cannot tell you what a specific contract's change or variation clause allows in your place; contract wording and local law govern that, and this is general information, not legal advice. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove extra hours were necessary or that a change was worth its price. What the record settles is the factual floor the fair conversation needs: what was agreed, what was delivered step by step, and where the job that ran diverged from the job that was quoted.

Frequently asked questions

I quoted a fixed price but the job took twice as long. Can I charge more?

For the part that was simply your underestimate, no: a fixed price means the time risk on the described job was yours, and the client bought exactly that certainty. For the parts where the job itself changed, yes, priced as changes. Sort the extra hours first. Your underestimate is absorbed, and its lesson goes into your quoting notes. Hidden conditions nobody could see or check at quote time are a fair mid job conversation: name the condition, the extra work it forces, and its price, and let the client choose between paying it and trimming scope to hold the original figure. Client-caused growth, extra rounds, new requirements, rework from changed inputs, was never inside the fixed scope, so price it as its own stage and get the yes before it runs. Whatever you do, raise it mid job, not on the final invoice: the same figure is a decision while work remains and an ambush when none does.

The client changed things as we went but says the price was fixed. Who is right?

Both of you, about different jobs. The price was fixed for the scope described in the quote, and the client is right that nothing inside that scope can be repriced. Changes the client introduced sit outside that scope by definition, and a fixed price has never meant unlimited free revision of the brief. The practical test is the written boundary: the quote's described deliverables, revision rounds, and input assumptions against what was actually asked for as the job ran. Where the record shows an ask beyond the boundary, price it as a change, with the date it was asked and the date it was agreed. Where there is no written boundary, expect to split the pain this once, and treat the missing boundary as the thing to fix in your next quote, because it is doing more damage than any single overrun.

Should I tell the client the job is taking longer than I expected?

Tell them early about changes and hidden conditions, and stay quiet about your own pace. A message that says the job is simply taking longer invites the client to manage your efficiency, which is the one thing a fixed price was supposed to take off the table, for both of you. A message that says a named thing has changed the job, here is the evidence, here is what it adds, here is the scope cut that avoids it, invites a decision, which is the client's real job in the project. The exception is the deadline: if your overrun threatens a date the client is depending on, the date is their business even when the hours are yours, and a short honest note about the date, with the recovery plan, is owed as soon as the risk is real.

How do I price the extra work fairly?

Price it the way the original quote was built, so the method is visibly the same: the same rate, the same rounding, applied to a named block of extra work with a stated boundary. Avoid the two shapes that poison the conversation: a round lump with no working behind it, which reads as a number invented under pressure, and a per hour meter quietly running on a job the client thought was fixed, which reads as the deal changing type mid job. A change priced as a stage, this work, this price, this end point, agreed in writing before it runs, is the shape clients accept, because it preserves the thing they valued in the fixed price: knowing the number before the work happens.

How does running the job on its own record help a fixed price stay fair?

It gives the sort a shared set of facts. When the work runs through Zambo, every step lands on the job record with a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, the client accepts on that record, and the acceptance view shows status, decider, date, and release state, so what was delivered, when the brief changed, and what was agreed at each stage is readable at a link instead of reconstructed from chat. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next fixed price job on one record with the scope boundary written at the start, so if the job grows, the growth is a priced stage on the same record, not a surprise on the final invoice: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related