Sign in

Team Plan

Expand a single-user habit into a shared workspace, pricing per seat while the shared workspace itself becomes the reason to stay.

Pro involved Pricing & Packaging Offers

What it adds

The builder uses your permission model, collaboration features, and account data to define a per-seat plan where the shared workspace, roles, and consolidated billing are the value, not merely multiple copies of the individual product. It converts because one enthusiastic user brings colleagues, and each added seat deepens the switching cost. The goal is expanding revenue inside existing accounts without new customer acquisition.

What your builder is told to do

7

The actual instructions, in order.
  1. 1

    Read the permission and collaboration source files and list every capability that only becomes meaningful with more than one person, such as shared assets, roles, review flows, activity visibility, or consolidated billing.

  2. 2

    Set the per-seat price against the individual plan and justify the difference with the shared capabilities rather than with a volume argument, since buyers immediately compare seat price to individual price.

  3. 3

    Define what a seat is with no ambiguity, covering whether seats are named or concurrent, whether inactive members occupy one, and how a removed member's work is retained.

  4. 4

    Establish the minimum and any included seats, then set the incremental seat price, and decide whether added seats are billed immediately, prorated, or at the next cycle.

  5. 5

    Build the invitation and role assignment flow as part of the offer itself, because the plan only delivers its value once a second person is inside, making activation the real conversion event.

  6. 6

    Add the administrative surface teams require before they will commit: a member list, role changes, seat count against billing, and a single consolidated invoice.

  7. 7

    Specify responsive behavior: on mobile, prioritise the member list and invite action with seat and billing summary collapsible; on tablet, show member management beside a persistent seat-and-cost summary; on desktop, present member list, roles, seat count, and projected charge together with inline editing.

Edge cases it handles

5

The things an agent skips when you only say "build a team plan".
  • Removing a member mid-cycle needs a stated billing outcome and a rule for what happens to their assets.
  • An individual subscriber upgrading to a team plan must retain their existing work and have their prior payment accounted for.
  • Teams that add and remove seats frequently will generate confusing invoices unless proration rules are simple and stated.
  • If roles and permissions are not actually implemented in the source files, the plan cannot promise them.
  • A single team member leaving the organisation while owning billing requires a defined ownership transfer path.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Seat definition covers named versus concurrent, inactive members, and removal handling.
  • Every shared capability listed exists in the source files.
  • Minimum seats, included seats, incremental price, and proration timing are all stated.
  • Invitation and role assignment are part of the purchase flow, not a later setup task.
  • An administrative view shows members, roles, seat count, and the resulting charge.
  • Mobile, tablet, and desktop layouts each present member management and billing summary as specified.
  • The builder reports which source files defined roles and collaboration features, and lists any seat or billing rule it had to assume.

Related offer files

Pricing & Packaging Offers

Multi-Product Bundle

Combine separate products into one subscription that solves a whole workflow, priced below buying each product on its own.

Build This Offer: Multi-Product Bundle

Pricing & Packaging Offers

License Renewal Offer

Renew expiring licenses by showing what was actually used during the term and what continued access protects going forward.

Build This Offer: License Renewal Offer

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.