Explain Per-Seat Pricing Without Surprises

A per-seat price looks simple until the buyer asks who counts as a seat and what happens when the team changes. Those details belong in the first serious quote.

Read the signal

Administrators, occasional users, contractors, and inactive accounts may be treated differently. A buyer budgeting from an incomplete headcount can be surprised later even if the unit price was accurate.

Make the next move

Define the billable seat in plain language. Show the assumed headcount, any minimum, true-up timing, and how seats can be removed. Ask the buyer to check the roles included in the estimate.

Language you can adapt

Illustrative wording:

This quote assumes 40 billable users and excludes read-only access. Does that match how your team would use the product?

The wording is a starting point. Replace the problem, evidence, and request with details the buyer actually gave you. If those details are missing, ask a question before sending a polished message. Specificity makes it easier for the buyer to correct your understanding and easier for you to see whether the opportunity is moving.

Decide what happens next

Revise the estimate when the roster changes. If your pricing policy is complicated, provide a worked example approved by finance rather than relying on verbal reassurance.

Write the result in your deal notes as an observable fact: who responded, what they agreed to do, and when. A friendly reply is useful, but a decision, a named owner, or a scheduled review tells you more. If the next step remains vague, treat that as information about the deal rather than a reason to send the same follow-up again.

Use these examples responsibly. Describe your product, pricing, and customer results accurately, and adapt every suggestion to the buyer’s stated process.