Per-Seat Licensing and the Governance Tax: Why Software Pricing Models Shape Organizational Behaviour

Per-user software pricing looks reasonable on the quote. It appears fair — pay for what you use, seat by seat. But for organizations where broad visibility is the entire point of the system, per-seat licensing creates a perverse incentive: it quietly taxes you for involving more people. The result, documented in a recent analysis on xnm.ca, is that communities ration access, share logins, and leave the people who most need visibility staring in from outside.

This is precisely backwards for capital portfolio management. The value of a shared system grows when more of the right people can see the same accurate picture. A pricing model that charges per head turns inclusion into a line item and nudges leadership toward keeping the circle small.

The Behavioural Problem with Per-Seat Models

Software pricing is not neutral. It shapes behaviour. When every additional viewer costs money, the organization faces a recurring micro-decision: does this person need access enough to justify the cost? For a capital program where councillors, coordinators, finance clerks, and housing officers all legitimately need to see the same data, that question should not need asking.

The downstream effects compound. Restricted access leads to information requests — emails asking someone with a login to pull a number. Those requests take time, introduce lag, and create opportunities for error. The person who pulls the number may not know the context behind the request. The person who asked may not get it before the meeting where it matters.

Over time, per-seat pricing creates two classes within the organization: those who can see, and those who must ask. That division is corrosive to the shared accountability that good governance requires.

What the Market Charges

The xnm.ca analysis surveyed the per-seat landscape for platforms commonly considered by Indigenous and public-sector organizations:

• Laserfiche: typically $53 to $93 per user per month, with 5 to 25 user minimums.

• OpenGov: often $50 to $200 per user per month.

• Microsoft 365 E5: around $57 to $60 per user per month — and that is before assembling the roughly ten products needed to approximate a portfolio management system.

Every one of these grows linearly with headcount. For a community that wants its entire administration — perhaps thirty to fifty people — to have visibility into the capital portfolio, the annual bill becomes significant before considering implementation and administration costs.

The Alternative: Pricing Against Project Value

Project-value pricing ties the cost to what actually matters — the scale of the work being managed — rather than the number of people who need to see it. This model decouples access from cost. Adding a councillor, a coordinator, or a contractor representative does not change the bill. The incentive structure flips: instead of rationing visibility, the organization is free to extend it wherever it adds value.

As documented on xnm.ca, under a project-value model a $5M capital project runs approximately $55,000 in the first year and roughly $22,500 annually thereafter — regardless of whether ten people or a hundred people use the system. The cost is predictable, justifiable against the project's budget, and does not penalize the inclusive access patterns that good governance demands.

The Governance Argument

This is not merely a budgeting question. It is a governance question. In an Indigenous capital context, accountability runs in multiple directions: to community members, to council, to funders, and to partners. Each of these stakeholders benefits from visibility into project status, spending, and decision history. A pricing model that restricts who can see is a pricing model that restricts accountability.

Unlimited-user access means the whole council can check project status without requesting a report. Finance can see project milestones without chasing the project manager. Housing officers can see budget context without waiting for a monthly meeting. The information asymmetries that per-seat licensing creates are precisely the ones that erode trust within an organization.

How to Evaluate Pricing Models

When assessing software for capital portfolio management, these questions expose the real cost:

1. Model the bill at full adoption, not pilot size. Per-user costs that look modest for ten people scale uncomfortably across a whole administration.

2. Notice what the pricing discourages. If adding a viewer costs money, you will under-share exactly the visibility a portfolio needs.

3. Ask how new users are added. Is it an operational step or a contract renegotiation? The answer tells you how access will behave in practice.

4. Tie cost to project value. A fee that tracks the scale of the work is easier to justify and predict than one that tracks headcount.

The Bottom Line

Per-seat licensing is not merely expensive at scale. It shapes organizational behaviour in ways that work against the shared visibility, broad accountability, and inclusive governance that capital portfolio management requires. For communities where the whole team needs to see the same picture, a pricing model that penalizes inclusion is a pricing model working against you.

The alternative — pricing against project value with unlimited users — removes the penalty for doing the right thing: letting everyone who should see the portfolio actually see it. That alignment between cost structure and governance needs is not a minor detail. It is the foundation on which sustainable, accountable portfolio management is built.

Source

xnm.ca — "Stop Counting Seats: Why Project-Value Pricing Beats Per-User Licensing" (https://www.xnm.ca/post/stop-counting-seats-why-project-value-pricing-beats-per-user-licensing)