Pricing

Pricing

The platform carries a price. The judgement carries a scope.

Three commitments you can put a number against — a diagnostic, a build, and the cycle that runs afterwards — plus the advisory judgement, which is scoped after the baseline because the honest answer depends on what the baseline finds.

What it costs

Four commitments. Three of them carry a number.

Take the annual cycle and the build is waived. Prices exclude VAT.

Start here

Baseline

Find out what your data says.

€2,900 fixed fee
  • One pay-period extract, mapped and analysed in full
  • All seven prescribed figures on your own data
  • Every category of workers against the 5% threshold
  • The decomposition: how much of each gap grade and tenure account for
  • Both remediation strategies, costed per category
  • One session to walk through the findings
A private diagnostic. Nothing is filed, and the analysis stays with you whatever you decide next.
Waived on annual commitment

Implementation

The platform, built in your subscription.

from €3,900 fixed fee
  • The governed data layer: every pay component, every source, versioned inputs
  • Your categories and evaluation scores carried into the model as dimensions
  • The disclosure threshold configured, with the reasoning recorded
  • The 16-page report suite deployed under your access model
  • Read-only by default, in your own Azure environment
Waived if you take the annual cycle. Payable only if you want the build without the subscription. Connection takes days; first governed reports follow inside the first week.

Annual cycle

The obligation, run.

from €2,000 /month
  • Refresh, validation and the ministerial report each cycle
  • Answers to employee information requests from the same model
  • The scenario modeller for remediation planning
  • Data held at category level between filings, so drift is visible early
  • Priced by headcount band
Includes the build. Employers of 150 to 249 file every three years and are priced per reporting cycle instead of monthly.

Advisory

The judgement the platform cannot make.

On scope by one of our experts
  • Job evaluation across all five statutory factors, including soft skills
  • Categories of equal work drawn, tested and justified
  • The methodology documented so it can be defended if it is questioned
  • Remediation strategy and the sequencing of it across pay rounds
  • Support through a joint pay assessment where a category stays above threshold
Delivered by one of our experts. Priced on scope after the baseline, and optional — if your job architecture already holds, you do not need it.
The subscription is billed monthly on an annual commitment that rolls. Your data stays in your own Azure subscription, and the exit is a standard SQL export with the mapping documented.
Why it is shaped this way

Six questions this page has to answer.

The line that matters runs between the first three commitments and the last. Everything else follows from where that line sits.

Why is the baseline a separate fixed fee?

Nobody can price the build honestly before seeing how the pay data is actually held, and you should not commit to a programme before seeing what your own numbers say. So it stands alone, and the analysis is yours whether or not anything follows.

Why is implementation priced *from*, and then waived?

The variable is not headcount, it is how much reconstruction the pay data needs — how many systems the components sit in and how far apart they are. The baseline is what makes that knowable. Take the annual cycle and we waive the fee entirely: the build pays for itself over the commitment, and you are not asked to fund a setup before you have seen the thing run. The figure stays on the page because a waived fee anchors what the build is worth.

Why is the cycle a subscription rather than a project?

Because the obligation recurs. The first report is due 7 June 2027 and every one after that on 15 April — and between them sit the employee information requests, which arrive whenever they arrive. The data has to be held at category level in between, which is a service, not a delivery.

Why does Advisory carry no number?

Deciding what a job is worth, which roles are equal work, and what a category can be defended as, is judgement. Pretending otherwise is how these projects go wrong. It is delivered by one of our experts, scoped after the baseline, and it is optional — if your job architecture already meets § 3(1), the platform runs on it as it stands.

Why are employers of 150 to 249 priced differently?

They file every three years rather than every year, so that band is priced per reporting cycle instead of monthly. The work is the same shape; it just recurs on a different clock.

What happens to the data if we stop?

It never left. The model sits in your own Azure subscription throughout — your residency, your ownership — and the exit is a standard SQL export with the mapping documented.

Next

Start with the baseline.

One pay-period extract, mapped and analysed in full. If the picture is one you would rather handle another way, nothing obliges you to continue and the analysis stays with you.