The Freelance Minimum Project Fee
Short answer: a minimum project fee is the smallest amount you'll take on any job, no matter how quick it looks. You need one because every project carries fixed overhead — the email back-and-forth, the contract, the invoicing, the context-switching — that doesn't shrink just because the work is small. A "ten-minute" task can quietly eat an hour once you count all of it, and at your normal rate that hour was never billed. A common floor is 2 to 4 hours of your rate, or a round number like $250–$500. Here's how to set yours and how to say it without losing good clients.
Your minimum is built on your hourly rate, so get that right first. The free Freelance Rate Calculator → shows your real take-home per hour after self-employment tax and expenses — multiply that by the hours a small job actually consumes (not just the billable ones) and you've found your floor.
Why small jobs lose money
The hours you bill are never the only hours a project costs. Every job, large or small, drags along a fixed tail of overhead:
- Onboarding — the intro call, understanding what they want, gathering assets and logins.
- Admin — the proposal, the contract, the deposit, the invoice, chasing payment.
- Context-switching — stopping your real work to do this, then ramping back up; the switch alone can cost 15–30 minutes each way.
- Communication — emails, revisions, "one more quick thing" requests.
That overhead is roughly the same whether the project is $200 or $5,000. On a big job it's a rounding error. On a tiny job it's the whole margin — which is exactly why a "quick $150 favor" often earns you less per hour than a job five times the size.
The hidden math of a "quick" job
A client asks for a "fast" 30-minute edit at your $80/hr rate — they expect to pay $40. But the real cost is: 15 min reading the request, 30 min doing it, 15 min two rounds of email, 10 min invoicing and follow-up, plus two context-switches. Call it 90 minutes of your day for $40 — an effective rate of about $27/hr, a third of what you charge. A minimum project fee is what stops that job from being worth taking at all.
Not sure your hourly rate is even right? Use the free Freelance Rate Calculator → first. Your minimum is a multiple of your true rate — if the rate is too low, your floor will be too low too, and small jobs will keep slipping under it.
How to set your minimum
Pick whichever of these gives the higher, cleaner number — there's no single right method, just one that protects your time:
- The hours method: minimum = your hourly rate × the real hours a small job consumes (usually 2–4, once you count overhead). At $80/hr, that's a $160–$320 floor.
- The round-number method: set a clean threshold — $250, $500, $1,000 — below which you simply don't open a project. Easy to quote, easy to hold.
- The "is it worth the switch?" method: set the floor at the point where the income clearly outweighs interrupting your main work. If a job doesn't clear that bar, it's a distraction, not income.
Typical minimums by work type
| Type of work | Common minimum project fee |
|---|---|
| Quick edits / small fixes / consults | $150–$300 (or a 1-hour minimum) |
| Design, copywriting, content pieces | $250–$750 |
| Web / development projects | $500–$2,000+ |
| Strategy, audits, specialized expertise | $1,000+ |
These are starting points, not rules. The right floor depends on your rate, your niche, and how much a small job really disrupts your day. If you've niched down, your minimum should sit at the higher end.
How to communicate it
State the minimum plainly and frame it as how you work, not as a barrier. Most clients accept it instantly when it's presented with confidence:
"Happy to help with this. My project minimum is [$X], which covers the setup, the work itself, and revisions. If you've got a couple of related tasks, we can bundle them under that minimum so you get full value from it."
That last line is the key move: when a job is below your floor, offer to bundle the client's small tasks together so they hit the minimum and feel they're getting their money's worth. You protect your rate; they get more done. Everybody wins.
How to handle pushback
| They say… | You say… |
|---|---|
| "But it's such a small task!" | "It is — but every job carries the same setup, admin, and revisions. The minimum covers that. Let's bundle a few small items so you get the most from it." |
| "Can't you just do this one quickly?" | "I keep a project minimum so small jobs stay worth doing well. If it's a one-off, [$X] is the floor; if there's more coming, a retainer might fit better." |
| "That seems like a lot for ten minutes." | "The price reflects the whole job, not just the typing — onboarding, communication, and invoicing all take time regardless of size." |
When to waive (or bend) it
A minimum is a default, not a law. It's reasonable to flex it when there's a strategic reason you control:
- An existing, valued client with a genuine quick request — goodwill on an established relationship is cheap insurance.
- A foot-in-the-door with a client likely to bring larger work, where the small job is really a paid audition.
- A task that's truly trivial for you and carries almost no overhead because the context is already loaded.
Outside those, hold the line. A minimum you abandon under mild pressure isn't a minimum — it's a suggestion.
Watch-outs
- Count the hidden hours. If you set the floor off billable time only, it'll be too low. Include onboarding, admin, and context-switching.
- Don't let "quick favors" pile up. Several sub-minimum jobs can crowd out the real, profitable work entirely.
- Bundle instead of refusing. Offering to combine small tasks keeps the client happy and your rate intact — better than a flat "no."
- It's not a deposit. A minimum is the floor on total fee; you still take a deposit on top for larger work.
A minimum project fee is one piece of a healthy pricing system — alongside pricing models, a rush fee for tight deadlines, and a plan for discount requests so your floor doesn't get negotiated away.
Build your floor on a rate that actually works
Your minimum is only as good as the hourly rate underneath it. The $9 Freelance Rate & Tax Calculator spreadsheet nets your income against self-employment tax and expenses so you know your real take-home — the number every minimum and quote should be built from. Quoting and invoicing small jobs too? Get the calculator + a clean invoice template in the $14 Starter Pack →
Frequently asked questions
What is a freelance minimum project fee?
It's the smallest amount you'll accept for any job, regardless of how small the task looks. It exists because every project carries fixed overhead — onboarding, admin, communication, invoicing, and context-switching — that doesn't shrink with the size of the work. The minimum ensures even quick jobs cover that overhead and stay worth doing well.
How much should my minimum project fee be?
A common floor is 2 to 4 hours of your hourly rate, or a round number like $250 to $500. Set it using whichever gives the cleaner, higher figure: your rate times the real hours a small job consumes (including overhead), a clean threshold below which you won't open a project, or the point where the income clearly outweighs interrupting your main work.
Why do small freelance jobs lose money?
Because the billable hours are never the only hours. Onboarding, the contract and deposit, emails and revisions, invoicing, and the cost of switching away from your main work all take roughly the same time whether the project is $200 or $5,000. On a small job that fixed overhead can consume the entire margin, dropping your effective hourly rate well below your stated one.
How do I tell a client about my minimum without losing them?
State it plainly as how you work, and frame it as covering setup, the work, and revisions. The most effective move is to offer to bundle the client's small tasks together so they reach the minimum and feel they're getting full value. Most clients accept a confidently stated minimum immediately, especially when you give them a way to make the most of it.
Should I ever waive my minimum project fee?
Occasionally, for a strategic reason you control: a quick request from an existing valued client, a foot-in-the-door with a client likely to bring larger work, or a task that's genuinely trivial because the context is already loaded. Outside those cases, hold the line — a minimum you abandon under mild pressure stops functioning as a minimum.