Learn how client concentration risk nearly killed my freelance business. Real lessons on revenue diversification, forecasting gaps, and protecting your solo dev income.
It was a Tuesday morning when the email landed in my inbox. "We're restructuring our engineering team and moving the project in-house. Your last invoice will be for this month."
Four years of steady work. Forty thousand dollars in annual revenue—nearly half of what I made that year—gone in two sentences.
I sat there staring at my screen, doing the math in my head. I had maybe three weeks of runway before my burn rate would start eating into savings. My other clients were smaller, more sporadic. I'd built a comfortable freelance income by doing exactly what every business textbook warns against: I'd let one client become too big to ignore.
That day taught me more about revenue planning than a dozen business courses ever could. It wasn't just about losing money. It was about the false sense of security that comes from watching one client's checks clear month after month, and the brutal cost of ignoring the gap between what I thought my business was doing and what it was actually doing.
This is the story of concentration risk—and why solo programmers need to understand it before it costs them everything.
Concentration risk sounds like a finance term, and it is. But strip away the jargon and it's simple: it's the danger that comes from depending too heavily on too few sources of revenue.
For solo developers, this usually means one or two clients making up a disproportionate share of your income. According to research on concentration risk across economic cycles, the vulnerability isn't just about losing money—it's about losing predictability. When one client represents 40%, 50%, or 60% of your revenue, you don't have a diverse business. You have a job with extra steps.
The financial services industry has strict rules about this. Credit managers track concentration limits carefully, knowing that overreliance on a single counterparty—whether a supplier or customer—creates systemic risk. Banks worry about it. Insurance companies worry about it. But most solo programmers? We ignore it until we can't.
There's a reason for that. When you're grinding through client work, trying to ship features and hit deadlines, thinking about portfolio risk feels abstract. Revenue is coming in. Invoices are getting paid. The spreadsheet says you're doing fine. So you keep your head down, deliver good work, and tell yourself you'll diversify "next quarter."
Next quarter never comes. Instead, you get an email like mine.
Let me walk you through exactly how this happened, because I suspect you'll recognize parts of your own business in it.
In 2019, I picked up a contract with a mid-sized SaaS company. The work was solid—building backend infrastructure, some DevOps, occasional architecture consulting. The rate was good. The communication was great. The project was interesting enough that I didn't dread Monday mornings.
Year one, they paid me $32,000. That was about 35% of my total revenue that year. The rest came from smaller retainer clients, one-off projects, and some fractional CTO work.
Year two, they increased my hours. I was now doing $38,000 with them. My total revenue stayed roughly the same because I naturally had less capacity for other work. They were now 42% of my revenue.
Year three, they asked me to go deeper on their infrastructure. More hours, higher scope. I said yes. Now they were $40,000 of my $83,000 total revenue. That's 48%.
At that point, I should have hit pause. I should have said: "I can't take on more work with you until I've built out my other client base to a healthier level." But I didn't. Here's why:
I was optimizing for certainty, not resilience. One big client felt safer than five small ones. The big client had a stable budget, predictable monthly work, and I didn't have to spend time hunting for new business. The smaller clients were inconsistent—some months they had budget, other months they didn't. From a cash flow perspective, that one big client was a security blanket.
I wasn't tracking the actual risk. I knew the client was big, but I didn't have a clear picture of what my business would look like if they disappeared. I wasn't running scenarios. I wasn't forecasting quarterly revenue by client. I was just looking at my bank balance and assuming things were fine.
I confused revenue with business health. Making $83,000 a year sounds solid for a solo dev. But if $40,000 of that is at risk, my actual stable revenue was only $43,000. That's a different number entirely, and it should have changed my planning.
When the client let me go, I had to confront all three of these failures at once.
Everyone's first instinct is to calculate the immediate financial hit. You lose $40,000 in annual revenue, which means you lose roughly $3,300 per month. That's painful. That's real.
But the total cost was much worse than that.
First, there's the scramble cost. I spent the first two weeks in panic mode, reaching out to old contacts, pitching new services, trying to piece together enough work to cover the gap. That's two weeks I wasn't shipping code for my remaining clients. It's two weeks of context-switching and sales conversations instead of deep work. For a solo dev, that's expensive—every hour spent selling is an hour not billed.
Second, there's the desperation discount. After two weeks of pitching, I was getting offers, but they were lower-rate work. One client wanted ongoing support at $35/hour instead of my usual $85/hour. Another wanted a fixed-price project that, when I did the math, came out to about $55/hour. I took both because I needed the revenue. Over the next three months, I probably left $8,000 on the table by accepting lower rates when I was under pressure.
Third, there's the opportunity cost. I should have spent that time building products, refining my positioning, or investing in better tools. Instead, I was in survival mode. I couldn't think about the next quarter or the next year because I was too busy figuring out the next month.
Fourth, there's the emotional cost. This one doesn't show up in spreadsheets, but it's real. I second-guessed my ability to run a business. I felt stupid for not seeing it coming. I lost sleep. That affects decision-making, and bad decisions made under stress cost money.
When you add it all up, that one lost client cost me far more than $40,000. It cost me momentum, confidence, and the ability to be strategic about my business for months.
After the dust settled, I got serious about understanding what I should have been tracking all along. Here's what I learned.
First, the easy stuff. Rules of thumb in concentration risk management suggest that if your top customer is more than 10% of revenue, or your top five customers are more than 25% of revenue, you're in risky territory.
For solo devs, I'd be even more conservative:
You know a client is becoming too important when you start making decisions based on their preferences instead of your business strategy. You take on work you don't want to do because they asked. You skip other opportunities because you don't want to overcommit. You negotiate less aggressively on rate because you don't want to lose them.
I did all of this with my $40K client. They asked me to learn a new framework, and I did it. They wanted me available for emergency calls, and I made myself available. When they asked for a 10% discount in year three, I took it rather than push back.
Each of those decisions made sense in isolation. Together, they signaled that I'd surrendered control of my business to that one client.
Another warning sign: you can't articulate why you'd lose the client. If I'd been asked in 2021 why that SaaS company might end our relationship, I would have said, "They wouldn't. They love my work." But companies restructure. Budgets get cut. Priorities shift. If you can't name three realistic ways a client could disappear, you're not thinking critically about your risk.
This is where most solo devs fall short. You track total revenue. You track expenses. But do you track concentration? Probably not.
Here's what I should have been measuring:
Revenue by client (as a percentage of total). This one's obvious, but you'd be surprised how many freelancers don't do it. Every month, calculate what percentage of your revenue came from each client. If any client is creeping above 25%, flag it. If it hits 30%, make it a priority to diversify.
Stable revenue vs. at-risk revenue. Divide your clients into two buckets: those you're confident will stick around (multi-year contracts, strong relationships, recurring work) and those that could evaporate. Your "stable" revenue should be at least 60% of your total. If it's less, you're running on fumes.
Revenue concentration risk score. This is a bit more advanced, but it's worth calculating. The formula is simple: take your largest client's revenue, divide it by your total revenue, then multiply by 100. If that number is above 30, you're in the red zone. If it's above 40, you're in crisis territory.
When I calculated this retroactively, mine was 48. I was in crisis territory and didn't even know it.
Quarterly revenue projections by client. This is the one that would have saved me. If I'd been forecasting my revenue quarter by quarter, broken down by client, I would have seen the concentration problem clearly. I would have known that Q1 and Q2 of that year depended almost entirely on that one client. That knowledge would have forced me to act.
This is exactly the kind of analysis that understanding concentration risk and its impacts is meant to surface. When you can see that one client at 40%+ of revenue is a vulnerability, you can't ignore it anymore.
After the client loss, I rebuilt my business with a much more disciplined approach to revenue planning. And I'm not talking about spreadsheet wizardry. I'm talking about a simple framework that forces you to think clearly about what's actually happening in your business.
Start by answering the question every solo dev secretly worries about: "How much should I be making this quarter?"
This isn't about pie-in-the-sky dreaming. It's about setting a realistic number based on your rate, your capacity, and your goals. Let's say you charge $80/hour and you can realistically bill 25 hours per week. That's $2,000 per week, or about $8,000 per month, or $24,000 per quarter.
Now you have a target. You can measure against it.
Take your actual revenue from the last three months and break it down by client. What percentage does each one represent? Are there any surprises? Is one client bigger than you thought?
This is where you'll spot concentration risk. If you see one client at 35%+ of your revenue, that's your signal to act.
For each client, estimate what you think they'll spend in the next quarter. Be conservative. If they've been inconsistent, don't assume they'll suddenly become predictable. If they've been growing, don't assume growth continues.
Add it all up. Is that number above or below your target?
If it's below, you have a gap. That gap is your concentration risk problem in disguise. You need new revenue sources, and you need them before you're desperate.
This is the critical step that most solo devs skip. You have a target ($24,000 for the quarter). You have a projection based on current clients ($16,000). That means you have an $8,000 gap.
Now you know exactly what you're hunting for. You're not looking for "more clients." You're looking for $8,000 in quarterly revenue. That changes how you sell. It makes you more intentional.
It also forces you to think about concentration. If you fill that $8,000 gap with one new client, you've just moved the problem around. Better to find two or three smaller clients, or to deepen a relationship with an existing client who's currently small.
Once a month, update your projections. Did a client deliver the revenue you expected? Did a new opportunity emerge? Is concentration getting better or worse?
This is where tools matter. You can do this in a spreadsheet, but it's tedious and error-prone. A better approach is to use software designed specifically for this kind of revenue planning. Cashierr does exactly this—it tracks your clients, projects your revenue, and flags concentration risk before it becomes a crisis. It's like having a personal CFO who actually understands the solo dev business model.
The key is to make this a regular practice, not a one-time exercise. Spend 15 minutes a month on it. That's all it takes to stay aware of your concentration risk.
Here's something I learned after digging into concentration risk research: diversification alone isn't enough. You can have ten clients, but if they're all in the same industry, and that industry tanks, you're still screwed.
Research on concentration risk across economic cycles shows that what matters isn't just the number of clients, but the quality of those relationships. A client that could disappear tomorrow is riskier than a client with a two-year contract, even if the second client is larger.
For solo devs, this means thinking about client stability in multiple dimensions:
Revenue stability. Is this client's budget predictable? Do they have recurring work, or do they hire you project-by-project? Recurring is better.
Company stability. Is this client's company financially healthy? Are they growing or shrinking? A startup client is riskier than an established company, even if the startup pays better.
Relationship stability. How long have you been working with them? Is there a contract? If your main contact left, would the relationship survive? The longer and deeper the relationship, the more stable it is.
Industry stability. Are they in a booming sector or a declining one? Are they selling something people will always need, or something that's trendy? This affects how much they'll be able to spend on engineering.
When I rebuild my client base, I stopped thinking about just the number of clients and started thinking about this stability profile. I wanted a mix:
If I could go back to 2019 and talk to the version of me who was about to become dependent on one client, here's what I'd tell him:
Your business isn't healthy unless you can answer two questions clearly:
Question One: How much should I be making this quarter? This isn't a guess. It's based on your rate, your capacity, and your goals. If you can't answer this, you can't measure whether your business is actually working.
Question Two: How's the business actually doing against that target? Are you on track? Are you ahead? Are you behind? And if you're behind, which clients are letting you down? Which gaps do you need to fill?
These two questions are the foundation of revenue planning. Everything else flows from them.
When I lost that $40K client, I couldn't answer either question confidently. I knew I was making decent money, but I didn't know if it was enough or if it was sustainable. I didn't have a clear picture of what my business would look like without that one client.
Now I do. And that clarity is worth more than the $40K I lost.
The way to get that clarity is to build a forecasting practice. Not a complicated one. Not one that takes hours every week. Just a simple, regular review of:
The year after I lost that client was hard. But it forced me to get serious about my business in ways I probably wouldn't have otherwise.
Here's what I did differently:
I set a hard rule about concentration. No single client can be more than 25% of my revenue. If a client is approaching that threshold, I stop taking additional work from them and focus on building other relationships. This rule has saved me several times since then.
I started quarterly planning. Every quarter, I sit down and forecast my revenue. I look at my current clients, estimate what they'll spend, identify gaps, and make a plan to fill them. It takes a couple of hours, and it gives me clarity for the next three months.
I built a "rainy day" reserve. I now keep three months of expenses in a separate account. This isn't an emergency fund for my personal life—it's a business reserve. If a client leaves, I can handle it without panic. That reserve gives me the confidence to be more selective about who I work with and how much I charge.
I got better at saying no. When a client wanted to increase my hours beyond 25% of my revenue, I said no. When a client wanted a discount, I negotiated harder. When a client wanted me to learn a new stack, I asked for a rate increase. I stopped optimizing for certainty and started optimizing for sustainability.
I got intentional about client diversity. I now have clients across different industries, different company sizes, and different types of work. If one sector tanks, I'm not dependent on it. If one company restructures, I have other revenue sources.
These changes took time. But they transformed my business from fragile to resilient.
Let me be honest: spreadsheets are not the answer. I tried. I built an elaborate Google Sheet that tracked clients, revenue, projections, and concentration metrics. It worked for about a month, and then I stopped updating it.
The problem with spreadsheets is that they're too easy to ignore. You can tell yourself you'll update it "later." You can rationalize not looking at it because you're busy. And then three months go by and the data is stale.
What you need is a system that forces you to stay aware. For me, that meant moving to a tool designed specifically for revenue planning. Cashierr does this by building revenue forecasting and concentration risk tracking directly into the interface. You log your clients, your rates, your projects, and it automatically projects your quarterly revenue and flags concentration risks.
The benefit isn't just the software. It's the practice. When you're using a tool that's designed around these questions—"How much should I make? How's the business doing? Where are the gaps? What's my concentration risk?"—you start thinking about your business differently. You become more intentional. You make better decisions.
But whether you use a tool or a spreadsheet, the key is consistency. Spend 15 minutes a month reviewing your revenue. Update your projections. Check your concentration metrics. That's it. That's the practice that prevents the crisis.
I've talked to dozens of other solo developers since my client loss, and almost all of them have a similar story. They've all had a client that was too big. They've all known it was risky. And they've all done nothing about it until something forced their hand.
Why? I think it comes down to a few things:
Optimization for the wrong metric. We optimize for revenue, not for stability. A big client feels like success. And in the moment, it is. But it's success that comes with hidden risk.
Lack of visibility. Most solo devs don't have a clear picture of their revenue concentration until it's too late. They're focused on shipping code and delivering for clients, not on analyzing their business metrics.
The illusion of control. When a relationship is going well, it feels permanent. You think, "This client loves my work. They're not going anywhere." But companies don't make decisions based on sentiment. They make them based on budgets, priorities, and org structure. Any of those can change without warning.
Complexity aversion. Revenue planning sounds complicated. So most solo devs don't do it. They just check their bank balance and assume things are fine.
But here's the thing: revenue planning doesn't have to be complicated. It can be simple. It can be a 15-minute monthly practice. And it can save your business.
If you're reading this and recognizing yourself in my story, here's what to do right now:
Step one: Calculate your concentration. Look at your revenue from the last three months. What percentage came from your largest client? Your top three? If any of those numbers are above 25%, you have a concentration problem.
Step two: Define your target. How much do you want to make this quarter? Be realistic. Base it on your rate and your capacity.
Step three: Project your revenue. Based on your current clients, how much do you think you'll make this quarter? Be conservative.
Step four: Identify your gap. Subtract your projection from your target. That's the revenue you need to find. That's your action item for the next month.
Step five: Build a plan to reduce concentration. If one client is too big, make a plan to reduce your dependence on them. It might mean finding new clients. It might mean asking them to reduce your hours. It might mean raising your rates so they're motivated to hire someone else. Whatever it takes.
Do these five things, and you're already ahead of where I was before I lost that $40K client.
Looking back, the loss of that client was the best thing that could have happened to my business, even though it felt catastrophic at the time.
It forced me to think about what "business health" actually means. It's not just revenue. It's stability. It's diversification. It's knowing your numbers. It's having a plan.
Most solo devs are good at the technical side of their work. We ship code. We solve problems. We deliver value to clients. But we're often terrible at the business side. We don't track metrics. We don't plan. We don't think about risk.
Concentration risk is one of those business fundamentals that feels abstract until it's not. Then it becomes very real, very fast.
The good news is that managing it doesn't require a business degree or an MBA. It requires a simple practice: know your numbers, understand your dependencies, and make intentional decisions about your revenue mix.
Do that, and you'll never have to send an email like the one I got on that Tuesday morning. And if you do, you'll be prepared for it.
That's worth more than any single client ever could be.
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.