The per-seat price on a vendor's pricing page is a floor, not a bill. Salesforce publishes Sales Cloud seats from $25 to $550 per user per month, and the capabilities most teams assume are included (quoting at scale, agentic AI, advanced analytics) are priced as separate products. Budget the workflow you need, not the seat you were quoted.

Why does the seat price mislead so consistently?

A seat price is a single number, and single numbers are easy to compare. That is exactly what makes it the wrong number to plan against. It describes access to a product tier. It does not describe the work your team actually needs to do inside that tier.

Salesforce's published Sales Cloud pricing in September 2026 makes the gap legible, because the company documents the ladder in public. Seats run $25 per user per month for Starter Suite, $100 for Pro Suite, $195 for Core, $395 for Advanced, and $550 for Max, with most tiers billed annually. That is roughly a 2.8 times spread between Core and Max on the same product line, before a single add-on.

The spread is not the interesting part. The interesting part is what sits outside the ladder entirely.

What is priced outside the seat?

Three categories of capability that buyers routinely assume are bundled turn out to be sold separately.

Quoting is the clearest case. Sales Quoting and Forecasting appears at the Pro Suite level, but advanced revenue operations route to Revenue Cloud, listed from $200 per user per month. That add-on is priced above the $195 Core seat it attaches to. A team that describes its requirement as "CRM with quoting" has, without knowing it, described a purchase where the attachment costs more than the platform.

Agentic AI is the second. Agentforce for Sales starts at $125 per user per month as a distinct product. The pricing page adds that AI can be added to Core and above, and directs buyers to contact a sales representative for detailed pricing. When a vendor stops publishing a number, the number has stopped being simple.

Advanced analytics is the third. Tableau Next Agentic Analytics is marked as available for purchase through Tableau+ rather than included in the sales tiers.

Run the arithmetic on a 25-person sales team. Twenty-five Core seats at $195 per user per month is $58,500 a year. Add Revenue Cloud for the same 25 people at $200 and the annual figure becomes $118,500. The budget did not grow by a line item. It roughly doubled.

Where the gap shows up in practice

The pattern is visible well outside vendor documentation. A video posted on 2026-08-28 by the creator kylercheatham walked a buyer through this arithmetic and drew 81,191 views, 3,686 likes and 239 comments. The turn in it is the moment a buyer's stated requirements (quoting, customer service, dashboards) collide with what the seat actually covers. The reaction volume is the tell. The arithmetic surprised people who buy software for a living.

Smaller vendors hit the same wall from the other side. An r/SaaS thread posted on 2026-08-16, titled "Built our own licensing service instead of paying per active user", describes a team walking away from Keygen, Cryptlex, LicenseSpring and LemonSqueezy licensing because per-active-user pricing did not match how their product was actually used. They wrote their own and released it under an MIT licence. That is a build-versus-buy decision triggered entirely by a pricing model rather than by a missing feature.

A second r/SaaS thread, posted on 2026-08-25, asks whether the per-seat model is dying and frames the old economics plainly: you could charge $49 per seat forever and the numbers still worked, because building a competitive product used to cost millions and take years.

Which questions actually protect the budget?

Four, asked before signing.

Which of our required workflows are separate products? Write the workflows down in plain language (quote a deal, escalate a ticket, build a board report) and make the vendor map each one to a line item. Anything that maps to a different product name is a second purchase.

What does the tier above us cost? Seats get upgraded because a needed feature sits one tier up. Knowing the Core to Advanced step ($195 to $395) before you sign converts a future surprise into a planned decision.

Which numbers has the vendor stopped publishing? "Contact a sales representative" is itself information. It usually means the price varies by negotiation, which means your leverage matters and your renewal is not fixed.

What does leaving cost? Seat pricing is a rental. The exit cost nobody prices into a software decision is the data, the integrations and the retraining, and it grows every quarter you stay.

When does building change the math?

Not always, and not early. A seat price is genuinely cheap for a small team using a product close to the way the vendor imagined it. The math changes when two things are true at once: the workflows you need keep landing outside the included tier, and the per-seat cost scales with a headcount that is growing.

At that point the comparison is not software versus custom software. It is a recurring cost that rises with your team, set against a one-time cost that does not. We have written before about when a platform pays for itself and about the signals that a business has outgrown its SaaS stack. Both turn on the same variable this article is about: the total of the line items, not the headline seat.

If the mapped workflows keep resolving to separate products, custom software development is worth pricing as a real alternative rather than a fantasy. The point is not that building is always cheaper. Often it is not. The point is that you cannot run the comparison at all until you have the real number, and the real number is never the seat price.