why per-seat pricing breaks pulse surveys

almost every team-engagement tool on the market is priced per seat. usually somewhere between five and fifteen dollars per employee per month, billed annually, with a discount if you commit to a multi-year contract.

this sounds fine, until you notice what it does to the product.

the incentive that per-seat creates

if i'm a manager and the tool charges per person, every person i invite costs me money. so i invite the smallest defensible group. core team only. exclude the contractors. exclude the part-timers. exclude the new joiner because they don't have enough context. exclude the person who's leaving.

every one of those exclusions is locally rational. each one shaves a few dollars a month off the bill, and each one feels like a sensible decision in isolation.

in aggregate, they ruin the survey. the people you didn't invite are exactly the people whose feelings you needed to read.

why this matters more for pulse surveys than for other tools

per-seat pricing isn't a problem for tools where the value scales with the user. a project management product where one person is fine and ten people is better. a crm where seats really do correspond to incremental capability. paying per active user makes sense there.

a pulse survey is the opposite. its value is in the coverage of the population, not in the number of users. you don't get a better signal by adding the engineering team's tooling vendor; you get a better signal by including the contractor who's been on the team for nine months and has stronger opinions than half the full-time staff.

coverage is the whole product. per-seat pricing makes you ration the product to fewer people, which damages the product itself.

the failure mode in slow motion

here is what plays out, repeatedly, in teams that adopt a per-seat pulse-survey tool:

1. the team signs up and invites everyone for the first month. the vendor's onboarding wizard encourages this; they want strong activation.
2. the first bill arrives. someone with a budget runs the numbers.
3. the invite list gets pruned. usually the prune happens with a justification like "let's keep it to permanent staff," but the actual driver is the line item.
4. response rates drop, because the people pruned were also the people most likely to answer candidly. (the contractor with nothing to lose. the new hire with fresh eyes.)
5. the signal narrows, because the remaining respondents are demographically more uniform. the result starts to look the same week over week.
6. the team concludes the tool isn't very useful, and either churns or downgrades.

nothing in this sequence is a bug. it's the incentive working as designed.

"we'll just absorb the cost"

a lot of well-intentioned teams say this and mean it. they're going to invite everyone, eat the bill, and not let the pricing model warp their behavior.

a year in, almost no one is still doing this. budgets get scrutinized. someone in finance notices the line item. there's a layoff and the survey gets cut first because it's "easy spend." the contractor's invite quietly doesn't get renewed. the invite list reverts to whatever the cheapest defensible scope is.

structural incentives outlast individual conviction. that's not a moral failing of anyone involved; it's how budgets work.

flat per-team pricing aligns the incentive

the alternative is straightforward. charge per team — or per group of teams, if there are multiple managers — and let the manager invite every person on that team without thinking about it. the marginal cost of the next invite is zero. the cost-benefit of broader coverage stops being a manager-level decision and becomes a one-time vendor-level decision.

this is what we do at jollygig. $49/month for one team, or $129/month for up to ten managers in a group. doesn't matter whether you have 7 members or 70.

it's not philanthropy. our incentive is to make the product that works best, and the product works best when everyone on a team is invited. the pricing has to make that the cheap, default choice — otherwise the customer makes it the expensive, non-default choice, and the product quietly degrades in their hands.

why this isn't more common

two reasons.

first, per-seat is mechanically convenient. it sells well to procurement. it scales linearly with the customer's size, which means revenue grows naturally as the customer grows. and enterprise buyers expect it; their finance teams have models built around it.

second, per-seat pricing is what you charge when you don't know how to charge for value. it's the default. it's what you copy from the company down the street, especially if you've never examined what the per-seat assumption does to your specific product.

most pulse-survey companies copied saas defaults from project-management companies, and project-management companies copied saas defaults from email companies, and so on. nobody stopped to ask whether the model still made sense in the new context.

the practical effect

a small thought experiment: which sentence do you want a manager to be saying internally?

"do i really need to invite the contractor? she only joined three months ago. we'd save $15 a month."

or:

"yeah, invite the contractor. invite everyone. the more people answer, the more we'll actually see."

the first sentence is what per-seat pricing produces. the second is what flat per-team pricing produces. that's the entire argument.

if you've been hesitating to invite everyone on your team to a pulse survey because of the pricing, that's the pricing's problem, not yours. you can try jollygig free for 30 days, invite every member of one team, and see what an actual full-coverage signal looks like.