How Much Should You Actually Charge? A Developer's Math for Setting Freelance Rates

You've built something people want. Clients are asking for your help. And then comes the question that makes your stomach tighten: "What do you charge?"

Most freelance developers answer by looking at what others are charging, checking what their friends make, or worse—picking a number that feels vaguely reasonable and hoping it doesn't scare clients away. The result? You end up either undercharging (and wondering why you're working 60-hour weeks on poverty wages) or overcharging (and losing deals to competitors with better marketing).

There's a better way. Instead of starting with market rates, you start with the only number that actually matters: how much money do you need to make this quarter?

This is the difference between guessing and planning. And it's the foundation of sustainable freelance income.

The Problem With Market-Rate Thinking

Let's be honest: market rate advice is mostly useless for solo developers.

You'll read that "junior developers charge $25–50/hour," "mid-level developers $50–100/hour," and "senior developers $100–150+/hour." These numbers appear everywhere—on Upwork's cost-to-hire guides, in global surveys of freelance developer costs, and in countless freelance rate guides. And they're not wrong, exactly. But they're not right for you, either.

Why? Because market rates are averages. And averages don't account for:

• Your actual business expenses. If you're in San Francisco and your competitor is in Mumbai, you're not operating in the same economy. Rent, taxes, health insurance, and software subscriptions are wildly different.
• Your real utilization rate. Market rates assume you're billable 40 hours a week, every week. In reality, you spend time on admin, sales, learning, and—inevitably—downtime between projects.
• Your income goal. Maybe you want to make $80k/year. Maybe you want $200k. Market rates don't care about your target.
• Your risk tolerance. Freelance income is lumpy. You need a buffer for slow months, unexpected expenses, and the fact that not every hour you work gets paid.

So when you anchor your rate to "what the market says," you're starting from a place that has nothing to do with your actual situation.

The smarter approach? Reverse-engineer your rate from your income goal. Start with the number you actually need to make, then work backward to figure out what hourly or project rate gets you there.

The Core Math: From Annual Goal to Hourly Rate

Here's the framework. It's simple, but it forces you to think clearly about what you're actually trying to accomplish.

Step 1: Define your annual income target.

This is the number you want to take home after expenses, taxes, and everything else. Not revenue—net income. The money that actually lands in your account.

Let's say you want to make $100,000/year. That's your starting point.

Step 2: Account for taxes and business expenses.

If you're a freelancer or solo founder, you're self-employed. That means you pay both halves of Social Security and Medicare (the employer and employee portions), plus income tax. In the U.S., that's roughly 25–30% of your gross income, depending on your tax bracket and deductions.

You also have business expenses: software subscriptions, professional development, equipment, accounting, insurance, and the occasional contractor. For a solo developer, this is often $5,000–15,000/year, depending on your setup.

Let's say you target 30% for taxes and $10,000/year for expenses. Here's the math:

• Income goal: $100,000
• Expenses: $10,000
• Subtotal needed: $110,000
• Divide by 0.7 (to account for 30% taxes): $157,000 in gross revenue

So you need to generate $157,000 in billable revenue to take home $100,000.

Step 3: Calculate your billable hours per year.

This is where most freelancers get it wrong. They assume they can bill 2,000 hours/year (40 hours/week × 50 weeks). But that's not realistic.

You don't work 40 billable hours every week. You spend time on:

• Admin and operations: invoicing, contract negotiation, bookkeeping, email
• Sales and business development: networking, proposals, discovery calls
• Learning and professional development: staying current with tools, languages, frameworks
• Downtime and transitions: gaps between projects, client delays, the time it takes to ramp up

For a solo developer, a realistic billable hour target is 60–70% of your available working hours. If you work 50 weeks/year at 40 hours/week, that's 2,000 hours available. At 65% utilization, you're looking at roughly 1,300 billable hours/year.

Some weeks you'll bill more. Some weeks you'll bill less. But 1,300 is a conservative, realistic target.

Step 4: Divide revenue needed by billable hours.

$157,000 ÷ 1,300 billable hours = $120.77/hour

That's your break-even hourly rate. This is the rate you need to hit your income goal, assuming 65% utilization and your stated expenses and tax burden.

Adjusting for Project-Based Work

Not every freelancer charges hourly. Many solo developers prefer project-based pricing—a flat fee for a defined scope.

The math here is different, but the logic is the same.

