guides
How to Research a DeFi Protocol's Treasury Before Proposing a Partnership
Learn what to check in a DeFi protocol's treasury — reserves, runway, token concentration — before you waste time pitching a partnership that can't be funded.
You spend three weeks crafting the perfect partnership pitch for a DeFi protocol. You get on a call with their BD lead, everyone nods, and then the deal quietly dies because their treasury had six months of runway left and zero appetite for new spend. That's a preventable dead end — and it happens constantly in Web3 BD.
What should you check first in a DeFi protocol's treasury?
Start with three numbers: total treasury value, stablecoin-to-native-token ratio, and monthly burn rate. If a protocol's treasury is 80%+ its own native token, that's a red flag — a market downturn of 30-40% could gut their actual spending power overnight, even if the headline treasury number looks impressive on a dashboard.
Most protocols with active treasuries publish this data on-chain or through a dashboard tool like DeepDAO, Llama, or their own governance forum. If you can't find a public treasury breakdown within 10 minutes of searching, that's itself a signal — either the protocol isn't transparent, or its treasury is small enough that they don't bother publishing it.
How do you calculate a protocol's real runway?
Runway = liquid treasury (stables + easily sellable assets) divided by average monthly burn. Most sustainable DAOs run 18-24 months of runway. Anything under 6 months means they're likely in survival mode, not partnership mode — no matter how friendly the community manager is on Telegram.
Pull the treasury address from their docs or governance forum and check it on a block explorer or Llama's treasury tracker.
Separate volatile assets from stables — only count stablecoins and blue-chip assets (ETH, BTC) as "spendable" for near-term deals.
Check governance proposals from the last 90 days for any treasury diversification or spending freezes — these tell you their current risk appetite.
Look at token unlock schedules — a big unlock in the next quarter can dilute their native holdings fast, changing their real spending power.
Cross-reference their multisig signers — fewer than 3-4 active signers on a large treasury is a governance risk worth flagging before you commit resources to the deal.
What does token concentration tell you about deal risk?
If the top 10 wallets hold more than 50% of circulating supply, one or two large holders can effectively veto or stall any partnership requiring a governance vote. This matters more than most BD reps realize — you can align with the core team and still get blocked at the DAO vote stage.
Check this on the token contract's holder list, or through analytics tools that show concentration over time. A protocol trending toward more decentralized holdings is generally a safer long-term partner than one where insider wallets are quietly accumulating.
Where do you find the people who actually control the treasury?
Treasury data tells you if a deal is fundable. It doesn't tell you who to call. Most protocols route treasury decisions through a handful of core contributors or multisig signers — names you can usually trace through governance forum posts, past proposal authors, or the team page.
Once you have names, the fastest path isn't scrolling Discord hoping someone responds. Pulling founder and core-contributor contact data from a registry or database, then converting phone numbers to Telegram usernames, gets you a direct line to decision-makers instead of a general inbox. CRMChat's Web3 B2B decision-makers database at crmchat.ai/web3-database is built exactly for this — pre-validated contacts by role, so you're not cold-DMing a community mod and hoping they forward your pitch.
How do you organize treasury research so it's actually usable?
Research that lives in five browser tabs and a Notion page you'll forget about is research you can't act on. You need it structured against your pipeline, tied to the actual contact you're going to reach out to.
CRMChat lets you log treasury findings — runway, concentration risk, decision-maker contacts — directly against a lead record with custom properties, so your BD team sees the same partnership-readiness picture before anyone sends a pitch. Pair that with Telegram group parsing to pull active members from the protocol's own community chat, and you get both the financial picture and a warm list of people already engaged with the project.
Log treasury size, runway, and burn rate as custom fields on the deal record.
Tag protocols by risk tier (high runway / mid / survival mode) so reps prioritize correctly.
Attach the multisig link and last governance vote date for quick reference before calls.
Sync decision-maker Telegram contacts to the same record so outreach and research live in one place.
If you're scaling this across dozens of protocols a month, doing it manually in spreadsheets falls apart fast. Check the top business registry databases piece if you're also sourcing traditional company data alongside on-chain treasury research, and see CRM data enrichment tools for keeping contact records current as teams and multisigs change.
What are common treasury red flags that kill partnership proposals?
Some warning signs are obvious once you know to look for them, but they're easy to miss if you're only skimming a dashboard screenshot someone sent you in a Telegram group.
Runway under 6 months with no active fundraise or token sale in progress.
Treasury concentrated in a single volatile asset — especially their own token — with no stablecoin buffer.
No governance activity in 60+ days, suggesting the core team may be inactive or deprioritizing the project.
Multisig with 1-2 signers controlling a treasury over $1M — a centralization and trust risk.
Recent large token unlocks that haven't been absorbed by the market, signaling likely sell pressure and reduced treasury value soon.
None of these automatically kill a deal — but each one should shift how much upfront commitment you ask for, and how you structure the proposal (revenue share vs. upfront grant vs. equity-style token allocation).
Should treasury health change how you pitch the partnership?
Yes — a protocol with 20+ months of runway can consider an upfront grant or retainer. A protocol running lean should get a performance-based or revenue-share pitch instead, since that's the only structure their treasury can realistically support without a governance fight.
Matching your ask to their actual capacity isn't just polite — it's the difference between a proposal that gets fast-tracked through governance and one that sits in a forum thread collecting downvotes for a month. Do the treasury homework first, then write the pitch. Not the other way around.
