# Whether — full text corpus

Whether is weekly operating guidance for startup leaders. We read interest rates and credit markets and tell you when to pause or resume hiring, spending and fundraising. Updated every Monday, with an email the day a line is crossed.

This file is the site's stable editorial content in one document. It does **not** carry this week's guidance. That changes weekly under one URL: fetch https://whether.work/brief.md for it, or https://whether.work/api/agent for JSON. A dated, citable copy of a past week lives at https://whether.work/brief/<year>-w<week>.

Endpoint map: https://whether.work/llms.txt · Agent manifest: https://whether.work/.well-known/whether-agent.json

## Decision answers

Each answers one operating question. The reading behind them moves weekly; the framing does not.

### Startup funding climate this week

URL: https://whether.work/answers/startup-funding-climate-this-week

Question: startup funding climate this week

Audience: Founders, finance leaders and board operators

Short answer: Read startup funding conditions through rates and credit alongside your runway, investor conversations and the milestone a round must fund.

What to do: Use the dated market reading below to review financing assumptions. Keep the company’s cash deadline and investor evidence in the decision; a broad funding score cannot tell you whether a particular round will close.

#### How interest rates and credit affect startup funding

Interest-rate changes can affect borrowing costs, asset prices and spending. A Fed rate cut alone does not establish easier financing for your company. Check loan terms and investor conversations, then review hiring, discretionary spend and fundraising assumptions against the cash plan.

Company inputs to check: Exposure to borrowing rates, debt repayment dates and financing terms. Investor response and the milestone that would justify a new round. Downside runway if customer payments or a financing close are delayed.

Decision note to complete: After [rate or credit change], review [financing assumption]. Keep [cash buffer] funded and change [commitment] only after [company evidence]. Owner: [name]. Review: [date].

References: Federal Reserve: how monetary policy works: https://www.federalreserve.gov/monetarypolicy/monetary-policy-what-are-its-goals-how-does-it-work.htm; Evidence behind the market reading: https://whether.work/signals

Decision areas: capital-raising, burn-discipline

### Is it risk-on or risk-off for startups?

URL: https://whether.work/answers/is-it-risk-on-or-risk-off-for-startups

Question: is it risk-on or risk-off for startups

Audience: Leadership teams

Short answer: Use risk appetite to review how much uncertainty new commitments carry; validate demand and cash capacity before increasing exposure.

What to do: Compare the current risk reading with the commitments you are considering. Better market conditions can support a review of expansion, but each bet still needs customer evidence, a spending limit and a way to stop.

#### Turn market changes into an operating review

Whether’s forecast concerns movement between operating conditions, not an exact recession date, company revenue or investment return. After a rate or credit event, inspect the dated evidence before changing a plan. Historical comparisons show how the model reads past conditions, not how your company would have performed.

Company inputs to check: The commitments that become harder to reverse as spending or hiring increases. Customer demand, available cash and the next evidence milestone for each bet. The market change and company result that would justify another review.

Decision note to complete: Review [commitment] after [market change]. Limit exposure to [amount or duration]. Pause if [your pause line] is crossed; resume after [demand and cash evidence]. Owner: [name]. Review: [date].

References: Compare historical conditions: https://whether.work/history/compare; How the signals are interpreted: https://whether.work/trust

Decision areas: expansion-bets, product-tempo, burn-discipline

### Should startups hire engineers right now?

URL: https://whether.work/answers/should-startups-hire-engineers-right-now

Question: should startups hire engineers right now

Audience: Engineering leaders and founders

Short answer: Hire when a specific delivery, reliability or revenue bottleneck justifies the full cost and the downside cash plan can fund the role.

What to do: Name the work an additional engineer unlocks and compare hiring with reducing scope or reassigning capacity. Approve the role only with a funded ramp period and a measurable outcome; a market score cannot establish that need.

#### Make the engineering hiring case

A reliability hire may protect existing revenue without a directly attributable payback period. A growth hire needs evidence that capacity, rather than weak demand, limits results. Use different evidence for those cases instead of applying one payback cutoff to every engineering role.

Company inputs to check: The delivery backlog, incident load or customer commitment this role would address. Salary, benefits, recruiting and onboarding costs, including management capacity during ramp. Cash remaining after the hire in a downside plan and a dated outcome review.

Decision note to complete: Approve [role] to address [bottleneck] within [cost envelope]. Hold further hiring if [cash or outcome limit] is breached. Reopen after [funding and delivery evidence]. Owner: [name]. Review: [date].

References: Should we freeze hiring this week?: https://whether.work/answers/should-we-freeze-or-selectively-hire

Decision areas: hiring, product-tempo, burn-discipline

### Should startups slow roadmap expansion?

URL: https://whether.work/answers/should-startups-slow-roadmap-expansion

Question: should startups slow roadmap expansion

Audience: Product and engineering leadership

Short answer: 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.

What to do: Separate committed delivery from optional expansion. Stage new scope behind customer evidence and a capacity check, then revisit it when the cash plan and team can support the next milestone.

#### Prioritize the roadmap during a downturn

A tighter budget should change the amount of work committed, not quietly lower the reliability of work already promised. Compare initiatives by customer consequence, remaining cost and time to evidence. Market guidance informs the review; it does not rank your backlog.

Company inputs to check: Customer commitments, retention risks and reliability work already funded. Remaining cost and capacity for each initiative, including maintenance after launch. The next customer validation milestone and which work would be displaced.

Decision note to complete: Keep [core commitments] and defer [new scope]. Pause expansion if [capacity or cash limit] is crossed. Resume at [customer milestone] with [funded capacity]. Owner: [name]. Review: [date].

References: Roadmap focus toolkit: https://whether.work/toolkits/focus

Decision areas: product-tempo, expansion-bets, burn-discipline

### Should startups raise capital now?

URL: https://whether.work/answers/should-startups-raise-capital-now

Question: should startups raise capital now

Audience: Founders, CEOs and CFOs

Short answer: Start fundraising preparation before your downside runway falls inside the time needed to reach investors, close a round and absorb delays.

