Ownership, assignment, and status rollups across the team's work.
When your week disappears into "who's working on what" Slack threads, the answer should be "the workspace tells me." m18t's team layer makes ownership and status visible at the level that matters — features, content, releases, events — across every brand the team owns.
Team features ship in Q3 2026.
m18t today is single-operator-shaped with multi-brand awareness. The team layer (multi-user-per-tenant, assigned-to fields, ownership, roles, granular permissions) is the next major release. Multi-user-per-tenant is near-complete; ownership and permissions land in the next iteration.
This page describes what's coming. Until shipped, your team's needs are partially served by /for/founders and /for/product-teams. If formal team support is a hard requirement for you today, wait for the Q3 release — and tell us at contact so we can keep you informed when it lands.
The surfaces that change when the team layer ships.
PD workspace with ownership
Every feature, model, controller, event has an owner. The team lead sees their own queue, the team's queue, and what's stalled — without asking. Status rollups extend to per-person and per-brand filters.
Content + assigned-to
The editorial queue with owners and due dates. Writer → editor → publisher handoff is clear. Marketing leads see what's in each lane.
Whiteboards for team rituals
Planning sessions, retros, project kickoffs — with the actual team's entities on the canvas. Boards stay relevant because they reference real entities the team owns.
Status rollups by team or brand
Same opinionated status set, seen across the work the team owns. Mine / theirs / stalled / due-this-week filters reflect actual ownership, not just project labels.
Per-brand role assignment
For agencies and multi-brand teams: which team members work on which brand, with brand-scoped permissions. No accidental cross-client edits.
Stop recovering state in 1:1s.
Today, most team leads spend mornings recovering state — checking Linear, scrolling Slack, asking the engineers what they\'re actually working on. The 1:1 becomes a status-update meeting because the workspace doesn\'t give a clean answer to "what does each person own and where is it?"
m18t\'s team layer makes that answer visible — with the same brand-switcher and the same status set the team already uses. PD entities show owners. Content pieces show editors. Release artifacts show authors. The team lead opens m18t and sees the picture without asking.
1:1s go back to being about people, not state.
Frequently Asked Questions
Get on the list for the team-features release.
Sign up now to be ready when it lands. Or contact the founder if your team has specific needs we should hear about.