Runway introduced its Team plan on September 4 for groups of two to nine people. The company lists web access at $69 per seat per month, or $55 per seat per month with annual billing. For a small creative studio, the subscription now links collaboration to the number of seats it buys.
Runway says teammates can keep references, Brand Kits and work in shared projects, then comment on generations and mention colleagues. That gives an art director and motion designer a common place to review an idea. The company claims that shared context improves consistency; it has not supplied an independent comparison in this announcement.
For a hypothetical fashion campaign, a producer could use the shared project to identify the approved reference image and keep feedback beside a draft. The team would still need to check the garment's construction and the treatment of the person wearing it. This is an editorial workflow suggestion, not a report that a fashion client achieved those results.
Removing access does not reduce the bill
Runway's seat guide says an invitation adds a paid seat if none is free. On monthly billing, a new seat costs $69 even late in the cycle; the renewal date stays unchanged. Annual additions use the time remaining until renewal, rounded up to a month. Removing a member frees their seat for reuse. The administrator must reduce the seat count to lower the subscription at the next billing period.
A producer hiring a freelancer for a short finishing pass should check the renewal date before inviting them. Runway warns that a late-cycle addition can renew soon after its first charge. Our reading: put the invitation date and the intended seat-removal date into the production schedule, alongside the freelancer's delivery dates.
Budget for attempts and separate workspaces
Each Team seat contributes 6,900 monthly credits to a shared balance. Runway permits up to one month of unused pooled credits to roll over; purchased credits do not expire. Administrators can buy more or enable automatic refills. The company treats web-app and API credits as separate balances, so this subscription does not fund a studio's API pipeline.
Runway's credit guide prices Gen-4.5 at 12 credits per generated second. A ten-second attempt therefore uses 120 credits. As a planning example, ten such attempts use 1,200 credits before any other charged work. That calculation describes generation consumption, not ten approved shots or a guaranteed amount of usable footage.
An agency also needs to distinguish projects from workspaces. Runway bills each Team workspace separately, with its own subscription, seats and credits. Its documentation says creators can keep generations in private assets or shared project space. Our recommendation: decide who should see a client's material before choosing the workspace, then check the actual sharing state.
Runway directs organizations needing SSO or control over third-party model access to Enterprise. The company also says existing multi-member Standard, Pro and Max workspaces retain their current members and pricing; adding members now requires Team. Existing collaborators should check their own workspace before assuming they must migrate.