Should we switch to per-seat pricing to boost team adoption for saas?

[HarperCH]

I've invested in some nice landscaping but struggle to keep everything maintained. What are your essential landscaping maintenance tips? I'm looking for advice on regular care schedules, seasonal tasks, and preventative measures. Also interested in garden tools recommendations that make maintenance easier.

[David_J]

I’m trying to decide if we should switch our SaaS product to a per-seat pricing model, but I’m worried it will actually discourage team adoption. Right now we have a flat monthly rate for unlimited users, which our bigger clients love, but our costs scale directly with their active users. I can’t tell if moving to a per-user charge would stabilize our revenue or just make our product less attractive for collaboration.

[Addison39]

We ran a six month pilot of per seat. Early on it felt like price friction—teams worried about monthly bills when new folks joined. Adoption dipped in some departments, and admins complained about tracking seats. We paused and kept unlimited for core teams while offering optional seats for collaboration.

[BenjaminP]

On the enterprise side, the flat unlimited plan is a budget anchor. Per-seat pricing felt like price creep as projects grew, and a few buyers pulled back at renewal time even if usage stayed high.

[EvelynIL]

We tried a hybrid: internal users on unlimited, external or contract collaborators on per-seat. It helped with budgeting and made leadership feel in control, but it also created resentment in teams where the value was the same.

[AbigailW]

Maybe the real issue isn't pricing. We improved onboarding, added short videos showing team wide ROI, and saw engagement improve more than any pricing tweak.

[Jason97]

We did a small policy change: cap seats at 25 and offer additional seats with a trigger (milestone). It softened the surprise when a new project started.

[AaronHC]

If you can prove value with usage data, you might keep unlimited and price by features instead of seats. Do you think the real driver is value not volume?

[RyanQJ]

Sometimes the easiest win was to simplify the admin experience: fewer price changes meant less back and forth with procurement. We traded that for better docs and an internal glossary; adoption still varied by team, but procurement headaches eased a bit.