How to Get a Market Maker for Your Token Launch

A token generation event is the single most scrutinised week in a project's life. Every exchange listing team, every prospective treasury allocator, and every trader who might become a holder forms a view of the asset from the first few days of price action. A book that gaps, a spread that sits at 4%, or a pool that drains on the first sizeable sell tells that audience the project could not organise the basics.

Fixing it afterwards costs more. Providers price a rescue mandate higher than a launch mandate because they inherit a damaged reference price and a nervous holder base. Exchanges that saw a bad opening are slower to approve additional pairs. The cheapest liquidity you will ever buy is the liquidity you arranged before anyone was watching.

Two numbers drive everything: circulating float at TGE and the depth you want visible at ±2%. If only a small percentage of supply is unlocked on day one, a provider physically cannot post deep two-sided quotes without dominating the book. Most launches reserve somewhere between one and three percent of total supply for liquidity operations, paired with a stablecoin counterpart of comparable value so the bid side is real rather than notional.

Be honest about vesting. If a large unlock lands six weeks after launch, the provider needs to know, because it changes how it manages inventory and how tight it can quote through that window. Hiding an unlock schedule from your liquidity desk is a fast route to a blown-out spread on the day it hits.

Weeks eight to six: define the budget, decide loan versus retainer, and finalise the venue shortlist. Weeks six to four: issue a single written specification to three or four providers so their quotes are directly comparable, and take reference calls with projects they supported at a similar market cap. Weeks four to three: negotiate and sign, including KPI schedule, reporting, notice, and termination.

Weeks three to one: complete exchange onboarding, sub-account creation, API key provisioning, and treasury transfers. Test the connection on a small pair or a testnet configuration. Final week: dry run. On listing day the desk should be quoting at the moment the pair opens, not requesting keys.

Scope: which venues, which pairs, and the hours of coverage. Performance: maximum time-weighted spread, minimum depth at each band, and minimum uptime, all with a defined measurement method. Economics: retainer amount or loan size, option strikes and expiries if applicable, and who pays exchange fees. Governance: reporting cadence and format, a cure period for missed KPIs, notice period, and a clean unwind mechanic.

Add two protective clauses that founders routinely omit. First, an explicit prohibition on self-matching, wash trading, and coordinated price movement. Second, a right to audit the provider's activity on your pairs through exchange sub-account reporting, so verification does not depend on the provider's own dashboard.

Resist the urge to open on six venues at once. Liquidity spread across many thin books looks worse than concentrated depth on two. A common structure is one tier-one or strong tier-two centralised venue for depth and price discovery, plus one DEX pool for permissionless access, with the provider arbitraging between them so a single coherent price exists.

Additional listings then become a reward for demonstrated volume rather than an expense. Exchanges look at your existing book quality when assessing an application, so a tight, well-supported pair on one venue is the best possible application document for the next one.

Spread on the primary pair holds inside a defined band through the opening hour rather than oscillating with each retail order. Depth at ±2% is present on both sides in similar size, so the book does not read as a wall of asks. The DEX pool price tracks the centralised book within arbitrage tolerance. And when volatility spikes, quotes widen and then re-tighten rather than vanishing.

You should receive a report at the end of day one showing measured spread, depth, uptime, and volume by venue. If your provider cannot produce that within twenty-four hours of the most important day of your project's life, that is the answer to whether they will produce it in month seven.

Signing a loan agreement without modelling the option strikes against the vesting schedule. Allocating float to liquidity that is also promised to an ecosystem fund. Choosing the provider with the lowest headline retainer without comparing depth commitments. Listing on a venue whose fee schedule makes tight quoting uneconomic for the desk. And treating the provider as a vendor to be onboarded by an intern rather than a counterparty to be governed.

Each of these is cheap to avoid in week eight and expensive to unwind in week two of trading.

Ask which of the venues on your shortlist the provider already holds an approved maker status on, and at what fee tier — a desk starting from the base fee schedule cannot quote as tightly as one on an enhanced tier, whatever its spread promises say. Ask for the names and market caps of two or three tokens it currently supports, and request permission to speak to those teams directly rather than relying on a written testimonial.

Ask how it capitalises the book: does it quote with its own balance sheet, with your loaned inventory, or a mix, and what proportion of quoted depth is genuinely at risk versus posted and cancelled reflexively. Ask what its reporting looks like on a bad day, not a good one — a provider that can only show you clean dashboards from calm markets has not been tested where it matters.

Finally, ask what it will not commit to. A desk that pushes back on a spread target your float cannot support, or declines a mandate where the numbers do not work, is telling you it prices risk honestly rather than simply saying yes to win the deal.

Arranging the market maker is only one of three parallel workstreams; the treasury side is usually the one that slips. Confirm well in advance which wallet or multisig holds the liquidity allocation, who has signing authority, and how transfers to the provider's venue sub-accounts will be authorised and logged. If a multisig requires three signers across time zones, build that lag into your funding timeline rather than discovering it the week before listing.

Decide the stablecoin counterpart early too. If treasury holds mostly the native token or illiquid ecosystem assets, converting enough into stablecoins to fund the bid side can itself take days and move price, so it needs to happen quietly and ahead of the final week rather than as a last-minute scramble that the market can see.

Day one performance matters, but the first thirty days is where a launch mandate is genuinely proven or found wanting. Review the KPI report weekly rather than waiting for a monthly cycle, and compare measured spread and depth against the specification you signed, not against a vague sense that things feel fine. Volatility events in this window — a broader market drawdown, a token unlock, an exchange listing announcement — are the real test of whether the provider's capital and inventory management hold up.

Use this window to decide whether to add a second venue or a second provider. A book that has held its KPIs cleanly through real volatility has earned the case for expansion; one that needed manual intervention or repeated exceptions has not, and that conversation is better had at day thirty than at day one hundred and eighty when the notice period is the only lever left.