The email arrives at 4:40 on a Tuesday. A client — or worse, a prospect who smells money on you — needs something by Friday. The work itself is ordinary. The timeline is not. You can feel the weekend rearranging itself already, and you can also feel the small guilty voice asking whether charging extra for this is somehow unfair.
It isn't. Rush pricing is not a punishment tax on disorganized clients, and it's not greed. It's arithmetic. Here's why the premium is legitimate, the tier structure most solo operators can defend without blinking, the exact sentence that makes it enforceable, and the two situations where you waive it on purpose.
Why rush work costs more — the honest reason
A one-person business sells one thing: hours, in sequence. You have roughly forty of them a week, and the good ones — the deep-focus mornings — are already spoken for by the work you agreed to last week. A rush job does not add hours to the week. It takes them from somewhere specific, and that somewhere has a price.
The cost comes in two parts, and naming them matters because clients who understand them stop negotiating.
Opportunity cost. The hours the rush job consumes were allocated to other client work, to the marketing you keep postponing, or to the evening you were going to spend not working. When you compress a project into a window that was already full, something else slips — and the thing that slips is usually yours, because clients get angry and your own backlog just gets quiet. The rush premium is you declining to absorb that slippage for free.
Schedule disruption. Context-switching is real overhead. Stopping a project mid-thought, loading a different client's codebase or brand voice into your head, and then reloading the first one on Monday costs hours that never appear on any invoice. Research on task-switching has been saying this for decades; your own calendar says it louder. A two-day rush job inserted into a full week doesn't cost two days. It costs two days plus the re-entry tax on everything around it.
So the fee is not "you were slow to plan, so I charge more." It's "your timeline consumes scarce capacity at an inconvenient moment, and scarce capacity at inconvenient moments costs more." That's a pricing statement, not a moral one — the same reason a flight costs more the week of departure.
The tier structure: 25, 50, 100
Flat rush fees ("$500 extra") break down because urgency is a spectrum. A percentage-of-project tier system scales with the work and reads as policy rather than mood. The structure that works for most solo operators:
Standard turnaround — booked with 10+ business days' notice: normal rate. Rush tier 1 — 5 to 9 business days' notice: +25% on the project fee. Rush tier 2 — 2 to 4 business days' notice: +50% on the project fee. Rush tier 3 — under 2 business days, or weekend/holiday work: +100% (double rate), and only if you genuinely have the capacity.
Two design notes. First, the tiers are measured in notice given, not in how fast you work. You are not promising to type faster; you're charging for jumping the queue. Framing it as notice also makes it objective — no arguing about whether the project "felt" rushed. Second, tier 3 exists mostly as a polite fence. Some things you simply cannot do well in 36 hours, and the 100% tier is how you find out whether the client actually means it. About half the time, "by tomorrow, whatever it costs" turns into "actually, next Thursday is fine" the moment it has a price.
Adjust the percentages to your market, but keep the shape: graduated, written down, and tied to the calendar rather than to how annoyed you are.
The exact sentence to put in your proposals
A rush fee you mention for the first time in the middle of a rush is a surprise, and surprises get negotiated. The fee works because it was sitting in the proposal the client already signed, next to the payment terms, before any deadline was on fire:
Work requested with fewer than 5 business days' notice carries a 50% rush premium, quoted and approved in writing before work begins.
Three deliberate choices in that sentence. "Quoted and approved in writing" means you'll confirm the number in an email before starting — no ambiguity later about whether they agreed. "Business days" preempts the Friday-afternoon request framed as "you have the whole weekend." And 5 business days as the trigger is the sweet spot: tight enough to catch genuine rush work, loose enough that normal projects never brush against it.
If you use the tier system, the proposal version can carry the whole table instead of the single line — but keep the single line even then, because it's the one people read.
Then, when the rush request lands, the reply writes itself:
Happy to take this on. Heads-up that with the Tuesday deadline it falls under the rush terms in our agreement — the fee with the 50% premium is [amount]. Confirm and I'll start today.
No apology, no lecture about planning, no exclamation points. You're not punishing anyone; you're reading the menu back to them.
When to waive the fee
A policy you never bend is brittle, and a policy you bend for everyone is decorative. Waive the rush premium in exactly two situations, and say out loud that you're doing it.
The good client, once. The client who books you months ahead, pays on receipt, and refers people — when that client has their one genuinely chaotic quarter, you absorb the rush. Say it plainly: "Normally this timeline carries the rush premium; I'm waiving it this once." Those last three words are the whole trick. Unannounced generosity reads as your real price, and next quarter's rush will be priced off this quarter's favor. Announced generosity builds loyalty and resets the expectation in the same sentence.
The genuine emergency, once. The site is down on launch day. The grant application portal closes Friday and their developer vanished. Real emergencies are recognizable because the client is slightly embarrassed and the deadline is imposed by physics or a third party, not by their internal scheduling. Help, at your normal rate, and note the exception. What you're buying with the waived fee is a client who will tell that story about you for years.
What's not on the waiver list: the chronic rusher. The client whose every request is urgent is not having a run of emergencies; they're outsourcing their planning to your evenings. The premium exists precisely for them, and waiving it teaches them the fee is negotiable theater. Charge it, cheerfully, every time. Chronic rushers either start planning ahead — a fine outcome — or keep paying double, which is also a fine outcome.
How to say no to a rush job you can't actually do
The hardest rush job is the one where the money is real and the timeline is fiction. Taking work you can't deliver well isn't revenue; it's a reputational loan at a bad rate. Declining it cleanly is a skill, and the wording matters because "no" delivered wrong costs you the client's non-rush work too.
I can't do this justice by Friday, and I'd rather tell you that now than hand you rushed work. What I can do: [deliver X by Friday and the rest by the following week] or [the full thing, starting Monday, done by the 18th]. If neither works, [name/this type of provider] may have slack this week.
Three moves. "I'd rather tell you now than hand you rushed work" frames the refusal as quality control, which is exactly what it is. Offering one or two honest alternatives keeps the door open — partial delivery or a realistic start date solves most real emergencies. And referring out, when you can, is the move that feels like a loss and behaves like an investment: the client remembers you as the person who told the truth at the expensive moment.
Notice what you never say: "I'm too busy." Busy is about you. The refusal is about their work getting done properly — keep it there.
The system, such as it is
Rush pricing works when it's boring: tiers written down, one sentence in every proposal, waivers announced and rare, refusals fast and honest. If you want the paperwork ready-made, the Client-Ready Business Templates ($19) include a proposal and service agreement with rush-fee language already in place, alongside the late-fee clause and change-order documents. The deadline terms pair naturally with an acceptance window — the statement of work piece covers that side. But the sentence above is complete as it stands. Put it in your next proposal while nothing is on fire, because the only version of this that fails is the one you invent mid-rush.