Enterprise Landing Page — Wireframe

A landing-page skeleton, modeled on Vanilla

Vanilla (justvanilla.com) is the B2B SaaS reference the sales sync called best-in-class. This is its proven solution-page structure rebuilt as a low-fidelity wireframe, with each section mapped to Blockstream content. Copy it for any of the seven first-build pages — the example copy here uses the Asset Tokenization / Asset & Wealth Management page.

Jun 8 2026 · source: justvanilla.com/solutions-mass-affluent · companion to the Page Specs
IntroWireframeMappingNotes

The pattern — why it works

  • The engine: value prop → social proof → alternating feature blocks → gated resources → convert.Every section either builds belief or captures intent. Nothing decorative.
  • Social proof sits high.A customer logo bar directly under the hero does the heavy lifting before the reader scrolls.
  • Features are shown, not listed.Four alternating 50/50 image-text blocks — each one capability, a visual, and a one-line outcome.
  • The lead magnets live near the bottom.Three resource cards (case study / blog / guide) catch the reader who isn't ready for a demo — the white-paper motion the sales sync described.
  • One persistent CTA."Get a demo" repeats in the nav, hero, and closing band. For us: "Talk to sales" / "Get a demo," plus a content download as the soft secondary.
heading body text image / visual primary CTA×N repeats

The wireframe

01
Sticky nav
Global navigation + persistent conversion. Logo left, menus center, CTA right; stays on scroll.
BlockstreamLogo · Product / Solutions / Resources / Company · Talk to sales button.
Talk to sales
02
Hero + logo bar
Value prop in one line, audience subhead, primary CTA, hero visual right. Customer/partner logos directly below for instant credibility.
BlockstreamH1: "Issue and distribute real-world assets on Bitcoin." Sub: "Tokenization for asset & wealth managers." Logo bar: issuers/partners on Liquid (STOKR, NexBridge, Metaplanet…).
Get a demoDownload guide
Hero visual
Trusted by / built on
03
4 benefit callouts
"Meet your clients where they are" — a centered headline over four icon + one-line benefit columns. Frames the buyer's situation.
BlockstreamIssue on Bitcoin · Compliance in the asset · Confidential amounts · Settlement assurance. (Swap to custody pillars on the custody pages.)
04
Feature flow ×4
The core. Four alternating 50/50 image-text blocks — one capability each: visual, headline, one-line outcome, optional link. Image side flips every block.
Blockstream1 Issue any asset (AMP) · 2 Transfer rules in the token · 3 Confidential Transactions · 4 Proof of reserves / settlement. Lead with the MMF "comfort" use case.
Visual
Capability 01
Visual
Capability 02 · image flips
↓ repeats for capability 03 & 04, alternating
05
Resource cards
Three linked cards (case study / blog / guide) = the lead magnets for readers not ready to demo. The white-paper motion.
BlockstreamWhite paper (gated, e.g. "Tokenizing private credit") · explainer blog · regulatory guide. Email capture = the inbound lead.
Cover
White paper
Cover
Blog
Cover
Guide
06
Closing CTA band
Centered headline + one button. The final conversion nudge.
Blockstream"Bring your assets on-chain." → Talk to sales.
Talk to sales
07
Footer
Multi-column link map + legal. Escape routes and SEO interlinking.
BlockstreamProduct / Solutions / Resources / Company + legal. Link the sibling solution & persona pages here.

Vanilla → Blockstream mapping

Vanilla sectionPattern / jobBlockstream equivalent (Asset Tokenization example)
Hero + logo bar
One-line value prop, audience subhead, customer logos for instant trust
"Issue and distribute real-world assets on Bitcoin" / "Tokenization for asset & wealth managers" + a built-on/issuers logo bar (STOKR, NexBridge, Metaplanet, MicroStrategy)
"Meet your clients where they are"
4 icon callouts framing the buyer's situation
Issue on Bitcoin · Compliance in the asset · Confidential amounts · Settlement assurance
4-part feature flow
Alternating 50/50 image-text, one capability each, shown not listed
AMP issuance · transfer restrictions in-token · Confidential Transactions · proof of reserves — led by the tokenized-MMF comfort use case
"Learn more" resources
3 cards = lead magnets for the not-yet-ready
Gated white paper + explainer blog + regulatory guide — the email-capture inbound motion
Bottom CTA
Final centered conversion nudge
"Bring your assets on-chain" → Talk to sales
Footer
Link map + legal + interlinking
Product / Solutions / Resources / Company; link sibling solution & persona pages

Adapting it per page

  • Inbound pages (solution + Asset & Wealth):keep the full skeleton — the resource cards and gated white paper are the whole point. Primary CTA can be "Download" with "Talk to sales" secondary.
  • ABM pages (Custodians, Exchanges):compress. Drop or shrink the resource-card row, make the contact form the hero's primary action, and swap the feature blocks for the partnership model + assurance pillars. These convert relationships, not search.
  • Logo bar honesty:only real issuers/partners. If the set is thin, use a "built on Liquid" framing rather than implied endorsements.
  • Design quality is the point.The sales sync's takeaway from Vanilla: when two products are close, the better-looking one wins. Hand this skeleton to design with real copy, don't ship the greybox.
  • No testimonials.We don't have customer quotes to show — the page leans on the logo bar and verifiable proof points (proof of reserves, live issuances) instead. Verify issuer proof points against current Liquid issuances before publish.
Companion: Persona Page Specs (per-page copy, keywords, CTAs) · Sales Intel. This wireframe is the shared layout; the specs are what fills each block.