Design Billing and Seat Management
Collaboration & Enterprise · enterprise, pricing, trust
Updated 2026-07-28
- Show what will be charged before the action, not on the next invoice. Adding a person mid-cycle should state the amount and the date in the same dialog.
- Explain proration in one sentence with real numbers. It is the single most common billing support question and it is entirely preventable.
- Separate the people from the licences. Someone can be in a workspace without a paid seat, and conflating the two makes both lists wrong.
- Make it obvious what happens when a seat is removed:
- Whether their content stays and who owns it.
- Whether the seat frees up now or at renewal.
- Whether a refund or credit applies.
- Never silently upgrade. Crossing a plan threshold should be a decision with a confirmation, not a discovery at the end of the month.
- Keep the downgrade path honest. Say what will be lost, what will be kept, and what happens to data over the lower plan's limits before the change is made.
- Send invoices and receipts to someone who is not only the account owner, since the person who pays is rarely the person who administers.
- Warn about failed payments early and repeatedly, with a direct route to fix, because losing an account to an expired card is avoidable churn.
Billing is where a product's honesty is tested, and every unexplained charge costs more trust than the amount involved.
Related guides
UX Handbook