What to do: Work backward from the date cash would reach your minimum buffer. Include preparation, investor conversations, diligence and a delayed close; do not wait for better market conditions if that leaves the company unable to fund its plan.

#### Raise now or extend runway?

Separate preparing a raise from accepting its terms. Compare an equity raise with a smaller operating plan using the same milestone and cash assumptions. Better public-market conditions do not establish investor demand for your round, and public SaaS multiples do not set a private valuation.

Company inputs to check: Downside cash runway and the minimum cash buffer you have committed to hold. Time and cost to a fundable milestone, plus the expected fundraising process and delay allowance. Investor conversations, acceptable dilution and terms, and a plan if the round does not close.

Decision note to complete: Begin [preparation or investor outreach] by [date] to fund [milestone]. Revisit the plan if [cash date or investor evidence] slips. Accept terms within [agreed limits]. Owner: [name]. Review: [date].

References: SaaS valuation multiples: https://whether.work/comps; Carta: preparing a startup fundraise: https://carta.com/learn/startups/fundraising/

Decision areas: capital-raising, burn-discipline

### When should startups cut burn?

URL: https://whether.work/answers/when-should-startups-cut-burn

Question: when should startups cut burn

Audience: Founders, CFOs, fractional CFOs and operations leaders

Short answer: Review burn when your cash plan no longer funds the next milestone with a contingency buffer; tighter funding conditions make that review more urgent.

What to do: Model a slower revenue or fundraising case before approving more recurring spend. Reduce commitments that do not protect delivery, retention or the next milestone, and set a cash buffer for restoring them.

#### Extend runway without an automatic hiring freeze

Cash runway is available cash divided by monthly net burn when burn is positive and stable. Use a cash-flow forecast when collections, renewals or one-off payments vary. Compare savings after cancellation costs and lost revenue; a cut that weakens retention can leave less cash than the headline saving suggests.

Company inputs to check: Available cash, monthly net burn and payment dates in a downside case. Cost and time to the next revenue or financing milestone, including a contingency buffer. Spend that can be stopped or renegotiated, its exit costs and the delivery or retention it protects.

Decision note to complete: We will reduce [spend] by [amount] to fund [milestone]. Protect [delivery or retention commitment]. Restore spend when [cash buffer and business result] hold. Owner: [name]. Review: [date].

References: How much runway should a startup have?: https://whether.work/resources/how-much-runway-do-we-need-tightening-market; Startup runway calculator: https://whether.work/operate/financial

Decision areas: burn-discipline, capital-raising

### Should we freeze hiring this week?

URL: https://whether.work/answers/should-we-freeze-or-selectively-hire

Question: should we freeze hiring

Audience: Founders, VP Engineering, CFO

Short answer: Freeze hiring when your cash plan can't support new commitments, and decide on backfills and critical roles one by one.

What to do: Review open requisitions against cash, customer commitments and existing capacity. Give every exception a named approver, a full cost and a review date, and define the evidence needed to reopen hiring.

#### Set hiring freeze and reopening criteria

A freeze controls new commitments; it does not resolve workload or determine which work can stop. Pair it with a scope review so the remaining team can meet the commitments you keep. Reopening should depend on affordable capacity needs as well as improving market conditions.

Company inputs to check: Cash impact of approved offers, open requisitions and essential backfills. Work to stop or defer if vacancies remain unfilled. The cash buffer, workload evidence and approver required to reopen a role.

Decision note to complete: Hold [requisitions] and allow exceptions for [specific need]. Defer [work] to match capacity. Reopen when [cash and workload criteria] hold. Approver: [name]. Review: [date].

References: The standing policy: which roles to keep, gate or pause: https://whether.work/resources/should-we-freeze-hiring-high-interest-rate-environment

Decision areas: hiring, burn-discipline, product-tempo

### Should we expand sales headcount now?

URL: https://whether.work/answers/should-we-expand-sales-headcount-now

Question: should we expand sales headcount now

Audience: CRO, CEO, finance leaders

Short answer: Add sales capacity when qualified demand exceeds current coverage and the cash plan can fund recruiting, ramp and the sales cycle.

What to do: Check whether the bottleneck is sales capacity or insufficient qualified demand. Add a small cohort of reps only after the existing team demonstrates repeatable conversion and the downside plan funds their ramp.

#### Separate sales capacity from demand quality

Hiring more reps cannot by itself repair weak demand or poor retention. Compare performance by tenure and territory so a few productive reps do not hide a weak ramp process. Set a company-specific payback limit against gross margin and available cash.

Company inputs to check: Qualified demand, win rate and coverage per fully ramped rep. Recruiting cost, compensation, ramp duration and sales-cycle length. Gross margin, collections and cash remaining if the new cohort ramps slowly.

Decision note to complete: Add [number] reps in [segment] within [cost envelope]. Pause the next cohort if [demand or ramp target] is missed. Resume after [conversion and cash evidence]. Owner: [name]. Review: [date].

References: Set the next growth spending step: https://whether.work/answers/how-fast-should-we-scale-go-to-market

Decision areas: hiring, expansion-bets, burn-discipline

### Should we delay new product lines?

URL: https://whether.work/answers/should-we-delay-new-product-lines

Question: should we delay new product lines

Audience: VP Product, CTO, strategy

Short answer: Delay a new product line when demand is unproven or its build and support costs would put the core business at risk.

What to do: Fund the smallest test that can establish demand before committing to a full product line. Set a customer milestone, a spending limit and an exit condition, including the ongoing support the product would require.

#### Compare a new product with investing in the core

Customer requests are a starting point, not proof of willingness to pay or sustained use. Compare the new line with the best use of the same capacity in the existing product. Keep discovery reversible until customers and the cash plan justify a larger commitment.

Company inputs to check: Evidence of paid demand or repeated use from the intended customer segment. Build, launch and ongoing support costs alongside the opportunity cost to the core product. Experiment budget, success milestone and the condition for stopping the test.

