67. Runway and Burn

Runway is the amount of time your startup has before cash runs out. Burn is the speed at which cash is leaving. These are simple ideas, but founders often make them fuzzy because the truth is uncomfortable.

Runway is not a vanity metric for investor updates. It is a deadline. It tells you how long you have to learn, sell, build, collect, fundraise, cut, or change direction.

Burn rate

There are two burn numbers every founder should know:

Gross burn: total cash outflow per month.
Net burn: cash outflow minus cash collected during the month.

Example:

Item	Amount
Salaries and contractors	Rs 8,00,000
Software, rent, tools, infra	Rs 2,00,000
Marketing and sales spend	Rs 1,50,000
Professional fees and admin	Rs 50,000
Total gross burn	Rs 12,00,000
Cash collected from customers	Rs 5,00,000
Net burn	Rs 7,00,000

If the company has Rs 70,00,000 in cash and net burn is Rs 7,00,000, simple runway is 10 months. But simple runway is often too optimistic because collections slip, hiring happens, taxes arrive, refunds happen, and one-time costs appear.

Conservative runway

Use conservative runway for decisions. It should assume:

Some customers pay late.
Some deals do not close.
Some expenses arrive earlier than expected.
Hiring and vendor costs increase once committed.
Fundraising takes longer than planned.
Statutory and professional costs are not optional.

A practical formula:

Conservative runway = cash available / expected monthly net burn under a cautious scenario

If you do not know the cautious scenario, build one. Reduce expected collections, include committed hires, include known one-time costs, and include tax/compliance reserves.

Fixed, variable, one-time, and hidden costs

Burn becomes easier to manage when costs are classified correctly.

Cost type	Examples	Founder question
Fixed costs	Salaries, rent, retainers, core tools, cloud baseline.	Can we carry this even if revenue slips?
Variable costs	Payment fees, logistics, cloud usage, support load, delivery cost.	Does this rise with customer activity?
One-time costs	Devices, legal project, deposits, migration, event, certification.	Is this truly one-time or becoming recurring?
Hidden costs	Founder time, implementation, support debt, refunds, delayed collections.	What cost is not visible in the expense line?

Hidden costs are especially dangerous. A customer who pays well but consumes endless founder time may not be profitable. A pilot that looks cheap but delays the product roadmap may be expensive. A large customer that pays late can damage runway even if the contract value looks attractive.

Burn quality

Not all burn is equal.

Burn type	Good version	Bad version
Learning burn	Customer discovery, prototypes, experiments with clear decisions.	Random experiments nobody reviews.
Revenue burn	Sales, onboarding, implementation, success for a defined ICP.	High-touch work for customers that will never repeat.
Product burn	Work that improves activation, retention, reliability, or differentiation.	Feature sprawl driven by anxiety.
Team burn	Hiring that removes a proven bottleneck.	Hiring to look bigger or avoid founder discomfort.
Brand/distribution burn	Content, events, partnerships, or community with a learning loop.	Spending for visibility with no conversion path.

The goal is not always to minimize burn. The goal is to spend on the work that buys learning, revenue, retention, or risk reduction.

Fundraising runway

If you plan to raise capital, runway must include fundraising time. Many founders start too late because they calculate runway as “months until zero.” That is dangerous.

Think in three zones:

Zone	Meaning	Founder action
12+ months	You have room to build evidence	Improve metrics and investor narrative
6-12 months	Fundraising or profitability plan must be active	Start process, tighten spend, improve collections
3-6 months	Decision pressure is high	Cut burn, close cash, consider bridge or strategic changes
Under 3 months	Survival mode	Founder must act immediately; optional work stops

Do not wait until the company is desperate. Desperation weakens negotiation, hiring, morale, and strategic judgment.

Runway scenarios

Build three views every month:

Scenario	Assumption	Use
Current	Present cash, present burn, expected collections.	Understand today’s trajectory.
Conservative	Lower collections, slower sales, committed hires, known one-time costs.	Make safety decisions.
Survival	Only essential costs, aggressive collections, delayed optional work.	Know the emergency plan before panic.

The survival scenario is not the plan. It is the escape route. You write it while calm so you are not inventing it while scared.

Cash Decision Dashboard

Every founder should have a small cash dashboard that can be reviewed in 15 minutes. It should not require a finance team or a complex model.