Let's say you want to do four projects/year, each taking 200 hours. That's 800 billable hours. Using the same revenue target ($157,000), your project rate would be:

$157,000 ÷ 4 projects = $39,250/project

Or, if you want to think of it in terms of your effective hourly rate: $39,250 ÷ 200 hours = $196.25/hour.

Notice that's higher than the hourly rate. Why? Because project-based work has different risks:

• Scope creep. Clients ask for "one more thing," and suddenly you're 40 hours over budget.
• Estimation risk. You might underestimate how long something takes.
• Revision cycles. More back-and-forth, more iterations, more time.

So you build in a buffer. A common approach is to estimate the hours, multiply by your hourly rate, then add 20–30% for risk and contingency. Or, you charge a flat fee that's higher than hours × hourly rate.

The key insight: your project rate should reflect your hourly rate, plus a buffer for the unique risks of project-based work.

Real-World Adjustments: Complexity, Expertise, and Market Position

The math above gets you to a defensible baseline. But there are legitimate reasons to adjust up or down.

Complexity and Specialization

If you're working with cutting-edge tech, managing complex systems, or solving hard problems, you can charge more. Not because the market says so, but because:

• You've invested time (and money) building expertise.
• You can solve problems faster than generalists.
• You reduce client risk by knowing the pitfalls.

Look at guides on freelance web developer rates and you'll see clear tiers: junior developers, mid-level, senior, and specialists. The difference isn't arbitrary. A senior developer who's spent five years optimizing React performance can solve in 10 hours what takes a junior developer 40 hours. The client gets more value; you should capture some of that.

If your expertise is rare or in-demand, add 20–50% to your baseline rate.

Retainer vs. Project Work

Retainer clients (where you bill a flat monthly fee for ongoing work) are more valuable than one-off projects, even if the hourly rate is lower. Why?

• Predictable revenue. You know what you're making next month.
• Lower sales overhead. No constant hunt for new clients.
• Deeper relationships. You understand their codebase, their processes, their preferences.

Many solo developers charge 10–20% less for retainer work because the stability is worth it. Calculating freelance web developer rates often factors in this trade-off.

If you're building a retainer-heavy business, you might set your baseline rate slightly lower, knowing that the recurring revenue and reduced sales cost more than make up for it.

Geographic and Market Factors