Decision note to complete: Test [product hypothesis] with [customer group] inside [budget]. Stop if [evidence target] is missed. Expand only after [demand proof and funded support]. Owner: [name]. Review: [date].

References: Launch gates toolkit: https://whether.work/toolkits/launch-gates

Decision areas: product-tempo, expansion-bets, burn-discipline

### How fast should we scale go-to-market?

URL: https://whether.work/answers/how-fast-should-we-scale-go-to-market

Question: how fast should we scale go to market

Audience: Growth leaders, CROs and finance partners

Short answer: Increase go-to-market spend in steps only when retention, conversion and gross-margin-adjusted payback support the added cash commitment.

What to do: Set the next spending increment against a proven customer segment or channel. Pause further increases when conversion, retention or payback misses the agreed range; resume after new cohort evidence supports the cash plan.

#### Connect acquisition-cost payback to available runway

Customer acquisition cost (CAC) payback estimates how long customer gross profit takes to recover what it cost to win the customer. A blended average can hide an expensive channel or weak cohort. Compare incremental acquisition cost, cash collection timing and retention before treating efficient past growth as evidence for a larger budget.

Company inputs to check: Acquisition cost and gross-margin-adjusted payback by channel and customer cohort. Retention, conversion and cash collection timing for the customers being added. The spending increment, test duration and cash buffer if results arrive late.

Decision note to complete: Increase [channel] spend by [amount] for [test period]. Pause the next increase if [conversion, retention or payback limit] is missed. Resume after [cohort evidence]. Owner: [name]. Review: [date].

References: Sales headcount approval: https://whether.work/answers/should-we-expand-sales-headcount-now; Bessemer: cloud growth and efficiency metrics: https://www.bvp.com/atlas/scaling-to-100-million

Decision areas: expansion-bets, burn-discipline, product-tempo

### How to brief executives on market conditions

URL: https://whether.work/answers/how-to-brief-executives-on-market-conditions

Question: how to brief executives on market conditions

Audience: Chiefs of staff, CFOs, executive teams and VC operating partners

Short answer: Brief executives on the dated change, the decision it affects, the company evidence and the trigger for revisiting it.

What to do: Keep the briefing to one decision note with a source date and an owner. State what changed externally, whether it changes the company plan, and the business evidence required before acting.

#### A market-conditions note for an executive meeting

Separate the external market reading from the cash, customer and delivery evidence behind management decisions. For a portfolio review, use the same questions across companies but keep each company’s runway and commitments separate. Historical reconstructions provide context; published weekly briefs document what was actually recorded.

Company inputs to check: The source date, the previous reading and any missing or fallback data. The company decision affected, its owner and the internal evidence supporting a change. The approval requested, review date and condition that would reverse the decision.

Decision note to complete: As of [date], [external change] affects [decision]. Our company evidence is [cash, customer or delivery result]. We propose [action] within [limit]. Revisit if [trigger]. Owner: [name]. Source: [dated link].

References: Published briefs and historical context: https://whether.work/history; Copy or share the weekly brief: https://whether.work/share

Decision areas: burn-discipline, capital-raising, product-tempo

### How much runway should we have before we raise?

URL: https://whether.work/answers/how-much-runway-should-we-have-before-we-raise

Question: how much runway do we need

Audience: Founders, CFOs and board members

Short answer: Size cash to the safe band for the current conditions — 9 to 18 months of runway in Sunny conditions, 15 to 24 in Cloudy, 18 to 30 in Freezing — and open the raise while you are still above the band's floor.

What to do: Enter cash, monthly spend and revenue in the runway planner, compare the result to the band your current conditions imply, and set the raise window the planner gives: months 4 through 8 with comfortable coverage, 2 through 5 when coverage is thin, immediately when it is critical.

#### Why the band moves with conditions

The band is the runway planner's model: it widens in Freezing conditions because closes take longer and rounds are fewer, and narrows in Sunny ones because capital is easier to reach. Stage widens it further — seed adds three months, Series A adds two. The band is a planning default, not a forecast: the record shows how conditions changed after each line, not what a particular round will fetch.

Company inputs to check: Cash in the bank and monthly spend, net of revenue. The months a raise consumes: preparation, partner meetings, diligence and a delayed close. Stage: the band widens by three months for seed and two for Series A.

Decision note to complete: Runway today: [months]. Safe band: [min] to [max] months. Raise opens: [month]. If runway falls below [min], cut burn by [amount] by [date]. Owner: [name]. Review: [date].

References: The runway planner: your numbers against the band: https://whether.work/operate/financial; Capital discipline for venture-backed companies: https://whether.work/resources/capital-discipline-venture-backed-companies

Decision areas: capital-raising, burn-discipline

### What should startups do before a downturn?

URL: https://whether.work/answers/what-should-startups-do-before-a-downturn

Question: prepare for a downturn

Audience: Founders, COOs and CFOs

Short answer: 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.

What to do: Put cash, burn and demand numbers next to the pause lines for hiring, roadmap and spend, and write down for each what you would cut, defer or stop if it trips — so a change of conditions triggers a decision you already made.

#### Why the lines are written in advance

Each pause line sits six points past the line where conditions change, and each resume line four points inside it, so one noisy reading cannot reverse a decision and restart it. The margin study found the published margin measures distance from that line, not probability. What the record cannot tell you is your own demand: the company inputs below are yours to fill in.

Company inputs to check: Runway in months against the safe band for the current conditions. Which commitments stop, defer or survive a pause in each area. The approver and evidence required to execute each cut.

Decision note to complete: If [score] crosses [line], we will [action] in [area] within [timeframe]. Approver: [name]. Evidence to reopen: [criteria]. Review: [date].

References: The margin study: what distance from the line is worth: https://whether.work/calibration; This week's scores against past downturns: 2001, 2008 and 2022: https://whether.work/history/compare; Board-level capital framework: https://whether.work/resources/board-level-capital-posture-framework

Decision areas: hiring, product-tempo, burn-discipline

### Should we hire our first salesperson now?

URL: https://whether.work/answers/should-we-hire-our-first-salesperson-now

Question: first salesperson

