Xiaobai
Developer · Builder
Building AI engineering systems, developer tools and long-term digital assets at XBSTACK.
About Xiaobai & XBSTACK →
How Much Cash Should an Indie Developer Keep? Think in Runway, Not a Fixed Number of Months
A practical framework for freelancers and indie developers with uneven income: separate liquid cash, essential living costs, business fixed costs, debt, stable income, variable income, known one-off expenses and protected reserves, then stress-test normal, half-income and zero-income scenarios.
离线实验免责声明 / DISCLAIMER
本文属于“小白”的个人投资逻辑复盘与技术回测记录。文中提及的所有标的、策略及数据分析仅作为全栈工程师的离线实验案例,不构成任何形式的买入建议或投资咨询。金融市场具有极高的非线性风险,代码逻辑不代表财富收益。请务必保持独立审计,资产安全由您自行负责。
A common personal-finance question is: should I keep three months, six months, or twelve months of expenses in cash?
For people with stable payroll income, a rule of thumb can be a useful starting point. For freelancers, indie developers and small product businesses with uneven income, I think a better question is:
If income drops sharply, how many months of decision time does my current cash buy me?
That is a runway question.
This is not an abstract finance exercise for me. In 2026 I am maintaining XBSTACK and my own apps at the same time, while servers, domains, developer accounts, model usage and software subscriptions do not disappear during a weak revenue month. I am not publishing private household cash figures, but that operating reality is why I built the framework and the calculator below: establish the minimum monthly cost of keeping life and products running before thinking about investment returns or growth.
Runway is not “more cash is always better”
The simplest formula is:
Runway = cash available to spend ÷ monthly net cash-flow deficit
But personal runway becomes misleading if the inputs are too coarse.
Your bank balance may include taxes due next quarter, a known annual insurance bill, hardware you already need to replace, or money you have explicitly decided not to spend except in a deeper emergency.
Your monthly expenses may mix rent with optional software subscriptions.
Your income may include a large one-off project that is unlikely to repeat.
A useful runway model starts by separating those things.
Step 1: Separate account balance from cash actually available for runway
I would subtract at least two categories before calculating runway.
Known one-off expenses. Taxes, tuition, planned repairs, annual insurance, equipment replacement or committed business expenses that are already likely to happen.
A protected reserve. Money you deliberately do not want the normal runway calculation to consume.
That gives a more conservative number:
Cash available for runway = liquid cash - known one-off expenses - protected reserve

This prevents a large account balance from creating false confidence.
Step 2: Split monthly costs into at least three layers
I would not use one “monthly spending” number.
First, essential household costs: housing, basic food, transport, family obligations and other expenses that are hard to cut quickly.
Second, business fixed costs: servers, domains, developer accounts, software, required contractors or other costs that keep the business operating.
Third, minimum debt payments.
Together, these form the monthly cost base before any emergency cost-cutting plan.
Step 3: Stable income and possible income are not the same thing
This is where variable-income workers can make their runway look much healthier than it is.
Stable income should contain only the high-confidence part: recurring contracts, durable subscriptions, salary or other predictable cash flow.
Variable income can still be included, but use a conservative estimate rather than the average of a few unusually good months.
Then look at three scenarios:
- Normal income: stable income plus conservative variable income.
- Income cut in half: all income at 50%.
- Zero income: current cash only.
The zero-income case sounds pessimistic, but it answers the cleanest question: if no new money arrives, how much time do I have before cash forces a decision?

Why six months is not a universal answer
The U.S. Consumer Financial Protection Bureau’s emergency-fund guidance does not prescribe one universal amount. It explicitly says the amount depends on your situation and discusses the additional challenge of saving when pay fluctuates.
Investor.gov notes that some investors keep up to about six months of income in savings, but presents that as a common practice rather than a mandatory standard. Its broader guidance places emergency savings, high-interest debt management and long-term investing in the same foundation-building process.
The important idea is not whether the magic number is three or six.
It is that an emergency reserve can reduce the chance that a financial shock pushes you into expensive debt or forces you to sell long-term assets at a bad time.
- CFPB: An essential guide to building an emergency fund
- Investor.gov: Save for a Rainy Day
A four-layer cash model
I now find it more useful to think of cash in four layers.
1. Operating cash
Money that will probably leave the account in the next month or two for normal life and business.
2. Known-expense reserve
Money for costs that are not monthly but are already foreseeable.
3. Runway
Cash that buys time when income falls.
4. Protected reserve
A final buffer that is not casually included in normal runway.
The benefit of this model is that cash stops looking like one big pile of “idle money.”
Some cash has a low expected return, but what it buys is option value: the ability not to accept a bad contract after one weak month, not to abandon a product because a launch slipped, and not to sell volatile long-term assets because living expenses arrived at the wrong time.
How long should runway be?
I do not think there is one correct answer.
Useful variables include:
- how long it usually takes to replace lost income;
- how many independent income sources you have;
- whether other people depend on your income;
- fixed debt obligations;
- business costs that cannot be stopped immediately;
- insurance coverage;
- other liquid or near-liquid assets;
- how aggressively you are willing to cut spending after an income shock.
A solo developer with a durable long-term contract and very low business overhead does not have the same cash-risk profile as someone supporting a family while funding a product with volatile revenue.
A better workflow is to choose a target runway for your own situation and reverse-calculate the cash required.
I built that process into a local browser tool:
It asks for:
- liquid cash;
- essential monthly living costs;
- business fixed costs;
- minimum debt payments;
- stable income;
- conservative variable income;
- known one-off expenses;
- a protected reserve.
It then compares normal, half-income and zero-income scenarios.
Keep runway cash and long-term investment money conceptually separate
If money exists to keep your household and business operating over the next few months, its primary job is not to maximize expected return.
Long-term investment capital can accept market volatility precisely because you do not need it immediately. Runway cash has the opposite job: it must be available when the shock occurs.
That does not mean holding unlimited cash.
Investor.gov also points out that cash savings can lose purchasing power to inflation over long periods, while long-term investing has a different role in wealth building. The answer is not to pretend the tradeoff does not exist. It is to match the asset to the time horizon.
Long-term money can tolerate long-term volatility.
Short-term survival money needs short-term availability.
For an indie developer, runway is not just financial conservatism. It is time to make decisions without being forced into them.
Related tools and reading
- Cash Runway Calculator
- Compound and FIRE Calculator
- Programmer FIRE system: income, savings rate and long-term cash flow
This article and calculator are for general financial-planning and scenario-analysis purposes. They are not individualized investment, tax or legal advice.
More to Explore
Topic hub →AI Engineering Weekly
Production changes, real failures, experiments and new XBSTACK assets.
DISCUSSION
Questions, verification and corrections
Sign in to comment. Every new comment is reviewed before publication; while pending, it is visible only to you and the administrator.