Few freelance conversations feel as uncomfortable as asking a client for more money on a project that's already underway. Many freelancers avoid it entirely and quietly absorb the extra work instead.
That avoidance is expensive. It trains clients to expect more for the same fee, and it hides useful information from them: the project has changed, and they deserve the chance to decide what to do about it.
TL;DR
Ask for more budget before the current budget runs out, and frame it as a decision for the client rather than a complaint. Show what has been used, what changed and what is left, then offer clear options in writing with a specific amount: increase the budget, reduce the scope or pause. In COLO, you can send a Contract Update Request with an amount and a message, and the client approves or declines it in their client portal.
Why the conversation feels hard
Most of the discomfort comes from three fears:
- Looking like you estimated badly. Sometimes you did, but more often the scope moved.
- Damaging the relationship. In practice, surprise invoices damage relationships far more than early, honest updates.
- Hearing no. A "no" is still useful. It tells you to stop, scale back or finish on your own terms, instead of guessing.
The way through all three is the same: make the request specific, grounded in evidence and early.
When to ask
The best moment is before you run out, not after. If you track your budget as you go, a natural trigger is when you reach around 80% of it and can see the remaining work won't fit. Our post on project budget tracking explains why that point matters.
Other good moments:
- right after the client asks for something clearly outside the agreed scope
- when a dependency on the client side (late feedback, missing content) has added work
- when you discover the work is genuinely larger than either of you expected
The worst moment is after the work is done and the extra hours are already spent. At that point you are asking the client to pay for decisions they didn't know they were making.
Gather your evidence first
A request backed by facts is a business conversation. A request without them sounds like a negotiation.
Before you write anything, collect:
- The original scope and budget. What was agreed, in the contract or proposal. If your scope wasn't written down clearly, see our freelance contract checklist for next time.
- What has been used. Hours tracked and invoices raised, against that budget.
- What changed. Specific requests, added deliverables, extra rounds or delays, with dates if you have them.
- What is left. The remaining work and a realistic estimate of what it will take.
- The amount you are asking for. A specific figure, not "a bit more".
Structure the request
A good change request does four things, in this order:
- States the situation plainly. Where the budget is now.
- Explains why. What changed, without blame.
- Offers options. At least two, so the client has a real decision.
- Asks for a clear answer. Approve, adjust or pause.
Scripts you can adapt
When scope has grown
"Quick budget update on the project: we have used about 80% of the agreed budget. Most of that is the original work, but the two extra landing pages you asked for last week weren't in the original scope. To finish everything, including the new pages, I'd need an additional [amount]. Alternatively, we can keep the original scope and move the new pages to a follow-up phase. Which would you prefer?"
When the work turned out larger than expected
"I want to flag something early. The data migration is turning out to be more involved than either of us expected when we scoped it. I estimate another [hours] to finish properly, which is [amount]. I'm happy to walk you through what I've found. If the extra budget isn't possible right now, we could simplify the migration and cover the rest later."
When the budget is already used up
"We have now reached the agreed budget for this project. The remaining work is [list]. I've paused billable work until we agree how to proceed. Options are: approve an additional [amount] to finish, reduce the remaining scope to [smaller list] or pause here. Let me know what works best for you."
Keep the tone factual. You are not apologizing and you are not demanding. You are giving the client the information they need to make a decision about their own project.
Make it easy to say yes (or no)
- Use a specific amount. Vague requests invite vague answers.
- Put it in writing, even if you discussed it on a call. A written approval protects both sides.
- Give a reasonable deadline for the decision, especially if work is paused.
- Accept a no gracefully. Then follow through on the option you offered, whether that's reducing scope or stopping.
Once agreed, the new amount should be reflected in the contract, not just in a message. The freelance contracts guide covers how to handle variations.
How COLO handles budget increase requests
In COLO, a project's budget is its contract total. When billable work reaches 100% of it, billable timers stop and a "Budget Limit Reached" modal gives you three choices. One of them is Request Contract Update: you enter the amount you need and a message explaining why.
The client then sees a "Contract Update Request" in the client portal, with your message, and can Approve or Decline it:
- Approve adds the amount to the contract total and makes the tasks billable again.
- Decline moves the project to internal mode, so any further work is tracked as non-billable.
While a request is waiting for an answer, new tasks are created as non-billable, so nothing is charged before the client agrees. You can read more on the project budgets and contracts pages.
FAQ
How do I ask a client for more money without sounding unprofessional?
Lead with facts: what was agreed, what has been used, what changed and what's left. Offer options and ask for a decision. Clear, early and specific requests come across as professional, not pushy.
Should I keep working while I wait for an answer?
That is your call, but don't keep doing billable work the client hasn't approved. Either pause or continue on your own time knowing you may not be paid for it. Our post on keeping working or pausing covers that decision.
What if the client declines?
Follow through on the alternative you offered: reduce the scope, finish only what fits, or stop. In COLO, a declined request moves the project to internal mode, so further work is tracked as non-billable.
Can the client approve the increase without emailing me back?
Yes, in COLO. The request appears in the client portal, and the client can approve or decline it there.
Final thoughts
Asking for more budget isn't a failure. It's how a project stays honest when its scope changes. Ask early, bring evidence and give the client a real choice.