Audience: Founders, CEOs and heads of sales

Short answer: Treat the first sales hire as an expansion bet: fund it one stage at a time with the stage gates written down, and size it against the risk appetite line like every other new bet.

What to do: Make the hire when founder-led sales shows repeatable evidence — the same segment, the same pitch, closed deals — and the fully loaded cost is in the cash plan with a written stop condition attached.

#### What the record can and cannot tell you

The risk appetite score says how willing markets are to fund risk and faster expansion; it does not say whether your deals convert. The hire is a bet on your own evidence, gated by the same line the other new bets use: when risk appetite falls below its pause line, new commitments stop — and a first salesperson who arrives just before that line is a bet made on the edge.

Company inputs to check: Closed deals from founder-led sales: count, segment and cycle length. The fully loaded cost of the rep and the cash plan that carries it. The stage gate in writing: the evidence that promotes the bet and the condition that stops it.

Decision note to complete: Hire [role] when [deal evidence] holds. If [stop condition] by [date], return to [founder-led sales]. Approver: [name]. Review: [date].

References: Capital discipline for venture-backed companies: https://whether.work/resources/capital-discipline-venture-backed-companies; Test the hire against this week's lines: https://whether.work/operate

Decision areas: expansion-bets

## Frameworks

### Capital Discipline for Venture-Backed Companies

URL: https://whether.work/resources/capital-discipline-venture-backed-companies

A 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.

#### Why capital discipline now defines board credibility

A board of a venture-backed company is now judged on what its spending taught the company and how much runway it kept, not on the plan it approved. Treat every dollar of spend as a commitment that must return information: a number that moved, or a test that passed or failed.

While capital was cheap, growth hid governance defects. Teams could grow into mistakes, raise again to cover uncertainty, and call a miss market noise. When capital tightens, the same defects show up as shorter runway, slower decisions, and hurried cuts that remove capability the company still needs.

A board’s capital discipline model needs three things: a fixed review schedule, thresholds that trigger intervention, and a way to undo each decision wherever one exists. Without them, leadership swings between overconfidence and panic. With them, the company keeps operating through volatility and keeps its options open.

#### Board-level architecture for disciplined capital allocation

The structure has to be specific, repeated every cycle, and checkable afterward. It has three parts: one standard decision packet, a stated confidence range for each major assumption, and a response agreed in advance for each threshold breach. Without that structure, whoever argues most urgently sets the decision.

Use one packet structure for every strategic bet: the objective, the spend required, the leading indicators expected to move, the conditions that would reverse it, and the named owner. If each proposal argues in its own format, the board cannot compare them.

Then hold three kinds of review. Weekly reviews check which way the indicators are moving. Monthly reviews check whether a move has lasted 30 days. Quarterly board sessions decide irreversible commitments. Keeping to these three meetings is what turns data into decisions instead of commentary.

#### Execution discipline: sequencing commitments in uncertain regimes

Most discipline failures are ordering failures: teams invest in the wrong sequence, not too much. Approve commitments that improve information before commitments that add fixed cost.

Use this order: first moves that protect runway, then experiments that produce evidence, then commitments that scale. The order stops a team from scaling an assumption before it has tested it.

Turn each strategic goal into staged funding. Instead of approving a full year of spend for one thesis, release funds in stages, each tied to a milestone the board can observe.

#### Governance operating cadence: 30-day confirmation and threshold response

Require a move in an indicator to last 30 days before it changes a decision. Thirty days is the shortest window that filters out a one-off weekly spike, and short enough that the board does not see deterioration a quarter late.

For the 30-day rule to work, write down three things: which indicators are watched, how long a move must last to count, and which spending change each lasting move triggers. If any of the three is left open, the rule gets applied differently each month.

The board enforces consistency. Management is free to act inside the thresholds but may not reinterpret them each month. Applying the same thresholds every month is what keeps the board’s trust when results are mixed.

#### What exemplary boards do differently

Strong boards rely on reusable documents, one shared vocabulary, and named owners rather than on speeches. That lets governance keep working as the company grows.

They treat a reversal that meets a predefined threshold as governance working, not as failure. Removing the stigma from rollback makes teams report problems sooner and shortens the time to correct them.

Instead of cutting every budget by the same share, they move money to the bets with evidence behind them, which keeps options open and keeps the team’s confidence.

#### Operating scorecards boards should require every month

Separate leading indicators from lagging ones, and note how far each can be trusted. Quarterly revenue growth is familiar and easy to present, but by the time a lagging number falls, the options have already narrowed. Add forward-looking measures: sales-cycle length, onboarding completion rate, and early cohort retention.

Mark how reliable each metric is. If a metric is improving but rests on incomplete instrumentation, say so on the page, so the board does not commit more money on a fragile reading. Before approving an incremental commitment, ask whether the improvement would survive better data.

Break metrics out by customer segment. A company-wide average can hide decline in high-value segments while low-value segments inflate top-line activity. With limited runway, that distortion steers spend toward traction that is not real.

Review cash conversion and decision speed together. If decisions take longer while burn stays flat, the company is paying for internal drag, not learning. Track spend against decision cycle time, and ask which approval steps slow decisions without producing information.

Add a variance note to each scorecard section. Finance, product, and sales and marketing often read the same movement differently; instead of forcing agreement, record each view with a confidence rating and the next check it calls for. The board sees the disagreement without the decision slowing down.

List on the scorecard every initiative paused or retired since the last meeting. Most board materials report the initiatives in motion and omit those paused or retired. Listing stops makes correction routine and, over time, returns more capital to better uses.

#### Board workshop agenda for capital discipline reset

Open with an inventory of current commitments, not with plans. Directors and executives list every fixed and semi-fixed obligation and mark how hard each is to undo: hiring commitments, vendor contracts, roadmap promises, and channel spend. The inventory shows where flexibility still exists and where it has quietly gone.

Second, test the assumptions. For each major commitment, ask which assumption does the most damage if wrong, which signal would confirm or disprove it, and how soon that signal can be seen. Putting each argument as a testable assumption replaces debate with a check.

