← all builds
● liveLive, build date unverified

HighIntentLead: the one-file lead-gen site

One static HTML file selling identity-resolved lead gen. The site's original build receipt is missing; the data pipeline behind it now has audited ones.

highintentlead.com

## the problem

Humbear Media, my agency, is positioned tightly around behavioral health marketing. The intent-data offer I sell reaches wider than that: personal injury, mortgage, financial services, solar, home services. Pitching a personal injury firm from a site built around addiction treatment is an uphill conversation. The offer needed its own front door.

I also did not want another agency site that takes weeks and a page builder. The pitch is one argument: stop paying for cold traffic, reach the buyer who is already shopping. One clear argument fits on one page if the page is built well.

Full disclosure on this one: it predates my habit of archiving every build session. The site is live and inspectable. The original prompts are not. That shapes how this build log is written, and the gaps are flagged at the bottom instead of papered over.

## what I built

highintentlead.com is a single-page marketing site for High Intent Lead, a Humbear Media property selling identity-resolved lead generation to high-CAC verticals. The hero reads Stop paying for cold traffic, under a live-styled status pill: SIGNAL: LIVE, IDENTITY RESOLUTION ACROSS 650,000 US WEBSITES. Six service blocks follow: identity-resolved audiences; Meta, Google and Amazon DSP; AI voice and chat; marketing automation and CRM; social media brand building; compliant infrastructure.

Technically it is about as small as a real site gets. One hand-coded HTML file around 50KB. Inline CSS, zero external JavaScript, a single Google Fonts request for Inter, served behind Cloudflare. No theme, no builder, no CMS generator tag anywhere in the source. Near-black background, purple and teal accents, mono-style section labels, an engineering-grid feel.

It doubles as the portfolio hub for the rest of what I run. The page previews case write-ups for EasyVOB and Career That Lasts and links to Humbear Media. The only call to action is a no-commitment 30-minute audit call. The footer says exactly what it is: a Humbear Media property.

## how Claude was actually used

  1. 01

    The original build, and the missing receipt

    I am on record in a saved session telling Claude that highintentlead.com is one of the things it helped me build. That is the honest extent of the receipt: the original build chats predate my transcript archive, so I cannot paste the prompts here. What I can do is read the shipped artifact, which is the next step.

  2. 02

    Reading the shipped artifact

    What is verifiable today by viewing source: the whole site is one hand-coded HTML file of roughly 50KB with inline CSS and no external JavaScript. Section structure is hero, services, work-preview, award, cta, with full OG and Twitter meta, a canonical tag, and an SVG favicon. No generator tag, no builder fingerprints. That is the output profile you get when you ask Claude for a fast landing page instead of standing up a WordPress install.

  3. 03

    Copy that makes one argument

    The page makes a single case: stop paying for cold traffic, reach the buyer who is already in-market. Headline, the SIGNAL pill, six service cards, a list of target verticals, one CTA. The big numbers on the page, 650,000 US websites and 40,000 plus intent topics, are the data vendor's figures, not mine, and they stay flagged below until I can cite the source.

  4. 04

    Theme extraction in a recorded session

    This part has a full receipt. In June 2026 I asked Claude to redesign the humbearmedia.com homepage using the Humbear identity plus the highintentlead.com theme. Claude pulled the live page with curl, counted hex color frequencies to find the palette (a near-black base with purple and teal accents), extracted the headings and structural patterns like the mono eyebrow labels and the live SIGNAL pill, and fused them into homepage mockups I then iterated on. A good build pays twice.

  5. 05

    Search plumbing

    highintentlead.com is a verified property in my Google Search Console account. I know because a later Claude Code session doing Search Console work for humbearmedia.com kept landing on the HighIntentLead property by default and had to switch off it. Small receipt, but it confirms the domain is wired for indexing, not just parked.

  6. 06

    Hardening the intent-data delivery pipeline

    In July 2026 the pipeline behind this offer got real Claude receipts. The intent-data vendor delivers audience files into an S3 bucket, and I ran a migration from a custom sync to the vendor's native S3 integration as a Claude Code project: nine commits, July 14 to 16, all of it documentation, IAM policy, and audit scripts rather than app code. Claude first ran a read-only audit of the bucket — 15,978 objects — and mapped the delivery pattern: 73 active audiences across 16 client folders, delivered between 00:00 and 01:05 UTC, with zero missed days in the trailing 30.

  7. 07

    Least-privilege access instead of a god key

    For the vendor cutover, Claude authored a dedicated IAM user with an inline policy scoped to the single delivery prefix, then verified it live: writes inside the prefix allowed, writes to the legacy paths denied. It also set a key-rotation deadline in the docs rather than leaving the credential to live forever. The honest status: as of this writing the old custom sync is still the live path and the vendor-native integration is pending cutover — the README banner says so, and so does this page.

  8. 08

    Where Claude goes next in this pipeline

    The site sells AI voice and chat qualification as part of the offer. I am not claiming that runs on Claude today, because I have not verified what is wired up behind it. It is the obvious slot: intent data finds the buyer, automation makes contact, a model qualifies before a human takes the call. That claim ships when I can show it working.

## stack

Claude CodeHand-coded static HTML and CSS, single file, no JavaScriptGoogle Fonts (Inter)CloudflareGoogle Search ConsoleAWS S3 (intent-data delivery)AWS IAM (least-privilege delivery credentials)n8n (delivery touchpoints, inventoried during the migration)

## results (the verifiable kind)

  • Live at highintentlead.com: a complete single-page marketing site positioning identity-resolved lead generation for personal injury, mortgage, financial services, solar, home services, and behavioral health operators.
  • The entire site is one HTML file of roughly 50KB with inline CSS and zero external JavaScript; no CMS, theme, or page-builder fingerprints in the source.
  • Six service sections shipped: identity-resolved audiences; Meta, Google and Amazon DSP; AI voice and chat; marketing automation and CRM; social media brand building; compliant infrastructure.
  • Cross-links live case previews for two other properties I own, EasyVOB and Career That Lasts, and links to Humbear Media in the footer.
  • Verified property in Google Search Console, observed in a recorded June 2026 session.
  • Its palette and design language were extracted by Claude from the live page in a recorded session and reused as the reference theme for the humbearmedia.com homepage rebuild.
  • The intent-data delivery pipeline behind the offer has audited receipts from a July 2026 Claude Code session: 15,978 objects reviewed read-only in the delivery bucket, 73 active audiences across 16 client folders, zero missed daily deliveries in the trailing 30 days, and a least-privilege IAM cutover authored and live-verified (in-prefix writes allowed, legacy paths denied).

## what I learned

  • Archive your build sessions. This site's whole premise on my end is receipts, and the one thing I cannot show here is the original build chat for the site itself. That is the failure on this one, and it is why everything I build now runs through sessions that get kept.
  • A one-file site is a feature. Nothing to update, nothing to patch, fast loads, and anyone can read the entire source in one pass. The tradeoff is real too: no CMS means every copy edit is a code edit.
  • Numbers you did not generate are liabilities. The intent-data figures on the page come from the vendor, so until I can cite the source they stay flagged, and the same discipline applies to this write-up.
  • Pointing Claude at a live URL and asking it to extract the theme works in one pass. It pulled colors by frequency count and structure straight from the raw HTML, no design files needed. That turned this site into the design system for the agency rebuild.

$ follow --the-build

Watch it happen, don't take my word for it

Every build on this site gets documented as it happens — the prompts, the dead ends, the results. No course at the end of this funnel. There is no funnel.

follow on x →