One plan your whole team builds from

Stop rebuilding the same argument in three documents. The plan is one artefact, versioned, with the reasoning visible to everybody who has to deliver it.

One artefact, one version, one argument

The cost of a team without a plan is not the missing document. It is the same disagreement re-litigated in three places — a deck, a thread and somebody’s notes — until the version a developer quoted against is nobody’s current one.

A versioned plan makes "we agreed something different last month" a question with an answer.

The problems this is for

What the team tier adds

Everything in Individual, plus what changes when more than one person owns the work.

Shared workspace

Two to ten seats on one workspace. Everyone sees the same plan, at the same version.

Plan versioning

Every revision kept, so "we agreed something different last month" is a question with an answer.

Comment threads

Disagreement happens on the section it is about, not in a reply-all.

Pooled credit

One balance for the team rather than a card per person.

Priority reviewer matching

Reviewers who already know your sector get your work first.

Exportable specs

Hand a dev shop something they can quote from without a fortnight of back-and-forth.

What teams ask before they add seats

How many people can share a workspace?

Five on Pro and no cap on Max. The pricing page lists the limit for every tier, and every row on it is a limit the platform actually enforces.

Does everybody need their own credit?

No. Credit is pooled at the workspace, so it is one balance for the team rather than a card per person.

What happens when two of us disagree with the plan?

The disagreement lands on the section it is about, as a comment thread, and every revision is kept. That is what makes “we agreed something different last month” a question with an answer rather than an argument.

Put the whole team on one plan

Start free, add seats when the argument needs more than one person in it.