Metric	Healthy	Warning	Danger
Conservative runway	12+ months for venture-backed execution, or clearly profitable path.	6-12 months with unclear next milestone.	Under 6 months without committed funding or profitability plan.
Net burn trend	Stable or improving because revenue/collections improve.	Burn rising faster than learning or revenue.	Burn rising while customer evidence is weak.
Receivables ageing	Most invoices paid within agreed terms.	31-60 day bucket growing.	90+ day bucket material to runway.
Hiring commitments	Each hire tied to a bottleneck and milestone.	Hiring because the plan assumed it.	Offers out while runway is already tight.
Revenue quality	Repeatable revenue from target customers.	One-off services or pilots hiding product weakness.	Revenue depends on customers that are expensive to serve.
Fundraising status	Process started before need, with evidence improving.	Investor conversations are vague.	Cash-out date is close and round is not real.

The dashboard should produce decisions. If a metric is red for two review cycles, assign an action owner. If everything is green, still ask whether the company is buying enough learning with its cash.

Hiring and runway

Every hire changes the company’s risk profile. Salary is not the only cost. Hiring also adds payroll taxes or statutory contributions where applicable, tools, management load, onboarding time, equipment, and severance or notice-period complexity if things go wrong.

Before each hire, ask:

What company risk does this hire reduce?
What evidence says this work is needed now?
How many months of runway does this hire consume?
What milestone should improve because of this hire?
What happens if we delay by 60 days?

Early hiring should usually follow proof. Hire when the work is repeated, valuable, and blocking progress. Do not hire merely to feel like a “real company.”

Extending runway

Runway extension is not only cost cutting. It can come from cash discipline, revenue design, and financing choices.

Options:

Collect receivables faster.
Move customers to prepaid or annual plans where value and trust justify it.
Reduce tools, subscriptions, contractors, and low-signal experiments.
Delay hires that are not tied to near-term learning or revenue.
Renegotiate vendors or payment terms.
Offer paid pilots instead of free pilots.
Add services revenue if it strengthens product learning and customer value.
Use grants, debt, or bridge financing carefully where appropriate.
Raise prices for segments that receive clear value.

Cutting burn is powerful, but cutting the wrong thing can damage learning or revenue. Do not cut customer discovery, core reliability, or the sales motion that is producing proof just because it is visible in the expense sheet.

Expense triage

When runway tightens, classify every recurring cost:

Category	Meaning	Action
Core	Required to serve customers, keep product reliable, or meet obligations.	Protect, but still monitor.
Learning	Produces evidence for current strategy.	Keep if the learning loop is clear.
Revenue	Directly supports pipeline, conversion, onboarding, retention, or collections.	Keep if ROI or strategic need is visible.
Optional	Nice, but not tied to current milestone.	Pause or reduce.
Waste	No clear owner, outcome, or use.	Cut.

This avoids performative austerity. You do not cut important work just because it is easy to cut. You cut the work that no longer serves the company.

Burn reduction without breaking the company

When cash pressure rises, founders often make two bad moves: they cut too little because they are scared of the truth, or they cut everything visible without understanding what keeps the company alive. A better approach is to protect the engine and remove the drag.

Area	Protect	Question before cutting
Customers	Support for paying customers, onboarding, bug fixes, collections relationship	Will this cut increase churn or delay cash?
Product	Reliability, core workflow, activation, retention, security basics	Will this cut make the product less usable for the target customer?
Sales	Founder-led selling, working channels, serious pipeline, proposal follow-up	Will this cut reduce near-term learning or revenue?
Team	People doing proven, essential work	Is the role tied to current proof or only to future optimism?
Compliance	Statutory, tax, payroll, accounting, legal obligations	Is this actually optional or just uncomfortable?

Then remove or reduce:

Tools nobody owns.
Agencies without a clear output.
Low-conviction paid marketing.
Events that produce visibility but no pipeline.
Consultants doing work the company will not use.
Custom customer work that is not priced properly.
Hires planned for a future stage the company has not earned.

Runway discipline should make the company sharper, not smaller in a random way.

Runway decision log

Keep a simple log of every major cash decision. It protects founders from rewriting history and helps investors or advisors understand the reasoning.

Field	Example
Date	2026-07-02
Decision	Delay senior marketing hire by 60 days
Cash impact	Saves two months of salary and hiring cost
Reason	Acquisition channel is not yet proven enough for a senior hire
Risk	Founder continues to own marketing longer
Review date	Revisit after 20 qualified demos or 90 days

This log is especially useful during stressful periods. If you cut, delay, hire, fundraise, or change pricing, write down why. The discipline prevents random decisions from pretending to be strategy.

Collections as runway

In Indian B2B, collections can be the difference between healthy and stressed runway. A signed contract may still require purchase order processing, vendor registration, GST-compliant invoices, internal approvals, and payment follow-up.

Build collections into the sales process:

