Discover the right runway for solo developers. Learn how to balance financial security with business growth and avoid the spreadsheet trap.
You're staring at your bank account on a Tuesday afternoon, and the same thought creeps in: How much money do I actually need to feel safe?
There's a number floating around in indie dev circles—six months, twelve months, sometimes eighteen. It gets thrown around like gospel, as if there's a universal formula that works for everyone from a freelance React developer to a solo SaaS founder shipping their first product. But the truth is messier and more personal than that.
Runway—the number of months your business can operate before you run out of money—matters. A lot. It's the financial shock absorber between a slow client month and a crisis. It's the difference between pivoting calmly and panicking. But the right runway for you depends on your income volatility, your burn rate, your risk tolerance, and whether you're juggling client work or betting everything on a product.
This isn't a generic "six months is the answer" piece. This is about understanding the real variables that matter for solo developers, looking at what the data actually says, and building a runway strategy that matches your situation—not some venture-backed startup's playbook.
Runway is straightforward in theory: it's your current cash divided by your monthly burn rate. If you have $30,000 in the bank and you spend $3,000 a month, you have ten months of runway.
But that simple math hides a lot of complexity for solo developers.
First, your burn rate isn't fixed. If you're a freelancer billing clients, some months you make $8,000 and some months you make $2,000. If you're building a SaaS, you might spend $500 a month on infrastructure but your personal draw varies wildly depending on whether you're reinvesting revenue or taking it home. If you're juggling both—client work and a side product—your burn rate is actually a range, not a number.
Second, runway assumes you're spending money at a constant rate until it runs out. But you're not passive. You'll cut costs if money gets tight. You'll take on extra client work. You'll pause development. Your runway isn't a countdown timer; it's a decision buffer.
Third, for solo developers, runway serves a different purpose than it does for a funded startup. A VC-backed company is racing to hit growth milestones before the money runs out. You're probably trying to answer two questions: Can I afford to take a slow month? and Can I afford to take risks with my time? Those are fundamentally different questions.
If you search for runway advice, you'll hit a few common benchmarks:
The six-month rule comes from the consulting and freelance world. The idea is simple: keep six months of living expenses in the bank. That's your safety net for slow seasons and unexpected gaps between projects. For a freelancer with a $4,000 monthly burn, that's $24,000. It feels reasonable, achievable, and not so large that you're sitting on a pile of idle cash.
The twelve-month rule shows up in SaaS and startup circles. The logic here is that building a product takes time, and you need enough runway to hit product-market fit, start getting traction, and ideally reach some level of revenue before you're forced to make desperate decisions. Twelve months gives you a full year to experiment, iterate, and prove the concept.
The eighteen-month rule is the optimistic version. How to Make 12 Months of Runway Last Like 18 explores the idea that with disciplined capital efficiency, you can stretch your runway significantly by compressing your build and growth phases. This assumes you're ruthlessly focused and willing to make hard trade-offs.
These aren't wrong, exactly. But they're designed for different situations than yours.
A freelancer with steady client work doesn't need twelve months of runway. You have income coming in most months. Your risk isn't that your business model breaks; it's that you have a slow month or lose a client. Six months is probably overkill.
A solo SaaS founder, on the other hand, might need more than six months. You're not billing clients; you're building a product and hoping it generates revenue. Your burn is pure cost with no offsetting income until you've gained traction. Six months might not be enough to know if your idea works.
The real question isn't "What does the industry say?" It's "What does your situation require?"
Here's what changes everything: how volatile is your income?
If you're a freelancer with a solid retainer client who pays you $5,000 every month like clockwork, your income volatility is low. You know what's coming in. You can predict your runway pretty accurately.
If you're juggling five clients, some project-based and some retainer, and they range from $1,000 to $8,000 a month depending on the season, your income volatility is high. You need more of a cushion because the worst-case scenario—losing two clients in the same quarter—is actually plausible.
If you're building a SaaS and your income is zero until it's not, your volatility is infinite. You have no predictable income. Your runway is your only lifeline.
The Solo Founders Report 2025 from Carta found that solo founders often underestimate their financial runway needs because they don't account for income variability. Many reported being surprised by how quickly cash depleted during slower periods.
This is why the generic "six months" or "twelve months" advice falls apart. It doesn't account for whether your income is stable or chaotic.
A better framework:
Runway is often framed as "months of living expenses," but for solo developers, it's more useful to think about it as "months of business operating expenses plus personal draw."
Let's be concrete. Say you're a freelancer. Your monthly costs look like:
Now, if you're billing clients $8,000 a month on average, your net cash flow is positive $2,600. You're making money. Your runway question isn't "How long until I run out?" It's "How long until a slow month or a client loss hurts?"
If you have $32,400 in the bank, that's six months of burn. But it's probably more than you need, because you're not burning through it at a constant rate. You're earning money most months. You only dip into savings when income dips below $5,400.
Conversely, if you're a SaaS founder with the same $5,400 monthly burn but zero revenue, that $32,400 is exactly six months. And that six months is a hard deadline, not a cushion.
The calculation matters because it changes your runway math. For income-generating businesses, you're not dividing total cash by burn rate. You're dividing cash by (burn rate minus average income). That number is usually much smaller.
Here's the thing about runway that nobody talks about clearly: it's not really about the math. It's about your psychology and your options.
Some people sleep well with three months of runway. They know they can pick up extra client work, cut costs, or launch a side project quickly if things get tight. They're confident in their ability to earn money. Their runway is a buffer, not a safety net.
Other people need twelve months. They have dependents, a mortgage, or health anxiety. They need to know they could go a full year without income and still be okay. For them, runway is peace of mind.
Both are valid. The question is: what's your number?
To figure it out, ask yourself:
For solo developers, the bootstrap path is usually the only path. That means you need enough runway to survive lean periods without external money.
After all the theory, here's what actually works for most solo developers:
If you're a freelancer with client work: Aim for four to six months of runway. This covers you for a slow quarter, losing a client, or taking time off. It's enough to make decisions from a place of strength, not panic. It's not so much that you're sitting on idle cash that could be invested in tools, learning, or a side project.
If you're a solo SaaS founder or building a product: Aim for nine to twelve months. You're not billing clients. Your runway is your only lifeline until the product generates revenue. Twelve months gives you time to build, launch, get feedback, iterate, and start acquiring customers without rushing.
If you're juggling both—client work and a side product: Aim for six to nine months. Your client work generates income, which extends your effective runway. But your product work is unpaid, which compresses it. The range accounts for volatility in client income.
These numbers assume you're disciplined about your burn rate and willing to cut costs if needed. If you're not, add three months to each.
Why these numbers? Because they balance three things:
Here's where runway intersects with something more important: revenue planning.
Runway tells you how long you can survive. But it doesn't tell you where you're heading. You could have twelve months of runway and still be on a path to making less money than you need. You could have three months of runway and be growing fast enough that you'll never need it.
The real question isn't just "How much runway do I have?" It's "How much runway do I have, and what am I doing with it?"
This is where Cashierr comes in. Runway is a static number—a snapshot of your current cash and burn rate. But your actual financial health depends on your trajectory. Are your client fees going up? Are you losing clients? Is your product gaining traction? Is your burn rate sustainable?
A revenue planning tool helps you answer those questions. It tracks your goals ("I want to make $10,000 a month by Q3"), projects your revenue based on your current clients and pipeline, and flags gaps before they become crises. It turns runway from a passive number into an active plan.
When you know your quarterly revenue target and you're tracking actual progress against it, runway becomes more meaningful. You're not just asking "How long until I run out?" You're asking "Am I on track to hit my goals before my runway runs out?"
There's a trap here, and it's worth calling out directly.
Many solo developers think that if they can just accumulate enough runway—say, twelve months or eighteen months—they'll feel secure. They'll be able to take risks. They'll be able to build their product without stress.
It doesn't work that way.
Runway is a necessary condition for security, but it's not sufficient. You can have twelve months of runway and still be stressed because you're not making progress on your product. You can have six months of runway and feel completely secure because your client work is stable and growing.
Security comes from three things:
What 4 Months of Solo SaaS Building Taught Me (The Hard Way) captures this well. The author found that even six months of runway wasn't enough to feel secure because the real issue wasn't cash; it was clarity. Once they figured out their product strategy and customer acquisition approach, the runway stress dropped significantly.
Runway is your first line of defense. But it shouldn't be your only one.
Smarter solo developers layer in contingencies:
Income diversification. Don't rely on one client or one revenue stream. If you're a freelancer, aim for three to five clients so that losing one doesn't crater your income. If you're building a product, keep some client work going to fund development. If you're doing both, you're already diversified.
Cost flexibility. Know which of your expenses are fixed and which are variable. Can you cut your cloud hosting bill? Pause your paid tools? Reduce your personal draw? The more flexible your costs, the longer your runway actually lasts.
Revenue acceleration options. What would you do if your runway was running low? Could you raise your rates? Take on more client work? Launch a paid tier of your product? Having a plan B makes runway less critical.
Skill diversification. This is less obvious, but important. The more versatile you are as a developer, the easier it is to pick up work if you need it. A full-stack developer has more options than a specialist in a narrow framework.
How to Extend Your Startup's Runway from Lenny's Newsletter covers practical strategies for extending runway without additional funding. Most of them apply to solo developers: cutting unnecessary costs, accelerating revenue, extending payment terms with clients, and being ruthless about prioritization.
Here's the dangerous part about runway: it's a static number that changes constantly.
Your runway today is based on your current cash and your current burn rate. But if you don't monitor both, you can wake up one day and realize you're in a worse position than you thought.
This happens in a few ways:
Slow-motion income decline. You lose a client, and you don't immediately replace them. Your burn rate stays the same, but your income drops. Your runway gets shorter every month, and you don't notice until it's critical.
Creeping burn rate increase. You add a new tool here, upgrade a service there, hire a contractor for a project. Your burn rate goes up by $200 a month. Over a year, that's $2,400, which compresses your runway by two months.
Opportunity cost blindness. You have six months of runway, but you're not tracking what you're doing with it. Are you building something that will generate revenue? Or are you just maintaining the status quo, burning through savings month after month?
This is why Cashierr exists. It's not just about planning your revenue. It's about tracking your actual numbers—income, expenses, client concentration, revenue growth—and flagging when things are drifting off track.
If you're monitoring your numbers, you catch problems early. If you're not, runway becomes a false sense of security.
There's a deeper question lurking here, and it's worth sitting with it.
Some solo developers optimize for runway. They save aggressively, build a big cash cushion, and feel secure knowing they can survive a long lean period. This approach makes sense if you're uncertain about your ability to generate income or if you have dependents and can't afford risk.
Other solo developers optimize for revenue. They keep minimal runway (three months or less) and focus all their energy on making more money. They'd rather be earning $15,000 a month with two months of runway than making $8,000 a month with twelve months of runway. This approach makes sense if you're confident in your ability to generate income and you want to maximize your earning potential.
Neither is wrong. But they're different strategies with different trade-offs.
The runway-optimization approach gives you peace of mind and flexibility, but it can lead to complacency. You have enough money, so you don't push yourself to grow. You stay comfortable.
The revenue-optimization approach forces you to stay sharp and focused, but it's stressful. You're always one bad month away from trouble.
Most solo developers are somewhere in the middle. They want enough runway to feel secure, but not so much that they lose the drive to grow. They want to balance peace of mind with progress.
If that's you, the sweet spot is probably four to eight months of runway, paired with a deliberate plan to grow your income. Not "accumulate runway and hope," but "keep enough runway to be safe, and use the rest of your time and energy to build something bigger."
Here's a risk that doesn't get enough attention: client concentration.
Imagine you're a freelancer with $8,000 a month in revenue. That sounds solid. But what if $5,000 of that comes from one client? You have four months of runway on paper. But if that client leaves, your actual runway is much shorter. You've lost 62% of your income, and your burn rate stays the same. Your effective runway just dropped from four months to less than two.
This is why understanding your client concentration matters. Cashierr tracks this for you, showing you what percentage of your revenue comes from your top clients. If one client represents more than 30% of your income, you're taking on risk.
The way to manage this risk:
If you've decided on your target runway, here's how to actually build it:
Step 1: Calculate your actual monthly burn. Don't guess. Track your spending for three months and average it. Include everything: personal draw, business expenses, taxes set aside.
Step 2: Decide your runway target. Based on your income volatility and risk tolerance, pick a number. Four months? Six? Twelve? Write it down.
Step 3: Calculate your runway goal in dollars. Multiply your monthly burn by your target months. If your burn is $5,000 and you want six months, your goal is $30,000.
Step 4: Build a plan to get there. If you're currently at $10,000 and your goal is $30,000, you need to save $20,000. At $2,000 a month, that's ten months. Be realistic about the timeline.
Step 5: Once you hit your goal, maintain it. Don't let it erode. As your burn rate increases (because you're earning more or living better), increase your runway savings proportionally.
Step 6: Monitor it monthly. Track your cash, your burn rate, and your income. Know your runway number. It should be as familiar to you as your current client list.
Runway is important, but it's not the whole picture.
The most successful solo developers I know have three things:
When you combine them—when you know your runway, you're tracking your revenue growth, and you're comparing your actual performance to your quarterly goals—you move from reactive ("Oh no, I'm running out of money!") to proactive ("Here's where I'm going and here's what I need to do to get there").
This is why tools matter. You can do this in a spreadsheet, but it's tedious and error-prone. A tool like Cashierr automates the tracking and gives you clarity. It answers the two questions every solo developer secretly worries about: "How much should I be making?" and "How's the business actually doing?"
After all of this, you might want a simple answer. "Tell me the number. How many months of runway should I keep?"
The honest answer is: it depends on your situation. But here's the framework to figure it out:
Start with your income volatility. Low, medium, or high? That's your baseline.
Layer in your risk tolerance. Can you handle stress? Or do you need security?
Consider your options. How quickly can you generate new income if needed?
Account for your responsibilities. Do you have dependents? Debt? Health issues? These affect how much cushion you need.
Build in your plan. What are you trying to do with your business? Your runway should be large enough to execute that plan without desperation.
For most solo developers—freelancers with some client work, maybe a side product, wanting to feel secure but not wanting to sit on idle cash—the sweet spot is six months of runway.
Six months is enough to handle a bad quarter. It's enough to take a risk on a new product or client type without panic. It's enough to feel secure. It's not so much that you're wasting opportunity cost.
But if your situation is different, adjust from there. More income volatility? Go to nine months. Less? Three months might be fine. Building a product? Twelve months. Freelancer with stable clients? Four months.
The number matters less than the thinking. Understand your situation, make a deliberate choice, and then monitor it. That's how you build real financial security as a solo developer.
Once you've figured out your runway, the next step is connecting it to your revenue plan.
Why Time Is A Lazy Way To Measure Your Startup Runway from Crunchbase makes an important point: measuring runway by months is less useful than measuring it by milestones. Instead of "I have six months of runway," think "I have enough runway to hit these revenue targets, launch this feature, and acquire these customers."
That's the shift from defensive (protecting yourself) to offensive (building something).
When you know your runway and you're deliberately using it to hit revenue targets, you're no longer just accumulating cash. You're investing in your business. You're building toward something.
That's when runway stops being a source of anxiety and becomes a tool for growth.
How to Make Your First 18 Months as a Solo Founder Count from First Round Review walks through how to structure your runway phases—building, growing, and sustaining—with clear milestones for each. Even if you don't have eighteen months, the framework applies. Know what you're trying to accomplish in each phase of your runway, and measure progress against that.
Andreessen Horowitz's perspective on runway focuses on the relationship between runway and fundraising cycles. For solo developers, this translates to: your runway should be long enough to reach a point where your business is clearly working (profitable, growing, or both) so that you don't have to make desperate decisions.
The common thread across all of this is the same: runway is a means to an end, not the end itself. The end is a sustainable, growing business that generates the income you need and want.
How many months of runway should a solo developer keep? There's no universal answer, but there's a thoughtful one.
Start with your income volatility, your risk tolerance, and your goals. For most solo developers juggling client work and building products, six months is a solid target. For pure freelancers with stable clients, four months might be enough. For SaaS founders with no revenue, twelve months is more realistic.
The key is to be intentional about it. Don't accumulate runway by accident. Decide on a target, build a plan to get there, and then maintain it. Monitor your numbers monthly so you catch problems early.
And remember: runway is only half the equation. The other half is revenue planning. When you combine them—when you know how long you can survive and you have a clear plan for growing your income—you move from anxiety to clarity.
That's when you can focus on what actually matters: building great work, shipping your ideas, and growing a business that pays you what you're worth.
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.