Design an institutional subscription around buyer, seats, and service

The buyer and the reader are different records

An institutional subscription usually has at least four roles: the contracting organization, billing contact, group manager, and individual reader. One person may hold several roles, but the data model should not assume that. Staff turnover should not erase the organization's entitlement, and replacing a reader should not create a new commercial contract.

Define what the buyer purchases: named seats, a seat band, domain-based access, site access, or a service bundle. Memberful's current group documentation is one primary example of software that separates a group manager from members and can exclude that manager from the consumed seat count. That capability illustrates the distinction; it is not a recommendation or a claim that every platform supports the same model.

Source notes: Add or remove group members

Package the group offer before setting the discount

Write the individual reader entitlement first: publications, archives, events, downloads, or research updates. Then add institution-level service: consolidated billing, seat administration, usage summary, onboarding, invoice documents, and a named support route. Do not promise custom research, unlimited training, or procurement work inside a seat price unless its capacity is modeled.

Choose a pricing unit that matches the control. Named seats support precise access but require adds and removals. Seat bands reduce invoice changes but create unused-capacity questions. Domain access simplifies joining but needs rules for contractors, alumni, shared domains, and verification. Site licenses need a clear eligible population. Stripe documents per-seat billing as quantity mapped to users; that is a billing pattern, not a complete access or contract design.

Source notes: Recurring pricing models

Cost the service layer as well as the content

Hypothetical offer: 25 named seats at $2,400 per year. Onboarding takes three staff hours, renewal and procurement take four, quarterly usage summaries take four total, and expected support takes six. At a $60 internal hourly rate, annual service labor is $1,020 before editorial production, payment cost, tax work, or platform fees. Gross revenue per contracted seat is $96, but the service layer consumes $40.80 per seat when all 25 are sold.

If only 12 seats are activated, the publisher still collected for 25 contracted seats under this hypothetical offer, yet reader adoption may threaten renewal. Track contracted seats, assigned seats, active readers, and buyer engagement separately. Never redefine low adoption as extra margin without considering the renewal risk and promised onboarding.

The example is planning arithmetic, not a market rate.

Run a buyer ledger and a reader ledger

The buyer ledger holds organization, billing contact, purchase order, invoice, term, renewal, promised service, seat allowance, and cash. The reader ledger holds person, organization, entitlement, assignment date, removal date, consent or communication preferences, and access activity under the publisher's policy. Link them with a stable organization subscription ID.

Before renewal, reconcile contracted and assigned seats, unresolved access, support work, service delivered, invoice status, and buyer feedback. Offer expansion only when additional seats or service solve an observed need. If the buyer declines, define how and when reader access ends and what reader data is retained under the applicable policy.

• Let the group manager administer readers without exposing billing controls unnecessarily.
• Define whether the manager consumes a seat.
• Record seat assignments and replacements without changing historical counts.
• Keep procurement and custom service out of the content-access promise unless priced.

Source notes: Add or remove group members