The infrastructure

The stack I run on.

72 AI systems in production across my businesses and my clients’ — running on eight layers of tooling I’ve shipped in real engagements. The same stack I deploy for partners.

  • BuildClaude Code · MCP · CursorThe build layer — where the systems themselves get written, tested, and wired together.
  • RuntimeClaude API · OpenAIThe models doing the work: writing, reasoning, classifying, deciding — inside every system below.
  • ComputeModal · Vercel · CloudflareWhere it all runs: sites, pipelines, and scheduled jobs that fire whether anyone is watching or not.
  • VoiceRetell AI · ElevenLabs · TwilioPhone agents that answer missed calls, qualify, and book — the system running for Horizon in Atlanta today.
  • DataAirtable · ClickUp · Webflow CMSWhere the records live: pipelines, content, ops state — the source of truth the systems read and write.
  • OutboundInstantly · Apollo · Slack · GmailThe outreach layer: personalized sequences, replies, and the routing that keeps a human in the loop.
  • SurfaceWebflow · Vercel · FramerWhat customers actually touch: the sites and pages in the case studies, shipped and iterated fast.
  • TestPlaywright · Puppeteer · GitHubThe proof layer: automated checks that pages render, flows work, and nothing ships broken.

The wiring board

Who runs what.

Every dot is a system family I built for a named engagement — pulled straight from the case pages.

EngagementSiteAdsContentVoiceLifecycleOps
Bowman Fly Fishingthe case →
Bella Cottage past engagementthe case →
Homegrownthe case →
Driftlinethe case →
Horizon Hygienethe case →
Confidential B2B SaaSWiring under NDA

A dash means it wasn’t part of the engagement — the board only claims what the case pages claim.

Why it matters to you

This is the difference between advice and infrastructure.

A consultant hands you a plan and leaves. This stack is what an engagement actually installs: systems that research, write, build, call, and report, running on your accounts, documented, owned by your team when I leave.

And because I run my own businesses on it, nothing here is theoretical. Every layer earns its place by working for my own revenue first.

“Knowledge is code. Code persists. People rotate.”

The systems are real. The next one can be yours.

Start a conversation