Third, rehearse an escalation. Pick two plausible bad scenarios and walk each through detecting the trigger, notifying the owner, preparing the board addendum, and acting. A rehearsal finds process gaps before real pressure does, and often shows that no one is sure who has authority.

Fourth, present each funding choice in stages rather than approve-or-reject: a base stage, the evidence gate, and the expansion stage. Work keeps moving while the downside stays capped.

Fifth, agree how to describe uncertainty. Trust drops fast when what management tells the board differs from what it tells the company. Leave with shared words for uncertainty, confidence, and the reasons for a reversal, and use them in both places.

Close by assigning owners and dates: who keeps the decision inventory, who reports on threshold status, and when retrospective findings change the process. Without named owners, the workshop changes nothing.

#### Board Q&A appendix: high-friction governance questions

What evidence would make us commit more today, and what evidence would make us pause? Without this question, the case for expanding stays vague while the pull to continue stays strong. A good answer names the metrics, the confidence required, and the person who monitors them. Require it on every material proposal, so no team wins approval on narrative confidence alone.

Where could this decision fail silently before lagging results show it? Silent failure shows up first in quality drift, rising support load, longer sales cycles, and fragile staffing. Name these channels early, and attach a leading indicator and an escalation rule to each before the damage compounds.

Which assumptions depend on outside events, and which can we control? Give outside dependencies larger buffers and shorter review intervals. Give internal assumptions a named owner and dated checkpoints. The split shows the board where its scrutiny can change the outcome.

How does this proposal change our options 90 days from now? A strong proposal keeps or widens the company’s options while it gathers evidence; a weak one uses options up fast and teaches little. Asking this makes directors judge flexibility, not an isolated return-on-investment story.

If a threshold is breached, what do we do in the first 48 hours? Strong teams set containment, communication, and the handoff of the decision in advance. Without a 48-hour plan, escalation turns into late triage and the damage spreads.

Which decision from last quarter would we make differently with what we know now, and what have we changed so we do not repeat it? The answer should name a rule, threshold or document the board changed after last quarter’s retrospective.

#### Implementation anti-patterns and remediation actions

Anti-pattern one: introducing too many categories, metrics and templates at once. Fix: start in the one decision area with the most risk, and expand only after teams produce reliable documents there.

Anti-pattern two: thresholds too wide to ever trigger, which leaves decisions under stress to whoever tells the best story. Fix: narrow the thresholds, set how long a breach must last, and give each threshold an action owner and a deadline.

Anti-pattern three: claiming a decision can be reversed without the means to reverse it, because the communication plan, the dependency map, or the handoff of authority is missing. Fix: run reversal drills regularly, and have an executive owner track each after-action report.

Anti-pattern four: board materials heavy on reporting and light on decisions. Fix: build each packet around the decision: what changed, what lasted 30 days, what did not, what action is requested, and what is being stopped.

Anti-pattern five: finance, product, and sales and marketing using different meanings for risk and confidence, which causes avoidable conflict. Fix: one shared glossary, and recurring cross-functional sessions to check that each team reads the numbers the same way.

Anti-pattern six: no record of past decisions, so teams re-argue settled assumptions and lose what they learned. Fix: a simple decision log that links each decision to its threshold history, its rating for how hard it is to undo, and its retrospective findings.

#### 12-month governance cadence blueprint

Month 1: list current commitments and mark how hard each is to undo. The board packet shows the current thresholds, a reliability note for each figure, and the gaps in the data. Leave the month with a named owner for each gap in instrumentation and each open question about who decides.

Month 2: set threshold levels and how exceptions are handled. Teams present draft escalation rules and rehearse one realistic breach. Directors confirm response windows and when the board is notified before the next cycle.

Month 3: review the first decisions made under the new process. Check that approved commitments matched the evidence and that paused decisions were revisited on the criteria set in advance. Change the process at once where the review shows a gap.

Months 4 to 6: finance, product, operations, and sales and marketing present one shared reading of the metrics and of proposed budget shifts. Where they disagree, update the glossary and metric definitions instead of writing compromise wording.

Month 7: the board runs a drill in which demand falls and delivery slips at the same time. Test whether thresholds trigger in the right order, whether the authority map holds, and whether a reasoned message can go out quickly.

Months 8 to 10: check the ratio of reversible experiments to irreversible commitments. Directors compare changes in the ratio with how well the evidence has held, and challenge any irreversible expansion not backed by evidence that lasted.

Month 11: measure the governance process itself: the share of packets completed, the time taken to answer escalations, rollback readiness, and the number of retrospective actions closed. Run governance as a system with its own reliability metrics.

Month 12: the board and executives agree what to simplify, what to tighten, and what to retire. Cut process steps that add little, and keep the rules where risk is concentrated.

#### Director checklist for every major capital decision

Can we state the main hypothesis, the evidence threshold, and the decision owner in one minute? If not, the proposal is not ready for approval.

Does the packet list which parts of the initiative can be undone and which cannot? A mostly flexible plan can hide one irreversible commitment.

Is each escalation threshold measurable, time-bound, and tied to a named response? A metric with no consequence gives false comfort.

Does the packet show the 30-day view: how long the move has lasted, how reliable the data is, and what spending change it could justify? Without it, teams overreact or underreact to short-term swings.

What is the first action if we are wrong? A strong proposal includes containment steps and the order of communications, not only the upside.

Which past decision in our records is closest to this one, and which lesson from it is built into this proposal?

If this initiative needs more capital than planned, what would we stop funding? A proposal that cannot answer has not weighed the trade-off.

Does the operating team actually use these documents? A framework nobody opens governs nothing.

### Board Level Capital Posture Framework

URL: https://whether.work/resources/capital-discipline-venture-backed-companies

A 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.

#### Defining board-level capital posture in practical terms

A board level capital posture framework is a fixed method for deciding how much capital the company commits, given market conditions and how well the company is executing. It is not a policy memo written once: the board re-runs it each month, and it ties evidence and confidence to who may act.

