Track the 5 essential metrics every solo developer needs for quarterly revenue planning. Skip the noise, focus on what actually matters.
You're three months into the quarter, and you realize you don't actually know if you're on track. You've got invoices scattered across email, some half-paid, a few clients who haven't paid yet, and a vague sense that you should be making more. So you open a spreadsheet, spend two hours pulling numbers together, and end up with a figure that might be right—or might be completely wrong because you forgot to account for that one project from February.
This is the moment every solo developer dreads. Not because the numbers are bad (though sometimes they are), but because you don't have a clear picture of what's actually happening in your business. You're flying blind, quarter to quarter, hoping the money keeps coming in while you ship code.
The good news: you don't need a complex accounting system or a business degree. You need five metrics. That's it. Five numbers, checked quarterly, that will tell you exactly where you stand and what needs to change.
This isn't about turning yourself into a CFO. It's about answering two questions every solo programmer secretly worries about: How much should I be making? and How's the business actually doing? When you know these five metrics, you stop guessing.
A lot of solo developers check their bank balance weekly—sometimes daily. That's not the same as understanding your business. A bank balance tells you what happened last month. It doesn't tell you if you're on track for your goals, if you're overreliant on one client, or if you're pricing yourself into a corner.
Quarterly check-ins exist for a reason. Three months is long enough to see patterns but short enough to course-correct before the year gets away from you. It's the sweet spot where you can actually influence the outcome.
When you track five key metrics every quarter, something shifts. You move from reacting to your business to steering it. You stop wondering if you should raise your rates—you know whether you can afford to. You stop hoping clients will pay on time—you know which ones won't and plan accordingly. You stop asking "how much should I make this quarter?" because you've already decided.
Tools like Cashierr exist specifically to automate this kind of quarterly revenue planning for solo developers, turning raw financial data into actionable insights. But before we talk about tools, let's talk about what actually matters.
This is your north star. Quarterly Revenue Run Rate is exactly what it sounds like: the total revenue you're on pace to generate in the current quarter, based on what you've already earned and what's committed.
How to calculate it:
Take your actual revenue so far this quarter, plus any invoices you've sent that are likely to be paid this quarter, plus any retainer income you know is coming. That's your QRR.
Let's say it's April (Q2), and you've already invoiced $8,000 in March and collected $6,000. You've got two retainer clients paying $2,000 each monthly, and you've just landed a $5,000 project that's invoiced but not yet paid. Your QRR calculation looks like this:
Compare this to your quarterly target. If you decided at the start of Q2 that you wanted to hit $30,000, now you know you're $7,000 short. That's not a surprise in July—you know it now, in April, when you can still do something about it.
The gap between your QRR and your target is your planning metric. It tells you whether you need to land new work, raise rates on renewals, or adjust your expectations. Most solo developers don't know this number until the quarter is almost over. That's why they're always scrambling.
This one is invisible until it isn't. Then it becomes a crisis.
Client revenue concentration measures how dependent you are on any single client. The metric: What percentage of your quarterly revenue comes from your largest client?
If one client represents 40% of your quarterly revenue, you have a concentration problem. Not because the client is bad, but because you're one conversation away from a 40% revenue drop. That's not a business—that's a hostage situation.
Here's how to think about it: Imagine your largest client decides to reduce their scope by 20%, or they hire an in-house developer, or they go out of business. Can your business absorb that hit? If the answer is "barely" or "no," you have a concentration problem.
The healthy range is roughly:
Many solo developers track this intuitively ("Yeah, Client X pays the bills"), but putting a number on it changes everything. Suddenly it's not a worry—it's a metric you can act on.
This is where reality crashes into optimism.
Invoiced revenue is what you've billed. Collected revenue is what's actually in your bank account (or will be, based on confirmed payment terms). The gap between these two is your cash flow problem.
Let's say it's mid-quarter and you've invoiced $15,000 total. But you've only collected $9,000. The remaining $6,000 is outstanding—some from net-30 invoices, some from clients who are slow to pay, some from projects still in progress.
If you're living on invoiced revenue ("I've billed $15K so I'm making $15K this quarter"), you're lying to yourself. You're living on credit. You're hoping those invoices get paid on time. And when they don't, you're suddenly short on cash.
The metric that matters: Collection rate. What percentage of your invoices are actually paid by the time you're checking in quarterly?
A healthy collection rate is 85-95%. If you're below 85%, you have a collection problem:
Once you see the pattern, you can change it. You can adjust payment terms, switch to upfront deposits for new clients, or—in the hardest cases—decide a client isn't worth the cash flow pain.
This is why Cashierr's approach to revenue forecasting emphasizes the difference between what you've billed and what you've actually collected. It's the difference between a plan and a fantasy.
Here's a metric that makes solo developers uncomfortable, which is exactly why you need it.
Your effective hourly rate is your actual collected revenue divided by the actual hours you worked. Not the rate you charge clients. Not the rate you think you're working at. The real rate, based on real numbers.
Let's say you collected $12,000 this quarter and you worked 400 billable hours (not including admin, sales, or the time you spent chasing down invoices). Your effective hourly rate is $30/hour.
Now compare that to what you think you charge. Maybe you quote clients at $80/hour. But between scope creep, clients who negotiate down, projects that take longer than expected, and time spent on unbillable work, your effective rate is $30.
This is the number that matters. Not what you charge—what you actually make per hour of work.
Why does this matter? Because it tells you whether your pricing strategy is working. If you're aiming for $100/hour effective rate and you're at $30, something is broken. Either:
Most solo developers never calculate this because it's uncomfortable. Their mental rate ($80/hour) is much higher than their real rate ($30/hour), and that gap is depressing. But that depression is actually useful—it's the motivation to change something.
This is the metric that separates chaos from calm.
Monthly Recurring Revenue (MRR) is the revenue you can count on every single month, without having to land new work. For most solo developers, this comes from retainer clients—the ones who pay the same amount every month for ongoing support, maintenance, or a fixed scope of work.
Let's say you have two retainer clients paying $2,000 and $1,500 per month. Your MRR is $3,500. That means, before you land a single new project, you know $3,500 is coming in next month, and the month after, and the month after that (assuming they don't cancel).
The power of this metric is predictability. If your MRR is $3,500 and your monthly expenses are $2,000, you know you have $1,500 of breathing room every single month. You can take on speculative work. You can take time off. You can invest in tools or learning without panicking about cash flow.
For quarterly planning, MRR tells you your baseline. Let's say your MRR is $3,500 and your quarterly target is $15,000. That means your retainers are generating $10,500 of that target (3 months × $3,500). You need to land $4,500 in project work to hit your goal. That's a much clearer target than "I need to make more money."
The secondary metric here is predictability—how stable is your MRR? If you have five retainer clients and one cancels, your MRR drops 20%. That's a concentration problem in disguise. If you have 15 retainer clients and one cancels, it's a rounding error.
When you track MRR quarterly, you start to see whether your business is getting more predictable or more volatile. Over time, the goal is to grow MRR (more stable income) while keeping project work (higher rates, lower volume) as the upside.
Individually, these five metrics tell you different things. Together, they paint a complete picture of your business.
Here's a realistic quarterly check-in for a solo developer we'll call Alex:
Alex's Q2 Check-In (mid-quarter, April 15th):
With $4,200 in guaranteed MRR, Alex has a solid foundation. The $22,000 QRR means Alex is on track for about $22K (vs. the $25K goal), which is a $3,000 gap. To close that gap, Alex could:
Without these metrics, Alex would just feel vaguely anxious. With them, Alex has a plan.
The biggest mistake solo developers make is tracking these metrics inconsistently. They check once, feel good or bad, then forget about it until crisis hits. Then they scramble, pull numbers together, and swear they'll track better next quarter. And they don't.
The fix is stupidly simple: Calendar a 30-minute meeting with yourself every quarter. Same day, same time. Put it on the calendar now for the next four quarters.
During that 30 minutes:
Do this four times a year, and you'll know more about your business than 90% of solo developers. You'll stop guessing. You'll stop panicking. You'll start planning.
For developers who want to automate this process, Cashierr handles the data collection and calculation, turning raw invoices and expenses into these five metrics automatically. But the habit—the quarterly check-in—that's on you. The tool just makes it faster.
Metrics are only useful if they drive action. Knowing your QRR is $22K instead of $25K doesn't matter if you do nothing about it.
Here's how solo developers actually use these metrics:
If your QRR is below target: You have a gap. Close it by landing new work, raising rates, or adjusting your target. If you're consistently missing targets, your target might be unrealistic. Adjust it and commit to it for the next quarter.
If client concentration is high: Start a deliberate diversification project. Spend 5 hours this quarter reaching out to past clients, updating your portfolio, or exploring new niches. The goal isn't to land a client immediately—it's to reduce risk.
If collection rate is low: Tighten your payment terms. Require 50% upfront on new projects. Follow up on invoices at day 15, not day 45. If a client is perpetually late, have a conversation about it or stop working with them.
If effective hourly rate is too low: Stop accepting scope creep. Set clear project boundaries. Raise rates on renewals. Or, if you're underpricing, raise rates on new clients immediately. It stings short-term; it saves you long-term.
If MRR is stagnant: This is actually fine if your project work is strong. But if you want more predictability, focus on converting one-off projects into retainers. Offer a "maintenance retainer" to past clients. Build recurring revenue intentionally.
The communities at Indie Hackers and discussions like what metrics indie developers track show that solo developers who track metrics consistently make better business decisions. They raise rates faster. They diversify sooner. They burn out less.
Even when solo developers start tracking metrics, they often make the same mistakes:
Mistake 1: Confusing invoiced with collected revenue. You billed $30K this quarter, so you think you made $30K. But if only $20K was actually collected, you made $20K. Plan based on collected revenue, not invoiced revenue. Your bank account is the truth.
Mistake 2: Ignoring the gap. Your QRR is $20K, your target is $25K. You tell yourself you'll "try harder next quarter." But if you don't know why you missed the target, you'll miss it again. Was it pricing? Not enough sales effort? Scope creep? Figure out the real reason, or the gap persists.
Mistake 3: Setting targets that are aspirational, not realistic. "I want to make $50K next quarter" sounds great. But if you've never made more than $30K, what's going to change? Targets should be ambitious but grounded in reality. They should stretch you, not demoralize you.
Mistake 4: Not accounting for seasonality. If Q4 is always slower because clients freeze budgets in November, don't set a Q4 target that's the same as Q3. Adjust for the patterns you know exist.
Mistake 5: Tracking too many metrics. You don't need 20 metrics. You need five. More metrics don't give you better clarity—they give you noise. Stick to the five that matter.
You can track these five metrics in a spreadsheet. Many solo developers do. It takes 30 minutes per quarter, and the math is simple.
But if you're already using invoicing software, expense tracking, or accounting tools, you're probably generating this data anyway. The question is whether you're pulling it together into a coherent quarterly picture.
Some developers use Baremetrics' guide to metrics for indie founders as a reference, or explore key metrics every indie hacker should track to understand what other solo developers are measuring. Tools like Cashierr automate this aggregation, pulling data from your invoices and expenses and automatically calculating these five metrics (plus others) every quarter.
The advantage of automation: you don't have to remember to do it. You don't have to manually pull numbers. You get a quarterly report that shows you exactly where you stand. The disadvantage: you have to set it up, and you have to trust the tool.
For most solo developers, a simple spreadsheet is enough. For those juggling multiple clients, retainers, and complex invoicing, automation saves time and reduces the chance of mistakes.
Resourceful developers also look at startup metrics for solo founders to understand how other indie developers think about their numbers, or explore SaaS metrics solo founders must track if they're building product-based businesses alongside client work.
Tracking these five metrics every quarter is a small habit. But it creates a massive mindset shift.
Without metrics, you're at the mercy of your business. You hope clients pay on time. You hope you're charging enough. You hope you're on track. It's exhausting and disempowering.
With metrics, you're steering. You know exactly where you stand. You know what needs to change. You can make decisions from a place of data, not fear.
This is what it means to actually run your business, rather than just executing work. It's the difference between being a freelancer (someone who trades time for money) and being a business owner (someone who builds something that generates predictable revenue).
You don't need a business degree. You don't need an accountant (though one helps). You need five numbers, checked quarterly, and the willingness to act on what they tell you.
Start with your next quarter. Pick a date. Put it on your calendar. Pull these five numbers. Write them down. Look at the gaps. Make one decision about what to change. Do that. Then check again in three months.
That's the quarterly revenue check-in. It's simple, it's powerful, and it's the difference between wondering how your business is doing and knowing.
If you've never done this before, here's exactly what to do:
Step 1: Gather your data. Pull your invoices from the last three months. Pull your bank statements. List your clients and how much each paid (or owes).
Step 2: Calculate the five metrics. Use the formulas above. If you're unsure about a number, estimate conservatively.
Step 3: Compare to your target. Did you hit your quarterly revenue goal? If not, by how much?
Step 4: Identify one thing to change next quarter. Higher rates? New client? Tighter scope? Pick one thing.
Step 5: Schedule the next check-in. Same time next quarter. Don't skip it.
That's it. You've just done what most solo developers never do: you've looked at your business objectively and planned the next quarter based on data.
The developers who do this consistently are the ones who never panic about money. They're not luckier. They're not smarter. They just know their numbers.
Now you do too.
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.