Project Management Cost Calculator

A project management platform bills per seat, and the invoice is the part everybody sees. The part that does not appear on it is the person who configures the workflows, maintains the templates, manages permissions, builds the reports and answers the questions. This calculator adds that second cost to the first.

At the default figures the split is stark. Fifty seats at 15 a month is 750, and eight hours of administration at 40 an hour adds 320, taking the monthly total to 1,070 and the annual to 12,840. That works out at 256.80 per user per year, and 29.9% of it is staff time rather than subscription.

Licence rates vary by platform, by tier and by contract, and any figure printed here would be stale before it was useful. The rate that belongs in the field is the one on the current invoice, at the tier actually in use.

Two structural things about that rate are worth knowing, because neither is visible in a single monthly number. Per-seat pricing usually steps up sharply between feature tiers rather than sliding, so the marginal cost of one capability can be the whole difference between tiers across every seat. And most vendors discount an annual commitment against monthly billing: at the defaults, a 15% annual discount takes the per-seat rate to 12.75 and the monthly total to 957.50, worth 1,350 a year.

Running more than one platform across different teams duplicates both halves of this calculation. Two tools mean two subscriptions and two sets of administration, and the administrative half rarely halves on consolidation because the surviving platform absorbs the workflows of the one that went.

The counterweight is real rather than rhetorical. No single platform suits every team equally, and a consolidation that leaves one function fighting the tool trades a licence line for lost throughput that never appears on any invoice. Running the calculation twice, once per current platform and once for a consolidated estimate, at least puts the licence and administration side of that trade in figures.

Quick example

With users of 50 and cost per user monthly of 15, plus admin hours monthly of 8 and an admin hourly rate of 40, the result is 1,070.00 a month. The supporting rows show 12,840 a year, 750 of licence, 320 of administration and 21.40 per user per month.

Which inputs matter most

Users and cost per user each move the total 0.70% per 1% change, and admin hours and admin rate each move it 0.30%. Those four figures are simply the two components' shares of the bill, so the ordering follows the shape of the deployment rather than anything general.

Within each pair the two inputs are interchangeable, since only their product enters the sum: fifty seats at 15 costs what twenty-five at 30 costs, and four admin hours at 80 costs what eight at 40 costs. That matters mainly for the admin rate, which is commonly entered as a salary-derived hourly figure when the employer cost is higher. Raising it from 40 to 60 to reflect employer contributions and overhead takes the monthly total from 1,070 to 1,230.

What is happening under the hood

Total is users multiplied by the cost per user, plus admin hours multiplied by the admin hourly rate. The annual figure is twelve times that, and the per-user total divides the monthly figure across the seat count.

Everything is linear. Per-seat cost does not step down with volume, so a negotiated or tiered rate has to be entered rather than derived, and administration is charged at one flat rate regardless of who does it or how many hours it takes.

Subscription is only half the cost

Tooling cost is only half the picture when the tool needs administering. At the defaults, 50 users at 15 a month is 750, while 8 admin hours at 40 an hour adds 320, taking the monthly total to 1,070. Nearly a third of the cost is staff time rather than subscription.

There is a third component the calculator does not ask about, and it is usually the largest avoidable one. Seats are billed as provisioned, not as used, so leavers who were never deprovisioned, contractors whose engagement ended and occasional users who log in twice a year all cost full price. On the default figures, 20% of seats sitting inactive is 150 a month, 1,800 a year, and 14% of the entire bill. A seat audit against actual login activity is the one exercise here that costs nothing and is measurable directly from the platform's own reporting.

Why admin hours are worth measuring

Admin hours are the input worth measuring rather than estimating. They tend to rise with the number of integrations, custom workflows, and reporting requirements rather than with user count, so a small team running a heavily customised setup can spend more administrative time than a larger one using defaults. Onboarding and training time during rollout is not captured here, and neither is the productivity effect the tool is presumably bought for, which sits on the other side of the ledger.

Two bodies are worth knowing on either side of that ledger. The International Project Management Association is a federation of national project management associations that maintains competence standards and certification, which is the discipline the tool is bought to support. On the cost side, the FinOps Foundation framework sets out an operating model for managing technology spend, and the practices it describes for allocation and rate optimisation apply to per-seat software as readily as to infrastructure.