telegram
How to Write a Liquidity Partnership Proposal for a DeFi Protocol on Telegram
Most liquidity partnership pitches die in the first three lines of a Telegram DM. Here's the structure that actually gets a reply from a DeFi protocol's BD team.
You spent three days researching a DeFi protocol's treasury, drafted a partnership pitch you're genuinely proud of, and sent it to their BD lead on Telegram. Forty-eight hours later: nothing. Not even a "seen" reaction. Your message is sitting in the same inbox as twenty other generic "let's collab" DMs from projects they've never heard of.
That's the real problem. It's not that your deal terms are bad — it's that your proposal never made it past the first three lines, because that's all a busy BD person reads before deciding whether to keep scrolling or reply.
What should the first message of a liquidity partnership proposal say?
Your opening message needs to answer three things in under 400 characters: who you are, what specific liquidity need you've identified in their protocol, and what you're offering in return. Protocols with active BD teams get anywhere from 15-40 inbound partnership pitches a week on Telegram — if your first message reads like a template, it gets archived in under 10 seconds.
Skip the intro paragraph about your team's mission. Lead with the number. Something like: "Noticed your USDC/ETH pool on [chain] is sitting at 62% utilization with thinning depth past the $50K mark — we can commit $200K in seed liquidity for a 90-day term." That single sentence tells them you did homework, and it's specific enough to warrant a reply.
What goes into the full proposal document
Once the opener earns a reply, you'll usually get asked to "send more details" — that's your cue to follow up with a structured one-pager, not a wall of text in the chat. A liquidity partnership proposal for a DeFi protocol should include:
Protocol snapshot — TVL, current liquidity pools you're targeting, and the specific gap you've identified (thin depth, imbalanced pairs, upcoming incentive expiry).
Proposed liquidity commitment — exact amount, asset pair, and whether it's one-sided or two-sided liquidity.
Term length — most proposals open with a 60-90 day pilot term, not a permanent commitment. Shorter terms get faster yes answers.
Ask — what you want back: emissions/incentive allocation, fee-share terms, governance token allocation, or a marketing co-promotion slot.
Exit clause — how either side can unwind the position, and the notice period required.
Points of contact — your team's Telegram handles and, ideally, a multisig or on-chain address history showing prior liquidity deployments.
Before you draft any of this, you need the treasury data to back up your number. How to research a DeFi protocol's treasury before proposing a partnership walks through pulling that data so your ask isn't a guess.
How do you find the right person to send it to?
Sending a proposal to a protocol's general support channel is the fastest way to get ignored — most DeFi projects route BD inquiries to a specific person, and general admins will just tell you to "DM the team" anyway. The move is finding who actually owns partnerships, usually someone tagged BD, growth, or ecosystem lead in the project's core Telegram group or associated investor/partner chats.
Protocol-specific Telegram groups, investor communities, and DeFi BD circles are where these contacts actually hang out and where their roles get referenced in conversation. CRMChat lets you search for these groups directly by keyword through its Telegram Group Finder, then pull member lists and bios from inside them so you can identify who's actually tagged as BD or growth before you ever send a message. That's a faster path to the right person than cold-messaging a support bot and hoping for a forward.
If you're already a member of a protocol's community or investor group, the Telegram Group Parser Chrome extension extracts the full member list in one pass — usernames, names, and bios — so you can filter for anyone with BD, growth, or partnerships in their profile before reaching out.
How do you follow up without sounding desperate?
Silence after the first message doesn't mean no — DeFi BD teams are often juggling five deals at once, and a proposal that isn't urgent slides down the priority list fast. A good cadence is one follow-up at 72 hours, referencing something new (a metric update, a related deal you just closed, a relevant market move), then one more at day 7 with a hard deadline attached ("we're allocating this liquidity by [date], happy to hold a slot if useful").
Two follow-ups with no reply is your signal to move on. Chasing past that point reads as desperate and burns the relationship for a future pitch.
Track every proposal you send with the date, amount, and term — don't rely on memory across dozens of parallel conversations.
Log replies and objections so your next pitch to a similar protocol pre-answers the same pushback.
Segment protocols by chain, TVL tier, or pool type so your follow-up messaging stays relevant to each one instead of generic.
CRMChat's CRM pipeline is built for exactly this — it tracks every Telegram conversation, tags deals by stage, and lets you bulk-message segmented lists of protocols when you have an update worth sharing across multiple open pitches at once. That's the difference between "I think I followed up with them" and knowing exactly where every proposal stands.
What mistakes kill liquidity proposals before they're even read?
Most rejected proposals aren't rejected on terms — they're rejected because they never got taken seriously in the first place. The usual suspects:
No on-chain proof of prior liquidity deployments. If you've never actually deployed capital into a pool before, say so honestly and lead with your team's background instead of bluffing.
Vague amounts. "Significant liquidity" means nothing. Give a number, even a range.
No exit terms. Protocols get burned by partners who dump liquidity without notice — proposals that skip the exit clause raise a red flag immediately.
Sending from a brand-new, unverified Telegram account. A freshly created account with no history reads as a scam attempt to anyone doing BD in DeFi. Warm the account up first — warming up a new Telegram account before outreach applies just as much to BD as it does to sales.
Pitching the same terms to every protocol. A protocol with 5x the TVL of another isn't going to take the same $50K ask seriously as a match.
Where CRMChat fits into the whole workflow
Web3 teams closing liquidity and partnership deals on Telegram typically run three motions at once: finding the right groups and contacts, sending personalized outreach at scale, and keeping every conversation tracked so nothing falls through. CRMChat's Web3 customers report faster investor meetings and partnership closes by moving from scattered DMs to a structured pipeline — one team cited going from chaotic Telegram conversations to a $2M funding round in six months once outreach was systematized.
Check the case studies for how other Web3 teams structured their pipeline, or the help center if you're setting up CRMChat for the first time.
