Commercial engine
Ecosystem infrastructure is the entry point. Financial products drive expansion.
Steer enters an ecosystem by deploying reusable market infrastructure across chains and execution venues, including integrations, liquidity operations, incentive workflows, and lifecycle automation. A Foundation or Labs team is typically the initial buyer; separate issuer and AMM agreements create downstream revenue.
Once established, the same stack can support additional issuers, managers, treasuries, and distribution partners without being rebuilt. Each new market or financial product adds implementation, recurring, activity-based, performance, management, execution, or licensing revenue.
This creates a land-and-expand: chains and Foundations provide an efficient entry point, while downstream products increase revenue and margins with lower incremental delivery effort.
Steer does not normally build the DEX. It provides the operating layer above it: integrations, Smart Pools and automated liquidity management, issuer onboarding, incentive workflows, and recurring lifecycle automation.
Customers and buying motions
| Customer | Initial need | Expansion |
|---|---|---|
| Chain or Foundation | Market infrastructure and ecosystem growth | Issuer onboarding, incentives, and product expansion |
| DEX or execution venue | Managed liquidity and market operations | Issuer programs and product inventory |
| Asset issuer or protocol | Token launch, treasury deployment, or market growth | Yield and structured products |
| Asset manager or treasury | Controlled onchain execution | Additional strategies and mandates |
| Wallet, exchange, or application | Investable product inventory | Broader distribution and product economics |
The commercial champion varies by customer, typically an ecosystem, treasury, product, investment, or partnerships lead.
Grants may fund the initial deployment, but the underlying purchase is infrastructure for creating and operating sustainable onchain markets and financial products.
One ecosystem relationship opens multiple revenue paths
A chain, venue, or anchor-issuer agreement establishes Steer as reusable market infrastructure. Once deployed, the same stack can support additional issuers, managers, and products through separate commercial agreements. Bundled new-market support lowers the cost and friction of a first deployment.
| Stage | Commercial outcome | Revenue impact |
|---|---|---|
| Ecosystem agreement | Steer is selected as operating infrastructure | Platform, integration, or implementation revenue |
| Infrastructure deployment | Venues, automation, and monitoring go live | Enables additional markets and products |
| Downstream launch | An issuer or manager launches through Steer | Deployment, service, management, or licensing revenue |
| Live operation | Steer operates capital and lifecycle actions | Recurring, activity-based, execution, or performance revenue |
| Repeat deployment | More products launch on the existing stack | Expansion revenue with lower delivery cost |
From market infrastructure to financial products
Steer does not need to replace its existing liquidity and market-infrastructure business to expand into structured financial products.
The existing chain, venue, automation, and issuer footprint provides the execution and distribution base from which additional products can be launched.
| Market-infrastructure motion | Product-expansion motion |
|---|---|
| Chain or venue integration | Product origination and issuance |
| DEX or AMM operating support | Policy-controlled product operation |
| Smart Pools and managed liquidity | Yield, protection, and structured exposure |
| Incentive programs | Funded product distribution |
| Issuer market launches | Treasury and managed-account products |
| Monthly service retainers | Management, execution, and licensing economics |
| Performance-linked liquidity fees | Product-level activity and performance fees |
The same integrations, automation, monitoring, and operating workflows can therefore support both the current market-infrastructure business and the emerging structured-product business.
The relationship creates two expansion loops
Capital activation
Ecosystem incentives, issuer capital, and treasury allocations are directed into operated market structures designed to achieve defined liquidity, yield, or market-health outcomes.
Steer provides the deposit, execution, and operating layer rather than distributing incentives without a defined market objective.
Ecosystem expansion
A chain, venue, or anchor-issuer relationship creates access to additional issuers, protocols, managers, and distribution partners.
These introductions can convert into separate deployment, operating, product-management, or distribution agreements.
Chains can continue using their preferred incentive-distribution systems. Steer sits beneath or alongside those systems as the operating layer that directs capital into defined market structures and manages the resulting positions.
Technical records for supported incentive integrations are available through Product & technical diligence.
Why the operating layer is necessary
A DEX can accept liquidity, but it does not manage an issuer’s positions or maintain a target market structure around the clock. Asset issuers rarely have the time or specialist capability to do so across volatile markets. Steer Smart Pools provide the algorithmic, 24/7 operating layer between issuer capital and the venue.
The same distinction matters for incentives. A chain is usually paying to create depth, improve market health, or drive a defined user action. By making managed vaults the deposit layer, Steer can direct participants toward specific liquidity structures and operate those positions after deposit. In those programs, Steer is not simply another rewards interface; it is the infrastructure that turns incentive spend into an operated market.
Revenue architecture
Steer monetizes multiple stages of the market and product lifecycle.
| Revenue layer | Commercial basis | Revenue character | Status |
|---|---|---|---|
| Ecosystem infrastructure agreement | Annual contracted fee | Recurring | Live |
| Venue integration and support | Implementation or annual support fee | Implementation and recurring | Live |
| Market or vault deployment | Per-deployment fee | Implementation | Live |
| Ongoing market operations | Monthly or annual operating retainer | Recurring | Live |
| Incentive administration | Percentage of incentives distributed | Activity-linked | Contract-dependent |
| Performance participation | Percentage of defined strategy performance | Variable | Contract-dependent |
| Product origination | Fee per financial-product launch | Implementation | Emerging |
| Product management and policy | AUM, account, or product-level fee | Recurring | Emerging |
| Execution infrastructure | Transaction or activity-based fee | Variable | Emerging |
| Embedded distribution | Revenue share or licensing fee | Recurring and variable | Emerging |
The current infrastructure business generates integration, deployment, operating, incentive, and performance-linked revenue. The structured-product expansion introduces additional origination, management, execution, policy, and distribution economics.
Representative current terms
The March 2026 commercial schedule provides representative terms for current market-infrastructure engagements. Actual economics vary by chain, venue, issuer, scope, capital level, and partner agreement.
| Revenue layer | Customer | Representative term |
|---|---|---|
| Chain or ecosystem program | Foundation or Labs company | $50K–$300K per year, scope and milestone dependent |
| AMM integration and support | Chain, DEX, or AMM | $12K–$24K per year |
| Recurring service retainer | Issuer or protocol | $1K–$2.5K per month |
| Custom vault or configuration | Issuer, AMM, or program | $1K–$2K per deployment |
| Performance participation | Vault or strategy program | 15% of defined performance |
| Incentive distribution | Chain, DEX, or issuer | 1%–3% of incentives distributed |
| Rewards integration | Chain, DEX, or issuer | $10K–$20K per implementation |
Representative terms are not intended to imply that every agreement contains every revenue layer.
Contract-level pricing, invoicing, collections, renewal terms, and revenue classification are available through Commercial & financial documents.
Why the model scales
The first deployment establishes the core integrations, security controls, automation, and operating workflows. Future products reuse this infrastructure instead of rebuilding it.
| First deployment | Repeat deployment |
|---|---|
| Higher integration and setup effort | Reuses adapters, templates, policies, and workflows |
| Longer launch cycle | Faster product launch |
| Higher delivery cost | Lower incremental cost |
| Establishes the ecosystem relationship | Adds recurring and expansion revenue |
As more products launch on the same stack, Steer improves delivery speed, contribution margin, and revenue per ecosystem.
Evidence and conversion
Steer’s operating footprint spans 45 active in-scope chains and 57 DEX or AMM integrations. Company program history includes more than 30 chain onboarding, day-one, and growth initiatives. Each active ecosystem can produce recurring market work and qualified downstream relationships; the footprint is not merely a compatibility count.
The commercial model should be measured through six conversion points:
- active and renewing chain agreements;
- qualified issuer and AMM introductions per chain;
- conversion from bundled support into a separate downstream contract;
- time from chain integration to the first funded market;
- capital and incentives routed through Steer-managed positions; and
- total recurring, performance, and expansion revenue per chain ecosystem.