The map of how Voyager runs. Systems, pipelines, tooling. Internal reference for Ben and Alex. Auto-deployed from GitHub on every push.
The five core systems and how they talk to each other. Notion, Portal, Orbit, MCP server, Claude surfaces. Click any node for detail.
Start: monthly quota. End: published + tracked. 8 phases with skills, MCPs, and human checkpoints. Loops back to feed itself.
Signed agreement to active retainer. Eight phases. Welcome, CRM setup, ID mapping, site provisioning, verification gate, Drive, billing, kickoff.
The Chat-to-Code spine. Spark in Chat, mission write to Notion, dispatch, Code execution, human merge checkpoint, ship-session, discoveries back to Notion. Loops.
The workshop. Tag every component good, leaky, duplicate, needs skill, needs automation. Exports as Markdown or as a ready-to-paste Claude prompt.
Every Voyager skill, org and dev, with trigger phrases and surfaces. Generated from the voyager-skills repo on every merge. "What can I ask Claude to do."
All ~200 Voyager MCP tools by category, searchable, with links to source. Generated from the tool registry on every merge. Living API documentation.
Every How-To and Playbook in the Knowledge Base, browsable outside Notion. Answers "where is the process for X" without asking Ben. Links into the live Notion entry.
Signed contract to managed-fleet client. 7 modules, 6 gates, two tracks (baseline spine vs client divergence). The canonical website-build flow — the agency's core delivery engine.
The monthly heartbeat of the managed fleet. Eight service lanes — SEO, content, social, ads, GBP, email, maintenance — across the month, converging on the day-7 report. Each lane links to its KB SOP.
The front of the business. Inbound lead → zero-drop triage into Attio → nurture → AI-briefed discovery call → fit score → proposal → Stripe close → onboarding handoff. Completes the funnel.
The retention engine. Weekly health scoring → monthly review → QBR, routing each client to renew, recover, or offboard. Every stage links to its KB playbook. The lifeblood of the agency.
What Voyager sells — services, pricing tiers, delivery cadence, and who owns each (Ben / Alex / Claude / automation). Every service links to its delivery map and KB SOP.
Map data lives in data/*.json; each map is an HTML file that fetches its JSON at load time. Hosted at voyager-agency-map.pages.dev. Auto-deploys from GitHub on every push. Updating a component = pushing one small JSON file. The triage editor (05) reads the same JSON as the stack map, so it never drifts. It's the lever for turning the map into sprints.
github.com/voyager-marketing/voyager-agency-mapdata/*.json (Sprint 04 Phase A). Claude pushes via Voyager MCP, Cloudflare rebuilds.