How to Structure a Vesting Schedule Proposal for a Launchpad IDO Partnership

You pitched three launchpads this month. All three asked the same question back: "What's your vesting schedule?" You sent a one-line answer — "12 month vesting, 6 month cliff" — and never heard back. That's not a coincidence. Launchpads reject more deals over vague tokenomics than over anything else in the deck.

A vesting schedule isn't a formality you bolt onto the end of your proposal. It's the first thing launchpad partnership teams actually underwrite, because it tells them whether your project is built to survive post-TGE or built to dump on their community. Get the structure wrong and the rest of your pitch never gets read.

What should a vesting schedule proposal include for a launchpad IDO?

A launchpad-ready vesting proposal needs five specific components: TGE unlock percentage, cliff length, linear vesting duration, allocation-by-category breakdown, and a monthly unlock table showing circulating supply at each milestone. Most launchpads want to see TGE unlocks capped around 10-20% for public/IDO allocations, with team and advisor tokens vesting over 18-36 months and a cliff of at least 6-12 months before any team tokens unlock.

If your proposal doesn't answer those five points in writing — not verbally, not "we'll finalize later" — expect the launchpad to send it back or quietly stop responding. They've seen too many projects promise reasonable terms in a call and then submit a term sheet with a 40% TGE unlock.

Why do launchpads reject vesting proposals that look reasonable on paper?

Most rejected proposals fail not because the numbers are wrong, but because the allocation categories don't match the unlock math. A launchpad underwriter will cross-check your total token supply against your unlock schedule line by line — if the numbers don't reconcile to 100%, that's an instant red flag on your financial diligence, not just your spreadsheet skills.

The second most common rejection reason: team and private-round vesting that's shorter than the public round's. If insiders can exit before IDO buyers, launchpads read that as a dump risk they'll get blamed for. Public allocation should always vest at least as long as, ideally longer than, team and VC tranches.

The allocation categories launchpads expect to see broken out separately

• Public/IDO round — lowest TGE unlock risk tolerance for launchpads, usually 10-25% TGE with 3-9 month linear vesting

• Private/seed round — typically 6-12 month cliff, then 12-24 month linear vest

• Team and founders — longest lockup, usually 12 month cliff minimum, 24-36 month linear vest

• Advisors — similar structure to team, sometimes shorter total duration (12-18 months)

• Treasury/ecosystem fund — often has its own multi-year unlock tied to milestones, not just time

• Liquidity provisioning — usually unlocked at TGE or near-fully, since it needs to be tradeable immediately

How do you build the unlock table a launchpad will actually ask for?

Launchpads want a month-by-month (or quarter-by-quarter) table showing cumulative circulating supply as a percentage of total supply — not just your per-category vesting terms in isolation. This is the single artifact that gets forwarded internally to their investment committee, so it needs to stand alone without your deck attached.

1. List every allocation category down the left column with its total token amount and percentage of supply

2. Add a column for TGE unlock amount per category

3. Add monthly columns for at least the first 24 months, showing tokens unlocked that month per category

4. Add a running total row showing cumulative circulating supply at each month

5. Convert the cumulative total into a percentage of max supply — this is the number launchpads actually scan for first

6. Flag any "cliff edge" months where multiple categories unlock simultaneously, since these create sell-pressure spikes launchpads specifically ask about

If month 12 shows a 15% jump in circulating supply because team, private round, and advisor cliffs all expire the same month, fix that before you submit. Staggering cliff endpoints across different months is one of the easiest ways to make a proposal look more thought-through than competitors who didn't bother.

What makes a vesting proposal credible enough to fast-track launchpad review?

Credibility comes from showing your reasoning, not just your numbers. Launchpads that have reviewed hundreds of IDO applications can tell within minutes whether a schedule was benchmarked against comparable projects or just guessed at.

• Reference 2-3 comparable projects in your category and cite their vesting terms as your benchmark

• Explain the logic behind your cliff length — tie it to your roadmap milestones, not an arbitrary round number

• Include a one-paragraph rationale for why your TGE unlock percentage is set where it is, especially if it's on the higher end

• Show the smart contract or vesting platform you'll use for on-chain enforcement — "trust us" vesting gets rejected on sight

• Disclose any previously negotiated side-deals with specific investors that deviate from the standard schedule

That last point matters more than founders expect. Launchpads have been burned by projects that showed a clean public schedule while quietly cutting better terms for a lead investor. If that surfaces after the IDO, it's the launchpad's reputation on the line with their community, not just yours.

How do you get the proposal in front of the right person at the launchpad?

Most launchpad partnership teams review deal flow through Telegram, not email — the back-and-forth of finalizing vesting terms happens in direct chats with BD leads and investment committee members who live in Telegram groups all day. If your outreach process can't keep track of who's seen which version of your term sheet, you'll end up sending the wrong draft to the wrong contact, which is its own credibility hit.

Structuring a DeFi partnership proposal follows a similar logic to vesting proposals — both get judged on whether your numbers reconcile and your terms protect the counterparty. The same discipline applies to tracking the deal once you've sent it.

CRMChat includes a deal flow tracking system built for exactly this — logging which launchpad contacts have which version of your vesting terms, what stage each conversation is at, and when you last followed up, all without leaving Telegram. If you're running outreach to multiple launchpads simultaneously, a dedicated deal flow tracking system for crypto fund investments keeps every term sheet revision tied to the right thread instead of buried in scattered DMs.

CRMChat also automates personalized follow-up sequences to launchpad BD contacts, so a revised vesting table doesn't sit unsent because someone forgot to resend it after the finance team made a change. For teams doing wider investor or launchpad outreach on Telegram, that same infrastructure is what CRMChat's Web3 CRM is built around — research, outreach, and deal tracking in one place instead of three disconnected tools.

What should you avoid putting in a vesting proposal?

• Don't propose a TGE unlock above 25% for public allocation without a strong justification — most launchpads will push back automatically

• Don't use "linear vesting" without specifying the interval — daily, weekly, and monthly unlocks read very differently to a modeling spreadsheet

• Don't leave treasury and ecosystem fund unlocks undefined — "TBD" on your largest allocation category kills trust immediately

• Don't submit a schedule where private round vests faster than public round — this is the fastest way to get rejected outright

• Don't omit the smart contract address or vesting vendor once you've selected one — launchpads will ask before final approval regardless

A tight, reconciled vesting proposal signals something bigger than good tokenomics — it signals you've thought about what happens to your community after the IDO closes. That's the thing launchpads are actually underwriting. The token math is just how they check your work.