Enterprise Suite — First-Build Landing Page Specs

Seven pages on a solution × audience matrix

Build-ready specs grounded in two inputs: the quantitative search-demand brief and the qualitative read from the enterprise sales sync. Three solution pages carry the searchable, inbound load; four persona pages — two Web3, two TradFi — serve the highly-targeted ABM motion. Section 1 walks the logic, Section 2 maps the build, and the rest are the specs.

Jun 8 2026 · built from the Sales Intel reconciliation + Quant brief
TL;DRThe logicBuild mapSolution pagesPersona pages

TL;DR — the seven pages

  • Two axes, two motions.Solution pages are named by what we sell and built for search (inbound); persona pages are named by who we sell to and built for the ABM motion (targeted, relationship-led). Together they form a clean solution × audience matrix.
  • Three by solution — the searchable load.Asset Tokenization (~46,600 demand), Tokenized Deposits ("deposit vs. stablecoin"), Institutional Custody (high-intent, low-volume).
  • Four by persona — the ABM load, balanced two Web3 / two TradFi.Web3: Qualified Custodians, Exchanges. TradFi: Banks, Asset & Wealth Management. These are the ICPs the sales sync named on the front line.
  • The matrix avoids cannibalization by design.Solution pages own the keyword-led terms (e.g. "private credit"); persona pages are framed audience-first ("tokenization for asset managers") and serve tailored messaging for named accounts. No two pages chase the same head term.
  • Each spec carries both signals.Search data sets the keywords, the page job, and the build order; the sales sync sets the persona, the objections, the proof points, and the tone.

01 — The logic behind the build

Two datasets drive the architecture, and they answer different questions. The quant brief tells us where buyers are searching — the addressable inbound demand. The sales sync tells us who actually buys, what they ask, and through which channel. Rather than force them onto one ranking, we give each its own axis: solution pages capture the search, persona pages capture the accounts.

From the quant brief

Search demand → solution pages

Demand concentrates on the tokenization side (~46,600, led by private credit at 22,000) and runs thin but high-intent on custody (CPCs $3.50–5.00). That maps to pages named by what we sell — the terms buyers type when self-educating.

These are the inbound engine: rank for the category and asset-class terms, convert to gated content.

From the sales sync

Named ICPs → persona pages

The front line works specific industries: on the Web3 side, qualified custodians and exchanges (won through partnership and conferences); on the TradFiside, banks and asset & wealth managers (the segments sales sees most).

These are the ABM motion: pages named by who we sell to, tailored to the buyer’s language and used as destinations for outbound and events.

Why this shape
  1. 1Solution pages do the searching. They earn organic traffic and white-paper downloads against the demand the quant brief sized.
  2. 2Persona pages do the targeting. Low or no search, but they speak directly to a named industry for the ABM list — the accounts sales is already working.
  3. 3Two Web3, two TradFi keeps it balanced. It mirrors how the market — and the sales pipeline — actually splits, and gives outbound a tailored page for each of the four priority industries.
  4. 4Audience-first framing prevents overlap. Where a persona page touches a solution page’s topic (custodians/custody, asset managers/tokenization), the persona page targets audience terms and tailored messaging while the solution page keeps the keyword-led terms.
▸
One shared thread from the sales sync: most TradFi evaluators are not web3-fluent— they’re technologists or strategists tasked with learning the space. The TradFi pages assume a smart but non-native reader (define terms, lead with the business outcome). The two Web3 pages can go a layer deeper technically. The common job title across segments is some variant of "digital assets."

02 — The build map

Seven pages on two axes: what we sell (solution, search-led) and who we sell to (persona, ABM-led). The persona set is balanced — two Web3, two TradFi.

