When to Raise Your Rates (And the Email Template That Actually Works)

You've been charging the same rate for eighteen months. Your skills have gotten sharper. Your clients trust you more. But your hourly rate? Still the same number you nervously quoted when you were first starting out.

The spreadsheet doesn't lie: you're working harder than ever, but your quarterly revenue projections aren't moving. And that's the real problem. Raising your rates isn't about greed or ego—it's about making sure your business actually sustains itself, that you're not burning out for peanuts, and that you can answer the question every solo programmer secretly asks: How much should I actually be making this quarter?

This guide walks you through the exact signals that tell you it's time, the math behind a fair increase, and the message that lands with clients so you don't lose them in the process.

The Real Cost of Staying Flat

Here's what happens when you don't raise your rates: inflation eats your margins silently. Your costs go up—software subscriptions, hardware, maybe a better coworking space. But your hourly rate stays frozen. That's a pay cut in real terms, and you probably haven't even noticed it yet.

Beyond inflation, there's the opportunity cost. Every hour you spend on a client paying you the old rate is an hour you're not spending on a client who'd pay more, or on building a product, or on anything that compounds. When you're a solo programmer, your time is literally your only asset. Pricing it wrong doesn't just hurt this quarter—it shapes every quarter after.

There's also a psychological component that most solo devs don't talk about. When you undercharge relative to your skills and market value, you unconsciously start to resent the work. Clients sense that resentment. The relationship gets weird. You start cherry-picking projects or dodging communication. Raising your rates actually improves the work because you're not secretly bitter about what you're being paid.

The good news: you have more leverage to raise rates than you think. Your existing clients have sunk cost in you—they know how you work, they trust your delivery, they've already paid the switching cost of finding you. That's your moat. Use it.

Five Clear Signals It's Time to Raise Your Rates

You don't raise rates on a whim. There are specific, measurable signals that tell you the market and your business are ready. Look for these:

1. You Haven't Raised Rates in Over a Year

This is the simplest signal. If your rates have been unchanged for 12+ months, five key indicators suggest you should raise them, including the fact that unchanged rates for over a year is a red flag. Inflation alone—roughly 3% annually in normal years—means you're effectively taking a pay cut. But this isn't just about inflation. It's about market movement. Salaries for junior developers have climbed. Freelance rates have climbed. Your skills have improved. Staying flat is falling behind.

2. You're Fully Booked or Turning Away Work

If you're at capacity and still have qualified leads asking for your time, you're leaving money on the table. This is the clearest signal. When demand exceeds supply, price goes up—that's basic economics. Being fully booked is one of the most obvious signs that it's time to raise rates, as it indicates strong demand for your services.

What does "fully booked" mean? It means you're at the capacity you've decided you want to work at. If you're consistently turning away work or have a waiting list, you're underpriced. A rate increase serves two purposes: it brings in more revenue per hour, and it naturally filters out price-sensitive clients, creating space for better-fit clients at higher rates.

3. Your Costs Have Gone Up

Your business expenses have probably increased. New tools, better hardware, maybe you upgraded your internet or moved to a quieter workspace. Clients don't see these costs, but they're real. If you're spending more to deliver the same service, your rates need to move up to maintain your margin. Key considerations for price increases include accounting for increased costs in your business.

Don't just think about direct costs. Think about the infrastructure you've built. You might have invested in better project management tools, automation, or systems that make you more efficient. Those investments deserve to be reflected in your pricing, not absorbed as a cost of doing business.

4. Your Skills Have Leveled Up

You're not the same programmer you were two years ago. You've shipped more projects, solved harder problems, picked up new specialties. You've probably become faster and more reliable. That's worth more. When production metrics and demand increase, it's time to implement pricing changes.

This is especially true if you've moved into a higher-value niche. If you started as a general web developer and now you're the person clients call for complex integrations or legacy system rescues, your rate should reflect that specialization. Niche expertise commands premium pricing.

5. Your Best Clients Are Happily Paying More Than Your Standard Rate

