Managing startup cash is not a bookkeeping exercise; it is a runway decision. In practice, startup treasury management is about deciding which dollars must stay liquid, which can earn a modest return, and what controls prevent mistakes or fraud. The right setup can buy time, reduce stress, and make board conversations much easier.
These are the cash decisions that matter most for a startup
- Build a weekly cash forecast before you optimize yield.
- Split cash into operating, reserve, and longer-dated buckets.
- Use banks, money market funds, and Treasuries for different time horizons.
- Write a treasury policy early, while the team is still small.
- Track runway, forecast accuracy, and concentration risk, not only yield.
What treasury management actually does for a startup
For a startup, the job is simpler than it sounds. I think of it as three questions: how do we protect the cash needed for payroll and tax payments, how do we keep excess cash from sitting idle, and who is allowed to move money when conditions change?
This is different from ordinary bookkeeping. Bookkeeping records what happened; treasury decides what should happen next. That means cash positioning, liquidity planning, payment controls, and a policy for where surplus funds can sit.
The practical benefit is that good treasury discipline shortens the distance between a funding event and a calm operating plan. It also reduces the chance that a single bank, a single signer, or a single bad transfer creates a crisis. Once that role is clear, the next question is how much cash has to stay instantly available.
Start with the cash map, not the yield
Before I think about instruments, I build a cash map. The simplest version is a 13-week forecast with weekly inflows, payroll, taxes, vendor payments, cloud bills, subscriptions, and any debt service. Monthly forecasts are often too blunt; they hide short-term squeezes that can matter a lot when the runway is tight.
The operating floor
Most startups need an operating floor that covers the next payroll run, near-term payables, and a buffer for delayed customer receipts. In many cases, that means keeping at least 8 to 12 weeks of operating cost in immediately accessible cash. If revenue is volatile, customer concentration is high, or the next fundraise is uncertain, I would move closer to 4 to 6 months.
That number is not a rule of law. It changes with burn rate, collections quality, headcount, and how painful a delay would be. A pre-revenue hardware company and a mature SaaS business should not use the same threshold. Once the floor is clear, the remaining balance becomes investable surplus.
Read Also: Startup Funding - Beyond VC: Find Your Best Fit
The investable surplus
Surplus cash is anything you do not expect to need inside the operating window. That might be 30 days for one company and 180 days for another. The mistake I see most often is treating every extra dollar as equally safe to lock up. The better habit is to label each bucket by time horizon and liquidity need before you assign it to a product.
That discipline makes the next decision easier: where each bucket should live without taking on unnecessary risk.
Choose the right home for each dollar
The best place for cash depends on how soon you might need it. The Investment Company Institute reported money market fund assets at about $7.90 trillion in late June 2026, which is a useful reminder that short-duration cash vehicles are still a standard part of business finance, not an exotic tactic.
| Cash bucket | Best use | Liquidity | Main trade-off | My read |
|---|---|---|---|---|
| Operating checking | Payroll, AP, tax payments, wires | Immediate | Low or no yield | Keep only the amount you truly need for near-term operations. |
| FDIC-insured sweep or business savings | Short-term buffer | Same day to next day | Yield is usually modest and coverage limits still matter | Useful bridge between transaction cash and reserve cash. |
| Government money market fund | Idle cash that still needs quick access | Often same day or next day | Not FDIC-insured and NAV can move slightly | Good for surplus cash when liquidity is still a priority. |
| U.S. Treasury bills | Cash needed in one to six months | Held to maturity unless sold early | Less flexible than a deposit account | Strong fit when you can match maturities to expected use. |
| Treasury ladder | Staged spending plans and runway extension | Staggered maturities | More planning and more moving parts | Best when you want yield without concentrating all maturities on one date. |
I usually avoid two extremes: leaving too much money in plain checking because it feels safest, or pushing operating cash into products that add delay when you need to pay people. The right answer is a layered structure, with each bucket serving one time horizon. From there, the real protection comes from controls, not just product choice.
Put controls in place before growth makes them painful
Good governance is what keeps treasury from becoming informal and error-prone. I want a written policy, named owners, transfer limits, and clear approval steps before the finance team gets busy. If the same person can initiate, approve, and reconcile payments, the control design is already too loose.
- Authorization matrix so large transfers need dual approval.
- Account inventory so every bank, wallet, and brokerage account has a purpose and an owner.
- Role-based access so people only see the systems they need.
- Monthly reconciliations so errors are caught quickly, not at quarter-end.
- Wire verification so beneficiary changes and payment instructions are confirmed through a second channel.
- Policy triggers so the rules are reviewed after fundraising, a hiring step-up, or a material change in burn.
In US startups, I also pay attention to concentration risk. Bank relationships should be deliberate, and insurance assumptions should be checked rather than guessed; coverage depends on ownership category and the institution, so you should not assume every dollar is protected the same way. A board or investor will care less about theoretical yield if a payment failure or fraud event hits the operating account. With the control layer in place, the next step is deciding which numbers deserve weekly attention.
Measure the few metrics that actually change decisions
I prefer a small dashboard over a long one. The goal is not to admire data; it is to catch problems while they are still fixable. If a metric does not change how you allocate cash, pay vendors, or delay spending, I usually drop it from the core report.
| Metric | Why it matters | Practical threshold |
|---|---|---|
| Runway | Tells you how long you can operate at the current burn | Review weekly when runway is under 12 months |
| 13-week forecast accuracy | Shows whether your cash plan is decision-grade | If misses are consistently above 10%, tighten the model |
| Idle cash ratio | Measures how much cash is not needed inside the operating window | Higher is better only if liquidity stays intact |
| Bank concentration | Exposes dependency on a single institution | Watch this closely once balances become material |
| Days to fund payroll | Tests whether cash can move fast enough when needed | Should be measured in hours, not days, for operating funds |
| Burn multiple | Useful for VC-backed SaaS when growth is the main output | Best used alongside runway, not instead of it |
If you are not a SaaS company, burn multiple may matter less than operating cash margin or gross margin discipline. I also set a cadence around those metrics. Weekly, I update the forecast and review exceptions. Monthly, I reconcile every account and check for policy breaches. Quarterly, I ask whether the cash structure still fits the business model, because a company that just raised capital should not use the same cash posture it had before the round.
The mistakes that quietly destroy runway
The failures I see are rarely dramatic. They are usually small design mistakes that compound for months before anyone notices.
- Chasing yield before liquidity and then discovering that payroll money is locked up.
- Keeping tax cash mixed with operating cash, which creates accidental spending pressure.
- Ignoring payment timing and assuming vendor terms will always behave the same way.
- Leaving too much authority in one person’s hands, which increases fraud and error risk.
- Failing to refresh the policy after fundraising, even though the balance sheet and risk profile changed.
- Using one bank for everything, which turns a single operational issue into a company-wide problem.
The pattern behind all of them is the same: the team optimizes for convenience until convenience becomes fragility. The fix is not a complicated treasury stack; it is a clearer operating model.
The starter setup I would use in a US startup
If I were putting this in place from scratch, I would keep it boring on purpose. One operating account for payments, one reserve layer for near-term cash, one short-duration investment bucket for money that is not needed soon, and one policy that explains exactly who can move funds and when. That gives you enough structure to protect the business without turning treasury into a full-time project too early.
- Keep only the amount you need for immediate operations in the operating account.
- Put the next layer of cash in a liquid reserve product or government money market fund.
- Match longer-dated surplus to Treasury bills or a simple ladder if the timing is predictable.
- Review the forecast every week and the policy every quarter.
- Revisit the structure after every funding event or meaningful change in burn.
The best treasury setup is the one that helps you sleep at night and still lets the company move quickly. If your team can pay bills on time, see runway clearly, and earn something reasonable on idle cash without taking unnecessary risk, the system is doing its job.