Confirm billing entity, GST details, and purchase order process before invoice.
Ask who approves payment and who processes it.
Put payment terms in the order form or contract.
Follow up before the due date, not only after.
Age receivables weekly: 0-30, 31-60, 61-90, 90+ days.
Escalate late payments with context and relationship, not only reminders.

Founders often find “runway” by collecting money already owed to them.

Receivables Aging Review

For Indian B2B founders, a weekly receivables review can be as important as pipeline review.

Bucket	Meaning	Founder action
0-30 days	Recently invoiced or within normal terms.	Confirm invoice receipt, PO reference, GST details, and payment date.
31-60 days	Slippage has started.	Founder or sales owner contacts business sponsor and finance contact.
61-90 days	Cash planning risk.	Escalate politely, pause extra unpaid work where appropriate, confirm dispute if any.
90+ days	Serious collection risk.	Senior founder call, written payment plan, legal/professional advice if needed.

Do not make collections feel like an admin afterthought. If the sale required founder effort, the collection may also require founder effort. The best time to prevent late payment is before the contract is signed: define billing milestones, payment terms, documents required, and escalation contacts.

The runway conversation

When runway becomes tight, founders often delay telling the team. Silence creates rumours and poor decisions.

A useful internal runway update should say:

Section	What to say
Reality	Current runway range, without unnecessary drama.
Cause	What changed: sales, collections, spend, funding, churn, or one-time cost.
Decision	What the company will do now.
Priorities	What remains important and what stops.
Ask	What every team or founder needs to own.

Do not share raw panic. Share clear reality and clear action.

Investor And Advisor Runway Update

When cash is tight or the company is changing spending, investors and advisors need a concise update. Hiding the situation usually makes help arrive late.

Use this format:

Section	What to include
Cash position	Cash in bank, conservative runway, and date of last calculation.
Burn movement	What changed in burn: hiring, tools, infra, sales, collections, refunds, or one-time costs.
Revenue and collections	Closed revenue, collected cash, overdue receivables, and near-term collection plan.
Milestone plan	What evidence the company will create before the next financing or profitability decision.
Actions taken	Cuts, delays, renegotiations, hiring changes, sales focus, or pricing changes.
Specific asks	Introductions, bridge interest, collections advice, hiring pause advice, finance/legal help.

The update should be factual, not theatrical. Strong founders do not pretend runway is infinite. They show that they understand the situation and are acting early.

Runway triage meeting

When runway becomes uncomfortable, founders need a more serious weekly meeting than the normal finance review. The goal is to decide what to preserve, what to cut, and what to accelerate.

Use this agenda:

Question	What to look for	Decision
What is the honest runway range?	Current, conservative, and payroll-first runway.	Which number should guide action?
What changed since last week?	Collections, sales, churn, expenses, hiring, funding, one-time costs.	Is the problem temporary or structural?
What must be protected?	Paying customers, core product, security, collections, team trust, compliance.	What cannot be cut casually?
What can be paused now?	Hiring, agencies, experiments, events, tools, low-priority roadmap work.	What stops immediately?
What can bring cash forward?	Receivables, annual plans, paid pilots, implementation fees, customer advances.	Who owns each cash action?
What hard decision has a deadline?	Layoff, pivot, bridge, shutdown, salary deferral, market change.	Date by which founders decide.

Triage should be calm but direct. The founder’s job is to create time for the company without pretending that time is free.

Cash actions by time horizon

Runway work should separate immediate cash actions from structural fixes. Mixing them creates confusion.

Horizon	Goal	Examples
7 days	Stop avoidable leakage and collect obvious cash.	Freeze non-essential spend, call overdue customers, cancel unused tools, pause new offers.
30 days	Reduce burn and improve near-term inflows.	Renegotiate vendors, reprice custom work, change payment terms, pause hiring, close paid pilots.
90 days	Improve the business model.	Focus ICP, simplify product scope, improve onboarding, increase gross margin, improve retention.
180 days	Reset strategy if needed.	Fundraise with evidence, become default alive, pivot, sell assets, seek strategic partnership, or shut down cleanly.

If a company has only 60 days of runway, do not spend all the time debating 180-day strategy. First buy time. Then improve the model.

Runway thresholds by company type

Different startups need different runway buffers. A bootstrapped services-to-product company, a regulated fintech, and a venture-backed SaaS company cannot use the same comfort number.

