5-person startup
Overview
Section titled “Overview”Team is sized for a five-person company: five seats and five projects, with sprints and unlimited MCP handoffs. That is enough to plan in GrowthOS and execute Native (board, Today, My Tasks) plus coding agents.
Roles vs seats: Org roles are Owner / Admin / Member / Viewer. Seats are Planner vs Viewer. Today personas (pm / engineer / designer / viewer) are UI slices, not extra RBAC.
Do not buy Team expecting Jira/Linear sync. integrations.connected is Enterprise / design-partner. Slack, if enabled, is notifications only.
Who / time / plan
Section titled “Who / time / plan”- Who: Founding team of about five people
- Time: First week of setup
- Plan: Team: 5 seats, 5 projects, sprints, unlimited MCP. Connected is still off in the plan table.
What you can do here
Section titled “What you can do here”- Assign one Owner (usually the founder) who is also a Planner.
- Give engineers Member + Planner (or Viewer if they only execute).
- Keep Native + agents as the default execution path.
When to use
Section titled “When to use”- You are five people (or fewer) leaving a shared spreadsheet / Notion / chat backlog.
- You need sprints this week, not a Connected evaluation.
Prerequisites
Section titled “Prerequisites”- Someone who can change billing to Team.
- A project with a backlog before you invite everyone.
Where to find it
Section titled “Where to find it”- Plans:
/org/billingor Billing docs. - Invite:
/org/invite. Roles: Organization → Roles & seats. - Today personas:
/today.
Step-by-step
Section titled “Step-by-step”- Upgrade to Team if you need five seats and sprints (Pro also has sprints but fewer seats/projects).
- Create Path A or Path B project and get a backlog before invites.
- Owner stays Planner. Invite eng as Member/Planner, designer as Planner if they own UX Spec, one Viewer if needed.
- Each person opens Today and picks the persona that matches their day.
- Engineers connect MCP keys (one key per user). Designer uses UX Spec / Figma playbook.
- Skip
/org/integrationsunless you are an Enterprise design partner.
What success looks like
Section titled “What success looks like”- Five seats filled against real people. One Native board. Agents on Native tickets only.
- Nobody is waiting on Jira sync that Team does not include.
Tips & best practices
Section titled “Tips & best practices”- Do not share one
gos_key across the company. - Viewer seat is enough for a stakeholder who only comments.
Common mistakes
Section titled “Common mistakes”- Inviting five people to an empty workspace.
- Assuming Team unlocks Connected.