Team plan use cases — when collaboration is the bottleneck

Pro is for one operator. The Team tier exists for when MDM becomes a multi-person workflow.

Team tier is in the roadmap — the surface exists in product (org-scoped projects, review queues, audit log per actor), pricing/upgrade is still self-serve via Clerk. If you're a team of 2+ and need this conversation, email ben@bensevern.dev.

The Pro plan is built for one operator running pipelines. The Team plan exists for when MDM stops being one person's job and starts being a small group's.

This page is the honest "is your situation Team-shaped?" check.

What changes when MDM is a multi-person workflow

The interesting shifts aren't quota-related. They're collaboration-related:

Two people approving the same review item

Pro: one person decides every ambiguous merge. Team: two stewards work the review queue in parallel; the conditional-UPDATE first-decide-wins guard prevents conflicts. Audit log captures which person made each decision, not just "someone".

Edits to survivorship rules need review

Pro: you edit a survivorship rule, it takes effect. Team: a rule change is a "policy" change worth two sets of eyes — the team-plan UI (TODO: not yet built) routes rule edits through a pending-approval state. Until shipped, the audit log is the after-the-fact compensating control.

Each person owns a slice of sources

Pro: one person knows all the sources. Team: you've assigned the Salesforce ingest to one person, the data-warehouse export to another, the CRM cleanup to a third. They each need their own scope; org-scoped projects already support this (workspace vs team vs org).

Onboarding new team members

Pro: every step is "ask the person who set it up". Team: the docs you're reading, the workbench's terminal-panel aesthetic, the audit log of past decisions, the existing review queue — all of these are designed so a new steward can come up to speed without an active hand-off session.

When Team is not the right tier

Plenty of multi-person setups still fit on Pro:

• One operator + one approver. The operator runs everything; the approver signs off on the export. This is a single-active-user workflow; Pro is fine.
• Data engineering team handles infrastructure, business owns the rules. If the business side is mostly reading dashboards (not opening review queues), Team isn't unlocking anything.
• You're using the API to dispatch pipelines, not the UI. Concurrent-job caps matter more than collaboration features; Pro's 5 concurrent + API key auth is plenty until you're 10+ concurrent.

The decision rule

If two or more people will be opening the review queue this week, you're Team-shaped. If review-queue work concentrates in one person's hands (regardless of headcount), you're Pro-shaped.

The other Team-tier knobs (multi-source ownership, rule-edit approvals, per-steward audit trails) all flow from that one observation.

What's still TODO on the Team surface

Honest snapshot:

• Org-scoped projects + review queues: ✓ shipped (Phase 4 + 5.5-A)
• Per-actor audit log: ✓ shipped (Phase 5 + 5.5-B)
• Multi-steward review queue with first-decide-wins: ✓ shipped (Phase 5.5-A)
• Rule-edit pending-approval workflow: ☐ not yet — audit log is the compensating control today
• Self-serve Team-tier upgrade in Clerk Billing: ☐ pricing surface is Pro + Enterprise today; Team is sold via email contact until a third pricing card is shipped
• Per-org-member resource caps: ☐ Pro's 5 concurrent is per-org today, not per-member

If your team needs any of the ☐ items urgently, email ben@bensevern.dev — we prioritize on customer demand.

Pricing

Team tier pricing is not yet listed on /pricing. For now: email and we'll quote based on team size + source count. The shape will be public once the first 2-3 Team customers are in production and we have a credible mid-tier price.