The board sets limits and leaves execution to management. The limits answer three questions: which commitments management may make, which need more evidence first, and which are off the table until conditions improve.

When the limits are written down, teams move quickly inside them. When they are vague, every decision becomes a one-off negotiation, so decisions slow down and risk rises at the same time.

#### The three-layer posture framework

Keep three layers apart: market conditions, company capacity, and decision rules. Separating them stops two common mistakes: blaming weak execution on the market, and treating a temporary market swing as a strategic collapse.

Layer one, market conditions, covers the cost of capital, demand reliability, and the company’s options for raising money. Layer two, company capacity, covers cash resilience, execution throughput, and strain on the organization. Layer three, decision rules, covers escalation thresholds, how hard each decision is to undo, and the review schedule.

Review all three layers in the same meeting. Reading one layer alone produces false confidence and decisions made in the wrong order.

#### Building a posture-to-action matrix the board can trust

Map each level of commitment to specific actions in hiring, roadmap scope, sales and marketing spend, vendor contracts, and financing options. Require every entry to say both when to expand and when to contract.

For each area, mark which decisions management makes and which the board reserves. Without that line, management expands commitments during a few good weeks, before the improvement has lasted.

Put the matrix in the regular board materials, not an appendix. If directors cannot find it, it will not change decisions.

#### Artifact governance: what must exist before approvals

The framework is only as strong as the documents behind it. Before a major commitment is approved, require five: the decision rationale, how hard it is to undo, a dashboard of its thresholds, an owner map, and a draft of the rollback communication.

Requiring them forces the preparation to happen before capital is locked in. It also shortens board discussion, because every proposal arrives in the same format.

Scale the requirement with the size of the commitment: a small proposal needs little evidence, and an irreversible one needs the full set.

#### How to implement the framework without creating bureaucracy

The usual failure is bureaucracy presented as rigor. Judge the rollout by whether it cuts ambiguity and rework without adding meetings: keep the existing meeting schedule, and replace low-value reports with the framework’s documents.

Roll out in phases: pilot in one decision area, refine the templates, then extend to the others. Pilot where the risk is highest, usually hiring pace or growth in sales and marketing spend.

Directors keep it consistent by asking for the same documents every cycle and refusing one-off exceptions that skip the process.

#### Framework diagnostics: how to know posture governance is actually working

A working framework changes decisions and behavior in ways you can measure. Early signs: fewer exceptions, escalated issues closed faster, and spending that moves when confidence moves. If none of these appear, the framework exists on paper only.

Count the board requests that management did not see coming. When management knows which documents will be required, surprise requests drop. Frequent surprises point to unclear limits or uneven enforcement.

Measure the quality of reversals, not only their number. A high count can mean healthy discipline or unstable planning. Score each reversal on four measures: time to detection, adherence to the notification rule, collateral impact, and a written lesson. Prefer a timely, open reversal to a delayed defense.

Watch where meeting time goes. Early on, most of it goes to arguing about data quality and who owns the process. Once the framework works, it goes to trade-offs and sequencing, a reliable sign the foundations are holding.

Track decision speed by class. Delegated decisions should get faster while reserved decisions stay deliberate and evidence-heavy. If every class slows down, the process is too heavy. If reserved decisions speed up without more evidence, rigor is slipping.

Audit threshold settings every quarter. A threshold that never triggers may be too loose; one that triggers constantly may be too sensitive or tied to a metric no one can act on. Setting thresholds is a quarterly job, not a one-time setup task.

#### Board implementation playbook: quarter-by-quarter sequencing

Quarter one: set the foundation: the levels of commitment, the decision classes, and the documents required for material commitments. Keep the scope narrow to avoid rollout fatigue. The goal is that every material decision uses the same format, even before the format is polished.

Quarter two: build the framework into budgeting, roadmap reviews, and hiring plans. Reuse the same data in each meeting so teams report it once.

Quarter three: review approved, paused, and reversed decisions. Compare the indicators each decision expected with what happened, and record any change in how thresholds were read. This stops the team from holding on to assumptions that have gone stale.

Quarter four: test the framework under stress. Run tabletop exercises on a market shock, a leadership change, and a funding squeeze. Check whether the authority map, communication templates, and escalation steps hold on a compressed timeline.

In every quarter, name one executive accountable for the framework and one director who enforces it. Shared ownership with no single accountable person is a predictable failure.

By the end of year one, the company should have a complete record: decision packets, escalation logs, variance addendums, and retrospective findings. New directors read that record to learn how the board decides.

#### Closing note: making the framework durable

Each month, restate the vocabulary, the thresholds, and the document standards, so decisions stay consistent through leadership turnover and market swings.

A new executive should be able to run the framework within weeks. If they need a lot of unwritten context, it depends too much on particular people; simplify it.

Each year, publish the board’s non-negotiables: evidence before expansion, thresholds before escalation, and a reversal plan before any irreversible commitment.

### Reversibility as Governance

URL: https://whether.work/resources/capital-discipline-venture-backed-companies

A 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.

#### Why reversibility is a governance function, not an execution detail

Reversibility as governance means rating how hard a decision is to undo before the board approves it, not after. Most companies raise the question only once the decision is made, when the chance to govern it has passed. Give the rating the same weight as the decision’s expected upside.

Hold a decision that cannot be undone quickly to a higher evidence bar and tighter escalation rules. Let a reversible decision proceed on less certainty, because its downside is already contained. Small experiments then stay fast, and commitments the company could not recover from wait for evidence.

When board packets leave out how hard each decision is to undo, directors cannot see options closing. Capital gets committed faster than it can be moved, and flexibility disappears just as uncertainty rises.

#### Reversibility taxonomy for board decision packets

Sort every decision into one of three classes so the board can compare them. Fully reversible: can be unwound within 30 days with little collateral damage. Conditionally reversible: can be unwound at moderate cost with controlled disruption. Effectively irreversible: unwinding would cost a material amount of money or trust.

Each proposal states its class, the evidence for that class, and the preparations that make an unwind possible. Treat a reversibility claim with no evidence behind it as an unresolved risk.

