The plan
In one line
Run the enterprise landing pages entirely on HubSpot — pages, forms, CRM, nurture, and reporting in one system. Build and deploy from Claude Code via HubSpot's Developer MCP, validate on a noindexed enterprise.blockstream.com with paid / ABM / outbound traffic, and graduate the proven pages to blockstream.com/enterprise where they earn SEO.
- One platform, maximum continuity.Everything — the pages and the lead lifecycle — lives in HubSpot. A standard system with a large talent pool and vendor support, so the org can run it after anyone leaves. This is the answer to the bus-factor concern.
- Still Claude-Code-native.HubSpot's Developer MCP server (GA Feb 2026) builds CMS templates and modules from Claude Code, and HubDB drives the programmatic page set from data. We keep our fast build loop; HubSpot hosts and serves.
- The subdomain is the lab; the main domain is the earned layer.Pages prove themselves on enterprise.blockstream.com where we iterate freely, then only winners graduate to the asset that's slow to touch.
- Ship now, don't wait on the corporate site.Connecting the subdomain to HubSpot is a single DNS record. We launch and iterate from day one; the main-domain move comes later, with evidence.
- The eng ask gets easy.We never ask to put 200 untested pages in front of blockstream.com. We ask to publish a handful that already drive pipeline.
One platform, end to end
Everything runs through HubSpot, built and deployed from the workflow we already use. No second system to stitch together, nothing custom to hand off.
HubSpot · built & deployed from Claude Code
Pages and lead lifecycle in one system
BuildClaude Code + Developer MCPScaffold CMS templates & modules in natural language (
hs mcp setup, CLI 8.2+).GenerateHubDB dynamic pagesOne template + one row per persona → the full page set from data.
CaptureNative forms → CRMEvery page's form creates a contact, tagged by page & persona.
ConvertNurture + routingWorkflows, lead scoring, LinkedIn sync, sales handoff — built in.
▸
Why all-HubSpot: a single platform is the strongest answer to continuity — one vendor, one skill set, vendor support, and nothing bespoke to document or lose. The honest tradeoff: HubSpot CMS pages are marginally less raw-fast than hand-rolled static, and the main-domain step still needs a reverse proxy. Both are acceptable costs for running the whole funnel in one system the org can own.
Phase 1 — Validate
Phase 1enterprise.blockstream.com · weeks 1–6 · no eng needed
Stand up the subdomain in HubSpot as a controlled testing ground and find what converts, fast.
Set up
Connect + build
CNAME enterprise.blockstream.com to HubSpot (native, auto-SSL). Build the template from Claude Code; HubDB rows generate the pages. Noindexed.
Drive
Paid / ABM / outbound
Don't wait for organic — send paid, ABM, and outbound traffic to each persona page.
Measure
Conversion by persona
Form-fills, demo requests, cost-per-lead — in HubSpot, segmented by persona and message.
Iterate
Tighten the loop
Redeploy from Claude Code, A/B test headlines and offers, kill losers weekly.
- Connecting the subdomain to HubSpot is one CNAME.HubSpot hosts it natively and provisions SSL — no proxy, no eng project to start. This is the only setup dependency for Phase 1.
- Noindex the whole subdomain.It's a lab driven by paid traffic, so organic isn't the signal. Keeping it out of Google's index means no duplicate-content question later and a clean slate when winners publish on the main domain.
- Conversion is the metric, not traffic.Define the winner bar before launch — a minimum lead volume and conversion rate per persona over a set window — so “best performing” is decided on data, not opinion.
- Plan the URL structure once.Slugs match what they'll be on the main domain (enterprise.blockstream.com/asset-tokenization → blockstream.com/enterprise/asset-tokenization), so promotion is a clean lift.
Phase 2 — Graduate the winners
Phase 2blockstream.com/enterprise · week 6+ · small eng ask
Take the pages that proved they convert and serve them on the main domain to earn organic search.
Select
Pick winners
Pages that cleared the conversion bar and have inbound/organic potential.
Serve
Reverse proxy
Route blockstream.com/enterprise/* to HubSpot via the edge, so the pages sit on the main domain.
Redirect
301 + canonical
301 the subdomain URL; canonical to the main-domain URL; index only the main one.
Link
Wire internal links
Link from existing high-authority blockstream.com pages and the blog cluster into each winner.
- The main-domain step needs a reverse proxy.HubSpot can't natively host a subdirectory of a domain rooted elsewhere, so an edge layer (Cloudflare / CDN / nginx) routes /enterprise/* to HubSpot. This is the one custom piece — documented and owned by the web/infra team.
- What we need from eng is small and evidence-backed.Route a handful of proven pages, not proxy 200 untested ones in front of the corporate site.
- Internal linking is the real SEO lever.The main-domain slot supplies authority; links from existing pages and the content-calendar blog cluster make each page rank. Plan those at graduation.
- Get the hygiene right:canonical to the main-domain URL, subdomain 301s in, page in the main sitemap — so all ranking signal consolidates on blockstream.com.
The lead lifecycle (HubSpot, both phases)
The lifecycle is constant across both phases. The page can live on the subdomain today and the main domain tomorrow; the form, the contact, and the nurture don't change — it's the same HubSpot record throughout.
Capture
Form → CRM
Native form creates a contact, tagged with page, persona, and source.
Nurture
Email sequence
Segmented track, typically 5–8 emails over 4–6 weeks for mid-funnel B2B.
Score
Lead scoring
Behavior adds points; threshold marks an MQL and branches the workflow.
Route
LinkedIn + sales
At intent: add to LinkedIn retargeting audience, create SDR task, notify account owner.
- Closed-loop reporting in one tool.Page → form → nurture → MQL → deal is a single attribution chain, so we can show which landing pages source pipeline, not just traffic.
- Continuity, fully addressed.Pages, leads, nurture, and reporting all live in a standard platform with a hireable skill set and vendor support — nothing depends on the person who built it.
What we need
- HubSpot Content Hub, Professional or Enterprise.Required now — dynamic pages, HubDB, and the reverse-proxy pattern need a paid CMS tier (plus Marketing/CRM for forms, nurture, LinkedIn sync). now
- HubSpot CLI 8.2+ with the Developer MCP.So we build and deploy CMS templates from Claude Code (
hs mcp setup). now - A DNS record for enterprise.blockstream.com.One CNAME pointing the subdomain at HubSpot. The only infra dependency to start. now
- Agreed validation criteria.The conversion bar and test window that define a “winner,” signed off before launch. now
- Reverse proxy at blockstream.com's edge.To serve the graduated winners at /enterprise. phase 2
- Open question to resolve before Phase 2:what currently fronts blockstream.com (Cloudflare? a CDN? raw origin?). That decides how the reverse proxy goes in — but it does not block Phase 1.
▸
The honest tradeoff: validating on a subdomain and migrating winners later isn't free — a 301 carries most, not all, of any equity built. The purest SEO play is to launch directly on the subdirectory, but that means waiting on the corporate site and shipping slowly. For paid/ABM-driven pages the subdomain penalty is small, and speed plus a single platform are worth more than perfect day-one SEO.
Timeline
Week 1
Stand up the lab in HubSpot. Connect enterprise.blockstream.com (CNAME), build the page template from Claude Code via the Developer MCP, load the persona set into HubDB, set pages noindexed, wire forms + nurture. Lock the validation criteria.
Weeks 2–6
Validate. Drive paid / ABM / outbound to each persona page. Measure conversion by persona in HubSpot, A/B test, iterate weekly from Claude Code.
Week 6
Pick winners. Score pages against the agreed bar. Decide which earn a main-domain slot (proven conversion + organic potential).
Week 6+
Graduate. Stand up the reverse proxy, serve winners at blockstream.com/enterprise, 301 the subdomain URLs, wire internal links. Bring eng the evidence and the short list.
Ongoing
Compound. Subdomain stays the lab for new personas and offers; the main domain accumulates the proven, ranking pages plus the blog cluster that links into them.
Companion docs: Content calendar (the SEO blog cluster that links into the winners) · HubSpot rationale (deeper on the platform choice). We rebuild the existing v3 wireframe set in HubSpot and validate those first.