Freelance Rate Calculator for Developers
Built around how freelance development work actually gets priced: the take-home target is higher, ongoing maintenance is usually a different pricing model, and project costs shouldn’t be mistaken for your own overhead.
Keep project costs separate from your own overhead
It’s tempting to lump API credits, cloud hosting, or a subcontractor’s day rate into the expenses field below, but those are usually specific to one client’s project — they belong on that project’s quote or invoice as a pass-through cost, not folded into your overhead. Expenses here should be costs you carry regardless of which client you’re working for: your own equipment, IDE and tooling licences, insurance, and accounting or business-entity fees. Keeping the two separate stops your day-to-day rate from quietly absorbing one client’s infrastructure bill.
How to use this
- Enter the yearly take-home pay you want after tax.
- Add your yearly business expenses.
- Set your tax rate and weeks off — your minimum hourly rate updates instantly.
- Day rate (8 billable hours)
- —
- Revenue needed per month
- —
- Revenue needed per year
- —
- Billable hours per year
- —
- Estimated tax per year
- —
A worked example
A freelance backend developer wants $110,000 take-home a year, has $7,500 in yearly overhead (equipment, IDE and tooling licences, insurance, accounting fees — not client-billable project costs), plans for 4 weeks off, pays an effective 27% tax rate, and bills 22 hours a week, the same planning assumption as any other freelancer juggling non-billable admin and business development time.
- Billable hours per year
- (52 − 4) × 22 = 1,056 hrs
- Grossed-up take-home
- $110,000 ÷ (1 − 27%) = $150,684.93
- Revenue needed per year
- $150,684.93 + $7,500 = $158,184.93
- Minimum hourly rate
- $158,184.93 ÷ 1,056 = about $150/hr
- Day rate (8 billable hours)
- about $1,198
These are the exact numbers already entered above — adjust any of them and the result updates live.
How this rate is worked out
Your take-home pay is grossed up for tax, business expenses are added, and the total is divided by the hours you can bill: (take-home ÷ (1 − tax rate) + expenses) ÷ billable hours.
How do I price ongoing maintenance or on-call support?
Not with this hourly rate directly — ongoing maintenance and on-call availability are usually priced as a retainer, since you’re being paid partly for availability, not just hours worked. Use this rate as your floor, then compare it against a flat monthly fee in the retainer tool; a retainer that pays less than this rate times your expected monthly hours usually isn’t worth it unless the predictability is worth the discount to you.
Should tooling and subscriptions be in my expenses?
Only the ones you’d pay regardless of which client you’re working for — your IDE and library licences, insurance, and accounting or business-entity fees. API credits, cloud hosting, or a subcontractor brought on for one project are usually specific to that client’s work; pass those through on the project’s quote or invoice instead of folding them into your day-to-day rate.
Why does my rate look higher than a typical salaried engineer’s hourly equivalent?
Because a salary figure already has employer-paid costs stripped out — benefits, downtime, equipment, taxes. Freelance developers also deal with longer sales cycles and gaps between contracts, which is exactly why the billable-hours field above should reflect real bookable time, not a full 40-hour week. If your rate looks high next to a job posting’s salary divided by 2,000 hours, that’s the calculation working correctly, not a sign to lower it.