The classes also set the order of work: run reversible experiments first, and hold irreversible rollouts until the evidence is stronger.

#### Escalation thresholds and rollback authority design

Reversibility protects the company only if escalation and authority are explicit. Thresholds set when a decision goes up for review; the authority map sets who can act without waiting.

Combine size and duration in each threshold. For example, a one-week anomaly triggers closer watching, while a breach that lasts two reporting cycles with falling confidence triggers action. This matches the 30-day confirmation rule.

Each authority map names a primary owner, a backup owner, and the point at which the board is notified. If authority is unclear during an unwind, the planning was wasted.

#### 30-day confirmation logic as the bridge between volatility and commitment

Weekly data is useful but noisy; quarterly reviews are stable but slow. A 30-day confirmation rule sits between them: an improvement must last 30 days before commitments expand, and a decline that lasts 30 days brings intervention forward.

Under reversibility governance, the rule decides between three paths: keep running reversible experiments, start a rollback, or ask the board to approve irreversible scaling. It is the clock the decision runs on.

Ask for a confirmation table in each monthly pack with five columns: indicator, current direction, confidence, days in the current state, and the date of the next decision checkpoint.

#### Institutionalizing reversibility as governance culture

Boards and executives should reward three behaviors: disclosing a warning sign early, rolling back on the agreed terms, and writing down the reasoning behind each decision.

Grade each decision on its process as well as its outcome: were thresholds set and followed, and was the reasoning written down? A well-made decision can still fail, and a good result can hide a poor process. Reversibility governance grades the process because the process is what the team controls.

Over time, teams stop fearing correction: they escalate sooner, the board intervenes earlier, and capital keeps moving to where the evidence is.

#### Reversibility drills: from policy statement to operational muscle

A rollback policy fails if the team never rehearses it. Require regular drills on high-impact decisions such as pricing changes, major feature launches, and channel experiments at scale. Each drill checks that a rollback can be started, communicated, and finished within the stated window.

Test detection first. Can the team spot a threshold breach quickly from trusted data? If detection depends on stitching data together by hand, the rollback window may close before anyone acts. Slow detection is often the largest hidden risk.

Second, test the handoff of authority. If the primary owner is unavailable, does the backup have written authority and enough context to act? Companies often find that backup ownership exists on the org chart but not in practice.

Third, test the order of communications under time pressure. Customers, internal teams, and partners need different messages at different times, and getting the order wrong can turn a manageable rollback into reputational damage.

Fourth, measure side effects. A reversal can protect capital but cause service instability or support overload. Each drill’s output lists the steps that protect customer trust during the unwind.

Finally, publish the drill findings with a named owner for each fix. Without visible follow-through, a drill is a box-ticking exercise that changes nothing.

#### Portfolio governance: balancing reversible exploration with irreversible commitments

A healthy portfolio mixes reversible experiments with a few deliberate irreversible bets. The board’s job is to let irreversible exposure grow only as the evidence improves. Review the ratio of the two every month and discuss any drift.

Give each experiment a fixed budget and a hard stop condition. Teams can then test quickly without returning for approval, and the downside stays capped. Speed with a capped downside is what reversibility governance buys.

Hold irreversible bets to a higher bar: strategic fit, evidence that has lasted, and a contingency plan ready to run. A compelling upside story without a contingency plan does not qualify for approval.

As the portfolio grows, map the dependencies between decisions. Two decisions that are each reversible can become hard to unwind together if they share infrastructure, sales commitments, or promises to customers. Group decisions that share infrastructure, sales commitments, or customer promises together in the board pack.

For each decision, list the future choices it rules out alongside its expected value. Reversible decisions keep future paths open; irreversible ones close them, so ration irreversible decisions deliberately.

Keep committing, but in a form the company can still change, and keep the cost of correcting below the level of material damage.

#### Closing note: why a board trusts a decision it can undo

A written way to undo each decision lets the board approve experiments without losing control, and step in quickly without disrupting execution.

When the route to correction is clear, teams are more candid about uncertainty. That candor improves the data the board sees and keeps spending tied to what is happening, not to what the team hopes.

The result over time is not perfect forecasts. It is fewer surprise failures, faster recovery when assumptions break, and more trust between management and the board.

Boards that keep this up over several cycles usually see better capital efficiency, clearer communication under pressure, and more confidence about when to accelerate and when to hold, reset, or reduce risk.

## Articles

### Hiring freeze policy for high interest rates

URL: https://whether.work/resources/should-we-freeze-hiring-high-interest-rate-environment

Decide which roles to keep, which to tie to milestones and which to pause while rates are high, then lift the freeze in stages.

#### Board summary

Keep roles that protect reliability, renewals and cash visibility open. Review each role’s cash impact within two quarters.

Approve unproven expansion hires one at a time against a 30-day milestone. Pause roles with no measurable business case.

Review the hiring policy when cash conversion worsens for 30 days, sales cycles lengthen and near-term financing becomes less likely.

Reopen hiring in stages after two consecutive monthly readings show stable burn multiple and demand quality.

#### Review roles before freezing hiring

A hire commits cash to payroll and onboarding. Compare the cost of leaving a role unfilled with the cost and time needed to unwind it if demand falls.

Replacing a reliability bottleneck and staffing an unproven growth team carry different risks. Review them separately before imposing a blanket freeze.

#### Which roles to approve or pause

Safe roles protect current operations or revenue: production reliability, renewals support and finance controls for cash visibility. Keep them open with constrained approval.

Risky roles support initiatives that have not shown repeatable demand. Approve one hire, set a 30-day evidence target and review the result before approving another.

Dangerous roles lack a clear owner, a validated market or measurable milestones. Pause them until the business case and resume conditions are explicit.

#### When to resume hiring

Set resume conditions using burn multiple, pipeline conversion and cash remaining after committed spend. Review demand and delivery weekly; use monthly readings to decide whether to reopen hiring.

An example requires three conditions: stable win rates and churn for 30 days, shorter delivery cycles with fewer emergency escalations, and financing access that no longer requires immediate cuts.

