Sign in

Per-Seat Team Offer

Price by the person, so revenue grows every time a customer adds a teammate to the workspace.

Pro simple Software Offers

What it adds

From the source files, the builder produces a per-seat offer where an admin invites members and billing scales with headcount. It converts by making the team, not the individual, the unit of value — collaboration features justify each added seat. The primary goal is landing an initial team and growing seat count as adoption spreads inside the account.

What your builder is told to do

7

The actual instructions, in order.
  1. 1

    Read the source role and pricing files first and define the admin, member, and any guest roles plus what each seat unlocks.

  2. 2

    Write a headline that frames the product as team infrastructure priced per person, not a solo tool.

  3. 3

    Build an admin invite flow where adding a seat is fast and the incremental cost is shown before confirmation.

  4. 4

    Surface the collaboration features that make each additional seat worth paying for.

  5. 5

    Show the running seat count and total, and define the billing trigger when seats are added mid-cycle (prorate now or settle at renewal).

  6. 6

    Give the admin a single "invite teammates" action and a plain seat-management view for adding or removing members.

  7. 7

    Specify responsive behavior: mobile gives admins a simple invite-by-email flow and seat total; tablet shows the member list with per-row actions; desktop shows the full team table with roles and billing summary.

Edge cases it handles

5

The things an agent skips when you only say "build a per-seat team offer".
  • A seat is removed mid-cycle — define credit or proration behavior per the source files.
  • The source files omit a per-seat price or minimum — flag it rather than assuming.
  • An invited member never activates — decide whether an unaccepted invite is billable.
  • Role permissions conflict (member needs an admin action) — define the escalation path.
  • Bulk invites exceed the plan's seat allowance — prompt to expand rather than silently failing.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Per-seat price and role definitions match the source files.
  • Adding a seat shows incremental cost before confirmation.
  • Collaboration features that justify each seat are visible.
  • The mid-cycle billing trigger for added seats is defined.
  • Seat-removal and unaccepted-invite billing rules are defined.
  • Mobile, tablet, and desktop admin/seat layouts are verified.
  • The builder reports source files used and flags unresolved price, minimum, or proration assumptions.

Related offer files

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.