If you've already raised rates for some clients or new projects, that's data. It tells you the market will bear higher prices. When your best clients don't blink at a higher rate, your standard rate is too low. This is the market telling you something. Listen to it.

Often, solo devs will raise rates for new clients but keep existing clients at the old rate "to be loyal." But that's backwards. Your best, most reliable clients—the ones who pay on time, communicate clearly, and respect your work—should be the ones you feel most confident raising rates for. They value you. They'll understand.

The Math: How Much Should You Actually Raise?

Once you've decided it's time, the next question is: by how much?

There's no single right answer, but there are frameworks. Here's the most practical one for solo programmers:

Start with Your Current Effective Hourly Rate

This is different from your quoted rate. Your effective rate is what you actually earn per billable hour, accounting for:

• Time spent on non-billable work (admin, proposals, learning, marketing)
• Unbilled waiting time between projects
• Scope creep and underestimated projects
• Vacation, sick time, and downtime

If you quote $100/hour but only bill 30 billable hours per week out of a 40-hour work week, and you spend another 5 hours on proposals and admin, your effective rate is closer to $60/hour.

Calculate this honestly. Pull your last three months of invoices and time tracking. Divide total revenue by total hours worked (not just billable hours). That's your real rate.

Benchmark Against Your Market

What are other developers with your skills, in your niche, charging? This is harder to find than you'd think, but there are signals:

• Freelance platforms like Upwork show rate ranges (though they're often skewed low)
• Industry surveys and salary data give you a floor
• Your peer network—ask trusted colleagues what they charge
• Job postings for similar work show what companies will pay

You don't have to match the market exactly, but you should know where you sit. If you're 20% below market rate for your skill level, that's a gap worth closing.

Calculate the Increase You Need

When determining how much to increase, consider which services to adjust and the amount of increase needed. A good rule of thumb: 10-20% is a standard, defensible increase. It's enough to matter (a $100/hour rate becomes $110-120, which adds up over a year) but not so aggressive that it shocks clients.

If you haven't raised rates in 2+ years, you might go 15-20%. If it's been one year, 10-15% is reasonable. If you're moving into a new niche or your skills have genuinely leveled up, you can justify 20-25%.

Don't overthink this. More important than the exact percentage is that you're raising at all. You can always raise again next year.

Factor in Your Business Goals

Here's where revenue planning and forecasting matters. Before you set a new rate, ask: What do I actually need to earn this quarter?

If you're aiming for $50,000 in quarterly revenue and you currently bill 500 hours per quarter, you need $100/hour. If your new goal is $60,000, you need $120/hour. Work backwards from your target, not just from a percentage increase.

This is where tools like Cashierr help. Instead of guessing, you can model different rate scenarios and see how they impact your quarterly revenue projections. You can ask: "If I raise rates 15% and lose one client, do I still hit my target?" The math becomes clear.

The Timing Question: When to Actually Implement the Increase

Timing matters. You want to raise rates at a moment that feels natural to the client, not arbitrary.

Best Times to Raise Rates

At the start of a new project or engagement. If a client comes to you with a new project, that's the moment to quote your new rate. No awkwardness. They're already expecting to negotiate.

At contract renewal or retainer reset. If you have monthly retainers or annual contracts, raise rates at the renewal date. Give 30-60 days notice. Clients expect price adjustments at renewal—it's normal.

After a major deliverable or milestone. If you've just shipped something big and successful, the client is happy and feeling good about the relationship. That's a natural moment to say, "As we move into the next phase, I'm adjusting my rates to reflect the increased complexity and value I'm delivering."

January or the start of a quarter. If you don't have a specific project trigger, the start of a calendar quarter or year feels natural. It's when people expect business changes.

Worst Times to Raise Rates

Avoid raising rates when a client is frustrated, when a project is troubled, or when they've just negotiated you down on scope. Wait for stability.

Also avoid raising rates mid-project on an hourly engagement. That's disruptive. Finish the project at the current rate, then move the next one to the new rate.

Communicating the Increase: The Email Template

This is where most solo devs get nervous. How do you tell a client their rates are going up without them leaving?

The key is to lead with value, give notice, and make it feel inevitable—not punitive. Here's a template that works:

---

Subject: Updated Rates for [Your Name] – Effective [Date]

Hi [Client Name],

I wanted to reach out with a heads-up on a change coming to my engagement terms.

Effective [date—30-60 days out], I'm adjusting my rates to $[new rate]/hour (up from $[old rate]/hour). This reflects the depth of expertise I've developed, the specialized work we do together, and the value I've consistently delivered to your projects.

Over the past [timeframe—e.g., "18 months"], we've shipped [specific wins—e.g., "three major features, a complete redesign, and the integration that cut your load times in half"]. I've also invested significantly in [specific skills or tools—e.g., "advanced optimization techniques, your specific tech stack, and systems that let me move faster"].

For your current project/retainer, we'll continue at the current rate through [end date]. Any new work or renewal after that date will be at the updated rate.

I'm committed to the same level of quality and responsiveness you've come to expect. This adjustment ensures I can keep delivering that standard and stay focused on your success.

Let me know if you have any questions.

Best, [Your Name]

---

Why this works:

1. It leads with notice, not surprise. You're giving them time to adjust mentally and budget-wise.

1. It connects the increase to value delivered. You're not raising rates because you need more money (they don't care). You're raising rates because you've delivered more value.

