Most freelancers set their rate by copying a number they saw on a Reddit thread, asking in a Discord server, or guessing what "sounds fair." None of those numbers know your expenses, your tax situation, or how many hours you can actually bill in a month. They're someone else's answer to a question only you can actually answer.
Start from your income target, not your hourly guess
Instead of picking a rate and hoping it adds up to enough, work backward. Decide how much you need to take home per month, add in expenses and taxes, then divide by the hours you can realistically bill.
- Monthly income target: what you actually need to take home, not an aspirational number
- Business expenses: software subscriptions, equipment, contractor help, coworking space
- Tax set-aside: a rough percentage based on your country/state and entity type
- Billable hours: working days × hours you can genuinely charge for (not hours spent at your desk)
Here's what that looks like with real numbers. Say you want to take home $5,000/month, you spend $300/month on tools and a laptop payment, and you set aside 20% for taxes. That's ($5,000 + $300) / 0.8 = $6,625 you need to actually invoice every month. If you work 20 days a month and can bill 5 hours a day, that's 100 billable hours, putting your baseline rate at $66.25/hour before you've even added a profit buffer.
Now scale that up. Say you're further along and targeting $8,000/month take-home, you've started paying a part-time virtual assistant $600/month to handle admin and scheduling, you spend $500/month on software and a contractor who helps with overflow design work, and you set aside 25% for taxes because you're in a higher bracket now. That's ($8,000 + $600 + $500) / 0.75 = $12,133 you need to invoice monthly. If you're more disciplined about your calendar at this stage and bill 6 hours a day across 21 working days, that's 126 billable hours, putting your baseline rate at $96.30/hour. Notice that the contractor and assistant costs didn't reduce your rate, they raised it, because someone has to pay for the time they free up.
Why "billable hours" is the part everyone gets wrong
If you work 8 hours a day, you are not billing 8 hours. Admin, sales calls, scoping new work, replying to emails, and ordinary breaks eat into that. Most freelancers can realistically bill 4-6 hours a day, even on a well-run schedule. New freelancers especially overestimate this number. They count "hours worked" instead of "hours invoiced," and then wonder why their actual income falls short of what their rate sheet implies.
A simple gut check: track your actual billable hours for two weeks using whatever method you already use (a timer, calendar blocks, anything). Most people are surprised by how low the real number is compared to their assumption.
Build in a buffer
Slow months happen. A client pauses a project, a deal falls through after weeks of back-and-forth, or you take a week off and don't replace that income. A 10-20% buffer on top of your bare-minimum number gives you room for the weeks when client work dries up or a project runs long without you having to renegotiate mid-project.
Rates differ by niche, and that's not arbitrary
The formula gives you a floor, but where you land above that floor depends heavily on what you actually do. A beginner web developer building basic WordPress sites might calculate a $35-45/hour floor and find that's roughly what the market supports too, because the work is relatively commoditized and there are a lot of other beginners competing for the same projects. A senior video editor who specializes in retention-optimized YouTube content for creators with six-figure channels might calculate a similar-looking floor based on living expenses, but charge $150-250/hour or a flat $2,000+ per video, because the skill is specialized, the client's downside risk (a bad edit tanking watch time) is high, and there are far fewer editors who can do it well. A specialized consultant, say someone who only does compliance audits for healthcare startups, might charge $300-500/hour, not because their living expenses are five times higher than the web developer's, but because the pool of people who can credibly do that work is tiny and the cost of getting it wrong is enormous for the client.
The lesson isn't "charge more because you can." It's that your income-target formula tells you the minimum you need, but the ceiling is set by scarcity and perceived risk reduction, not by your personal budget. Two freelancers with identical expenses can have wildly different ceilings depending on what they specialize in.
Pricing across borders and cost-of-living differences
If you're pitching clients in a higher cost-of-living country than the one you live in, don't anchor your rate to your local expenses alone. A freelancer based somewhere with a low cost of living, quoting a client in a major US or European city, is often tempted to charge dramatically less because "that's still a great rate for me." It is, in the short term. But you're leaving money on the table that the client would have paid anyway, and you're training that client to associate your work with bargain pricing, which makes a future rate increase much harder to justify.
A more sustainable approach is to price closer to what the client's local market actually pays for the skill level you offer, then let your lower personal cost of living translate into a higher savings rate or profit margin, not a lower invoice. If a US-based designer with your skill level charges $80/hour, quoting $70/hour as a value-conscious alternative is reasonable. Quoting $25/hour because that number feels enormous relative to your local expenses is leaving the difference on the table for no reason.
If your calculated number is way above what the market pays
Sometimes you run the formula honestly and get a number that the clients you're currently talking to simply won't pay. That's a real signal, but it's rarely a signal to just lower your price and accept thinner margins forever. It usually means one of two things: you're talking to the wrong clients, or you're competing in a niche that's commoditized at your current skill level.
The fix is almost never "charge less for the same work to the same audience." It's either niching down (specializing narrowly enough that you're no longer compared against a crowded general pool) or moving upmarket (targeting clients who have bigger budgets and more on the line if the work goes wrong). A generalist freelance writer competing on content mills will struggle to hit $60/hour no matter how the math works out. A writer who narrows into, say, technical documentation for fintech APIs, can often charge triple that to a smaller but better-funded pool of clients, doing comparable work.
Common mistakes that quietly wreck the math
A few mistakes show up constantly when freelancers run this calculation for the first time.
- Forgetting software and subscription costs entirely, then wondering six months later why take-home pay never matches the rate sheet
- Forgetting self-employment tax, which in many countries sits on top of regular income tax and surprises almost everyone the first year
- Counting hours worked instead of hours billed, which inflates the denominator and produces a rate that's too low to actually hit your income target
- Setting the rate once and never revisiting it, even as expenses rise, skills grow, and inflation quietly eats into what last year's number is actually worth
- Not accounting for unpaid work that's still real work: proposals, discovery calls, scope negotiation, and invoicing all take time that doesn't show up on a client's invoice but absolutely shows up on your calendar
Raising your rate without losing the client
Once you have a number, treat it as a range rather than a single price: a minimum safe rate for must-take work, and a premium rate for projects that are urgent, complex, or outside the work you'd prefer to do. As you gain experience, testimonials, and a backlog of inbound requests, that whole range should move up, and you don't need to wait for permission to do it.
For existing clients, the easiest approach is a short, calm heads-up with notice: "Starting next month, my rate for new projects will be $X. Happy to keep working together at this new rate, or wrap up the current scope at the old one first, whichever works better for you." Clients who value your work will usually just say yes. The ones who push back hard on a reasonable, well-communicated increase are often telling you something useful about how the relationship would have gone long-term anyway.
Once you land on a number you're confident in, it's worth treating it as a living number you revisit every few months rather than a one-time decision. Your expenses, your skill level, and the market all keep moving, and your rate should move with them.