You quoted a fixed fee, the client agreed, and an advance landed. Now you're three days into the actual work and the real scope is becoming clear, more hours than you estimated, more revisions than you budgeted for, more back-and-forth than the number accounted for. The fee is locked in on paper and partially paid. The question is what to actually do about a project that's already running at a loss.
Here is how to handle a lowballed quote once work has already started, without blowing up the client relationship or quietly eating a loss you didn't need to.
First, confirm it's actually underpriced, not just slower than expected
Calculate your real hourly rate on this project so far: total hours logged divided into the fee, compared honestly against what you need to earn per hour to make this worthwhile. A project running slower than planned because you're being careful isn't the same problem as a project where the original estimate was simply wrong for the amount of work involved, and the fix for each is different. Only treat this as a true lowball once the math confirms it, not just because the week felt harder than expected.
This is the same calculation worth doing before you ever quote a fixed fee in the first place, see the guide on why your project estimates keep running over for where this kind of gap usually originates.
A small gap on an otherwise good client is usually worth just absorbing
If the shortfall is modest and the client relationship is otherwise solid and likely to continue, deliver the current project at the quoted fee and treat the loss as the cost of learning the real scope of this type of work, then quote differently next time. Renegotiating a small gap on a client you want to keep often costs more in relationship friction than the money actually recovers, especially on a first or early project where establishing trust matters more than this specific invoice.
A real gap, caused by scope that's grown beyond what was quoted, is worth raising now
If the actual scope has expanded past what you originally quoted for, more revision rounds, additional deliverables, requirements that weren't part of the original brief, that's a legitimate renegotiation, not a confession that your original number was wrong. Document specifically what's grown: "The original quote covered two rounds of revisions, we're now on round five with three new sections added that weren't in the initial brief. I'd like to true up the remaining work at my standard rate for additional scope." This reframes the conversation around what changed, not around your original estimate being bad.
If the scope genuinely hasn't changed and the number was just wrong from the start, that's a harder conversation to have mid-project, and usually the smaller-gap approach above is the more realistic path forward on this specific engagement.
Fix the method, not just this one quote
A single lowballed project is a pricing mistake. A pattern of lowballed projects is a broken estimation process, and the fix belongs there, not in trying to recover money project by project after the fact. Build in a buffer, commonly 15 to 20 percent above your best-guess hours, specifically for the discovery that always happens once real work starts, and track actual hours against every quote going forward so the next estimate is grounded in real data instead of optimism.
Seeing the real gap between quoted and actual, project by project
Rinto shows the budget and logged hours for every project side by side, so a lowballed quote shows up clearly in the numbers rather than staying a vague feeling that this particular project felt harder than it should have. See the full breakdown in the guide on how to price a freelance project properly for a method that builds the buffer in from the start.
Frequently Asked Questions
What should I do if I realize I lowballed a project fee mid-project?
First confirm it's a real underpricing problem, not just a slower week, by calculating your actual hourly rate on the project so far. For a modest gap on a client you want to keep, it's usually best to absorb it and price differently next time. For a real gap caused by scope genuinely growing beyond what was quoted, document the specific additions and raise a renegotiation around that change, not around your original estimate being wrong.
Can I ask a client for more money after agreeing to a fixed fee?
Only if the scope has genuinely grown beyond what the original fee covered, more revisions, added deliverables, requirements outside the initial brief. Document exactly what's changed and frame the ask around that specific growth, not around the original number being too low. If the scope hasn't actually changed, renegotiating mid-project is a much harder conversation and usually not worth the relationship cost on a client you want to keep.
Should I just finish a lowballed project at a loss?
For a modest shortfall on an otherwise good client relationship, usually yes, treat it as the cost of learning the real scope of this type of work and price differently on the next project. Renegotiating a small gap often costs more in relationship friction than the money actually recovers, especially early in a client relationship where trust matters more than any single invoice.
How do I stop lowballing fixed-fee projects?
Build in a buffer, commonly 15 to 20 percent above your best-guess hours, specifically to account for the discovery that happens once real work starts. Track actual hours logged against every quote you send, so future estimates are grounded in real historical data about how your projects actually run, not just optimism about how smoothly this one will go.
How do I know if a project is actually underpriced or just feels harder than expected?
Calculate your real hourly rate so far: total hours logged on the project divided into the fee, then compare that honestly to what you need to earn per hour for the work to be worthwhile. A project that's slower because you're being careful is a different problem than one where the original number was simply too low for the actual work involved, and only the math, not the feeling, tells you which one you're dealing with.