1. It's specific, not generic. "I've gotten better" is weak. "We shipped three major features and the integration that cut your load times in half" is concrete.

1. It's calm and confident, not apologetic. You're not asking permission. You're informing them of a change.

1. It acknowledges the transition. If applicable, you're honoring the current rate through a certain date, which softens the blow.

1. It reassures on quality. The last line matters: you're not raising rates and cutting corners. You're raising rates and staying committed.

When communicating rate changes, timing and clarity matter—you want to give clients notice and explain the reasoning behind the increase.

Variations for Different Client Relationships

Not all clients are the same. Adjust your approach:

For Long-Term Retainer Clients

These are your bread and butter. They've been with you for years. You have options:

• Raise their rate at renewal. Give them 60 days notice. Most will accept it because switching costs are high.
• Offer a loyalty discount but still raise. "I'm moving to $120/hour for new clients, but I'm grandfathering you in at $110 as a valued partner." They feel special, you get the raise.
• Tie the increase to expanded value. "As we take on more strategic work together, I'm adjusting my rate to $X. This reflects the scope we're now covering."

Long-term clients are usually your most understanding about rate increases. They've seen you grow.

For Project-Based Clients

Simpler: quote the new rate on the next project. "Based on the scope and complexity you've described, my rate for this project is $[new rate]/hour." No drama. It's just the current market price.

For Clients You're Not Sure About

If you're worried a client might leave, you have options:

• Raise rates on new work, not existing retainers. Keep them on the old rate for their current project, but new projects are at the new rate.
• Raise rates gradually. Instead of 15% at once, do 7-8% now and another 7-8% in six months. Less shock.
• Make it a conversation. "I'm thinking about adjusting my rates. How would you feel about that?" This opens dialogue and gives them a voice.

But here's the truth: if a client will leave you over a 10-15% rate increase after you've delivered real value, they were probably a marginal client anyway. Your best clients will understand.

What Happens After You Raise Rates

Once you've sent the email and the new rate is live, what comes next?

Monitor Your Pipeline

Watch for the first few weeks. Do prospects push back more on pricing? Do existing clients accept the increase? This is real data about how the market responds to your new rate.

If you lose a client or two over the increase, that's usually fine. It means you were slightly overpriced for them, and now you have capacity for a better-fit client at the higher rate.

Track Your Revenue Impact

This is where forecasting matters. Once you've raised rates, you want to know: Is my quarterly revenue actually going up?

If you raised rates 15% but lost 20% of your billable hours, that's a problem. You need to adjust. Understanding the impact of your pricing changes requires careful tracking and analysis.

