Playbooks / Port the funnel onto a client's own domain, repo, Vercel, ActiveCampaign and Calendly

Port the funnel onto a client's own domain, repo, Vercel, ActiveCampaign and Calendly

Port the funnel onto a client's own domain, repo, Vercel, ActiveCampaign and Calendly

Coming

The playbook for running Timo's funnel legs on a client's existing domain: /masterclass-live to evergreen /watch, all CTAs to /watch, contact form to their AC, /apply Calendly auto-height, /api/health showing both bookings paths, attribution kit as a branch on their repo with 4 env vars on their Vercel.

Kit

No separate kit. The playbook is self-contained.

You need

AccountWhyFree or paidPlan
Claude Code (Anthropic Claude Pro or Max)The AI operator every system runs through. Skills, hooks, memory, MCP servers and the Brain plugin all load inside Claude Code.PaidClaude Pro (20 USD/mo) works for light use; Max (100 USD or 200 USD/mo) for daily multi-hour sessions. Anthropic terms require each user to hold their own subscription; never share a login.
Node.js 24 (npm, npx)Runs Claude Code, the Vercel CLI, HyperFrames renders, Playwright, the MCP servers and every serverless function locally.FreeFree. Node 24 LTS (the Brain MCP server and Vercel functions target Node 24).
GitHubEvery site, dashboard and workflow lives in a repo. Actions run scheduled jobs (email snapshots, daily scrapes). Issues double as an email alert channel for bookings.FreeFree plan. Actions minutes on the free plan cover the cron jobs used here (a few minutes a day).
VercelHosts every site, funnel, dashboard and serverless API (subscribe, book, attribution, AC proxy). Runs the cron jobs declared in vercel.json.Free tier availablePro (20 USD/mo per seat). The Hobby plan forbids commercial use, so any client site or paid product must be on Pro. Hobby is fine for a personal portfolio.
ActiveCampaignEmail list, broadcasts, automations and tags. The email engine drafts into a dashboard queue and sends through the AC API; funnels subscribe leads via the API; replies come back through an AC webhook.PaidMarketing Lite or Plus (from about 15 USD to 49 USD/mo at 1,000 contacts). API access is on every plan. Webhooks (for reply tracking) need automations, which Lite has.
CalendlyBooking page for discovery chats. The funnel embeds it, the booking-alert system polls it, the calls page reads upcoming events.Free tier availableFree plan is enough for one event type and the API (Personal Access Tokens work on free). Standard (10 USD/mo) adds webhooks and reminders; the systems here poll instead, so free works.
SupabasePostgres database, auth (dashboard logins), row level security, Realtime pulse, Edge Functions and pg_cron for every dashboard, the attribution tables, booking alerts and the Brain state.Free tier availablePro (25 USD/mo) for anything a client logs into. The free tier pauses a project after 7 days without traffic and caps an org at 2 active projects; a paused free project took three client dashboards offline at once (a project log).
Meta Business Suite (Pixel, Conversions API, Marketing API)Facebook and Instagram ads. The funnel fires Pixel events, the attribution system sends server-side Conversions API events, the Meta Ads tab pulls ad-level insights, and social posting reaches your Pages through Zernio.FreeBusiness account is free; you pay for ad spend only. Requires a verified business and a domain verification TXT record for the Pixel.
Playwright + headless Chrome (and Safari for the final check)Renders pages to PNG for visual QA, drives the dashboard verification protocol, captures library stills, renders HTML titles and animations offline.FreeFree. Google Chrome installed for headless screenshots; Playwright installs its own Chromium and WebKit.

What you bring

  • A client repository and hosting project, when you build for clients
  • A client email platform key and list ids, when you build for clients
  • A client booking token, when you build for clients

The steps

  1. Put the handoff folder in their repo and give the AI the port prompt
  2. Mount the seven pages as routes and rewrite the internal links
  3. Port the three routes and the contact form to their ActiveCampaign
  4. Add `/api/health` so the plumbing is visible without a real booking
  5. The booking fallback for when their Calendly token is not ready
  6. The attribution kit as a branch on their repo
  7. Verify every arrow on production, then the one check only a human can do

Goes further if you have already built Set up first-party attribution and tracked short links. You can build this without it.

Get the full playbook

Part of: Build your website