When all three hold, reopen safe roles first, a few at a time. Keep risky hires tied to milestones and dangerous roles paused until two monthly confirmations pass.

#### Build the role list

List each open role and planned backfill with its purpose, cost if unfilled, evidence window and time to reverse. Classify it as safe, risky or dangerous.

Review the list with finance and hiring managers. Record one measurable indicator per approval, the pause and resume lines, and an owner and review date for each exception. Include the list in the weekly memo.

#### Should startups freeze hiring when rates are high?

High rates alone do not require a blanket freeze. Keep roles that protect operations or current revenue open, tie expansion hires to milestones and pause roles without a measurable business case.

#### How long should a hiring freeze last in a tightening market?

Review monthly. Reopen in stages after two consecutive monthly readings show stable burn multiple and demand quality; keep the role-specific milestones in place.

#### What should I send my board about hiring?

Send the approved role list, exceptions with owners and review dates, and the pause and resume lines.

### How much runway should a startup have?

URL: https://whether.work/resources/how-much-runway-do-we-need-tightening-market

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.

#### Board summary

Use 18–24 months as a planning range during tightening. Favor the upper end when commitments are slow to reverse or financing is uncertain.

Separate the cash floor for essential operations from the buffer available for new investments.

Release new spending in stages after demand and financing access improve for 30 days. Keep projected runway above the agreed floor.

#### Account for the time needed to cut costs

Set the target using demand uncertainty, fixed costs and the time needed to respond when assumptions fail. A payroll or vendor commitment may keep consuming cash for months after you decide to stop.

Separate the cash needed to sustain essential operations without emergency financing from the buffer available for new investments. Model both before approving more spending.

#### Runway bands

Safe band: 20–24 months when financing is uncertain and a large share of costs is hard to reverse.

Risky band: 15–19 months with mixed demand. Review burn multiple monthly, set stop conditions for each investment and hold irreversible expansion.

Dangerous band: below 15 months with limited financing options or high fixed costs. Inventory commitments, sequence cash-preservation actions and freeze non-core spending.

These are planning defaults. Adjust them for revenue concentration, collection risk and the time your company needs to cut costs.

#### When to change the runway target

Agree on numerical limits and review periods for retention, gross margin and cash forecast error before changing the runway target.

Example pause line: retention stays below your limit for two consecutive monthly readings while gross margin keeps falling. Increase the runway target and suspend non-core commitments.

Example resume line: renewals and conversion improve for 30 days, cash forecast error narrows and financing access improves. Release one investment installment while keeping projected runway above the agreed floor.

#### Test the cash forecast

Calculate runway under a base case, a downside case and a case where payroll and vendor costs take longer to unwind. List each major cost with its exit terms and time to stop.

Check the roadmap against those cases. Fund retention and measurable customer learning before scaling new initiatives. Seek board approval for any plan that would take projected runway below the agreed floor.

#### What runway target should startups use in a recession risk environment?

Start with an 18–24 month planning range during tightening. Adjust it for fixed costs, collection risk and financing access.

#### Is 12 months of runway enough in a tightening market?

Test whether cash lasts through a downside case and the time needed to cut costs. A 12-month runway leaves less room for delays; reversible costs and available financing matter.

#### How do boards evaluate runway confidence?

Compare downside cash forecasts, recent forecast errors and the time needed to exit major commitments.

## Terms

### Funding pressure

A 0-100 score for how hard it is for U.S. companies to raise or borrow money. Higher means harder: conserve cash and extend runway.

### Risk appetite

A 0-100 score for how willing U.S. investors and buyers are to fund new products, hires and growth bets. Higher means more willing.

### Operating latitude

A 0-100 score: room to hire, spend and commit; higher means more room. Weighted mostly toward risk appetite: (risk appetite × 0.7) + ((100 − funding pressure) × 0.3).

### Recession warning gauge

The ten-year Treasury rate minus the two-year rate. Below zero, short-term borrowing costs more than long-term. That has preceded most U.S. recessions.

### Short-term borrowing rate

The baseline cost of short-term borrowing in U.S. markets, read from the 1-month Treasury bill. Higher means borrowing costs more.

### Conditions (the four weather labels)

Each week falls into one of four: Sunny (money cheap and available), Cloudy (available but pricey), Stormy (changing week to week), Freezing (expensive and hard to raise).

### Pause if

The reading at which hiring, spending, long-term commitments or another area of decisions pauses. Stated as a number agreed in advance.

### Resume when

The reading at which paused decisions re-open. It sits past the pause line, so conditions have to improve beyond where they worsened, not merely back to it.

### Conditions change if

The reading at which conditions themselves change, and the weekly guidance with them, rather than pausing a decision inside the current ones.

### Margin (close to, within reach of, or clear of the line)

How far this week's scores sit from the nearest change line, in points. Close means a small move would change conditions, so keep commitments reversible. The API calls it confidence; it is not a probability.

### Saved copy

When a live source does not answer, the brief uses the last reading it saved and says so with the date. Fine for reversible decisions; wait for live data before irreversible ones.

### Yield curve

The interest rates the U.S. government pays to borrow for different lengths of time — one month, three months, two years, ten years.

### Spread

One rate minus another. A ten-year minus two-year spread of +1.2% means long borrowing costs 1.2 percentage points more than short.

### Inversion

A spread below zero: short-term borrowing costs more than long-term.

### High-yield credit spread

The extra interest riskier companies pay to borrow over what the government pays. It widens when lenders get nervous.

### VIX

An index of how much stock-price turbulence traders expect over the next month. Higher means more expected turbulence.

### Chicago Fed financial conditions index

A Federal Reserve summary of how easy or hard overall borrowing is. Zero is average; above zero is tighter than average.

### St. Louis Fed (FRED) series codes (DGS1MO, DGS2, DGS10)

FRED is the Federal Reserve's free public data service. DGS1MO is the one-month Treasury bill used as the short-term borrowing rate, DGS2 the two-year Treasury rate, DGS10 the ten-year.