How to Startup: Your 13-Week Cash Control System

How to Startup is returning with a narrower promise: practical operating systems that help founders make better decisions before urgency takes over.

We are starting with cash—not because every startup should optimize for survival at the expense of growth, but because a company without financial room eventually loses the ability to choose.

Most founders know their runway number:

Runway = cash on hand ÷ average monthly net burn

Stripe defines net burn as monthly cash expenditures minus monthly revenue and describes runway as cash on hand divided by monthly net burn.

That calculation is useful. It is also too coarse to run the business.

A startup can appear to have nine months of runway and still face a cash problem in six weeks because payroll, annual contracts, taxes, delayed customer payments, and hiring plans do not arrive in smooth monthly averages.

The better operating tool is a 13-week cash forecast.

It does not try to predict the company’s distant future. It turns the next quarter into a weekly decision system.

Why thirteen weeks works

Thirteen weeks is long enough to expose trouble before it becomes immediate and short enough to use real information rather than strategic fiction.

It captures roughly one quarter of:

• Payroll cycles

• Customer collections

• Tax and vendor deadlines

• Hiring decisions

• Marketing commitments

• Financing conversations

The U.S. Small Business Administration’s recent cash-flow training materials explicitly include building a 13-week forecast, managing inflows and outflows, and identifying shortages before they become major problems.

The value is not a perfectly accurate forecast. The value is seeing which assumptions control the company’s options.

Build the first version

Create one column for each of the next 13 weeks and five sections.

1. Opening cash

Begin with money the company can actually use—not unsigned financing, unapproved credit, or an invoice you hope will be paid early.

2. Cash inflows

List collections by expected week:

• Contracted recurring revenue

• Invoices already issued

• Usage or transaction revenue

• Tax refunds or grants that are sufficiently certain

• Financing only after its conditions are understood

Keep pipeline separate from committed collections. A sales opportunity is not cash.

3. Cash outflows

List the dates and amounts the company is expected to pay:

• Payroll and contractor payments

• Taxes and benefits

• Rent, cloud infrastructure, and software

• Marketing commitments

• Inventory or manufacturing

• Debt payments

• Legal, insurance, and professional services

Do not spread a large annual payment evenly across twelve months if the bank account will experience it on one date.

4. Net weekly cash flow

For each week:

Net cash flow = cash collected − cash paid

5. Ending cash

Ending cash = opening cash + net cash flow

The ending balance becomes the following week’s opening balance.

The lowest projected balance matters more than the average.

Separate facts from assumptions

Every important forecast item should be classified:

• Committed: contractually scheduled or highly certain

• Expected: supported by current operating evidence

• Conditional: depends on a decision or event that has not happened

This keeps a likely-but-uncertain fundraise, enterprise deal, or cost reduction from silently becoming part of the base case.

A useful forecast can be pessimistic without being theatrical. The point is to expose dependence.

If one late customer payment creates a crisis, the vulnerability is not forecasting accuracy. It is concentration and insufficient liquidity.

Add three scenarios

Duplicate the forecast into:

1. Base case: the team’s most defensible current assumptions

2. Downside case: slower collections or weaker revenue with committed costs unchanged

3. Decision case: the specific actions management could take and when they would begin

Avoid a vague “cut costs if things get bad.” Define observable triggers.

Examples might include:

• Pause a planned hire if projected cash falls below an internal floor

• Require founder approval for new recurring commitments after a downside trigger

• Escalate overdue receivables on a fixed timetable

• Begin fundraising or financing conversations before the company needs the money

• Reduce an experiment when its committed spend exceeds its pre-agreed loss limit

These are examples, not universal thresholds. The right triggers depend on the business, jurisdiction, financing model, and obligations.

Run the weekly cash meeting

Once a week:

1. Replace the completed week’s forecast with actual cash movements.

2. Explain the largest differences between forecast and actual.

3. Roll the model forward by one week so it always covers thirteen weeks.

4. Update collection dates and committed payments.

5. Check whether any decision trigger has been crossed.

6. Assign one owner and deadline to every material cash action.

The most valuable line in the meeting is not the ending balance. It is the explanation for why reality differed from the forecast.

That is where operating problems appear:

• Sales are closing but customers pay slowly

• Revenue looks strong while gross margins deteriorate

• Hiring commitments are ahead of validated demand

• “Temporary” tools and contractors have become permanent costs

• Growth depends on a channel whose payback period is longer than the remaining runway

Profit is not the same as cash

A company can show accounting profit while cash is tied up in receivables or inventory. It can also receive cash before recognizing the associated revenue.

That is why the 13-week model should be tied to bank-account timing, not only the income statement.

Long-term forecasts still matter for fundraising, hiring, and strategy. The weekly model has a different job: protecting decision time.

The founder test

Open the forecast and ask:

• Which incoming payment would hurt most if it arrived four weeks late?

• Which cost is treated as variable but is operationally difficult to remove?

• Which growth plan assumes financing that has not closed?

• What is the first trigger that changes hiring, spending, or fundraising behavior?

• How many weeks would pass between seeing trouble and being forced to act?

The last question is the real measure of control.

Runway is a summary. A 13-week cash forecast is an operating system.

Reply and tell me: what is the one cash assumption in your business you trust least?

Sources

• Stripe: What burn rate is and how to calculate it

• U.S. Small Business Administration: Cash Flow Management 101

• U.S. Small Business Administration: Why Bother with Financial Forecasts

This publication provides general educational information for founders and operators. It is not accounting, tax, legal, or investment advice. Business obligations and appropriate financial controls vary by company and jurisdiction.