The Bear Market Survival Playbook
Bear markets do not kill projects in a single week; they kill them by attrition. Runway leaks, the team drifts, the community goes quiet and the token chart becomes the only story anyone tells about you. Surviving one is an operating discipline, not a mood. This playbook covers the four decisions that matter most: money, scope, communication and the position you want to hold when liquidity returns.
Start with an honest runway model
Runway in crypto is usually overstated because it is denominated in assets that fall together. Rebuild the model with three columns: stablecoins, liquid majors, and your own token. Only the first column is runway you can plan against.
- Value your own token at zero in the base case. If the plan only survives when your token holds a price, it is not a plan.
- Model liquid majors at a deep drawdown, not at last quarter's price.
- Separate committed spend (payroll, audits, infra) from discretionary spend (events, campaigns, tooling).
- Convert the result into months at current burn, then at a 30% reduced burn. Those two numbers drive every other decision in this article.
Treasury structure is its own topic — crypto treasury and token allocation benchmarks covers how much of the supply should have been reserved for exactly this scenario.
Cut scope before you cut people
Most teams cut marketing first because it is the easiest line to zero. That is usually the wrong order. Marketing that produces compounding assets — documentation, search-visible guides, a working community — costs little and keeps paying after the cut. Marketing that rents attention stops the day the invoice stops.
A workable order of cuts:
- Paid reach and event sponsorships, which stop producing the moment they stop being paid.
- Retainers with no defined deliverable attached.
- Tooling duplication — two analytics vendors, two CRMs, three design subscriptions.
- Roadmap scope, honestly and publicly, so the remaining work is deliverable.
- Headcount, last, and only once the first four have been genuinely exhausted.
Keep shipping something visible every two weeks
In a quiet market, evidence of life is the scarcest asset a project has. The cadence matters more than the size of each release. A fortnightly changelog, a testnet milestone, a docs rewrite or a fee-switch parameter change all read as a team that is still working.
Two rules keep this sustainable: only announce work that is finished, and never announce a date you have not already met internally. A missed date in a bear market costs more than the same miss in a bull market, because there is no incoming attention to bury it.
Run community on a lower, fixed cadence
Communities do not need daily noise during a downturn; they need reliability. Reduce to a schedule you can hold for a year with a smaller team:
- One weekly written update, same day, same channel, even when the update is short.
- One monthly call with the founders, recorded and published for the people who miss it.
- A visible contributor path so the twenty people still active have something to do beyond price chat.
The structural side of this — channel design, moderation and ambassador programs — is covered in the Web3 community management guide and the ambassador program playbook.
Build the assets that only work when you have time
Downturns are the only period when a team has the slack to do work that compounds slowly. The highest-leverage items we see:
- Search-visible content. Guides that answer real founder or user questions rank over months, not days. See the crypto SEO guide.
- Documentation and integration guides, which turn every future partnership conversation into a shorter one.
- Audit remediation and security hygiene, cheaper to do now than under launch pressure.
- Listing preparation. Review teams read history; a clean, boring twelve months is an asset. The CEX listing tiers breakdown explains what they look at.
Protect the narrative without pretending
Two failure modes dominate. The first is silence, where the team disappears and the community fills the gap with the worst available explanation. The second is forced optimism, where every post insists things are great while the roadmap slips.
The workable position is plain: state what the market is doing, state what you are doing about it, and state what you are not doing. Teams that say "we cut spend by 40%, extended runway to 24 months, and paused the mobile app" keep more credibility than teams that go quiet for two quarters.
Know what re-entry looks like
The point of surviving is to be positioned when conditions change. Write the re-entry plan now, while it is cheap to think clearly: which channel you turn on first, which product milestone gates the marketing spend, and what evidence tells you the window is open. Market cycle launch timing covers the signals worth watching, and the bull market launch playbook covers what to do once they appear.
Talk it through
If you are re-planning a downturn budget and want an outside read on what to cut and what to protect, book a strategy call.
🔗 Related reading from the Metamoonshots Journal
FAQ
How much runway should a crypto team hold in stablecoins?
Enough to cover committed spend — payroll, audits, infrastructure — for the period you cannot raise in. Teams that plan against their own token price discover the shortfall at the worst possible moment.
Should we keep marketing during a bear market?
Keep the marketing that compounds: content, documentation, community and search visibility. Pause the marketing that rents attention, such as paid reach and sponsorships, because it stops producing the day you stop paying.
Is it safe to delay a token launch until the market recovers?
Delaying is usually cheaper than launching into no liquidity, provided you use the delay to ship product and prepare listings. The cost of waiting is only high when the team stops producing evidence of progress.
How do we keep a community engaged when there is no news?
Replace volume with reliability: a fixed weekly update, a monthly founder call, and a contributor path for the people who remain. Predictable cadence holds attention better than sporadic announcements.