Skip to content
Lunera Pitch Lunera

5 min read ·

Startup Finance: Build a System for Cash, Costs and Decisions

A practical startup finance workflow for technical founders: reliable books, cash forecasts, delivery economics, spending decisions and ownership records.

Share X in f
Lunera · 5 min read

Startup finance is the work of tracking money, forecasting cash needs, allocating capital and managing financing and ownership. Fundraising is only one part of it.

For a technical founder, the useful output is not an elaborate spreadsheet. It is a system that answers three questions: What can we afford? What evidence will this spending produce? What will we do if the plan slips?

Build that system around five connected practices.

1. Keep accounting and cash planning separate—but reconciled

Your books explain what happened. Your forecast estimates what happens next. Neither replaces the other.

Three financial statements provide different views:

  • Income statement: revenue, costs and profit or loss over a period.
  • Balance sheet: assets, liabilities and shareholders’ equity at a point in time.
  • Cash flow statement: cash moving through operating, investing and financing activities.

Profit is not the same as cash generated, and cash received from issuing equity or borrowing is not customer revenue. The SEC’s financial-statement guide explains these distinctions and the separate treatment of financing cash flows.

As a starting workflow, reconcile company bank and card accounts monthly, retain invoices and contracts, and review unpaid customer invoices and supplier bills. Replace elapsed forecast periods with actual receipts and payments, and tie the next period’s opening cash to the reconciled balance, excluding restricted amounts. Ask your accountant to establish the appropriate treatment of subscriptions, credits, development costs and taxes for your jurisdiction.

You can delegate bookkeeping, but not understanding. Y Combinator’s finance guidance explicitly warns founders against accepting monthly reports without reviewing or questioning them.

2. Forecast cash by payment date

Start with cash available for company spending, separating restricted amounts. Then forecast receipts and payments when you expect them to reach or leave the bank—not simply when a sale is agreed or an expense is incurred.

A practical starting point is a weekly forecast for the next 13 weeks, plus a monthly view through your next operating milestone. Include:

  • Customer collections, with realistic payment delays.
  • Payroll, employer costs, contractors and planned start dates.
  • Cloud usage, software renewals and minimum commitments.
  • Tax payments, legal bills, equipment and debt service where applicable.
  • Expected financing receipts in a separate section, with their status and timing explicit. Keep uncertain funding out of the case used to test whether you can meet existing obligations.

Financing already received belongs in opening cash; do not count it again as a future receipt.

The basic cash equation is:

Closing cash = opening cash + cash receipts − cash payments

For orientation, runway is available cash divided by monthly net burn when burn is positive and reasonably stable. But a dated forecast is more useful when costs are changing. YC likewise cautions that burn can change and recommends checking cash numbers at least weekly in its startup finance lesson.

For example, a hypothetical company with $600,000 available and $60,000 monthly net burn has ten months of runway. Adding $15,000 of monthly costs from now reduces that to eight months, assuming everything else stays constant. A planned hire should enter the forecast at its expected payment dates—even before the historical burn report catches up.

Use the burn-rate and runway guide for the calculation details. Do not treat investor interest as spendable cash; track progress separately using the financing-round guide.

3. Connect product usage to delivery costs

For developer tools, data infrastructure and applied AI, forecast costs from the activities that generate them: queries, storage, inference calls, data transfer, retries, support and required human review.

Avoid assuming that revenue and cloud spending will grow at the same rate. Test the relationship explicitly.

Consider a hypothetical customer generating $1,000 in monthly revenue and $300 in directly attributable delivery costs. The resulting delivery margin—revenue minus those costs, divided by revenue—is 70%. If those costs double while revenue stays flat, it falls to 40%—before broader engineering, sales and administrative expenses.

Use this as an operating analysis, with a documented cost definition; it is not automatically your accounting gross margin. Track whether heavier usage produces more revenue, whether pricing covers expensive workflows, and whether customer-specific support makes an apparently attractive account costly to serve.

Before revenue exists, measure cost per completed workflow alongside evidence of willingness to pay. Do not manufacture precision from a handful of experiments.

4. Budget around evidence, not departments

Give each significant spending decision an owner, an expected result, a deadline and a cash limit.

“Hire two engineers” is a cost. “Complete three production integrations and test whether customers renew” is an operating objective. The finance plan should connect them without pretending the outcome is guaranteed.

Build a base case from identifiable drivers: customers, conversion, pricing, usage, staffing and payment timing. Keep supporting evidence beside the assumptions. EY’s financial-modeling guide describes bottom-up forecasting and recommends substantiating assumptions with contracts, pricing validation, historical sales and other evidence.

Then model a downside case: later customer collections, slower sales, higher delivery costs or a delayed launch. Specify the response before it becomes urgent—for example, deferring an uncommitted hire or reducing a discretionary project. Distinguish genuinely reversible spending from contractual obligations.

If the milestone requires outside capital, use the funding-options guide to assess financing fit rather than assuming every cash gap calls for venture capital.

5. Run a small, repeatable finance review

A useful starting cadence is:

Cadence Review Decision
Weekly Available cash, upcoming payments, overdue collections and forecast changes What needs action now?
Monthly Reconciled accounts, actual versus forecast, delivery economics and milestone progress Which assumptions or spending plans should change?
Before hiring or signing a commitment Full cost, payment timing and downside cash impact Can we afford the obligation if revenue slips?
Before financing Cash need, use of funds and ownership scenarios Does this financing support the plan on acceptable terms?

Keep ownership records current alongside the cash model: issued equity, options, SAFEs, notes and their supporting documents. Use the cap-table guide to distinguish current ownership from modeled dilution.

The founder should be able to explain the current cash balance, the largest forecast uncertainty and the next spending decision. That is the minimum useful finance system—not a dashboard nobody uses.