Three by solution — search-led Inbound
  • Asset TokenizationAMP
    The inbound engine. ~46,600 segment demand; ranks for the asset-class terms, converts to white-paper downloads. Spec §03.
  • Tokenized DepositsAMP + Custody
    Built on "tokenized deposit vs. stablecoin," the recurring bank question. ~6,350 demand. Spec §03.
  • Institutional CustodyCustody
    High-intent, low-volume (~8,810). The capability page that converts sales-led and search traffic. Spec §03.
Two Web3 — ABM
  • Qualified CustodiansCustody ABM
    Custodian-facing cut of custody — verifiable infrastructure custodians build their offering on. Christy’s #1 ICP (Hex Trust). Spec §04.
  • ExchangesLiquid + Custody ABM
    Liquid integration + custody cross-sell. Pure partnership play, no search surface. Spec §04.
Two TradFi — inbound + ABM
  • BanksAMP + Custody ABM
    Industry landing for large banks. Named-account ABM plus inbound via deposits. Spec §04.
  • Asset & Wealth ManagementAMP + Custody Inbound
    The segment sales sees most. Audience cut of the tokenization story; asset vs. wealth split. Spec §04.
▸
Read as a matrix: Asset Tokenization (solution) and Asset & Wealth Management (persona) cover the same product from two angles — keyword-led vs. audience-led; likewise Institutional Custody (solution) and Qualified Custodians(persona). That’s intentional coverage, not duplication — each targets different terms and a different reader.

03 — Solution page specs

Three by solution — search-led
S1Asset TokenizationAMPInbound · search + white paper

The inbound engine. Highest search demand of any segment, and the buyer asset managers, wealth managers, and bank tokenization teams all converge on. The page’s job is to rank for the asset-class terms and convert researchers into gated-content leads.

Persona
Head of Digital Assets / VP Digital Asset Solutions at asset managers, wealth managers, and bank tokenization teams; tokenization project leads. Smart, mandate-driven, often not web3-native.
Search demand
Segment ~46,600. The volume sits in the asset classes, not in "tokenization" itself — the page must target the asset terms directly.
What they care about
From the sales sync: the comfortable entry point is the tokenized money market fund (liquid, low-risk). From there, private credit, real estate, alternatives, equities. Real-estate interest is specifically about liquidity and exit — fractional ownership and a secondary market on an otherwise locked-up asset.
Page job
Rank for asset-class terms → convert to a white-paper download (email capture) → nurture sequence. The lead magnet of the build.
Hero angle
Issue and manage tokenized assets on Bitcoin's most proven layer.Private credit, funds, real estate, and equities — issued with built-in transfer rules and confidential amounts on Liquid, via AMP.
Page outline
  1. 1Hero + primary CTA (download) and secondary (talk to us).
  2. 2Use-case grid — one tile per asset class (MMF, private credit, real estate, equities, alternatives), led by the MMF tile (the comfort entry).
  3. 3How AMP works — issuance API, transfer restrictions in the asset, Confidential Transactions — business-outcome framed.
  4. 4Proof / live issuances — real assets already on Liquid.
  5. 5Why Bitcoin/Liquid — settlement assurance, no new trust assumptions.
  6. 6White-paper CTA band.
Proof points
BMN2MicroStrategy CMSTRMetaplanet CMTPLNexBridge USTBLUSDt on LiquidConfidential Transactions
Target keywords
private credit22,000real world assets4,300tokenized stocks3,200real estate tokenization2,500tokenized fundsKD6security token offeringsKD11
CTA & magnet
Primary: “Download: Tokenizing real-world assets on Bitcoin”Secondary: “Talk to our issuance team” · inbound form, never buried.
Tone
Educational, business-first, asset-class fluent. Assume the reader knows finance, not crypto. Define every chain term inline.
S2Tokenized DepositsAMP + CustodyInbound · content-led

The sales-validated page. Modest search volume, but it answers the single most recurring question the front line hears from banks — tokenized deposit vs. stablecoin — with a sharp, high-value buyer attached.

