The Product Team Stack

A Switchy Project for the 2–8 person product team that lives between the backlog, the doc, and the design file.

Spinning this stack up creates a Switchy Project - your team chats together, @-mentions every model and MCP listed below with shared context, and that whole memory becomes its own MCP server inside Claude Code, Cursor, Claude Desktop, and ChatGPT for every teammate.

Heads up: this stack uses 4 MCPs. Pro is needed for unlimited MCP connections - Starter ships with 1.

The Switchy Project a small product team runs the week from. Sonnet 4.7 as the default for spec drafting, ticket grooming, and turning a messy discovery call into a tight problem statement; Opus 4.7 when you need the hard reasoning — cutting scope on a roadmap, pressure-testing a bet, or untangling a dependency nobody wants to own; GPT-5 for a second opinion in a different voice and for structured output you'll paste straight into a PRD template. Linear keeps the work honest in the room: "@linear what's still open for this cycle", "@linear summarise everything tagged needs-spec". Notion is where the thinking lives: "@notion pull the latest from the positioning doc", "@notion draft a one-pager from this thread". Figma puts the design surface in the conversation — "@figma what changed in the latest frame" — so a PM, a designer, and the AI are reading the same artifact instead of three different screenshots. Slack is the connective tissue: "@slack catch me up on what eng flagged in #build overnight." The quiet win is that the *why* behind every decision stops evaporating. A Switchy Project remembers the trade-offs you made and the context you made them in, and that memory is exposed as an MCP server — so the same context shows up inside every teammate's Claude Code, Cursor, Claude Desktop, and ChatGPT automatically. When a new PM or a contract designer joins mid-quarter, they walk into the room with the full decision history already loaded, not a Notion archaeology assignment. Start free on Starter, stay solo as long as you want, invite the rest of the product team when you're ready — nothing to migrate.