Company type	Why runway need differs	Founder guidance
Bootstrapped product or services-to-product	Cash comes from customers, but founder income may be uneven.	Keep enough personal and company buffer to avoid accepting bad work out of fear.
B2B SaaS	Sales and collections cycles can be slow, especially enterprise.	Keep runway for sales cycle plus onboarding plus payment delay, not only closing.
Marketplace	Growth can consume cash through both sides of the market.	Watch contribution margin, trust/safety, support, and refunds before scaling incentives.
D2C/commerce	Inventory, logistics, returns, and ad spend can trap cash.	Model working capital separately from P&L profitability.
Fintech/health/regulated workflows	Compliance, security, licenses, and trust take time.	Keep extra buffer for regulatory, security, audit, and partnership delays.
AI/infrastructure product	Compute and technical experimentation can spike unexpectedly.	Track usage cost per customer or workflow before scaling usage.

The point is not to copy someone else’s runway target. The point is to set a threshold that fits your sales cycle, cost structure, obligations, and funding strategy.

Runway and morale

Runway is financial, but it affects morale quickly. Teams can handle difficult reality better than vague anxiety. When cash is tight, communicate enough for people to understand priorities without turning every employee into a finance detective.

Situation	Poor communication	Better communication
Runway is healthy but lower than planned	”Everything is fine."	"We are tightening spend so we can protect the next milestone.”
Hiring is paused	Silence or endless delay.	”We are pausing hiring until revenue/funding evidence improves.”
Costs are being cut	Random cancellations.	”We are protecting customer work and cutting non-core spend.”
Fundraising is active	Overpromising.	”We are in process, but no money is counted until it is in the bank.”
Survival decisions may be needed	Panic in private, cheerfulness in public.	”We have a decision date and are working the plan.”

Founders should not overshare every cash detail with everyone. But if the team can feel pressure and leadership refuses to name it, trust falls. Clear priorities protect focus.

Payroll-first runway

When runway is tight, calculate a payroll-first view. This is the number of months the company can meet people commitments while keeping essential operations alive.

Include:

Salaries, contractors, interns, consultants, and founder salary commitments.
Applicable payroll processing, statutory, benefits, and professional costs.
Core tools and infrastructure required for the team to work.
Customer support, hosting, and security costs that protect existing customers.
Minimum compliance and accounting costs.

Exclude:

Optimistic future sales.
Uncommitted investment.
Optional marketing experiments.
Hiring that has not yet been approved.
Customer payments without a confirmed date and owner.

Payroll-first runway is useful because it forces the founder to separate hope from obligation. If simple runway says 8 months but payroll-first conservative runway says 4 months, the company should act like it has 4 months.

Bridge financing decision screen

Bridge financing can help a strong company cross a temporary gap. It can also delay a necessary cut, pivot, or shutdown. Before taking bridge money, run a decision screen.

Question	Good reason to bridge	Bad reason to bridge
What will the bridge prove?	A specific milestone: revenue, retention, enterprise close, regulatory step, or fundraise-ready evidence.	”We need more time” without a sharper plan.
Why is the gap temporary?	Deal slipped, round delayed, receivable delayed, or milestone almost reached.	Core business model is not improving.
What changes after the bridge?	Higher valuation evidence, profitability path, strategic buyer interest, or stronger investor process.	Same company, same burn, same uncertainty.
What is the cost?	Terms are understood and acceptable.	Founder accepts any terms because cash is low.
What is the alternative?	Clear comparison against cuts, revenue, customer advances, or slower plan.	No serious non-dilutive or cost action considered.

Do not use bridge money to avoid hard thinking. Use it only when the next proof point is specific enough to justify the dilution, debt, or obligation.

Common mistakes

Counting committed investment before it lands: term sheets, verbal interest, and “almost done” rounds are not cash.
Using best-case revenue in runway: runway should survive disappointment.
Ignoring one-time costs: legal, audit, deposits, devices, migration, travel, and compliance can hit cash suddenly.
Cutting too late: small cuts early are easier than painful cuts under crisis.
Cutting blindly: runway should be extended in a way that preserves the startup’s learning engine.
No receivables discipline: unpaid invoices quietly become emergency fundraising.

Practical process

Calculate gross burn and net burn for the last three months.
Build three runway views: current, conservative, and post-hiring.
Create a receivables ageing list and assign follow-up owners.
Mark every expense as core, useful, optional, or waste.
Decide the runway threshold that triggers cost action.
If fundraising is needed, start before the company enters the danger zone.

Runway Rescue Plan

Write a rescue plan before you need it. The goal is not pessimism. It is to prevent panic from making expensive decisions.

Create three triggers:

Trigger	Example meaning	Action
Watch zone	Runway is healthy but trending down	Freeze nice-to-have spend, increase collections discipline, review hiring timing
Decision zone	Runway is approaching the company’s minimum comfort level	Pause non-critical hiring, renegotiate vendors, prioritize revenue and funding actions
Survival zone	Runway is too short for normal execution	Cut fast, preserve customers, protect core team, communicate clearly, raise only with honesty

