MKT1 Newsletter with Emily Kramer · Emily Kramer
articleplaybookInside team MKT1's multiplayer AI setup
17 September 2026Growth
Source excerpt
About MKT1 Newsletter with Emily Kramer2 GitHub repos, 1 MCP, 100+ skills, 30+ routines, and the “vacation test” for multiplayer AI | Part 3 of 3
This is a limited feed-provided excerpt, not the full original work.
Apollo layer
What a founder can learn
Founder takeaway
Treat team AI as shared infrastructure, not a collection of personal prompting habits. Centralize reusable skills and routines, connect them to common tools, and design the setup so work can continue when any one person is unavailable.
Why it matters
A shared system turns individual AI productivity into organizational capability. It improves consistency, reduces duplicated effort, and prevents critical workflows from depending on a single employee.
Relevant guides
Put it to work
Choose one recurring workflow and ask: What knowledge, instructions, tool access, and checks would we need to document so another teammate could run it successfully while its owner is away?
Private notes