Persona
Digital asset / innovation leads at large banks, plus operations and technology owners (CITO / CIO-adjacent) tasked with evaluating. Conservative, compliance-aware, settlement-minded.
Search demand
Segment ~6,350, plus the high-intent informational query “tokenized deposit vs. stablecoin” the sales sync flags as a top conference question.
What they care about
First project is usually a tokenized money market fund (low-risk comfort entry). The bigger pull is the tokenized deposit — plainly, 24/7/365 mobility across time zones. The live decision they’re stuck on is deposit vs. stablecoin.
Page job
Win the "deposit vs. stablecoin" search → deliver the comparison as a gated white paper → nurture toward a meeting.
Hero angle
Move deposits 24/7, across time zones, with bank-grade settlement.Tokenized deposits and funds issued on Liquid — with the settlement assurance and confidentiality a bank requires.
Page outline
  1. 1Hero + the 24/7 mobility promise.
  2. 2Deposit vs. stablecoin — a clean comparison block; the SEO and credibility hook. Mirror it in the white paper.
  3. 3Tokenized MMF as the low-risk first project.
  4. 4Settlement & confidentiality — atomic settlement, Confidential Transactions.
  5. 5Compliance posture — transfer rules in the asset; gesture to regional regulatory explainers.
  6. 6White-paper CTA band.
Proof points
AMP issuance on Liquidatomic settlement — KD 0Confidential TransactionsNexBridge USTBL
Target keywords
tokenized deposit vs stablecoininfotokenized depositstokenized money market fundKD5atomic settlementKD0
CTA & magnet
Primary: “Download: Tokenized deposits vs. stablecoins — a banker’s guide”Secondary: “Discuss a pilot” · inbound form.
Tone
Measured, compliance-aware, settlement-literate. Lead with operational outcomes, not crypto upside.
S3Institutional CustodyCustodyInbound · capability page

The capability page for the custody product. Low search volume, so it’s built to convert — search and sales-led traffic alike — on credibility and verifiable assurances. (The named-account custodian pitch lives on the Qualified Custodians persona page.)

Persona
Regulated institutions needing custody infrastructure— treasury, security, and digital-asset operations leads. Evaluating "how do we hold this safely and provably."
Search demand
Segment ~8,810; head term "qualified custodian" only ~60 GL, CPC $3.50–5.00. High intent, tiny audience. Search is a credibility check, not a traffic source.
What they care about
Verifiable safety: no rehypothecation, provable reserves, no new trust assumptions. The differentiator is verify, don’t trust.
Page job
Convert high-intent traffic to a meeting via an unmissable inbound form. The sales sync flagged we lose opportunities because buyers can’t find a way to reach us.
Hero angle
Custody you can verify, not just trust.Multisig + HSM, segregated accounts, on-chain proof of reserves, and no rehypothecation — built on open primitives.
Page outline
  1. 1Hero + prominent contact form.
  2. 2Assurance pillars — no rehypothecation, proof of reserves, multisig + HSM, segregated accounts.
  3. 3Verify, don’t trust — the technical differentiation.
  4. 4Who it’s for — regulated institutions, treasuries, custodians.
  5. 5Contact band — repeated form, calendar link.
Proof points
no rehypothecationon-chain proof of reservesmultisig + HSMsegregated accountsopen primitives
Target keywords
qualified custodian60 / KD2digital asset custody1,100crypto asset custody250proof of reservesrehypothecation3,600
CTA & magnet
Primary: “Talk to our custody team” — prominent inbound form.Secondary: “See how proof of reserves works” · ungated explainer.
Tone
Credible, precise, technically confident. A proof page for an informed buyer.

04 — Persona page specs

Two Web3 — ABM
A1Qualified CustodiansCustodyABM · infrastructure-led

The custodian-facing cut of custody. Where the Institutional Custody solution page sells the capability to search, this speaks directly to custodian businesses choosing the infrastructure to build their offering on — the ICP the sales sync put at the top of the DeFi-side pipeline.

