Rush Fees for Solo Founders — Price Urgency Without Resentment
Urgent work is genuinely more expensive to deliver: it displaces planned work, compresses your focus, and arrives at the worst moments. A rush fee prices that reality — and a good rush policy turns "emergency" from an ambush into a product with a price tag.
This guide covers when to say yes to rush work, how to price the premium honestly, the capacity rules that keep rush promises deliverable, and the quote language that makes clients accept the fee without flinching.
The short answer
- Rush premiums of 25-100% are standard across service industries; below 25% rarely compensates the disruption.
- Publishing rush terms in advance increases acceptance — surprise fees stall, expected fees are budgeted.
- Capping rush work (e.g., one rush slot per week) is what keeps the premium deliverable without breaking the rest of the calendar.
Who this playbook is for
Built for solo founders who keep absorbing emergency deadlines at normal prices and resenting every minute of it.
Step 1: Decide what "rush" means in your business
Define it mechanically: delivery in less than half the standard timeline, or weekend/after-hours work, or insertion into a fully booked week. Publish the definition. Without one, every client’s impatience becomes "urgent" and your calendar becomes negotiable by whoever asks hardest.
Step 2: Price the premium on disruption, not guilt
Formula: base price × 1.25 for compressed-but-manageable timelines; × 1.5 for same-week insertion; × 2 for weekends or same-day. The fee compensates real costs: displaced work, evening hours, higher error risk, and the opportunity cost of the slot they are buying.
Step 3: Sell rush slots as a scarce product
"I hold one rush slot per week — it’s open Tuesday start, 25% premium, delivery in half the standard time. Want it?" A named product with one slot converts better than a grudging favor, protects your calendar by construction, and lets clients plan around a real mechanism instead of testing your flexibility.
Step 4: Confirm rush scope in writing, tighter than usual
Rush work needs harder boundaries: fewer revisions (one round), explicit inputs due by a stated hour, and a clause that timeline promises void if inputs arrive late. Compressed projects have no slack for ambiguity — the change-order conversation happens before the work, never during.
Step 5: Decline impossible rushes with an alternative
When the timeline truly cannot work: "I can’t deliver quality in 48 hours here. What I can do is [partial version by Friday] or [full version Tuesday at standard rate]." Offering a shape of yes preserves the relationship; a flat no just moves the emergency to someone who will fail at it.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Setup once | Rush definition, premium schedule, one-slot rule published | 1 hr |
| Per rush request | Quote with the premium line item visible | in-flow |
| Per rush project | Tighter scope doc; inputs deadline confirmed | 30 min |
| Monthly | Review rush revenue and calendar damage | 15 min |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Rush acceptance rate | Tracked per premium level | Zero acceptance means overpriced; always acceptance means underpriced |
| Rush premium earned | 25%+ average | The reward for the disruption actually being collected |
| Standard-work slippage from rush jobs | Under one day per rush | The one-slot rule doing its job |
| Rush rework rate | Low | High rework means inputs discipline is missing |
Common mistakes to avoid
- Charging rush fees retroactively. The fee is quoted at sale or not at all — surprise invoices read as punishment, not pricing.
- Letting rush premiums become the normal price. If most work is "urgent", your timeline promises are wrong — fix the standard delivery expectation instead of living at 1.5x.
- Taking rush work while promising original deadlines hold. Something slips; rush clients pay for the slot, they did not pay to quietly break promises to others.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Your proposal template | A standing rush line item |
| Calendar | The visible weekly rush slot |
| Dubsado / Bonsai | Rush clauses with inputs-deadline language |
| Your services page | Published rush terms |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- The Deposit Policy Every Solo Founder Needs
- Money-Back Guarantees for Service Businesses
- Scope Creep Contract Language
FAQ
Q: Is a rush fee unprofessional to charge?
Charging nothing is what creates resentment and slipping quality — the fee professionalizes urgency. Framed as a scarce, published product ("one rush slot weekly, 25% premium"), clients respect it; framed as a guilt-driven surprise, they resent it. Publish, then charge.
Q: How do I price rush work for retainer clients?
Retainers can include a rush allowance: one expedited request per month within the fee, additional rushes at the published premium. This gives key clients a real benefit while capping your disruption exposure — and makes the premium a feature they can buy more of.
Q: What if a client refuses the rush fee but insists on the deadline?
Then the honest answer is a scoped-down version or a declined project. Delivering normal-speed work at normal price while silently killing your evenings is how solo founders burn out one favor at a time. The fee is the boundary.
Q: Should rush work get different quality expectations?
Same quality, fewer iterations — state it: "Rush includes one revision round and requires inputs by [time]." Clients buying speed are buying your focus; tightening scope protects the focus they are paying for.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.