Case study — Legal Nodes
Turning volatile organic search into a predictable pipeline engine.
Legal Nodes is a global legal and compliance platform covering 150+ legal tasks. The company needed a marketing manager to accelerate growth across organic and paid channels — and to fix the core problem: content marketing was a volatile, unpredictable lead generation source. I rebuilt it into one that compounds.
01 The baseline
A lead source that wouldn't hold still
The mandate when I came in was twofold: accelerate growth through organic and paid marketing channels, and turn content marketing from a volatile, unpredictable lead generation source into something the sales team could plan around. Rankings and traffic swung month to month, and none of it was reliably tied to pipeline.
There was one early signal worth chasing: the company was already getting real leads and real pipeline from AI assistants — ChatGPT, Perplexity, Claude — without ever having optimized for them. SEO was still the only channel being deliberately worked. The AI visibility was an accident. Nobody was managing it.
02 The strategic tradeoff
Why build for AEO on top of SEO
The obvious play was to keep pouring effort into SEO alone and treat AI traffic as a fluke. I made the opposite call: keep the SEO program running, and build a deliberate AEO layer on top of it. The market had already voted — AI assistants were sending qualified leads before we ever asked them to. The opportunity was to systematize an accident.
The bet: fewer, deeper cornerstone assets built around high-intent regulatory topics, each structured for both search engines and LLM retrieval. That meant investing in SME review workflows with subject-matter lawyers, schema and content structuring for AI retrieval, and conversion-focused landing pages — slower to ship, but compounding. The methodology became the AEO Implementation Playbook, which I authored and now share publicly.
03 The execution
The AEO workflow and content engine
I built an AEO/GEO workflow that tracked how articles and white papers were cited across ChatGPT, Perplexity, and Claude — then fed those findings back into the editorial calendar, so every cycle sharpened what the AI surfaces actually retrieved.
The engine itself: compliance cornerstone articles (EU AI Act, DORA, MiCA, AI in recruitment, RWA tokenization, UAE crypto licensing), customer case studies (Preply, Boosty Labs), conversion landing pages (/rwa, /mica, /dora), Typeform assessments and templates, and expert webinars with practicing lawyers — all published through a Webflow CMS calendar I owned end to end.
Around the content, I ran Google Ads and LinkedIn Ads for lead generation, set up HubSpot landing pages with a Factors.io attribution engine, and ran 50+ messaging and CRO experiments on landing pages and CTAs — so every content asset had a measured path to demo requests.
04 The attribution
Measured in the sales CRM, not asserted
The number leadership cared about was Marketing-Influenced Leads, measured in the sales CRM. Every asset was mapped to a funnel stage and tracked through Factors.io into HubSpot, with weekly executive reporting on performance. Content-to-pipeline mapping and lead handoff alignment with sales meant the $700K in marketing-influenced pipeline was read off the CRM, not claimed.
The compounding result: 45% cumulative quarterly brand awareness growth, 2.5x ROAS across three paid ad groups in a single quarter, and an organic engine that stopped depending on any single ranking.
Legal Nodes — Proof
Published artifacts
- EU AI Act: Compliance Roadmap for August 2026 Deadline
- AI in Recruitment Processes: Navigating High-risk Systems for AI Deployers
- Guide to the Scope and Practical Aspects of DORA Compliance
- Legal Belongs in the GTM Engine. Here's Why
- Preply's Approach to Privacy Compliance, Supported by Legal Nodes
- Structuring a Legal Model For a New DAO Venture
- Landing pages: RWA Tokenization, MiCA Licensing, DORA
- Webinar: The AI Governance Gap — Deploying Agentic AI Systems that Scale