Then list the actions available:

Collect faster: receivables follow-up, annual prepay offers, milestone billing, payment links, founder calls to overdue customers.
Reduce waste: unused tools, weak contractors, low-quality marketing spend, travel, low-priority agencies, duplicated software.
Delay commitments: hiring, office, equipment, non-critical legal work, experimental product bets.
Increase cash: services revenue, implementation fees, paid pilots, bridge round, grants, customer advances, strategic partnerships.
Protect learning: do not cut the only channel, product workflow, or customer-support loop that proves whether the startup should exist.

Every rescue action has a cost. Cutting blindly can save cash while killing the startup’s learning engine. The founder’s job is to preserve the core bet and remove everything that does not help it survive.

30-Day Cash Emergency Operating Plan

When runway gets uncomfortable, founders often jump straight to dramatic action: fire people, beg investors, push customers too hard, or disappear into spreadsheets. A better response is a short operating plan with facts, owners, dates, and communication.

Use this 30-day plan when runway falls below your written comfort zone, a fundraise slips, collections are delayed, or payroll confidence becomes shaky.

Day 1: Establish the real cash position

Do not start with the P&L. Start with bank reality.

Create one sheet with:

Item	What to capture
Bank balance	Actual cash available across accounts
Payroll due	Salary, contractor, consultant, PF/ESI/TDS obligations where applicable
Statutory dues	GST, TDS, ROC, professional tax, and any pending filings or penalties
Vendor dues	Cloud, tools, rent, legal, finance, agencies, contractors
Customer receivables	Invoice amount, due date, buyer, payer, blocker, owner
Committed inflows	Signed contracts, approved POs, confirmed payments, grants, investment money already wired or formally scheduled
Uncertain inflows	Verbal promises, likely renewals, investor interest, “expected soon” payments

Separate committed cash from hoped-for cash. Hope is allowed in founder life; it is not allowed in runway math.

Days 2-3: Build the survival calendar

Convert runway into a calendar, not only a number.

Date:
Opening cash:
Expected inflows:
Mandatory outflows:
Optional outflows:
Payroll confidence:
Statutory/compliance risk:
Customer delivery risk:
Decision needed:

Make this weekly for the next 13 weeks. If the company cannot confidently pass the next payroll, the founder’s priority changes immediately. Product roadmap, hiring, brand, and long-term strategy all become secondary to cash control and stakeholder trust.

Days 3-5: Freeze new commitments

Announce a commitment freeze before making cuts. This prevents the hole from getting deeper while you gather facts.

Freeze:

New hiring and offer letters.
New annual software contracts.
Non-critical agency retainers.
Travel, events, office expansion, devices, and discretionary reimbursements.
New product promises that require custom delivery.
Founder reimbursements that can responsibly wait.

Allow exceptions only if the spend protects payroll, statutory compliance, security, customer retention, revenue collection, or a near-term signed deal.

Days 5-10: Pull cash forward responsibly

Start with money the company has already earned or can earn cleanly.

Cash action	Founder script
Overdue invoice	”We are closing our month-end cash planning. Can you help us get this invoice cleared by [date]? Is anything blocking payment from your side?”
Milestone billing	”We have completed [milestone]. Can we raise the next invoice now and align the remaining delivery schedule?”
Annual prepay	”If we move you to annual billing, we can offer [fair discount/extra support]. Would that work for your budgeting cycle?”
Paid pilot	”We can run this as a paid pilot with clear success criteria instead of a free experiment.”
Implementation fee	”This setup requires meaningful work. We charge an implementation fee so the team can support you properly.”

Do not mis-sell to solve a cash problem. Bad-fit revenue can become refund risk, support burden, churn, and reputation damage.

Days 7-14: Decide cuts by function, not panic

Use a four-bucket review:

Bucket	Meaning	Default action
Survival-critical	Payroll, statutory dues, hosting/security, core customer delivery	Protect
Evidence-critical	Work that proves demand, retention, revenue, or fundability	Protect or narrow
Useful but deferrable	Helpful work that does not change near-term survival	Pause or reduce
Comfort/status/noise	Spend that mostly reduces inconvenience or looks good	Cut

The hardest calls are usually in the “useful but deferrable” bucket. Be honest. A good founder can pause useful work without pretending it was useless.

Days 10-20: Communicate before trust breaks

Cash pressure becomes more dangerous when people sense it before leaders explain it. Communicate with the right level of detail.

Team message:

We are tightening cash discipline because [facts].
Payroll and customer commitments are the first priority.
For the next [period], we are pausing [items], continuing [items], and reviewing [decision] by [date].
This is not a performance judgment. It is a runway decision.
I will share updates every [cadence].