Persona
Qualified / digital-asset custodians (e.g. Hex Trust). Decision-makers are C-suite (CEO/CFO/CCO) and Heads of Digital Assets; partnerships and product open the door. Usually web3-fluent — this page can go a layer deeper technically.
Channel
ABM — conference- and outreach-fed. Near-zero net-new search; this is a destination, not a magnet.
What they care about
Custodians are licensed to hold client assets; what they need is secure, verifiable infrastructure to do it — without building it in-house or trusting a black box. The page must make Blockstream the credible, open, provable choice to build on.
Page job
Convert sales-led / conference traffic to a custody conversation via a prominent inbound form.
Hero angle
Run a licensed custody business on proven Bitcoin infrastructure.Offer your clients custody with provable security — no rehypothecation, on-chain proof of reserves, and open-source infrastructure with no lock-in.
Page outline
  1. 1Hero + “talk to us” form.
  2. 2The infrastructure — what you build on, and why it beats building in-house or a black-box vendor.
  3. 3Assurance pillars — no rehypothecation, proof of reserves, multisig + HSM, segregated accounts.
  4. 4Verify, don’t trust — deeper technical depth allowed here.
  5. 5Why build on Blockstream — open primitives, vendor independence.
  6. 6Contact band.
Proof points
no rehypothecationon-chain proof of reservesmultisig + HSMsegregated accountsopen primitives
Distinct from
Institutional Custody (solution): the capability/SEO page for institutions holding assets. This page: the infrastructure pitch for custodian businesses building their offering on our tech. Different reader, different ask.
CTA
Primary: “Talk to our custody team” — inbound form.Secondary: technical overview / proof-of-reserves explainer.
Tone
Credible, technical, builder-to-builder. Assumes a fluent reader.
A2ExchangesLiquid + CustodyABM · partnership

The pure partnership play. No meaningful search surface — this is the destination for the coordinated exchange outreach, framed around what an exchange gains by integrating Liquid and adopting the custody stack.

Persona
Exchange partnerships / BD, product, and C-suite at digital-asset exchanges. Web3-native; evaluating new listings, settlement rails, and infrastructure.
Channel
ABM / partnership. Run alongside the broader exchange motion; the page is the credible landing spot for those conversations.
What they care about
From the sales sync, two hooks: (1) Liquid integration — build products on the sidechain, expand what they can list and settle, grow TVL; (2) custody technology as a cross-sell. The page sells the integration value and a clear path to partner.
Page job
Convert outreach into a partnership conversation; show concrete integration value, route to the partnerships team.
Hero angle
Expand what your exchange can list, settle, and secure — on Liquid.Integrate Bitcoin's most proven asset layer, and custody it with infrastructure you can verify.
Page outline
  1. 1Hero + partnerships CTA.
  2. 2Why integrate Liquid — new assets to list, faster settlement, Confidential Transactions.
  3. 3Custody technology — the verifiable custody cross-sell.
  4. 4What partners build — concrete integration examples.
  5. 5Contact band — partnerships team.
Proof points
Liquid Networkexisting exchange integrationsAMP issuanceConfidential Transactionsverifiable custody
Handle with care
The sister-company (BSTR) BTC-deployment hook is an internal sales talking point, not public page copy— keep it out of the published page and in the rep’s conversation.
CTA
Primary: “Talk to our partnerships team”Secondary: integration / developer docs.
Tone
Web3-fluent, partnership-oriented, concrete. Speak builder-to-builder.
Two TradFi — inbound + ABM
A3BanksAMP + CustodyABM + inbound

The industry landing page for large banks — the marquee TradFi accounts. Named-account ABM, with some inbound via the deposit terms. Which banks is handled by the ABM list; the page speaks to the industry, not a tier.

