Setting Rates
The most common mistake new freelance engineers make with pricing: they take their salary, divide by 2,080 hours (40 hours times 52 weeks), and call that their hourly rate. A 72/hour. This is catastrophically wrong. At $72/hour, you will earn far less than you did as an employee, work harder, and wonder why you ever went independent.
Your freelance rate must account for everything your employer used to pay for: taxes, health insurance, retirement contributions, paid time off, equipment, software, and the hours you spend on non-billable work. The real multiplier is 2-3x your equivalent hourly salary, not 1x.
Why Your Salary Divided by 2,080 Is Wrong
As a full-time employee, your salary is just part of what you receive. Your employer also pays:
Base salary: $150,000
Employer FICA (7.65%): $11,475
Health insurance (employer share): $12,000
401k match (4%): $6,000
Paid time off (20 days): $11,538
Paid holidays (10 days): $5,769
Equipment and software: $3,000
Training and conferences: $2,000
Office space and overhead: $5,000
Disability and life insurance: $1,500
--------
True cost to employer: $208,282
Your employer pays roughly 150,000 salary. As a freelancer, you pay all of these costs yourself. If you charge $72/hour, you are taking a massive pay cut.
The 2-3x Rule
A practical starting point: multiply your equivalent hourly salary by 2.5.
Salary: $150,000
Hourly equivalent: $150,000 / 2,080 = $72/hour
Freelance rate: $72 x 2.5 = $180/hour
But this is just a starting point. Let us build the rate from the ground up to understand why the multiplier works.
Building Your Rate From the Ground Up
Start with what you want to take home, then add back every cost.
Step 1: Target Take-Home Pay
What do you want to earn after all expenses and taxes? Be honest. For this example, let us say $150,000 net.
Step 2: Add Self-Employment Tax
As a freelancer, you pay both the employee and employer portions of FICA. That is 15.3% on the first $168,600 (2024 threshold) and 2.9% above that.
Target income: $150,000
Self-employment tax: ~$21,000
Subtotal: $171,000
Step 3: Add Federal and State Income Tax
Your effective tax rate on $171,000 of self-employment income will be roughly 22-30% depending on your state.
Subtotal: $171,000
Income tax (~25%): $42,750
Subtotal: $213,750
Step 4: Add Benefits You Must Buy Yourself
Health insurance: $7,200/year ($600/month)
Retirement savings: $23,000/year (max 401k equivalent)
Disability insurance: $2,400/year
Life insurance: $600/year
Subtotal: $246,950
Step 5: Add Business Expenses
Software and tools: $3,000/year
Accounting and legal: $3,000/year
Coworking space: $3,600/year
Hardware: $2,000/year (amortized)
Professional development: $2,000/year
Subtotal: $260,550
Step 6: Divide by Billable Hours
Here is the critical part most people miss. You will not bill 2,080 hours per year. You will not bill 1,800. Realistically, a successful freelancer bills 1,000-1,400 hours per year.
Where does the time go?
Total work hours in a year: 2,080
Vacation (4 weeks): -160
Sick days and personal time: -40
Holidays: -80
Sales and business development: -200
Admin (invoicing, bookkeeping): -100
Learning and skill maintenance: -100
Unbillable gaps between projects:-200
-----
Realistic billable hours: 1,200
Step 7: Calculate Your Rate
Required gross revenue: $260,550
Billable hours: 1,200
Required hourly rate: $260,550 / 1,200 = $217/hour
That 200-220/hour to maintain the same lifestyle. Not $72.
Value-Based Pricing vs Hourly
Hourly billing has a fundamental problem: it penalizes you for being efficient. If you solve a problem in 2 hours that would take someone else 20 hours, hourly billing means you earn 10x less for delivering the same value. That is backwards.
When Hourly Works
- Long-term staff augmentation contracts (you are essentially a temporary employee)
- Maintenance and support work where scope is genuinely unpredictable
- Early client relationships where neither side knows the scope well
When to Use Value-Based Pricing
Value-based pricing means charging based on the value you create for the client, not the hours you spend.
Scenario: A client's deployment pipeline takes 4 hours per deploy.
Engineers deploy 3 times per week.
5 engineers x 4 hours x 3 deploys = 60 engineer-hours/week wasted
At $100/hour loaded cost = $6,000/week = $312,000/year
You can fix this in 2 weeks of work.
Hourly pricing: 80 hours x $200/hour = $16,000
Value pricing: $50,000 (still saves them $262,000/year)
The client is thrilled to pay 312,000 annually. You earn 3x more than hourly. Everyone wins.
How to Propose Value-Based Pricing
- Understand the client's problem and quantify the cost of not solving it
- Propose a fixed price that is a fraction of the value you deliver
- Define clear deliverables and scope boundaries
- Include a change order process for scope additions
Project-Based Pricing
A middle ground between hourly and value-based. You quote a fixed price for a defined scope of work.
Project: Build a customer data integration pipeline
Scope: Ingest from 3 sources, transform, load to data warehouse
Includes monitoring, documentation, and 2 weeks of support
Price: $35,000
Timeline: 4 weeks
The key to project pricing: add a buffer. Whatever you think the project will take, add 30-50%. Scope always expands. Requirements always change. Your buffer is not padding -- it is realism.
Estimated hours: 120
Buffer (40%): 48
Total hours: 168
At $200/hour: $33,600
Rounded to: $35,000
Protecting Yourself on Fixed-Price Projects
- Write a detailed scope document before quoting
- Specify exactly what is included and what is not
- Include a revision limit (e.g., "two rounds of revisions included")
- Add a change order clause: any work outside scope is billed hourly
- Get 30-50% upfront before starting work
Raising Your Rates
If you have been freelancing for a year and have more demand than you can handle, your rates are too low. Raising rates is uncomfortable but necessary.
For New Clients
Simply quote your new rate. No explanation needed. No apology. If you were charging 225/hour, just quote $225 to new prospects.
For Existing Clients
Give notice. A professional approach:
"Starting [date 60 days from now], my rate will be increasing
from $175/hour to $200/hour. I want to give you plenty of
notice so you can plan accordingly. I'm happy to discuss how
we can continue working together at the new rate."
Tips for raising rates with existing clients:
- Give 30-60 days notice
- Increase by 10-15% at a time, not 50% overnight
- Time it with a natural project boundary
- Some clients will leave. That is fine. Better clients will replace them at your new rate.
The Fear of Losing Clients
New freelancers dramatically overestimate how many clients they will lose to rate increases. Most clients who value your work will absorb a 10-15% increase without blinking. They know what it costs to find, vet, and onboard a replacement.
If a client balks at a reasonable rate increase, they were probably not a great client to begin with.
Rate Benchmarks for Engineers
Rates vary enormously by specialty, location, and experience. These are rough ranges for the US market:
Junior/generalist: $75 - $125/hour
Mid-level specialist: $125 - $200/hour
Senior specialist: $200 - $300/hour
Expert/niche: $300 - $500/hour
Fractional CTO/VP Eng: $250 - $400/hour
Specialties that command premium rates:
- Security and compliance (SOC2, HIPAA, FedRAMP)
- Infrastructure and DevOps (Kubernetes, cloud architecture)
- Machine learning and data engineering
- Performance optimization
- Legacy system migration
Retainer Agreements
A retainer is a guaranteed monthly payment in exchange for availability. This is the holy grail of freelancing because it provides income predictability.
Example retainer:
$8,000/month for up to 40 hours of work
Hours roll over for one month
Unused hours are not refunded
Additional hours billed at $225/hour
Retainers work well for:
- Ongoing advisory and architecture review
- On-call support for critical systems
- Fractional CTO or tech lead roles
The client gets priority access to you. You get predictable income. Structure the retainer so the effective hourly rate is slightly below your standard rate -- the client gets a discount for the commitment, and you get stability.
Common Pitfalls
- Dividing your salary by 2,080 to get your rate. This ignores taxes, benefits, unpaid time, and expenses. You will earn 40-60% less than your old salary.
- Competing on price. If a client picks the cheapest freelancer, they are not your client. Compete on expertise, reliability, and outcomes.
- Not tracking your actual billable hours. You cannot set accurate rates if you do not know how many hours you actually bill per year. Track everything.
- Quoting a fixed price without a detailed scope document. This is how you end up working 300 hours on a "small project" for $15,000.
- Being afraid to say your rate out loud. Practice it. "$200 per hour." Say it until it feels normal. If you flinch when you say your rate, clients will sense it.
- Discounting for "exposure" or "future work." Exposure does not pay rent. Future work is not guaranteed. Charge your rate.
- Not raising rates annually. Inflation alone justifies a 3-5% increase every year. If your skills and demand are growing, increase by more.
Key Takeaways
- Your freelance rate should be 2-3x your equivalent hourly salary, not 1x
- A realistic freelancer bills 1,000-1,400 hours per year, not 2,080
- Build your rate from the ground up: target income + taxes + benefits + expenses, divided by billable hours
- Use value-based or project pricing when possible -- hourly billing penalizes efficiency
- Always include a 30-50% buffer on fixed-price projects and a change order clause
- Raise rates for existing clients with 30-60 days notice, 10-15% at a time
- If you have more demand than capacity, your rates are too low