LogoLogo
Using BunnyDeveloper
  • Getting started
    • Welcome to Bunny
    • Superdesk - Sample SaaS Co.
  • Product tour
    • Admin UI
      • Tables
      • Forms
      • Search (beta)
    • Product catalog
      • What's a product?
      • Product quick start
      • Products
      • Features
      • Feature editor
      • Plans
      • Price lists
      • Charges
      • Coupons
      • Categories
      • Platforms
      • Tenants
    • Customer management
      • Accounts
      • Contacts
      • Deals
      • Subscriptions
      • Leads
      • Campaigns
    • Subscription management
      • What is a subscription?
      • Subscription states
      • Trial subscriptions
    • Quoting
      • What is a quote?
      • Quote states
      • Quote builder
      • Building a quote
      • Sharing a quote
      • Applying a quote
      • Undoing a quote
      • Amendments
      • Renewals
      • Cancellations
    • Approval workflows
      • How approvals work
      • Approvers
      • Approval rules
    • Customer portal
      • Viewing quotes
      • Invoice history
      • Paying invoices
      • Subscriptions
    • Billing
      • Bill runs
      • Invoices
      • Credit notes
      • Price adjustments
      • Proration
      • Billing day
      • Currencies
      • Sales tax and VAT
      • Payment methods and types
      • Payment plugins
      • Usage records
      • Revenue movements
    • Entities
      • Invoices
      • Quotes
      • Branding
    • Accounting
      • GL mappings
      • Journal entries
      • Revenue recognition
      • Intracom VAT summary
    • Workflows
    • Analytics
      • Using analytics
      • Trials
      • Monthly Recurring Revenue
      • Collections
    • Access control
      • Users
      • Roles
      • Groups
      • API clients
    • Settings
      • Company
      • Outbox
      • Jobs
      • Security
      • Single sign-on
  • Advanced guides
    • Integrations
      • Airbyte
      • Avalara AvaTax
      • Docusign
      • Dropbox Sign
      • HubSpot
      • Mailchimp
      • QuickBooks
      • PandaDoc
      • Salesforce
      • SendGrid
      • Slack
      • Stripe
      • Xero
    • Single sign-on
    • SCIM user provisioning
  • Best practices
    • Pricing by number of users
    • Committed + overage pricing
  • Release notes
    • April 22, 2025 release
    • Mar 28, 2025 release
    • Mar 13, 2025 release
    • Feb 27, 2025 release
    • Feb 13, 2025 release
    • Jan 24, 2025 release
    • Jan 16, 2025 release
    • 2024 Releases
      • Dec 19, 2024 release
      • Dec 12, 2024 release
      • Dec 9, 2024 release
      • Nov 21, 2024 release
      • Nov 14, 2024 release
      • Nov 1, 2024 release
      • Oct 25, 2024 release
  • Legal
    • Terms of service
    • Privacy
    • Subprocessors
Powered by GitBook
On this page
  • Recurring – enforced user limit
  • Usage-based - no user limit enforcement

Was this helpful?

  1. Best practices

Pricing by number of users

PreviousSCIM user provisioningNextCommitted + overage pricing

Last updated 3 months ago

Was this helpful?

A common way of pricing SaaS products is charging by the number of users, also sometimes called seats, agents or licenses. There are two common ways of modeling this:

  • Recurring - The customer pays for X users every month and the limit is enforced by the SaaS platform.

  • Usage-based - The customer is charged every month for the number of users they have at that particular time.

The next two sections go into more detail.

Recurring – enforced user limit

This model was been the traditional seat-based model used by companies like Salesforce and Zendesk. The customer buys a number of users which is then enforced in the SaaS platform. When the customer reaches the limit, they need to purchase more users which will increase the user limit in the platform. The charge looks like this in Bunny.

Usage-based - no user limit enforcement

This model is used by companies like Slack and is considered a more fair pricing model by some. Instead of committing to a number of users that you may or may not use, you only pay for the current number of users. Or in Slack's case, the number of active user.

One benefit of this model is that you don't have to enforce the limit in your SaaS platform and the customer can just add users as they need them without having to worry about the upgrade processs. A downside of the model is that it works best with monthly billing whereas with the enforce limit, you can get a customer to prepay annually in return for a discount.

In this scenario, your SaaS platform enforce a user limit, but sends Bunny usage records with the current user count. Bunny will then calculate the user count at the end of the customer's billing period using the usage calculation type.

  • Minimum - the customer is charged for the lowest count in the period

  • Maximum - the customer is charged for the largest count in the period

  • Sum - the customer is charged for the sum of user counts in the period

Your platform only needs to send one usage record per billing period, but since the billing day varies by account, you can also just report the numbers daily.

In this scenario, you need to have provisioning enabled in Bunny. When the subscription's seat limit is changed, Bunny will send a to your platform with the new seat count and user can now add more seats.

tenantProvisioningChange