Persona
Digital-asset / innovation leads at large banks (e.g. JP Morgan, Morgan Stanley tier — internal targeting note), plus operations and technology owners. Conservative, compliance-first, not web3-native.
Channel
Primarily ABM (named accounts, conferences), with inbound pull from the deposit/MMF terms.
What they care about
From the sales sync: the tokenized MMF as the comfortable first project; tokenized deposits for 24/7 mobility; the deposit-vs-stablecoin decision; and compliance by region (Genius Act, MiCA).
Page job
Tailored industry destination for the ABM list and inbound; gated white paper; nurture toward a pilot conversation.
Hero angle
Digital-asset infrastructure for banks.Tokenized deposits, funds, and settlement — issued on Bitcoin, with the custody and compliance a bank requires.
Page outline
  1. 1Hero + the bank-grade promise.
  2. 2Entry points — tokenized MMF → tokenized deposits, framed as a low-risk progression.
  3. 3Settlement & confidentiality on a network banks can reason about.
  4. 4Compliance posture — transfer rules in-asset; regional regulatory framing.
  5. 5Proof + white-paper CTA + talk to us.
Proof points
AMP issuanceatomic settlementConfidential TransactionsNexBridge USTBLverifiable custody
Distinct from
Tokenized Deposits (solution)owns the keyword-led "deposit vs. stablecoin" search; this page is the industry-framed destination spanning deposits, funds, and custody for the bank ABM list.
CTA & magnet
Primary: “Download: Digital assets for banks — an infrastructure guide”Secondary: “Discuss a pilot.”
Tone
Measured, compliance-aware, institution-grade. Lead with operational and regulatory outcomes.
A4Asset & Wealth ManagementAMP + CustodyInbound + ABM

The segment sales sees most — the audience cut of the tokenization story. Framed buyer-first so it complements rather than competes with the keyword-led Asset Tokenization solution page, and split to address asset managers and wealth managers, who want different things.

Persona
Head of Digital Assets / VP Digital Asset Solutions at asset managers and wealth managers. Per the sales sync, the two diverge: asset managers think issuance / product; wealth managers think client access / distribution. Address both.
Channel
Inbound (audience-framed search) + ABM (tailored destination for the segment). The most searchable of the four persona pages.
What they care about
Tokenized MMF as the entry; then private credit, real estate, alternatives, equities. Wealth side wants client access to these; asset side wants issuance and distribution with compliance built in.
Page job
Tailored industry landing for inbound + ABM; gated white paper; nurture.
Hero angle
Tokenization for asset and wealth managers.Issue and distribute private credit, funds, real estate, and equities on Bitcoin — with compliance built into the asset.
Page outline
  1. 1Hero + download CTA.
  2. 2Split section — "For asset managers" (issuance / product) vs. "For wealth managers" (client access / distribution).
  3. 3Use-case grid across the asset classes.
  4. 4How AMP works — business-outcome framed.
  5. 5Proof + white-paper CTA.
Proof points
BMN2MicroStrategy CMSTRMetaplanet CMTPLNexBridge USTBLUSDt on Liquid
Distinct from
Asset Tokenization (solution) owns the asset-class keywords (private credit, RWA). This pageowns audience terms ("tokenization for asset managers") and the asset-vs-wealth split — no head-term overlap.
CTA & magnet
Primary: “Download: Tokenization for asset & wealth managers”Secondary: “Talk to our team.”
Tone
Business-first, asset-class fluent, non-web3. Two clear audiences, one page.

Sources & method

INPUTWHAT IT SET IN EACH SPEC
Quant search brief
Segment demand, target keywords + volumes/KD, the page job, and which pages are search-led. The keyword chips and demand figures come from this corpus.
Enterprise sales sync (Jun 8 2026)
The persona set and its Web3 / TradFi split, what each buyer asks for, objections, proof points, channel, and tone. Used at the ICP / channel level.
Enterprise primer
The live proof points (BMN2, CMSTR, CMTPL, USTBL, USDt) and the custody assurance pillars.
▸
Companion briefs: Sales Intel reconciliation · Quant search demand · Content calendar · Enterprise primer. Proof points to be verified against current Liquid issuances before publishing.