Learn how to work backward from your desired lifestyle to set a realistic hourly rate. The complete guide for solo developers to calculate income targets.
You've probably done this dance a hundred times. A potential client asks your rate. You either throw out a number you half-remember from the internet, or you do that awkward pause-and-think thing where you're trying to reverse-engineer a price on the fly. Neither feels right.
Here's the thing: most freelance developers price backward. They start with what they think the market will bear, or what they saw someone else charge, or what sounds "professional enough." Then they hope that number somehow covers their actual life.
It almost never does.
The real move—the one that actually works—is to flip the script entirely. Start with the life you want to live, the expenses that life requires, and the taxes you'll actually owe. Then work backward through your business capacity to find the hourly rate that makes sense. This is reverse-engineering, and it's the only way to price yourself with confidence instead of anxiety.
This guide walks you through that math, step by step, using real numbers and the occasional hard truth. By the end, you'll know exactly what you need to charge—and more importantly, you'll understand why that number isn't negotiable.
Before we touch the numbers, let's name the real problem. You're not just trying to figure out an hourly rate. You're trying to answer two deeper questions:
"How much should I actually be making this quarter?" This isn't about greed. It's about whether your business is on track to fund the life you're building—the apartment, the equipment, the time off, the financial security.
"How's my business actually doing?" You need to know if you're profitable, if you're vulnerable to losing one client, if you're working 60 hours a week for poverty wages, or if you've actually built something sustainable.
These questions are hard to answer when you're bouncing between client emails, debugging code, and staring at a spreadsheet that never feels complete. That's where the reverse-engineering framework comes in. It gives you a North Star.
Tools like Cashierr exist specifically to turn this backward math into a living, breathing plan—one that tracks your actual revenue, flags gaps before they hurt, and tells you whether you're on pace to hit your targets. But first, you need to understand the framework itself. That's what we're building here.
This is the hardest part, and it's the most important. You need to know what you actually spend money on. Not what you think you spend. Not what you should spend. What you do spend, plus what you want to spend.
Break this into two buckets:
Essential expenses. These are the non-negotiables: rent or mortgage, utilities, insurance, food, transportation, phone, internet. If you have dependents, add childcare. If you have debt, add minimum payments. If you're saving for something specific (a house down payment, a sabbatical, a new laptop), add that too.
Discretionary expenses. This is where most people lie to themselves. Coffee, dining out, travel, hobbies, subscriptions, gifts, home improvements. Be honest. If you spend $200 a month on coffee and craft beer, write down $200. If you take one international trip a year, calculate the annual cost and include it. If you want to work three days a week instead of five, that's a lifestyle choice with a real cost—it means less billable time.
Add them together. Let's say your number is $5,000 a month. That's $60,000 a year in actual spending.
But that's not your income target yet. You still have to pay taxes.
Here's where most freelancers get blindsided. When you're an employee, your employer withholds taxes. You see a paycheck and it's already been handled. When you're freelance, you earn gross revenue, and taxes are your problem.
As a solo programmer, you're likely a sole proprietor or an S-corp. That means:
Self-employment tax (Social Security + Medicare): roughly 15.3% of your net profit. You pay both the employer and employee side.
Income tax: federal (10–37% depending on bracket), state (0–13% depending on where you live), and sometimes local. This stacks on top of self-employment tax.
Effective tax rate for a freelancer: somewhere between 25% and 50% of gross revenue, depending on your location, profit level, and deductions. A reasonable estimate for most solo developers is 30–40%.
Let's work with 35% as a middle ground. If you need $60,000 to live on, and 35% goes to taxes, you need to earn:
$60,000 ÷ 0.65 = $92,308 in gross revenue.
That's your baseline. Before you even think about business expenses, growth, or padding for slow months.
Some resources like How Much Income Do You Need? and Financial Goal Definition walk through this calculation in more detail, though they typically assume W-2 employment. The freelance version is more aggressive because you're covering both sides of the tax bill.
Now subtract your actual business costs. These are the things you spend money on to run your freelance operation:
So your actual income requirement is:
$92,308 (after-tax living expenses) + $5,000 (business expenses) = $97,308 in gross annual revenue.
But there's one more layer. You're not working 52 weeks a year, and you're not billable 100% of the time.
Here's where the math gets real. You can't work 40 hours a week and bill 40 hours a week. There's admin time, client management, proposal writing, invoicing, financial tracking, and the occasional panic when your main client goes quiet.
Most solo developers are realistically billable 25–32 hours per week. Let's use 30 as a reasonable target.
But you also take time off. Vacation, sick days, holidays, the occasional mental health day. If you take 3 weeks off a year (which is reasonable), you're working 49 weeks.
30 billable hours/week × 49 weeks/year = 1,470 billable hours per year.
Now divide your revenue requirement by your billable hours:
$97,308 ÷ 1,470 hours = $66.20 per hour.
There's your number. That's what you need to charge—not what you could charge, but what you must charge to fund your actual life and run your actual business.
If that feels low, you're probably underestimating your expenses or overestimating your billable capacity. If it feels high, you might be able to work more hours, take fewer days off, or cut some discretionary spending.
That $66.20/hour is your break-even rate. It's the minimum. But it assumes perfect conditions:
$66.20 × 1.35 = $89.37 per hour, rounded to $90 or $95.
That's your real number. Not a guess. Not what someone on the internet said. Your actual, defensible, math-backed hourly rate.
Resources like How To Calculate Your Hourly Rate As A Freelancer and How To Calculate Your Target Hourly Rate walk through similar frameworks, though they may not account for the full self-employment tax burden that solo developers face.
Once you know your hourly rate, you can set meaningful quarterly targets. This is where the planning actually becomes useful.
If you charge $90/hour and you're targeting 30 billable hours per week:
Per week: $90 × 30 = $2,700 Per quarter (13 weeks): $2,700 × 13 = $35,100 Per year: $2,700 × 52 = $140,400
But remember—that's gross revenue. After taxes and business expenses, you'll keep roughly 60–65% of that, which should cover your living expenses and give you a real profit margin.
This is the number you should be tracking every month. Not "how much did I invoice," but "am I on pace to hit my quarterly target?" If you're halfway through Q1 and you've only billed $15,000 instead of $17,500, you know you need to either pick up more work or adjust your timeline.
Tools designed specifically for this—Cashierr's revenue planning and forecasting capabilities let you set these targets, track actual revenue against them, and see the gaps before they become problems. But you don't need fancy software to do this. A spreadsheet works fine if you update it weekly.
Here's a hard truth: if one client represents more than 30–40% of your revenue, you're taking on serious risk. If they cut you off, reduce scope, or go under, your business collapses.
This is a hidden cost of the reverse-engineering framework. When you calculate that you need $90/hour, you're assuming you'll consistently find clients at that rate. But if you're dependent on one big client, you lose negotiating power. You become an employee without benefits.
The math here is simple: if you need $140,400 in annual revenue and you have one client paying $50,000/year, that client represents 36% of your income. You're vulnerable.
The solution is to deliberately diversify. Aim to have no single client be more than 25–30% of your revenue. This means you need to:
The framework above works for a solo developer with a standard lifestyle and moderate expenses. But your situation might be different. Here's how to adjust:
If you have high fixed costs (mortgage, dependents, student loans): your baseline living expenses are higher, which means your hourly rate needs to be higher. Do the math with your actual numbers, not estimates.
If you want to work fewer hours: this is a lifestyle choice, and it's valid. But it means your hourly rate needs to be higher to compensate. If you want to work 20 hours/week instead of 30, divide by 1,040 billable hours instead of 1,470. Your rate goes up proportionally.
If you want to build a savings cushion or invest in growth: add that to your living expenses. If you want to save $20,000/year, add it to your baseline. This is how you fund sabbaticals, equipment upgrades, and business experiments.
If you're in a high-tax state or country: adjust your tax rate accordingly. California, New York, and many other states have higher income taxes. Some countries have VAT or different self-employment structures. Know your actual tax burden.
If you're scaling toward a team: the math changes significantly. You'll need higher revenue to cover salaries, but your billable hours might go down (because you're managing instead of coding). Plan for this explicitly.
Here's what happens when you reverse-engineer your rate instead of guessing:
You stop feeling guilty about charging what you're worth. You're not picking a number out of thin air. You've done the math. You know what your life costs. You know what your business needs. You know what you deserve.
This is powerful. It changes how you talk to clients. Instead of "my rate is $90/hour, but I could probably do it for less," you say "my rate is $90/hour, and here's why." Confidence sells. Desperation doesn't.
It also changes how you make business decisions. When a client offers you $60/hour, you don't have to agonize. You know it's below your number. You can either decline or negotiate. When a client offers $120/hour, you know you have room to say yes and still be profitable.
Most importantly, it forces you to think like a business owner instead of a freelancer. A freelancer sells hours. A business owner sells outcomes and manages capacity. Once you know your true cost per hour, you can start thinking about how to increase the value you deliver per hour—through better estimates, faster execution, productized services, or retainers. That's where real profitability lives.
Once you've set your rate and your quarterly targets, the work is just beginning. You need to know, every month, whether you're on pace.
Here's the minimum you need to track:
That's what Cashierr's agentic forecasting does. It's not just tracking. It's planning. It answers the question "how's the business actually doing?" not just "how much did I bill last month?"
But whether you use a tool or a spreadsheet, the discipline is the same: know your targets, track your progress, and adjust when reality diverges from the plan.
Before you lock in your rate, watch out for these:
Underestimating living expenses. People are terrible at knowing what they actually spend. Go back through three months of bank and credit card statements. Add up every category. You'll probably find you spend 20–30% more than you thought.
Forgetting taxes. This is the biggest mistake. Developers often calculate their rate as if they're employees, forgetting that they pay both sides of the payroll tax. Don't make this error. Your effective tax rate as a freelancer is significantly higher.
Overestimating billable hours. You're not working 40 billable hours a week. You're probably working 25–30, if you're honest. Factor in client meetings, proposal writing, invoicing, admin, and the occasional slow week. Use conservative estimates.
Not accounting for time off. If you take 4 weeks of vacation a year (which is reasonable), you have 48 working weeks, not 52. If you don't account for this, your rate will be 8% too low.
Ignoring seasonal variation. Some months you'll have more work than you can handle. Some months will be quiet. Your rate needs to average across the whole year, not just the busy months.
Skipping the buffer. Your break-even rate is not your selling rate. You need 20–50% margin for reality, growth, and profit. Don't be tempted to quote your break-even number.
Your rate and targets shouldn't be set in stone. Every quarter, do a quick review:
Tools like How Much Do I Need to Retire? and How Much Money Do You Need to Retire? approach this from a long-term perspective, but the principle is the same: know what you need, calculate what you need to earn, and adjust when circumstances change.
Once you've reverse-engineered your hourly rate and proven you can hit your targets, you're in a position to think bigger. Most solo developers eventually move away from pure hourly billing toward retainers or productized services. Here's why:
Retainers give you predictable revenue. Instead of billing 30 hours/week at $90/hour, you bill a flat $3,000/month for 20–25 hours. This is less total revenue, but it's more stable and requires less admin.
Productized services let you standardize your offering and increase your value per hour. Instead of custom development, you offer "website migration" or "performance optimization" as a fixed-price product. You do the work faster because you've done it 50 times, and you charge more because you're delivering a proven outcome.
Both of these require you to first know your baseline rate. You can't price a retainer if you don't know what your time is worth. You can't price a product if you don't know your cost structure.
This is the real power of reverse-engineering: it's not just about setting an hourly rate. It's about understanding your business fundamentals deeply enough to evolve beyond hourly billing into more sustainable models.
Knowing your hourly rate answers one question: "How much should I charge?" But it's connected to the two bigger questions we started with:
"How much should I be making this quarter?" Now you know. It's your hourly rate × your billable hours × the number of weeks in the quarter. Track it. Adjust if you're off pace.
"How's the business actually doing?" Now you can answer this too. If you're hitting your quarterly targets, your margins are healthy, and your clients are diversified, the business is doing well. If you're missing targets, your margins are thin, or one client is carrying too much weight, you have work to do.
These aren't abstract questions. They determine whether you can take time off, invest in your business, save for the future, or sleep at night. They're the foundation of a sustainable freelance career.
Here's what to do, starting today:
When you reverse-engineer your rate, you move from hoping to knowing. You move from anxiety to confidence. You move from wondering "am I making enough?" to knowing exactly what you need and whether you're on track to get it.
That clarity is worth more than any hourly rate increase. Because once you know what you need, you can stop second-guessing yourself and start building a business that actually works.
Master the 3-bucket system for solo developers: operating, tax, and profit accounts. Stop leaving money on the table and make tax season painless.
Master your solo dev finances in 30 minutes every Friday. Track revenue, expenses, goals, and cash flow with this step-by-step ritual.
Master revenue forecasting by tracking just 5 metrics. Learn which data points drive 80% of forecast accuracy for freelance developers.