Segmenting Prospective Clients by Investment Profile

Welcome. This begins the Institutional Discovery and Solution Design module: the part of the course that turns product knowledge into a disciplined institutional-sales process.

Before discussing any particular Exponent deployment, you need a way to distinguish genuinely different prospects. “Asset manager,” “treasury,” and “family office” are useful labels, but they are not segments by themselves. A treasury holding long-duration SOL and an operating company treasury that must make payroll in stablecoins may share a label while having incompatible needs. The relevant unit of analysis is the specific portfolio sleeve and mandate under discussion.

This lesson develops a five-axis segmentation model for prospective Exponent clients: mandate, portfolio composition, return target, liquidity horizon, and operational sophistication. The purpose is not to make a recommendation yet. It is to form a defensible hypothesis about what the client is trying to accomplish, whether an on-chain yield-market conversation is relevant, and what must be validated next.

---

Segment the mandate, not the logo

An institution can run several portfolios with distinct objectives, risk budgets, liquidity rules, and decision-makers. A single firm may simultaneously be:

• a long-only digital-asset allocator,
• a market-neutral hedge-fund manager,
• an operator of a corporate treasury,
• and a provider of liquidity to other market participants.

Each activity needs separate segmentation. The central opening question is therefore:

What is the mandate of the capital that could be deployed?

An Investment Policy Statement is often the most efficient source of evidence. It turns broad intentions into practical constraints: eligible assets, risk limits, liquidity needs, authority, benchmarks, and reporting requirements.

A useful mandate taxonomy for initial Exponent outreach is:

Mandate type	Primary objective	What matters most in segmentation
Income or reserve allocation	Preserve capital while earning a defined return	Asset denomination, maturity matching, liquidity certainty, governance
Yield enhancement	Improve return on existing crypto holdings	Current yield exposure, return hurdle, tolerance for variable yield
Relative-value or macro trading	Express a view on rates, yield dispersion, or basis	Rate-view process, turnover, execution and risk infrastructure
Market making	Earn spreads and provide two-sided liquidity	Inventory capacity, hedging ability, latency, active risk management
Strategic digital-asset allocation	Build long-term exposure to a blockchain ecosystem	Solana allocation policy, custody, size limits, investment-committee process
Family-office or bespoke capital	Combine capital preservation, growth, and access to opportunities	Account-specific goals, concentration, bespoke reporting, governance maturity

These are starting hypotheses, not final client categories. A digital-asset fund may have an income sleeve and a trading sleeve; one could plausibly use a fixed-maturity yield product while the other has a very different reason to engage with rate markets.

---

The five segmentation axes

The five axes work together. A high return target alone does not imply a good prospect; it may instead reveal an unsuitable expectation. Likewise, a sophisticated investor may be operationally unable to transact on Solana through its current custody and approval framework.

1. Mandate: the job the capital must perform

The mandate states the required outcome and the constraints around it. Capture it in plain language:

• Is the priority income, capital preservation, total return, hedging, market making, or yield speculation?
• Is performance assessed against cash, staking yield, a token benchmark, a fixed-income benchmark, or an internal hurdle?
• Does the mandate allow spot crypto assets, liquid-staking tokens, derivatives, DeFi protocols, or only approved counterparties?
• Who owns the decision: portfolio manager, treasury committee, CIO, risk committee, or founder?

For an Exponent conversation, one distinction is especially important: does the client need to lock a return on an existing yield-bearing asset, or does it seek to outperform a market-implied future yield? These are materially different motivations, even where both parties hold the same underlying asset.

2. Portfolio composition: what the client already owns and owes

Portfolio composition identifies the economic exposures that an Exponent yield market could complement, hedge, or complicate. Do not stop at total assets under management. Focus on the deployable sleeve.

Relevant evidence includes:

• Holdings by denomination: SOL, liquid staking tokens, stablecoins, tokenized real-world assets, and other yield-bearing assets.
• Existing yield sources: native staking, liquid staking, lending, liquidity provision, credit, or incentive farming.
• Liabilities and obligations: redemptions, operating expenses, collateral calls, or client withdrawal commitments.
• Concentration: one liquid staking provider, one stablecoin issuer, one chain, or one liquidity venue.
• Whether the portfolio reports in USD, SOL, or another base currency.