Use tools to track this. Cashierr can help you model different scenarios and track whether your actual revenue is hitting your projections after a rate increase. You can see in real time: "I raised rates, and here's how it's affecting my quarterly revenue."

Plan Your Next Increase

Once you've raised rates successfully, you've broken the seal. The next increase is easier. Most solo devs should raise rates annually, even if it's just 5-10% to keep up with inflation and skill growth.

Make it a calendar event. Every January, or every quarter, ask: Should I raise rates again? Don't wait for a crisis or until you're desperately underpriced. Make it a regular rhythm.

Common Objections (And How to Handle Them)

Your clients might push back. Here's how to handle the most common objections:

"Your rates are now higher than other freelancers."

Response: "I'm not the cheapest option, but I'm the most reliable. I deliver on time, I understand your business, and I've proven that. You could find someone cheaper, but you'd lose the continuity and quality you've come to expect."

Don't compete on price. Compete on value.

"We're on a tight budget this quarter."

Response: "I understand. Let's look at what we can accomplish within your budget. We could reduce scope, extend the timeline, or adjust the engagement. What matters most to you right now?"

This opens a conversation instead of a standoff.

"Why are you raising rates now?"

Response: "A few reasons. I've invested in new skills and tools that let me deliver better results faster. My costs have gone up. And frankly, I haven't raised rates in [timeframe], so this is overdue. I'm still committed to delivering the same quality you expect."

Be honest. Clients respect honesty more than you'd think.

The Bigger Picture: Revenue Planning and Forecasting

Raising your rates is one lever. But it's part of a bigger picture: understanding your business health and planning for growth.

Every solo programmer should be able to answer two questions:

1. How much should I be making this quarter? (This is your revenue target, based on your goals, costs, and ambitions.)
2. How's the business actually doing? (This is your actual revenue, tracked against that target, with visibility into where it's coming from.)

Rate increases help you hit higher targets. But you need to know what your target is in the first place. Cashierr helps you answer both questions. It tracks your goals, projects your revenue, and flags gaps before they hurt. You can model rate scenarios, see how they impact quarterly projections, and make data-driven decisions about pricing.

Without that visibility, you're flying blind. You might raise rates and still miss your targets because you lost too many hours to admin work or scope creep. Or you might leave money on the table because you don't realize how much capacity you actually have.

The point: raising rates is tactical. But it works best when it's part of a broader revenue planning strategy.

The Confidence Factor

Here's the thing most solo devs don't talk about: raising rates is uncomfortable because it forces you to claim your own value.

When you're charging $80/hour, you can tell yourself you're being reasonable, humble, accessible. When you raise to $95/hour, you're saying: "I'm worth this. My work is worth this." That's vulnerable.

But here's the reality: if you're good at what you do, if you deliver on time, if clients are happy and coming back—you're already worth more. Raising rates isn't being greedy. It's being honest about the market.

Your clients aren't paying you for your time. They're paying you for the problems you solve, the code you write, the reliability you bring. That value doesn't change based on your confidence level. Your confidence just changes whether you charge for it.

Confidently raising rates and shifting to value-based pricing is a key part of freelancer growth.

So raise your rates. Give notice. Explain the value. And move forward.

Moving From Rates to Revenue Planning

Once you've raised your rates, the next step is making sure they actually translate to higher quarterly revenue. That means understanding your full business picture: not just what you charge, but how many hours you're actually billing, where your revenue concentration risk is, and whether you're on track to hit your targets.

This is where revenue forecasting becomes essential. You need to know: if I raise rates 15% but lose one client, what does my Q3 look like? If I take on two new projects at the higher rate, can I hit my $70K quarterly target?

These aren't abstract questions. They're the foundation of a sustainable freelance business. And they're exactly what Cashierr is built to answer. It tracks your goals, projects your revenue, and flags gaps before they hurt. You get a personal CFO for your dev business.

The combination is powerful: you raise rates (tactical), and you track the impact against your goals (strategic). Together, they answer the question every solo programmer secretly asks: How much should I be making, and how's the business actually doing?

Raise your rates. Then measure the impact. That's how you build a business that actually sustains you.