Buying & budgeting
What performance management software really costs
A rate per user is the smallest part of what a performance platform costs. How the pricing models work, where the rest of the money goes, and what to ask before you sign.
By the CLEAR Talent team12 min read
Key takeaways
- The headline rate is one line in a three-year total. Implementation, integration and the modules you switch on later are usually what move it.
- Establish who counts as a billable user before comparing anything — managers only, everyone rated, or every record in the HRIS.
- Ask for implementation as a fixed number with a written scope. A percentage of licence fees is not a scope, and it grows with the thing it is a percentage of.
- Normalise every quote to cost per employee per year across three years, at the headcount you expect in year two.
- A published price list is not the same as a lower price. It means you can do this arithmetic before you talk to anyone.
Ask what performance management software costs and the answer is usually a rate that tells you very little: a figure per user, with no indication of which users are counted, what the platform does at that price, or what has to be paid before anyone logs in. Two quotes carrying the same headline rate can settle at very different totals once implementation, integration and the modules you actually need are added.
This guide is about the arithmetic rather than the rate. It covers the pricing models you will meet, the variables that move a quote, the costs that never appear on a price page, and the questions worth asking before the renewal is the thing that teaches you about them.
It deliberately publishes no “typical” market band. The spread inside any such band is wider than the band itself, it is out of date by the time you renew, and it cannot be checked. What is worth having instead is a method that turns whatever you are quoted into one number you can compare.
The shapes a quote arrives in
Before comparing numbers, work out which of these you are holding. Quotes in different shapes cannot be read line by line against each other, and vendors rarely convert for you.
- Per user, per month
- A rate multiplied by a user count, billed monthly or annually — often abbreviated to PEPM where the unit is the employee. It is the easiest model to read and the easiest to mis-compare, because everything rests on the definition of a user.
- A plan fee with an included allocation
- A flat monthly fee covering a set number of users, with a stated rate for each user beyond it. The cost per person falls as you fill the allocation, then steps when you cross it. Work out where your headcount sits relative to that step: just over it is the expensive place to be.
- Platform fee plus per seat
- A fixed tenancy charge on top of a per-user rate. The platform fee is the part that does not fall when your headcount does, so it dominates the cost per employee in smaller organisations and barely registers in large ones.
- Modular licensing
- A base licence with reviews, goals, 360° feedback, competencies, succession or analytics priced as separate lines. It looks competitive on the base licence alone, so build the quote from the modules you have decided you need rather than the ones in the first proposal.
- Quote only
- No published figure at any level. This is normal at the enterprise end and is not by itself a warning sign, but it means your first comparable number arrives after a discovery call — so the shortlist has to be built on capability and the cost tested afterwards.
Two quotes in different shapes are not two prices. They are two pricing models that happen to produce a number.
The variable that moves everything: who counts as a user
Every per-user model rests on a definition, and the definitions differ far more than the rates do. A platform billed for every employee record and a platform billed only for managers and administrators can quote near-identical rates and invoice very different amounts for the same organisation.
Get the answer in writing for each of these: employees who are rated but never log in; managers; HR administrators; executives who only read reports; leavers whose records stay for the audit trail; contractors, bank and agency staff; and seasonal people who are on the system for part of the year. In a performance platform specifically, ask about external raters too — a 360° cycle that pulls in peers from outside the licensed group is either included or it is not.
Then ask how the count is taken. A count on the first of the month, a peak count across the month and a contracted minimum are three different bills for the same workforce, and the difference shows up in exactly the organisations whose headcount moves.
None of this is a trick. It is a modelling decision each vendor made years ago and has stopped noticing, which is why it is rarely explained unprompted and almost always answered accurately when asked.
Published prices, “from” prices and quote-only
A price page tells you something even when the number on it is not yours: it tells you what the vendor is willing to commit to in public.
- A published list price
- Prices, allocations and add-on rates stated on the site. You can model your own cost before speaking to anyone, and any eventual invoice is measured against something public.
- A “from” price
- One starting figure with the conditions elsewhere or absent. Useful only once you know what it includes — the entry plan frequently does not contain the capability you are evaluating, which is what makes the figure quotable.
- Quote only
- The number follows a scoping conversation. Reasonable where deployments genuinely differ; it simply means cost cannot be a shortlisting filter, so decide your capability requirements first and let the quotes land against them.
Whichever you are dealing with, ask for the renewal rate in the same conversation as the first-year rate. A first-year discount that lapses is a cost you have already agreed to, and it is far easier to negotiate before signature than at renewal.
Work out the cost per employee per year, over three years
This is the calculation that makes two differently shaped quotes comparable. It takes about twenty minutes and it survives the demo.
Fix the headcount you are pricing
Use the headcount you expect in year two rather than today’s, and apply each vendor’s own definition of a billable user rather than one number across all of them.
Annualise the subscription
Take the monthly fee at that headcount, including every user above an included allocation, and multiply by twelve. Apply an annual-commitment discount only if you are genuinely prepared to commit for the term.
Add the one-off costs once
Implementation, configuration, migration and any integration build. These land in year one, which is precisely why comparing first-year totals alone flatters whichever vendor carries the higher subscription and the lighter setup.
Add the modules you will switch on in year two
Not everything you were shown — the things you have decided you need. Price them at the rate quoted now, and ask whether that rate is held for the term or reprices when you add them.
Add your own effort
Estimate the administrator days to run a cycle and the manager time to complete one, then price them at a loaded internal rate. You are allowed to be approximate. You are not allowed to leave it out, because it is the line that differs most between platforms.
Divide
Three-year total, divided by headcount, divided by three. That is your cost per employee per year — the single figure that puts a flat plan, a per-user rate and a modular licence on the same basis.
Run it twice: once at the headcount you expect and once at a headcount meaningfully below it. A model that only works if you grow is a commitment rather than a price.
Nothing in this method needs a market average. It needs the quote in front of you and an honest estimate of your own time.
The pricing questions to ask every vendor
Work through this with each shortlisted vendor and record the answers in one place. The value is in asking all of them the same questions, in the same order, before anyone mentions a discount.
Checklist
Performance management software pricing checklist
Five groups, from the definitions that make a quote comparable to the contract terms that decide what year three costs.
Before you compare any numbers
- The pricing model is identified: per user, plan with an allocation, platform fee plus seats, modular, or quote only.
- The definition of a billable user is in writing, including leavers, contractors and people who are rated but never log in.
- It is clear how and when the user count is taken, and whether a contracted minimum applies.
- The currency, the billing period and whether the rate is fixed for the term are all stated.
- The capability you are actually buying is confirmed to sit in the plan quoted, not a higher one.
On the subscription
- The rate for each user above the included allocation is stated, with any maximum the plan carries.
- The annual-commitment discount is quantified, and what happens if headcount falls mid-term is covered.
- Every module you expect to switch on later has a price now.
- Test environments, additional languages and additional legal entities are priced or confirmed as included.
- The renewal rate, any annual uplift and its cap are in writing.
On implementation
- Implementation is a fixed number against a written scope, not a percentage of the licence.
- The deliverables are listed: configuration, data migration, integration, training and go-live support.
- The number of configuration rounds included is stated, along with the rate for any beyond it.
- Responsibility for data mapping is agreed, and the handling of rejected records is understood.
- There is a realistic date by which a first cycle could actually run.
On integration and IT
- Each required integration is confirmed as existing today or identified as build work.
- Single sign-on is priced or confirmed as included in the plan quoted.
- The effort expected from your own IT and HRIS teams is estimated in days.
- Data residency, export format and what happens to your data at the end of the contract are answered.
- Any API access you need is confirmed as included rather than assumed.
Before you sign
- A three-year cost per employee has been calculated the same way for every shortlisted vendor.
- The model has been re-run at a lower headcount as well as the expected one.
- Internal administrator and manager time is included in the total, however roughly.
- Notice periods, termination terms and any early-exit charge are understood.
- Whoever will own the renewal conversation knows what was agreed and where it is written down.
Print this page or paste the list into your evaluation sheet. The comparison is only as good as its consistency — ask every vendor the same questions in the same order.
Comparing quotes that are not the same shape
Once every quote is expressed as a cost per employee per year, the remaining work is deciding what the difference buys. That is a capability question, and it is worth separating deliberately from the price question: a platform that costs more per head and removes a fortnight of administrator work from every cycle is not the expensive option.
Score capability before the final numbers arrive, against weights you set in advance. Deciding what matters after the discounts land is how organisations end up buying the cheapest quote and running a process they did not want.
Be equally careful in the other direction. A long feature list is not a reason to pay more if your first cycle uses six of the features, and the modules you never switch on still cost you in configuration decisions, training and the time managers spend working out which parts to ignore.
Where CLEAR Talent fits
CLEAR Talent publishes list pricing by plan rather than a single per-employee rate. The plans, what each one includes, the rates for additional staff and admin users, the annual discount, the free trial and the point at which an Enterprise plan is quoted instead are all on the pricing page — which exists so you can run the arithmetic above before you speak to anyone.
Setup is quoted against the package rather than published as a fixed figure, because implementation scope genuinely differs between a single team and a multi-site rollout. A number invented before the scoping conversation would be exactly the kind of figure this guide argues you should not trust.
One boundary worth stating when you compare a specialist quote with a suite quote: CLEAR Talent is built to run alongside an existing HRIS rather than replace core HR, payroll or applicant tracking. The two quotes are not covering the same ground, and the honest comparison is the total cost of everything you will actually be running.