This last point prevents a common communication error. A principal token may embed a fixed return in units of its underlying asset at maturity, but that does not by itself eliminate the USD price risk of the underlying asset. A client whose liability is denominated in dollars needs that distinction made explicit.

3. Return target: both level and shape

A return target has two components.

1. Level: What return is required or expected?
2. Shape: Must the return be known in advance, can it vary with market conditions, or is it explicitly intended to be directional?

For example, two clients might each mention an annual target of 8%, but their profiles may be opposite:

• A treasury may want a predictable, maturity-matched return and regard any material drawdown as unacceptable.
• A crypto fund may view 8% as a minimum hurdle for taking variable yield exposure and may tolerate marked-to-market volatility.

Treat an advertised or requested return as an input to investigate, not as permission to pursue it. The CFA Institute framework is useful here: risk need, risk-taking ability, and tolerance for loss are related but distinct. An ambitious required return cannot override short liquidity needs or limited loss capacity.

4. Liquidity horizon: distinguish maturity from exitability

Liquidity horizon is not merely “how long the client intends to invest.” It has at least three practical layers:

Liquidity question	What it reveals
Economic horizon	How long can capital remain exposed before it is needed for a liability or redeployment?
Execution horizon	Does the client require immediate entry and exit, or can it use limit orders and wait for a desired rate?
Stress horizon	Could the client hold through spread widening or thin secondary liquidity without forced selling?

A maturity-aligned allocator may be content to hold an instrument until settlement. A market maker needs continuous ability to manage inventory. A fund with weekly redemptions may have a nominally long investment thesis but a practically short liquidity horizon.

This distinction is central to fixed-maturity markets. A position that has an attractive payoff when held to maturity may still be unsuitable for a client that could need to sell early into limited liquidity.

5. Operational sophistication: ability to execute and govern the position

Operational sophistication is often mistaken for investment sophistication. They are different.

A CIO may understand yield curves and DeFi risk extremely well while the firm cannot yet custody Solana assets, whitelist protocol interactions, obtain internal approvals, or reconcile on-chain positions into fund accounting. Conversely, an experienced market maker may have excellent execution infrastructure but no mandate for long-term yield allocation.

Assess operational sophistication through evidence, not self-description:

Operating level	Observable evidence	Segmentation implication
Exploratory	Research interest, but no approved Solana custody or DeFi policy	Education and feasibility assessment precede deployment discussion
Execution-capable	Wallets, authorized signers, basic transaction controls, crypto operations staff	Can assess a constrained pilot if mandate permits
Institutionally deployable	Defined custody model, approval matrix, compliance review, reporting and reconciliation	Can evaluate a governed allocation process
Market-infrastructure capable	Automated execution, risk limits, monitoring, inventory management, hedging procedures	Relevant for active rate trading or liquidity provision

The right question is not “Are you institutional?” It is: “Can this particular entity approve, execute, monitor, account for, and exit this specific position within its controls?”

The custody video below is useful as a discussion prompt because it illustrates the questions institutions commonly ask about safekeeping and legal structure. Its five-point standard is the speaker’s personal framework, not a universal legal definition of qualified custody. Requirements differ by jurisdiction, legal entity, asset, and custody arrangement; verify claims through the custodian’s documentation, counsel, and the client’s own control requirements.

---

Relate the segments to Exponent’s yield-market conversation

Exponent’s yield markets split a yield-bearing underlying asset into principal and yield exposure for a fixed maturity. At a high level:

• Principal-token exposure is relevant to someone considering a fixed rate through maturity.
• Yield-token exposure is relevant to someone assessing whether future realized yield and incentives will exceed the market-implied rate paid at entry.
• Immediate versus limit-order execution matters most when execution certainty, rate control, and position size are part of the mandate.

A client segment should produce a reason to investigate, not a premature product recommendation. The following examples show the distinction:

