LenderHawk analysis. Not affiliated with or endorsed by The Permanent Podcast.
A Permanent Podcast roundtable breaks down the Silicon Valley Bank collapse, focusing on the mix of interest-rate risk, deposit concentration, and panic that turned a liquidity problem into a run. Nikki Galloway then lays out practical treasury steps for portfolio companies: understand cash needs, call your bank, and use insured cash-management products to protect operating funds.
Owners, CFOs, and searchers who want practical treasury-risk playbooks for operating businesses with more than $250k in cash.
A bank can fail for duration risk even when it holds high-quality assets if its liabilities are demand deposits and customers rush for cash at once.
If operating cash exceeds the FDIC limit, the balance is only partially protected unless it is intentionally spread across insured structures or multiple banks.
The first treasury question is not return; it is whether the business can access the cash when payroll, suppliers, or seasonal working capital needs hit.
A bank relationship should be managed proactively, not only when a loan is needed, because deposit products and insured sweeps are relationship-dependent.
Holding an emergency reserve at the same bank as operating cash defeats the purpose of having an emergency reserve.
Locking cash into CDs or similar products is a bad fit for payroll money because early liquidity needs can force losses or delays.
Panic can turn a solvable liquidity mismatch into a full bank run when depositors coordinate withdrawals faster than the bank can liquidate assets.
Cash management should be ordered by basic need: first make funds safe, then make them liquid enough to support operations, and only then optimize for yield. The episode frames that as the correct sequence for treasury decisions.
When to use: When deciding where to hold operating cash or reserve cash for a small business.
FDIC insurance covers up to $250,000 per deposit account balance.
The discussion uses SVB to explain why many operating accounts were only partially insured.
Some portfolio companies had cash balances above $250,000 and would have been stressed if they lost access to their bank accounts.
Nikki explains why the Permanent Equity portfolio needed treasury-risk planning.
Silicon Valley Bank’s deposits reportedly grew from about $60 billion to a couple hundred billion dollars.
Tim and Nikki describe how startup and VC deposits exploded during the low-rate period.
A typical insured sweep can spread about $1 million into chunks near $250,000 across multiple banks overnight.
Nikki describes how an insured cash sweep works for full FDIC coverage.
ICS-style insured sweep services can charge around $50 to $100 in fees for the safety and liquidity they provide.
The episode compares insured sweeps with other cash-management options.
Short-term CDs in the discussion were described as paying about 2.5% for four weeks, with higher rates possible depending on term.
Nikki uses CDs as an example of yield gained at the cost of liquidity.
Tim notes that a three-month crypto staking example generated 10% in dot-denominated return, but the asset value still ended below the purchase price.
The hosts use this as a cheap lesson in liquidity and asset risk.
The episode says several thousand companies could have missed payroll, affecting roughly 4 million workers, if access to SVB deposits had not been restored.
This is used to justify the government’s emergency response.
Map cash by use case before choosing a banking product.
Why: Operating money, reserve money, and near-term payroll money need different liquidity profiles.
Call your bank and ask what insured sweep, money market, and CD products they offer.
Why: Treasury protection is easier when you know the menu of products before an emergency hits.
Keep payroll money in instruments you can access immediately.
Why: If the business needs cash next week, locking it into a CD or speculative asset creates avoidable operational risk.
Use insured sweeps or multiple-bank structures when balances routinely exceed the FDIC cap.
Why: Diversifying deposit locations reduces the chance that one bank failure disrupts operations.
Treat yield as a secondary concern after liquidity and safety are satisfied.
Why: Chasing a little extra return can create outsized downside if the company needs the cash suddenly.
Nikki explained that most portfolio companies held balances above the FDIC cap, so a bank disruption would have left them only partially protected. The lesson was that companies with working capital, seasonal cash spikes, or prepaid customer money need explicit treasury planning before a crisis.
Lesson: If cash is mission-critical, structure it as a treasury system rather than a single checking account.
Tim described buying Polkadot and later staking it for three months at a 10% stated return, only to receive back fewer dollars than he started with because the token price fell. The anecdote was used to show that nominal yield can hide real loss when the asset itself is volatile.
Lesson: A high stated return does not make a position safe if principal value can collapse while the money is locked up.