Why Pricing Is the Hardest Part of Freelancing
Most IT freelancers are technically excellent but commercially uncertain. Undercharging is rampant — partly from imposter syndrome, partly from not knowing the market, and partly from fear of losing work. This guide gives you a systematic way to set rates you can actually defend.
Step 1: Calculate Your Floor Rate (The Number You Cannot Go Below)
Before setting any rate, you need to know your minimum viable hourly rate. This is the rate below which you're actually losing money once you account for:
- Living expenses — rent, food, utilities, insurance
- Business expenses — software subscriptions, hardware, professional development
- Tax obligations — self-employment tax is higher than employee tax; set aside 25–35% depending on your jurisdiction
- Non-billable time — admin, sales, marketing, and learning time (typically 30–40% of your working hours)
- Unpaid vacation / sick time — you don't get this automatically as a freelancer
Formula: (Annual expenses + desired salary + tax buffer) ÷ billable hours per year = your floor rate
If you work 40 hours/week but only 60% is billable, that's roughly 1,250 billable hours per year. If you need $80,000 net after all expenses, your floor rate is about $64/hour before tax considerations are fully accounted for.
Step 2: Research the Market
Your floor rate tells you the minimum — market research tells you what's possible. Research rates for your specific skill set and region:
- Check platforms like Upwork, Toptal, and Contra for posted rates
- Ask in developer/freelancer communities (Reddit r/freelance, relevant Discord servers)
- Review salary data on Glassdoor and Levels.fyi and apply a freelance multiplier (typically 1.5–2.5× employee rates to account for benefits, overhead, and instability)
Hourly vs. Project-Based Pricing
| Factor | Hourly Rate | Project/Fixed Rate |
|---|---|---|
| Risk | Client bears scope risk | You bear scope risk |
| Best for | Ongoing, unclear, or evolving work | Well-defined, bounded projects |
| Earning potential | Capped by hours worked | Higher if efficient |
| Admin overhead | Requires time tracking | Requires detailed scoping |
| Client preference | Budget uncertainty | Budget certainty |
For most IT freelancers early in their career, hourly is safer. As you gain experience scoping projects accurately, fixed-price work can be significantly more profitable.
How to Handle Rate Negotiations
- Always quote first — Let them react, not anchor you. When a client asks your rate, give it confidently.
- Justify with value, not time — "This integration will save your team 10 hours a week" is more compelling than "I charge $120/hour."
- Offer scope reduction, not rate reduction — If a client pushes back on price, offer to remove deliverables rather than cutting your rate.
- Have a walk-away point — Know the number below which you'll politely decline. Projects below your floor rate aren't just unprofitable — they crowd out better opportunities.
Common Pricing Mistakes to Avoid
- Charging "what feels comfortable" — This usually means undercharging. Base rates on math, not feelings.
- Discounting for "exposure" — Exposure doesn't pay rent.
- Forgetting scope creep — On fixed projects, every additional request is a change order. Document scope clearly upfront.
- Not raising rates — Review your rates at least annually. As your skills grow, your rates should too.
When to Raise Your Rates
You should raise your rates when: you're winning more than 80% of proposals (demand exceeds supply), you've added significant new skills or certifications, you've taken on higher-complexity work, or it's simply been more than 12 months since your last increase.
Final Thought
Pricing is a skill, and like all skills, it improves with practice. Start with honest math, research your market, and remember that low rates attract difficult clients. Value-conscious clients who pay fair rates are almost always a better experience than bargain-hunters.