Prospect archetype	Likely segmentation profile	Reason to investigate Exponent	Critical unknowns
Crypto treasury with SOL or liquid-staking-token reserves	Capital preservation or income mandate; low tolerance for forced sales; known cash needs	May value a known maturity and predictable underlying-denominated payoff	USD liabilities, liquidity buffer, asset eligibility, approval authority
Multi-strategy crypto fund	Existing yield positions; return target linked to opportunity set; moderate liquidity horizon; strong operations	May trade differences between realized yield expectations and implied rates	Position limits, risk budget, valuation treatment, redemption terms
Market maker	Inventory-based portfolio; spread and fee target; short execution horizon; advanced operations	May provide or take rate liquidity as part of market-making activity	Hedging process, inventory limits, rebalancing costs, capacity
Traditional allocator exploring Solana	Strategic or pilot allocation; high governance burden; long research horizon; operational maturity may be low	May have interest in fixed-maturity on-chain yield but need an institutional feasibility path first	Custody support, legal review, approved assets, reporting and control design
Family office with a digital-asset sleeve	Bespoke objectives; variable sophistication; potentially concentrated holdings	May seek clarity about fixed versus variable yield on existing assets	Decision rights, drawdown tolerance, tax/accounting treatment, exit needs

Notice that “family office” and “asset manager” appear in multiple forms. The segmentation dimensions, not the firm type, determine the quality of the opportunity.

---

A practical client-profile record

For early pipeline work, maintain one concise profile for each entity–sleeve–mandate combination:

1. Entity and decision unit: legal entity, strategy, decision-makers, investment committee.
2. Mandate: desired outcome, constraints, benchmark, allowed instruments.
3. Portfolio composition: current relevant assets, yield sources, liabilities, concentrations, reporting currency.
4. Return requirement: target level, whether fixed or variable, and consequence of underperformance.
5. Liquidity profile: planned holding period, redemption cycle, potential cash calls, acceptable early-exit risk.
6. Operational readiness: custody, wallet authority, transaction approvals, compliance, accounting, monitoring.
7. Evidence and confidence: what has been verified, what is client-stated, and what remains unknown.

Mark each field as verified, reported, or unconfirmed. This prevents a common sales error: treating a promising verbal statement such as “we want on-chain yield” as evidence that capital is deployable.

The Exponent dashboard can help illustrate the visible market experience, including maturities, implied yields, and available markets. But a polished dashboard is not evidence of institutional readiness. Readiness depends on the client’s mandate and operating environment as much as the protocol interface.

---

Segmentation red flags

A prospect may be strategically interesting while not being ready for an active opportunity. Escalate or slow the process when you observe:

• a stated return target without clarity on denomination, maturity, or downside tolerance;
• a liquidity need that conflicts with the proposed holding period;
• no approved custody or transaction-authority path for Solana;
• no identified owner for smart-contract, protocol, or operational risk;
• a mandate that prohibits DeFi, derivatives, or the relevant underlying asset;
• a client seeking “fixed yield” but assuming this means no underlying-asset, protocol, or early-exit risk;
• a requested position size that is disconnected from available liquidity and an exit plan.

These are not necessarily disqualifiers. They identify the due-diligence work, education, or internal coordination required before discussing a deployment design.

---

Key takeaways

Effective institutional segmentation for Exponent works at the portfolio-sleeve level, not the company-label level. The five essential dimensions are:

• Mandate: what the capital must achieve and what it is permitted to do.
• Portfolio composition: relevant holdings, liabilities, yield sources, and denomination.
• Return target: both the required level and whether returns must be predictable or may be variable.
• Liquidity horizon: ability to hold to maturity, execute patiently, and withstand a stressed exit.
• Operational sophistication: demonstrated capacity to custody, approve, execute, monitor, and report the position.

The result is a structured hypothesis: which conversations are relevant, what evidence is missing, and where the opportunity may be blocked. In the next lesson, you will turn these five axes into a focused discovery-question set that uncovers risk limits, liquidity needs, custody arrangements, and the client’s actual decision process.