ABM Landing Page Builder
Drop a domain. Get a landing page tuned to their role, their stack, and what they're researching right now.
An HTML-ready landing page tuned to role, stack, and live intent
| Block | Signal it cites |
|---|---|
| Hero | Industrial Copilot rollout (Microsoft, May 2024) |
| Stat strip | $3.99B IT spend · 312k employees · 3 clouds active |
| Pain block | FAI: Engineering owns 8% of CRM signal; no LLMOps tool detected |
| CTA | "Show me the Azure-native observability layer your team is missing." |
Overview
Personalized ABM landing page for one target account — HTML copy blocks, headline + sub-head, CTA framing, and design notes — tuned to the buyer's role plus the live intent signals running through their company right now.
Use cases
Your ABM team stops shipping templated landing pages
Today the ABM team writes one landing page and recycles it across 30 accounts with the company logo swapped. This workflow swaps that for a per-account page where every block — hero, stat strip, pain framing, CTA — cites a current HG signal for *that* domain. Same effort, an order of magnitude more relevance.
Sales-cycle handoff that survives discovery
When the AE follows up the prospect can't say 'this landing page felt generic'. The page named their CIO's department, their stack, and the intent topic they're spiking on. The AE's discovery call picks up exactly where the page left off — no jarring tone shift.
View workflow prompt
# ABM Landing Page Builder
## Parameters
- `{{domain}}` *(required)* — Target account domain HG Insights uses for lookup. Example: `siemens.com`
- `{{buyer_role}}` *(required)* — Role the page is aimed at — title or function. Example: `CIO`
- `{{product_pitch}}` *(required)* — One-sentence positioning the page is built around. Example: `AI observability and LLMOps for industrial Copilots.`
## Purpose
Produce an HTML-ready landing page for {{domain}} aimed at the {{buyer_role}}, framed around {{product_pitch}}. Every section anchors on a *current* signal from HG data so the page reads as built-for-them, not built-from-a-template.
## Process
1. **Account snapshot** — `company_firmographic` for {{domain}}. Confirm parent/subsidiary, employees, industry — the hero block's identity stamp.
2. **Functional owner** — `company_fai` for the department the {{buyer_role}} owns. The product framing speaks to operational pain, not abstract ROI.
3. **Live intent** — `intent_category` for categories adjacent to {{product_pitch}}. Use top spike as the page's "you're already looking at this" anchor.
4. **Stack evidence** — `company_technographic` for current tools + 1-2 recent adds. The "we integrate with" block lists their real stack, not generic categories.
## Output Format
Markdown with:
- `# ABM Landing Page — {{domain}} × {{buyer_role}}`
- `## Hero Block` — headline ≤80 chars + sub-head ≤180 chars (both citing a signal)
- `## Stat Strip` — 3 hero stats from HG data (employees · IT footprint · live intent signal)
- `## Problem-You-Have` — 3 bullets framed as their FAI department's actual pain
- `## Solution Sections` — 3 sections, each tied to one of their stack items
- `## Social Proof Block` — placeholder for a relevant logo + customer line
- `## CTA` — primary + secondary (one's a meeting ask, one's a tailored asset)
- `## Design Notes` — color, type, layout suggestions tied to brand cues
## Quality Checklist
- Every block cites the HG signal it's anchored on
- Buyer role appears in copy, not just metadata
- Stack section names tools, not categories
- CTA leads with a verb