Investor/advisor message:

Current runway:
Main cash risks:
Actions already taken:
Help needed:
Decision date:

Customer message, if delivery is affected:

We are changing the delivery timeline for [item].
What remains unchanged:
What changes:
Your point of contact:
Next review date:

Do not create panic with unnecessary drama. But do not hide facts from people whose work, money, or trust is affected.

Days 20-30: Choose the strategic path

After the emergency actions, choose the path deliberately:

Path	When it fits
Continue with reduced burn	Core demand is real and cuts create enough runway to prove the next milestone
Revenue sprint	Short-term customer cash can extend runway without damaging trust
Bridge round	Existing investors believe the next milestone is credible and specific
Strategic sale/acquihire	Team, product, customers, or IP may be worth more inside another company
Pivot	The current direction lacks evidence but a sharper hypothesis can be tested within remaining runway
Shutdown	Continuing would damage employees, customers, creditors, family finances, or founder integrity

The decision should be written, even if it is short. Cash crises punish vague optimism. They reward calm, dated decisions.

Cash Crisis Red Lines

Some actions can keep the company alive for a few more weeks while creating personal, legal, or ethical damage. Avoid them.

Red lines:

Do not delay statutory dues casually. In India, GST, TDS, PF, ESI, ROC, and payroll-related obligations can create serious downstream risk.
Do not use employee reimbursements, contractor payments, or vendor dues as invisible financing without communication.
Do not promise salary dates you are not confident about.
Do not collect customer money for work you know you cannot deliver.
Do not sign a bridge, debt, or customer contract whose obligations you have not understood.
Do not mix personal and company money casually without accounting and advisor review.
Do not hide material cash risk from co-founders or directors.

In a runway crisis, reputation is also capital. Preserve it.

Runway Stress Test

Runway should be tested against disappointment. Once a month, stress-test the plan before reality does it for you.

Stress case	Question
Revenue delay	What happens if expected collections arrive 30-60 days late?
Sales miss	What happens if new revenue is 50 percent of plan for the next quarter?
Hiring delay	What happens if key hires join two months late or not at all?
Cost surprise	What happens if cloud, AI, legal, compliance, or support cost doubles for one month?
Funding delay	What happens if the round closes 90 days later than hoped?
Churn shock	What happens if the largest customer pauses, churns, or delays payment?

For each stress case, write:

Runway impact:
Decision trigger:
Action if this happens:
Owner:
Date to review:

This exercise is not pessimism. It gives the founder optionality. If the company can survive only the best-case plan, the plan is not a plan; it is a wish with a spreadsheet.

Runway Trigger Matrix

Runway decisions become easier when triggers are written before the company is under pressure. Do not wait until cash is frightening to decide what you believe.

Create a trigger matrix:

Runway level	Founder stance	Default actions	Communication
18+ months	Build and learn with discipline	Keep hiring tied to proof, monitor burn quality, avoid lazy spending	Normal investor and team updates
12-18 months	Focused execution	Freeze speculative hiring, improve collections, prioritize milestones that increase financing or revenue options	Explain priorities clearly to leadership
9-12 months	Decision zone	Review every hire and vendor, start fundraise or revenue acceleration early, cut weak experiments	Share runway logic with core team and advisors
6-9 months	Hard choices	Reduce non-core spend, protect payroll and customers, narrow roadmap, push collections personally	Communicate calmly; avoid surprises
3-6 months	Survival mode	Cut fast, sell or fundraise honestly, preserve legal/compliance/payroll, consider bridge or strategic options	Direct founder communication to team, investors, and key customers
Under 3 months	Emergency	Only survival-critical work remains; decide shutdown, bridge, sale, or drastic restructuring	No vague optimism; clear plan and dates

Add company-specific rules:

Minimum runway we will tolerate:
Hiring pause trigger:
Fundraising start trigger:
Cost-cut trigger:
Founder salary/reimbursement trigger:
Customer collection escalation trigger:
Shutdown planning trigger:

The matrix is not a promise to cut at an exact month. It is a way to prevent denial. If revenue quality, fundraising likelihood, or gross margin is weak, act earlier. If revenue is reliable and collections are strong, you may have more room. The founder’s job is to interpret runway with context, not obey a spreadsheet mechanically.

For India, include receivables separately. A company with 10 months of runway on paper and 90-day enterprise collections may be less safe than it looks. A company with 7 months of runway but annual prepaid customers, low churn, and fast collections may have more control.

Runway Mode Switch

A founder should know which operating mode the company is in. The same decision can be wise in one runway mode and reckless in another.