Yes, location matters—not because clients care where you are (many don't), but because your cost of living does.

If you're in San Francisco or New York, your rent, taxes, and general cost of living are 2–3× higher than in rural areas or lower-cost countries. Your rate should reflect that. Global surveys of freelance developer costs show this clearly: developers in the U.S. and Western Europe charge $80–150/hour, while equally skilled developers in Southeast Asia charge $15–40/hour.

But here's the thing: if you're a U.S.-based developer competing for clients in the U.S. market, you should charge U.S. rates. Your cost of living is what it is. Undercutting to compete with cheaper markets is a losing game—you'll just work yourself to exhaustion.

The Utilization Reality Check

This is the part where most freelancers lie to themselves.

You calculate your rate based on 1,300 billable hours/year. But then you only actually bill 900 hours. Why? Because:

• You had a slow month and spent time on admin instead of sales.
• You took on a project that ran over, eating into your available time.
• You spent three weeks learning a new framework.
• A client delayed a project, leaving you with a gap.

If your actual utilization is lower than your target, your effective hourly rate drops. Let's say you target $120/hour but only bill 900 hours/year:

900 hours × $120/hour = $108,000 gross revenue

After taxes and expenses, that's closer to $70,000 take-home. Not $100,000.

So you have three options:

1. Raise your rate. If you're consistently underutilized, a higher rate (say, $160/hour) gets you closer to your goal, even with lower billable hours.
2. Improve utilization. Invest in sales, marketing, and processes that keep you booked. Use tools and automation to reduce admin time.
3. Accept lower income. Be realistic about what you can actually achieve, and adjust your target accordingly.

This is where Cashierr comes in. Instead of guessing whether you'll hit your revenue goal, you can track your actual billable hours, project pipeline, and client concentration in real time. The app's agents flag when you're on pace to miss your quarterly target, so you can adjust before it's too late—raise rates, take on more clients, or reduce expenses.

The Client Concentration Problem

Here's a scenario that breaks a lot of freelancers: you land a big client. They're paying you $80k/year. You're thrilled. You adjust your rates down slightly because you have steady income.

Then the client cuts their budget. Or they hire someone in-house. Or they go out of business.

Suddenly, you've lost 40% of your annual revenue, and you have no pipeline to replace it.

This is the client concentration risk. And it's one of the biggest threats to freelance income stability.

The math here is simple: no single client should represent more than 20–30% of your annual revenue. If they do, you're taking on too much risk. If that client leaves, you're in crisis mode.

When you're setting rates and planning your business, you need to account for this. If you want $157,000 in gross revenue, you shouldn't rely on one client for $50k. You should have:

• 3–5 retainer clients at $20–30k/year each
• 2–4 project clients at $15–25k/year each
• Some mix that keeps any single client under 30% of revenue

This means you might need a slightly higher rate to make it work with more clients (because each relationship has some overhead), but the stability is worth it.

Pricing Strategies: Hourly, Project, and Hybrid

Once you've calculated your baseline rate, you need to decide how to present it to clients.

Hourly Rates

Pros:

• Simple to communicate and invoice
• Fair if scope is truly unclear
• Easy to track and adjust

Cons:

• Clients hate open-ended costs
• Incentivizes you to work slowly (perverse incentive)
• Hard to sell value; it's just hours × rate

When to use: Early-stage projects where scope is genuinely uncertain, retainers, or when you're working closely with a client and they want flexibility.

Project-Based (Fixed-Fee) Pricing

Pros:

• Clients know the total cost upfront
• Incentivizes you to work efficiently
• Easier to sell and close deals
• Higher perceived value

Cons:

• Requires accurate estimation
• Scope creep kills profitability
• Riskier if requirements change

When to use: Well-defined projects with clear scope, repeat work you've done before, or when you want to emphasize efficiency and value.

Hybrid (Retainer + Hourly or Project)

Structure:

• Base retainer for ongoing support, maintenance, and availability
• Hourly or project rates for work beyond the retainer scope

Example:

• $3,000/month retainer for 40 hours of support, updates, and minor features
• $150/hour for work beyond 40 hours

This is often the sweet spot for solo developers. It gives you predictable revenue while allowing you to capture value from bigger projects.

The Discount Trap

At some point, a client will ask for a discount. "Can you do it for 10% less?" Or they'll say, "We're a startup, can you give us a break?"

Here's the hard truth: if you discount, you're not actually lowering the price. You're lowering the value you place on your work. And once you've done it, it's almost impossible to raise rates later.

Practical guides on calculating freelance web development pricing often mention discount strategies, but the real strategy is not to discount at all. Instead:

• Adjust scope. "I can do a simpler version for less."
• Extend timeline. "I can fit this in Q3 instead of Q2 for a lower rate."
• Offer payment terms. "If you pay upfront, I can offer a 5% discount."
• Walk away. "That doesn't work for my business model, but here's someone who might help."

Discounting trains clients to expect it. It erodes your margins. And it signals that you're not confident in your value.

Building Your Rate Into Your Business Plan

Once you've set your rate, the next step is planning around it. This is where most solo developers fail.

You set a rate of $120/hour, but you don't have a plan for hitting 1,300 billable hours/year. You don't know how many clients you need, what size projects, or what your pipeline looks like. So you end up taking whatever work comes, at whatever rate you can negotiate, and wondering why you're not hitting your income goal.

Instead, think about it like this:

If I charge $120/hour and want $157,000 in gross revenue, I need:

• 1,300 billable hours/year
• ~110 billable hours/month
• ~25 billable hours/week

That means:

• Option A: 1 retainer client at 25 hours/week ($120/hour = $3,000/week = $12,000/month)
• Option B: 2–3 project clients, averaging 8–12 hours/week each
• Option C: Mix of retainers and projects

Once you know your target, you can build a sales and marketing plan around it. You know exactly how many clients you need, what size projects, and what your pipeline should look like.

Cashierr helps you track this. Instead of hoping you'll hit your revenue goal, you can see your projected quarterly revenue, gap-to-goal, and which clients are on track. The app's agents flag when you're falling behind, so you can take action before it's too late.

The Confidence Factor

Here's something nobody talks about: your rate is also a signal of confidence.

When you charge $50/hour, clients assume you're junior or desperate. When you charge $150/hour, they assume you're experienced and in-demand. Neither assumption is necessarily true, but rates create perception.

This is why Forbes' guide on pricing freelance services emphasizes value-based pricing: you're not selling hours, you're selling outcomes.

Once you've calculated your rate based on your income goal and business model, own it. Don't apologize for it. Don't discount it. If a client can't afford it, they're not your client.

The right clients—the ones who value your work and respect your time—will happily pay your rate. The ones who won't? They're usually the ones who cause headaches anyway.

Quarterly Planning and Adjustment

Your rate isn't set in stone. You should revisit it every quarter.

Have you hit your billable hour target? Are you consistently booked or struggling to find work? Have your expenses changed? Has your income goal shifted?

Every quarter, ask yourself:

1. Did I hit my billable hour target? If not, why? Do you need to improve sales, reduce scope, or raise rates?
2. What's my projected revenue for the quarter? Based on current projects and pipeline, will you hit your goal?
3. Is my rate still appropriate? Have your skills improved? Has the market shifted? Do you need to adjust?
4. What's my client concentration? Are you too dependent on one or two clients?

This is where Cashierr becomes invaluable. Instead of manually tracking projects and revenue, the app aggregates your data and shows you exactly where you stand. The AI agents answer the questions you should be asking: "How much am I on track to make this quarter?" and "What gaps do I need to close?"

Common Pricing Mistakes to Avoid

Mistake #1: Setting rates based on what competitors charge

Your competitor's rates don't matter. Their cost of living, their business model, their income goal—all different from yours.

Set rates based on your actual situation, not theirs.

Mistake #2: Underestimating expenses and taxes

Most freelancers are shocked when tax time comes around. They made $100k in revenue but owe $25k in taxes, plus they've spent $8k on software and equipment.

Build these into your rate from day one.

Mistake #3: Assuming 100% utilization

You will not bill 40 hours every week. You will have admin time, downtime, and slow periods. Plan for 60–70% utilization, not 100%.

Mistake #4: Forgetting about cash flow

You might invoice $157,000/year, but if clients pay 60 days late, you'll have cash flow problems. Build in a buffer, use tools like Wave or Freshbooks for invoicing, and consider requiring deposits or milestone payments.

Mistake #5: Not adjusting as you grow

Your rate should increase as you gain experience, build a reputation, and take on more complex work. Review your rate annually and raise it if you've earned it.

Putting It All Together: Your Rate-Setting Worksheet

Here's a simple framework to calculate your rate:

1. Annual income goal: $______

2. Business expenses (annual): $______

3. Tax rate (estimate 25–30%): ______%

4. Gross revenue needed: (Income goal + Expenses) ÷ (1 - Tax rate) = $______

5. Billable hours per year (estimate 60–70% of available hours): ______

6. Hourly rate: Gross revenue ÷ Billable hours = $______/hour

7. Adjustments: - Specialization/expertise: +_____% - Market position: +_____% - Retainer discount: -_____% - Final rate: $______/hour

8. For project-based work: Estimated hours × Hourly rate × 1.25 (buffer) = $______/project

Once you've done this math, you have a defensible, sustainable rate. Not based on guessing or market averages, but on your actual business needs.

Beyond the Rate: Building a Sustainable Business

Setting the right rate is the foundation. But it's only the beginning.

Once you know your rate, you need to:

• Build a pipeline. Know how many clients you need and what size projects, so you're not scrambling for work.
• Track your metrics. Billable hours, project revenue, client concentration, cash flow. You can't manage what you don't measure.
• Adjust quarterly. Review your progress, update your forecast, and take action if you're off track.
• Invest in your business. Tools, education, marketing. These aren't expenses; they're investments in your ability to charge higher rates.

Tools like Harvest and Bonsai can help with time tracking and invoicing. But for the bigger picture—understanding whether you're on track to hit your revenue goal, spotting client concentration risk, and planning ahead—you need something more.

That's where Cashierr comes in. It's built specifically for solo developers and freelancers who want to answer two questions: "How much should I be making?" and "How's the business actually doing?" The app's AI agents track your goals, project your revenue, and flag gaps before they hurt.

The Bottom Line

You shouldn't charge what the market says. You should charge what you need to make to hit your income goal, run a sustainable business, and not work yourself to exhaustion.

Start with your target income. Work backward through taxes, expenses, and realistic utilization. Land on a rate. Own it. Build your business around it.

Then track it. Quarterly. Adjust as needed.

That's how you move from guessing to planning. From "I hope this works out" to "I know exactly where I stand."

And that's the difference between a freelance gig and an actual business.