Comparing token market making firms: start with mandate fit, not the ranking.

A firm can't be assessed against a mandate the issuer hasn't defined. Start any comparison of token market making firms by specifying the work required: target venues, token stage, relevant markets, available inventory, and expected operating scope. A firm suited to a newly listed token on a limited set of venues may not fit a project with established trading and broader venue requirements.

A token market-making mandate is a written specification of the venues, inventory, quoting activity, controls, and reporting expected from a market maker. It defines the engagement — it is not a promise of price, trading volume, or continuous liquidity. Deeper order books and narrower spreads may be objectives, but market conditions and available counterparties affect results.

Keep execution separate from other outcomes. Quoting activity doesn't determine whether an exchange lists a token, support its price, or generate organic demand. Listing decisions belong to venues; demand depends on market participants. OTC activity involves privately negotiated transactions, and investment services are a different mandate entirely — neither should be assumed to form part of liquidity provision.

Assess liquidity using defined measures. Spread is the difference between the best available buy and sell prices. Depth describes the quantity available at specified price levels. Slippage captures how an executed trade price differs from the expected price. These indicators help frame performance, but none alone proves that a market is consistently executable at the size or timing the project needs.

Prepare a concise mandate brief before reviewing firms: the project's current stage, intended venues, token distribution, and operational readiness; how inventory will be sourced and controlled; who can approve transfers or changes; and what reporting the project needs. Have each firm respond to the same brief, so capabilities and fit are compared on consistent terms rather than broad service labels.

Once the mandate is defined, compare proposals against identical categories. A firm's headline label reveals little about who controls execution, where inventory sits, or what the issuer can verify. Compare: what activity is included and expressly excluded; whether execution is delegated to a managed desk or operated through software; who controls the assets and what transfer and approval procedures apply; whether payment is fixed, linked to token inventory or options, or tied to performance; which venues are covered and what “coverage” means in practice; and what execution data, exceptions, and inventory information will be delivered, at what cadence.

A managed desk takes on delegated execution within an agreed scope. The issuer still sets governance, approves inventory arrangements, and reviews performance, but the provider handles day-to-day quoting and operational monitoring. With self-service software, the issuer configures and operates the tool, so responsibility for strategy, settings, surveillance, and interpreting results stays in-house. These are different engagement categories — compare them by allocation of responsibility, not by product label.

A retainer is a fixed payment for defined services; it makes the commercial obligation easier to identify, but the contract still needs a precise scope and reporting standard. Token-linked arrangements call for additional analysis. Under a token loan, tokens are made available for use under agreed terms; a call option may give the counterparty a right to purchase tokens at a specified strike price. Neither label establishes the actual economics.

Examine repayment obligations, option exercise conditions, strike, allocation, and treatment of unused inventory in the governing documents. A token-linked structure may create exposure to token value that a fixed retainer doesn't, and performance-linked compensation raises questions about how “performance” is calculated. Don't assume any model aligns incentives by default — assess the obligations, measurement method, and potential conflicts together.

A firm name is a research lead, not evidence of fit. Public profiles can describe a provider's stated services and operating model; they don't, by themselves, establish current venue access, performance under a particular mandate, or the protections in a proposed contract. A useful comparison separates what a dated source says from what the issuer concludes.

Names such as Wintermute, GSR, Flowdesk, Keyrock, Kairon Labs, Empirica, DWF Labs and Auros appear regularly in comparison coverage — that inclusion alone doesn't establish mandate, venue coverage, or current service terms. Review each firm's current public materials individually: stated operating model, relevant project-stage evidence, venue claims, and disclosed conflict controls, without assuming the firms are equivalent. Self-service tools such as OctoBot are a different category again — a software-model candidate, not a managed desk.

Public materials can establish what a firm says it does, where it says it operates, and how it describes its model. They can't independently confirm client outcomes, execution quality, or the scope offered to a particular issuer. Label claims as firm-stated unless corroborated. If a source is missing or dated, mark the field unavailable for comparison — that's a limit in the evidence, not proof of a firm's weakness.

Match stated venue coverage against the project's actual listing and liquidity priorities. Separate named venues from broad claims such as “global coverage,” and distinguish operating history from evidence relevant to the issuer's stage. Keep the record auditable: for each entry, preserve the source, the date, the exact claim, and any qualification, and classify conclusions as verified public description, issuer interpretation, or unresolved. That gives decision-makers a defensible basis for shortlisting rather than a borrowed ranking.

A signed mandate is only useful if the issuer can supervise it. Treat contract review and reporting design as one control framework: each obligation should have a corresponding record, metric, or escalation route. This is where headline proposals become operational commitments.

Set the pre-signature sequence in writing. Mandate: covered venues, quoting parameters, permitted activity, exclusions, and who can authorize changes. Inventory: asset ownership, source, custody arrangements, permitted use, and any loan or option terms. Controls: approval rights, access permissions, conflict disclosures, and procedures for incidents or exceptions. Reporting: KPI definitions, data access, venue-level detail, and delivery cadence. Escalation: how missed parameters, operational incidents, and proposed mandate changes are reported, reviewed, and resolved.

KPIs measure execution quality, not token-price performance. Define the spread and order-book depth to be observed, how uptime is calculated, which venues count toward coverage, and the reporting cadence. Specify measurement windows and how exceptions, such as venue interruptions, are treated so the data can be interpreted consistently. Guaranteed token prices or trading volumes shouldn't be treated as standard deliverables.

Read inventory provisions alongside compensation terms: ownership, loan repayment obligations, option exercise conditions, allocation, and the consequences of termination. Review disclosure of conflicts, venue relationships, subcontracting rights, and information-sharing obligations. Have qualified counsel interpret contract language — this article is not legal advice.

Require recurring reports that connect activity to agreed KPIs: venue-level activity, spread and depth observations, uptime, coverage, inventory movements, exceptions, and access to supporting data. And make escalation usable — name the responsible contacts, required notice, and review path when a parameter is missed. A reporting structure without an escalation path records problems but doesn't govern them.

A comparison is useful only if it leads to a mandate the project can govern. Xavion Capital matches token issuers and trading venues with vetted market makers based on project stage and listing venues. Rather than relying on a generic ranking, we connect the issuer's requirements with a suitable market-maker profile, then help define the engagement.

Matching starts with the issuer's specific context rather than a provider's general market profile. Project stage and listing venues inform which market makers are relevant. The resulting scope documents venue objectives, inventory arrangements, operating expectations, reporting, and approval responsibilities — selection criteria and performance expectations in writing before engagement, so both sides have a reference point for supervision.

Before an engagement begins, prepare a concise brief that turns the project's needs into reviewable terms: summarize the mandate (stage, target venues, liquidity priorities, inventory context, intended scope), set reporting requirements, assign oversight (governance responsibilities, approval rights, escalation routes, review cadence), and record the basis for selection. These steps make matching accountable and give the issuer a clear standard for determining whether the mandate remains appropriate as needs change.

The next decision isn't which firm has the strongest profile — it's whether the proposed arrangement can be governed clearly as the project evolves. Market conditions remain outside any provider's control; disciplined selection and oversight give your team a stronger basis for managing the work.