Mode	What it means	Founder behavior
Build mode	Runway is healthy and proof is improving	Invest behind the clearest constraint; keep burn quality visible
Focus mode	Runway is acceptable but uncertainty is rising	Narrow roadmap, slow speculative spend, protect customer learning
Decision mode	Runway requires a major decision soon	Freeze non-essential commitments, update investors/advisors, choose a dated path
Survival mode	Cash can no longer support normal execution	Protect payroll, customers, statutory dues, and responsible options
Closure mode	Continuing may harm stakeholders	Prepare shutdown, sale, bridge, or restructuring with advisor support

Switch modes deliberately. Do not let the company behave like it is in build mode while the cash reality says decision mode.

Mode-switch triggers can include:

Runway falling below the written threshold.
Receivables aging beyond the forecast.
A funding process slipping by more than 30-45 days.
Gross margin getting worse as revenue grows.
A major customer churn, payment delay, or contract dispute.
Payroll, tax, vendor, or statutory obligations becoming unclear.
Founder health or team trust degrading because of cash pressure.

When mode changes, send a short internal note:

We are moving from [mode] to [mode] because [facts].
For the next [period], our finance priority is [priority].
This means we will continue [work], pause [work], and review [decision] by [date].

This protects morale because the team sees logic instead of sudden founder mood. It also prevents fake normalcy. Cash pressure is easier to handle when everyone understands the operating mode.

Extending runway is not only cutting costs. It is a menu of cash, revenue, scope, financing, and timing moves. Each move has tradeoffs.

Move	When useful	Risk
Tighten collections	Customers owe real money and payment follow-up is weak.	Can damage relationship if handled carelessly.
Annual or prepaid plans	Customers trust the product and want discount or commitment.	Discounting too heavily weakens future pricing.
Paid pilots or implementation fees	Setup work creates real customer value.	Can become services work without product learning.
Vendor renegotiation	Tools, cloud, agencies, rent, or contractors have flexibility.	Saves little if founder time cost is high.
Hiring delay	Role is useful but not yet tied to a proved constraint.	Overloads team if delayed too long.
Scope reduction	Roadmap is too broad for current cash reality.	Can hurt morale if not explained clearly.
Founder-led sales push	Founder can convert cash faster than a new hire.	Pulls founder away from product or team if unmanaged.
Bridge or insider round	Existing investors trust the next milestone.	Weak bridge without plan only postpones the problem.

Do not use all moves at once. Pick the few that fit the real bottleneck. A company with poor collections needs different action from a company with no demand.

Hiring Freeze Rules

Hiring freezes fail when they are emotional or vague. A good freeze protects the company while allowing exceptions that truly matter.

Write freeze rules:

Rule	Example
Default stance	No new roles until runway is above 12 months or revenue milestone is reached.
Exception path	Role must unlock revenue, retention, compliance, security, or delivery bottleneck.
Approval	Founder and finance owner review runway impact before offer.
Backfill policy	Backfills are not automatic; role must be re-justified.
Contractor policy	Contractor spend follows the same logic as hiring.
Review date	Freeze is reviewed every 30 days with cash and milestone evidence.

The message to the team should be honest: “We are not freezing because people failed. We are freezing because the company needs more proof before adding fixed cost.”

Revenue Pull-Forward Without Breaking Trust

Pulling revenue forward can help runway, but it can also create future pain. Use it only when the customer receives real value.

Healthy pull-forward:

Annual prepay with fair discount.
Paid implementation where setup work is real.
Upgrade tied to usage or additional team.
Early renewal for a satisfied customer.
Pilot fee with written success criteria.

Unhealthy pull-forward:

Deep discount to close a weak-fit customer.
Prepayment for a product that will not be ready.
Renewal pressure on an unhappy customer.
Custom promise made only for cash.
Channel stuffing or inflated booking.

Cash collected by damaging trust is expensive capital. The founder should prefer slower cash with a clean promise over faster cash that creates churn, refunds, support debt, or reputation damage.

Default Alive Path

A company is default alive when its current path can reach sustainability before cash runs out, without depending on a new financing round. Not every startup must be default alive at every stage, but every founder should know whether they are.

Write a default alive path:

Question	Answer
Current cash
Conservative runway
Current monthly burn
Revenue collected last month
Gross margin after delivery/support
Monthly revenue needed for break-even
Most realistic path to that revenue
Time needed to reach it
Cuts needed if revenue is slower
Financing needed if path is not realistic

Default alive signals

Signal	Meaning
Revenue is recurring or reliably repeatable	The business has a base to build on.
Gross margin is healthy after real support/delivery cost	Growth can fund more of itself.
Collections are predictable	Runway math is not fantasy.
CAC or sales effort is understood	Growth spend can be controlled.
Churn is low enough	New revenue is not replacing leaking revenue.
Hiring can be delayed without killing the core business	Fixed cost is not running ahead of proof.

