Guides
Answers to the decisions operators ask about most, each marked with where it stands this week.
This week's answers, by area
Under this week's guidance: Conditions are tightening. Protect the revenue you already have, and hold off on new bets until money gets cheaper.
4 of 5 areas are on hold.
Hiring
On holdShould startups hire engineers right now?
Hire when a specific delivery, reliability or revenue bottleneck justifies the full cost and the downside cash plan can fund the role.
Should we freeze hiring this week?
Freeze hiring when your cash plan can't support new commitments, and decide on backfills and critical roles one by one.
Should we expand sales headcount now?
Add sales capacity when qualified demand exceeds current coverage and the cash plan can fund recruiting, ramp and the sales cycle.
What should startups do before a downturn?
Work out now what each pause line would mean for your company. The stop points are already set, so getting ready means knowing your runway, burn and demand, not guessing when things turn.
Hiring freeze policy for high interest rates
Roadmap
11 pts from pausingShould startups slow roadmap expansion?
Cut new scope if it would push out work customers are counting on, or if you don't have the people for it. Protect work that clearly delivers or keeps customers.
Should we delay new product lines?
Delay a new product line when demand is unproven or its build and support costs would put the core business at risk.
Fundraising
On holdShould startups raise capital now?
Prepare now if the time to close a round plus a delay would leave less than your minimum cash buffer. Do not wait for better conditions to start.
Startup funding climate this week
CloudyRead startup funding conditions through rates and credit alongside your runway, investor conversations and the milestone a round must fund.
Spending
On holdWhen should startups cut burn?
Review burn when your cash plan no longer funds the next milestone with a contingency buffer; tighter funding conditions make that review more urgent.
How to brief executives on market conditions
Brief executives on the dated change, the decision it affects, the company evidence and the trigger for revisiting it.
How much runway should a startup have?
Use 18–24 months as a planning range in a tightening market, then adjust for the time it takes to cut costs or raise money.
New bets
On holdHow fast should we scale go-to-market?
Increase go-to-market spend in steps only when retention, conversion and gross-margin-adjusted payback support the added cash commitment.
Is it risk-on or risk-off for startups?
CloudyPartly: investors are selective, not shut. Fund the commitments that carry proof, stage the rest behind a review date, and keep a way to stop.
Governance frameworks
- Capital Discipline for Venture-Backed CompaniesA monthly scorecard, a checklist for every major spending decision, a workshop agenda and a 90-day plan for keeping spend tied to proof in a venture-backed company.
- Board-Level Capital Discipline FrameworkA matrix that turns market signals and your company's own readiness into what the board approves, defers or stops. It lists the documents each approval needs and a quarter-by-quarter rollout.
- Reversibility as Governance for Board DecisionsA way to sort decisions by how hard they are to undo, decide who can call a rollback and when, and rehearse the rollback. It comes with a 90-day plan to adopt it.
- How VC firms can enforce capital discipline across portfoliosA portfolio-level operating standard: one guidance reading, one set of pause and restart lines, applied across every company a firm backs.
More tools
One-decision worksheets: PMFRoadmap FocusCommitment & RollbackDecision RightsLaunch GatesOps CapacityClaims & Positioning
Series A
Clear stage choiceAt Series A, it sets hiring, spend and roadmap limits for the next six to eight weeks, before habits you can't afford settle in.
Most useful for: Hiring and burn limits
Best use: Write short-cycle rules with a pause line and a restart line for each.
- Founders setting hiring pace and burn.
- A first head of product arguing from limits rather than preference.
How each team should read this stage