Enterprise Landing Page — ABM Variant

The same skeleton, compressed for the ABM motion

The inbound wireframe is built to rank and capture downloads. This variant is built to convert a named account in one visit: the contact form is the hero, an infrastructure block replaces the feature flow, and the gated resource row is gone. Use it for the two Web3 persona pages — Qualified Custodians and Exchanges — where the buyer arrives from outreach or a conference, not a Google search.

Jun 8 2026 · companion to the inbound wireframe & Page Specs
IntroWireframeMappingNotesInbound WFABM WF

What changes vs. the inbound wireframe

  • Hero is form-first, not download-first.An inline contact form sits in the hero as the primary action. No keyword to win, so don't make the reader hunt for "talk to us" — put it front and center.
  • An infrastructure block replaces a feature.The defining section: "custody infrastructure, not a black box" (Custodians) or "integrate Liquid, expand what you can list and settle" (Exchanges). This is what the ABM buyer came to understand.
  • Feature flow compresses from four blocks to one.One credibility block ("verify, don't trust") instead of a four-part walkthrough. The buyer is already qualified; depth > breadth.
  • The gated resource row is dropped.No white-paper lead magnet — replace with a single ungated technical overview for the evaluator. The conversion is the meeting, not the download.
  • One CTA, repeated: talk to us.Nav, hero form, and closing band all point to the same conversation. No competing "download" path.
heading body text image / visual contact form primary CTA

The wireframe

01
Sticky nav
Minimal. Fewer menu items than the inbound page — this is a focused destination, not a browse surface.
BlockstreamLogo · Solutions · Resources · Talk to sales (Exchanges: "Talk to partnerships").
Talk to sales
02
Hero — form-first
Headline + 3 proof bullets on the left, an inline contact form on the right. The form is the page's primary action.
BlockstreamH1: "Run a licensed custody business on proven Bitcoin infrastructure." Bullets: no rehypothecation · provable reserves · open primitives. Form: name / company / email / "Request a call."
changed · button → inline form
Talk to our team
Request a call
03
Infrastructure / integration
The defining block. A build-vs-buy contrast under a plain headline — why build on Blockstream instead of from scratch.
BlockstreamCustodians: "Custody infrastructure, not a black box" — verifiable, open tech to build your offering on. Exchanges: "Integrate Liquid" — what you can newly list, settle, and secure.
new · replaces a feature block
Build it in-house · slow, costly
Build on Blockstream · proven, open, verifiable
04
Assurance pillars
3–4 compact cards carrying the proof that matters to this buyer. Replaces the inbound page's 4-icon callout row.
BlockstreamCustodians: no rehypothecation · proof of reserves · multisig + HSM · open primitives. Exchanges: new listings · faster settlement · confidential transactions.
05
Credibility block ×1
A single deeper 50/50 block — the technical differentiation, with an ungated overview link. One, not four.
Blockstream"Verify, don't trust" — how proof of reserves works, the open-source primitives. Link: technical overview (no gate).
compressed · 4 blocks → 1
Technical visual
Verify, don't trust
06
Named proof
A "who we work with" logo row — account-level proof for an account-level buyer. No testimonials; logos only. Drop the section entirely if there are no real names to show.
BlockstreamLogo row of existing integrations / issuers — real names only.
Who we work with
07
Closing CTA
Repeat the same conversation. Either the form again or a centered band — one ask, no download alternative.
Blockstream"Talk to us" → Talk to sales / partnerships. Same destination as the hero form.
Talk to sales
08
Footer
Standard link map + legal. Same as inbound.
BlockstreamProduct / Solutions / Resources / Company + legal; link sibling pages.

Inbound → ABM, section by section

SectionInbound wireframeABM variant
HeroValue prop + download CTA + hero image; logo bar belowInline contact form as primary action; proof bullets instead of image
Section 34 icon benefit calloutsInfrastructure / integration block (build-on-Blockstream / Liquid integration)
Features4 alternating 50/50 blocks1 credibility block ("verify, don't trust") + assurance pillars
Resources3 gated resource cards (white paper, blog, guide)Dropped — one ungated technical overview instead
ProofAdvisor testimonialNamed-account logo row (no testimonials — we don't have them)
Closing"Bring your assets on-chain" + demo"Talk to us" — same form/conversation
Primary CTADownload (talk-to-sales secondary)Talk to sales only — no download path

Per-page notes

  • Qualified Custodians:the infrastructure block is "custody infrastructure, not a black box" — verifiable, open tech to build on; assurance pillars are no-rehypothecation / proof-of-reserves / multisig+HSM / open primitives. This page can go technical — the reader is web3-fluent.
  • Exchanges:the integration block is "integrate Liquid" — new assets to list, faster settlement; pillars become integration benefits. Keep the BSTR BTC-deployment hook out of page copy (rep talking point only).
  • Don't fake the proof row.If named logos are thin, use a single strong partner quote rather than implying a roster.
  • Form length is the conversion lever.Keep it to 3–4 fields. The qualifying happens on the call, not the form.
Pair with: Inbound wireframe (solution + Asset & Wealth pages) · Persona Page Specs (the copy that fills each block). Two layouts, seven pages: inbound skeleton for the five searchable pages, this ABM variant for Custodians & Exchanges.