Freelance Hourly Rate Calculator: What You Actually Need to Charge

The most common way freelance developers calculate their hourly rate is dividing a target annual income by 2,080, the number of hours in a standard 40-hour, 52-week work year. It’s a clean, simple calculation, and it’s wrong in a way that quietly underprices nearly every freelancer who uses it, sometimes by close to half. It assumes every single working hour is billable, with no time spent on proposals, client communication, administrative work, vacation, sick days, or the gaps between projects that happen to every freelancer eventually.

This calculator, a direct follow-up to the pricing guide on this site, uses actual realistic billable-hours math instead. Run a target income of $90,000 through the naive full-time assumption and it suggests roughly $43 an hour. Run the same target through a realistic billable-hours model, accounting for genuine time off and a real, honest billable percentage, and the number comes out closer to $77 an hour, a gap wide enough to represent the difference between a sustainable freelance income and a quietly underpriced one.

Calculate Your Real Rate

Why the Naive Calculation Underprices Nearly Everyone

Dividing a target salary by 2,080 hours treats every single working hour as billable client time, which no freelancer’s actual week looks like. Writing proposals, discussing scope with prospective clients who don’t end up hiring you, handling invoicing and bookkeeping, responding to email, and the inevitable slow weeks between projects all consume real working hours without generating any billable revenue at all. A commonly cited, more honest estimate puts the actually billable share of a freelancer’s working time somewhere between 60 and 70 percent, which means roughly a third of the working year needs to be accounted for as real, unbillable overhead rather than assumed away entirely.

Vacation and sick time compound this further, and it’s specifically the part freelancers tend to underestimate, since there’s no employer-provided PTO forcing the question. A freelancer who never explicitly budgets time off either burns out trying to maintain a genuinely full 52-week billing year, or quietly takes the time off anyway and finds their actual annual income falling short of the target because the rate was calculated as if that time didn’t need to be planned for.

Breaking Down Each Input

Target annual revenue

This should represent gross business revenue, not personal take-home pay, since the calculator separately accounts for business expenses on top of it. It’s worth basing this number on genuine research into what similar freelancers in your specific niche and region actually earn, rather than picking a number purely from personal financial need, a mistake the companion pricing guide on this site covers in more depth, since a rate justified purely by personal expenses tends to sound defensive rather than confident in an actual client conversation.

Annual business expenses

This is easy to underestimate by only counting the obvious costs, a laptop, a code editor subscription, and missing the less visible ones that add up over a year: business insurance, accounting or bookkeeping software, a portion of home office costs if applicable, professional development and courses, and payment processing fees on every invoice, which quietly eat a percentage of revenue that’s easy to forget when estimating expenses from memory rather than reviewing actual past spending.

Weeks off per year

Budgeting genuine time off into the rate calculation, rather than treating vacation as something that happens “if there’s room,” is what actually makes taking that time off financially sustainable rather than something that quietly shrinks annual income every time it happens. A freelancer who budgets four weeks off and takes them is earning the target income. One who calculates a rate assuming zero weeks off and then takes a real two-week vacation anyway has just built an unplanned income shortfall into their year.

Hours worked per week

This should reflect a genuinely sustainable pace, not an aspirational one. Calculating a rate around 50 or 60 planned weekly hours, in an attempt to lower the required hourly rate on paper, tends to produce burnout rather than actual sustained output at that level, and a rate that only works assuming an unsustainable pace isn’t really a solved pricing problem, it’s a deferred one.

Billable percentage

This is the input most freelancers get wrong by assuming a number far higher than their actual practice supports. Tracking real time for a month, genuinely logging hours spent on client-billable work versus proposals, admin, and communication, is worth doing at least once to calibrate this number against reality rather than guessing. A freelancer who assumes 90 percent billable and actually operates closer to 60 percent has built a rate calculation on a number that doesn’t reflect their actual working pattern, and the gap between assumed and actual billable time is exactly where a lot of freelance income shortfalls quietly originate.

What to Do With the Number Once You Have It

Treat the calculated rate as a floor, the minimum needed to hit your target income given the assumptions entered, not necessarily the number to actually quote a client. Comparing it against genuine market research for your specific niche and experience level tells you whether the calculated floor is realistic for what clients in your market actually pay, or whether the target income itself needs adjusting to match what the market currently supports at your experience level.

Rounding the number to something clean and easy to communicate, $75 rather than $76.92, is a reasonable, common practice, and it’s worth rounding up rather than down when the calculated number falls close to a round figure, since the calculation already represents a floor rather than a comfortable margin.

Adjusting the Rate Over Time

Revisiting this calculation at least annually, and after any meaningful change to expenses, target income, or actual billable-hours experience, keeps the rate grounded in current reality rather than a snapshot from whenever it was first calculated. A freelancer whose actual billable percentage turns out to run lower than assumed, once tracked honestly over a few months, should recalculate rather than continuing to operate on an optimistic assumption that isn’t matching reality.

Raising rates for new clients as demand grows, rather than only when personal expenses increase, keeps pricing aligned with actual market position rather than purely reactive to cost changes. A freelancer who’s been consistently fully booked for months is showing a clear signal that current pricing sits below what the market would support, independent of whether personal expenses have changed at all.

Rate Doesn’t Solve Every Pricing Model

This calculator produces an hourly number, and it’s directly useful for hourly-priced work and as a sanity check when estimating a fixed-price project’s total based on expected hours. It doesn’t, by itself, address fixed-price scoping risk or value-based pricing at all, since those models are priced against defined scope or business value rather than time directly. The full comparison of hourly, fixed-price, and value-based pricing models, including how to scope fixed-price work safely and when value-based pricing actually becomes viable, is covered in the companion guide to pricing freelance development projects, which this calculator is meant to pair with rather than replace.

A Note on Taxes and Business Structure

This calculator deliberately treats the target revenue figure as a pre-tax number and doesn’t attempt to model your specific tax situation, since that depends on your location, income level, and business structure in ways a general calculator can’t account for responsibly. Self-employed freelancers in many jurisdictions owe additional self-employment tax on top of standard income tax, which is worth planning for by setting aside a meaningful percentage of revenue specifically for tax obligations rather than treating the full calculated revenue as available income. How you’re structured, as a sole proprietor versus an LLC, also affects some of these tax and liability details directly; this guide on LLC vs sole proprietorship for freelance developers covers that decision in depth, and an actual accountant familiar with your specific situation is the right source for tax planning beyond the general awareness this note is meant to provide.

Real Scenarios

Common Mistakes

Assuming a billable percentage far above actual practice, often 80 or 90 percent, without ever having tracked real time to verify it, produces a calculated rate that looks appealing on paper but doesn’t reflect the freelancer’s actual working pattern, leading to a real income shortfall once genuine non-billable time is accounted for in practice rather than assumption.

Forgetting to include less obvious business expenses, payment processing fees, software subscriptions that renew annually and get overlooked, a portion of home office costs, understates the true revenue needed and produces a rate that’s technically insufficient once the full, honest expense picture is accounted for.

Calculating a rate once and never revisiting it, even as expenses, target income, or actual billable-hours experience change meaningfully over time, leaves pricing anchored to an outdated snapshot rather than current reality.

And treating the calculated number as fixed and non-negotiable in either direction, rather than as a floor to weigh against real market research, misses the point of doing this calculation at all. It exists to establish the minimum that supports your actual target income given honest assumptions, not to dictate the final number without checking it against what your specific market will actually bear.

FAQ