Back to blog

How to Answer a SaaS Buyer About Per-Seat Pricing on X

Find out which team members need paid seats, calculate an estimate from your published terms, and separate that price from anything needing a quote.

ReachFast cover about answering a buyer’s per-seat SaaS pricing question

When a buyer asks what your SaaS costs “for our team,” don’t multiply the headcount by a headline rate. Identify what each person needs to do, match those roles to your current seat definitions, and calculate only the price your published terms support. If the roles are unclear, ask one focused question before giving a total.

Find out who actually needs a paid seat

Start with the buyer’s work, not their job titles. “Ten people will use it” does not tell you whether all ten need to edit, administer, collaborate or only view. Ask: “Of the ten, how many need to make changes, and how many only need to view?” Then check your own current plan terms for the access each role requires. Don’t assume that a viewer is free—or that every invited person pays—unless your terms say so.

Seat rules can differ substantially by access level. For example, Figma’s billing guide describes Full, Dev and Collab seats that contribute to subscription cost, alongside a free View seat; it says plan type and seat type affect the cost. That is an illustration of why roles matter, not a pricing rule to apply to another seller’s product.

Calculate from the plan the buyer would purchase

Before doing the multiplication, verify the applicable plan, currency, rate for each paid seat type and billing period in your published terms. Check whether there is a minimum seat commitment, a base fee, a different rate for annual billing or an add-on the buyer needs. A per-seat rate alone cannot establish the whole bill if any of those conditions apply. If the buyer hasn’t chosen a plan, name the plan your estimate assumes rather than presenting its price as universal.

Here is a wholly hypothetical estimate. Suppose a fictional seller’s published Standard plan charges $18 USD per editor per month on monthly billing, permits view-only users at no charge and has no minimum seats or base fee. A fictional buyer confirms that six distinct people will edit and four other people will only view. The covered subscription price is 6 × $18 = $108 USD per month; the four view-only people add $0 under these assumed terms. This is a monthly estimate for that plan and those roles, not a verified price for any real product.

Now suppose the same buyer also wants an add-on whose price is not published. Keep $108 as the estimate for the specified seats, but do not call it the all-in total: the add-on requires a separate quote. If the buyer’s four viewers actually need editing access, recalculate after confirming the roles. If a published minimum or base fee applies, include it before sharing a figure. The point of the calculation is to show exactly which assumptions would change the answer.

Give the estimate without promising an unquoted total

For the hypothetical buyer above, a useful X reply would be: “If six people need editor access and four only need to view, our Standard plan’s published monthly terms put those seats at $108 USD/month: 6 editors × $18, with view-only access at no charge. The add-on you mentioned isn’t included in that figure; we’d need to quote it separately. Do any of the four viewers need to edit?” It answers the price question, states the plan and billing period, and makes the remaining decision easy for the buyer.

If the buyer has not supplied a role split, resist giving a single team total. You can still share a verified per-seat rate with its plan and billing period, then ask how many people need the paid access. If pricing for their configuration is available only by quote, say so rather than inventing a rate. Keep renewal dates and cancellation effects out of this seat calculation; those are separate questions covered in the subscription renewal and cancellation guide.

ReachFast says it finds and ranks relevant public X posts and prepares a reply that opens typed in the X thread for you to send. If it surfaces a pricing question, use the draft as a starting point: compare every seat, rate and total against your current terms and the buyer’s stated roles, then edit it before you choose to send. ReachFast helps you find the conversation; your published pricing determines the answer.

Sources

  1. Guide to billing at Figmahelp.figma.com
  2. SaaS lead generation from people asking on X | ReachFastreachfa.st

Your next customers are already asking on X

ReachFast finds people asking for your products on X, and ranks them by how ready they are to buy.

Try ReachFast