Pipeline that compounds. Not four dashboards
CRM, outbound, and paid wired into one system. One source of truth, built and run until the pipeline holds.
Built and run, not advised
Pipeline architecture
CRM, outbound, and paid connected into one operating model. One source of truth, not four disconnected dashboards.
RevOps and attribution
Lifecycle stages, routing, and reporting that show exactly where the signal breaks.
Outbound that lands
Sequences and targeting built on real ICP signal, enriched and personalised with AI. Not spray.
Most GTM problems are not strategy problems. They are plumbing problems. I fix the plumbing.
Built and running, not slideware
GTM systems and tools I designed, shipped, and still operate. Each one links to the live build or the breakdown.
AdsAI / Ad Assistant
Google Ads cockpit with AI-driven ICP lead scoring (0-100). Shifts optimisation from CPL to CPL-ICP-fit, with campaign priorities and next-best actions in one workspace.
- Problem
- Ad optimization work was split between reports, intuition, and repeated checks.
- System
- Budget, ICP, ROAS, alerts, and actions are pulled into one decision loop.
- Artifact
- Live dashboard with campaign priorities and optimization queue.
Claude Code GTM Agent Starter Pack
Open-source starter pack for building AI GTM agents with Claude Code. Designed for growth operators who want to ship AI-native workflows without starting from scratch.
- Problem
- Operators wanted AI-native GTM workflows but had no structured starting point: just blank Claude sessions and scattered prompt tips.
- System
- 4-layer agent stack: CLAUDE.md operator identity → MCP tools → client memory files → 5 reusable operator skills. Covers research, enrichment, sequence drafting, and CRM updates.
- Artifact
- Open-source GitHub repo with full starter pack: CLAUDE.md template, skill definitions, folder structure, and MCP source.
Outbound intelligence system
Replaced a broken spreadsheet-and-gut-feel outbound motion with a structured AI agent stack: enrichment, scoring, and sequence drafting in a single operator loop.
- Problem
- A B2B SaaS team was running outbound from a mix of manually-enriched spreadsheets, Apollo exports, and instinct. Coverage was inconsistent, personalization was template-based, and the cycle from list to sent sequence was two to three weeks.
- System
- Claude Code with four MCP integrations (LinkedIn, Apollo, HubSpot, Clearbit), a client-specific CLAUDE.md operator brief, and named skills for each stage: account scoring, ICP classification, signal extraction, and sequence drafting. Each run produces scored accounts with drafted sequences ready for human review, not a bulk send.
- Artifact
- Operator stack: CLAUDE.md brief, four MCP connections, five named skills. A 50-account cold CSV goes to scored accounts with personalized sequence drafts in under an hour. Output reviewed and approved before any contact is made.
Pipeline leaking somewhere you cannot see
Send the current stack and the bottleneck. I will tell you where the signal breaks and where I would start.