Default alive is not a badge. It is a planning state. A venture-backed company may choose to be default dead for a period if it is buying a meaningful milestone. But the founder should be honest about that trade.

Default dead but fundable

If the company is not default alive, ask:

What evidence must we create before cash runs out so financing, acquisition, or profitability becomes realistic?

That evidence may be revenue growth, retention, gross margin, enterprise pipeline, product usage, regulatory approval, strategic partnership, or a strong acquisition path. If the cash burn does not buy evidence, it is not strategy. It is drift.

Burn Quality Review

Burn is not good or bad by itself. The question is what burn is buying.

Classify burn:

Burn type	Good version	Bad version
Product burn	Builds core workflow, reliability, security, or activation	Builds speculative features for unclear customers
GTM burn	Tests a narrow channel with learning and conversion	Creates broad awareness without qualified demand
Hiring burn	Adds capacity to a proven bottleneck	Adds roles before work is understood
Support burn	Protects retention and exposes product fixes	Repeats manual rescue without system change
Founder burn	Gives founder focus and stamina	Hides unsustainable personal finances or lifestyle spend
Admin burn	Keeps legal, finance, compliance, payroll clean	Creates process theater before scale

Monthly burn quality questions

Ask:

Which costs bought customer evidence?
Which costs bought product evidence?
Which costs protected retention, trust, or compliance?
Which costs were convenience or status?
Which recurring costs no longer match the company stage?
Which spend should stop, shrink, or become milestone-based?
Which underfunded area could create bigger risk later?

Runway is not only extended by cutting. It is extended by spending behind the right bottleneck. A company that cuts learning spend and keeps status spend is not disciplined; it is confused.

Runway Commitment Freeze

When runway tightens, the most dangerous spend is often not today’s expense. It is tomorrow’s commitment: a hire, office, vendor contract, annual SaaS tool, agency retainer, custom project, debt repayment, or customer promise that locks the company into future burn.

Create a commitment freeze before cash pressure becomes visible to everyone.

Commitment type	Freeze question
New hire	Is this role tied to a proven bottleneck or speculative growth?
Contractor/agency	Can the work be paused, narrowed, or milestone-based?
Vendor renewal	Is this essential to revenue, product, compliance, or security?
Annual contract	Does the discount justify the loss of flexibility?
Customer promise	Does the promise require new cost before cash is collected?
Office/equipment	Is this necessary for execution or a comfort/status expense?
Marketing spend	Does the channel have evidence, or is it hope under pressure?

Use three modes:

Mode	Rule
Normal	Commitments allowed inside approved budget.
Watch	New recurring commitments require runway impact review.
Freeze	No new recurring commitments unless founder approves against a named milestone.

Write the freeze rule in advance:

If conservative runway falls below ___ months, all new recurring commitments pause until reviewed.
Exceptions allowed only for payroll, statutory dues, committed customer delivery, security, and revenue-critical work.

This helps founders avoid emotional cuts later. The best runway protection often happens before the company has to cut anything: stop adding future obligations until the next proof point is real.

Hiring Affordability Gate

Hiring is usually the largest recurring burn decision. A founder should not approve a hire only because the role sounds important. The question is whether the company has enough evidence, runway, and management capacity for that recurring commitment.

Before any full-time hire, run this gate:

Gate	Question
Bottleneck proof	What painful bottleneck will this hire remove?
Evidence	Is the bottleneck proven by customers, revenue, product velocity, support load, compliance, or founder time?
Alternatives	Could a contractor, agency, tool, advisor, intern, or founder process fix this for now?
Runway impact	What happens to conservative runway after salary, hiring cost, equipment, tools, payroll taxes, and benefits?
Management load	Who will manage this person weekly?
Success metric	What should improve within 30, 60, and 90 days?
Exit cost	What happens if the role is wrong or the plan changes?

Write the decision:

Role:
Monthly fully loaded cost:
Runway before hire:
Runway after hire:
Milestone this hire supports:
Alternative considered:
Decision:
Review date:

Use a hard rule:

Do not hire permanently against low-confidence revenue, vague investor interest, or a problem the founder has not personally understood.

In India, hiring ahead of proof can hurt twice: salary burn rises, and letting people go is emotionally, reputationally, and operationally costly. When runway is short, prefer milestone-based help unless the role protects revenue, product reliability, compliance, or a proven bottleneck.

Reader action

Calculate your conservative runway today. Then write one sentence: “If runway falls below ___ months, we will ___.” A decision rule written before panic is more useful than courage after panic.