Personio migrates its installed base off employee-band pricing onto PEPM, with a list-price increase and standardised annual contracts

On 27 August 2024 Personio published two near-identical customer-facing migration pages within two minutes of each other — personio.com/pricing-updates-v6/ (JSON-LD datePublished 2024-08-27T12:22:46Z) and personio.com/pricing-updates-v5/ (12:20:44Z), each with a German twin at personio.de/preise-update-v6/ and -v5/. Both were still live and archived more than a year later. They are the clearest artefact of a repricing programme in the corpus: a vendor writing down, for its own customers, exactly what it is changing and what they may object to.

What the notice says, in Personio’s words. On the model: “Instead of our previous pricing model where you would pay for a range of employee seats, you now pay for the employees you expect to have. … Your total price will be your per-employee-per-month price x # of employees, minus any discounts.” On the increase, under the heading “Why did my list price increase?”: “We have invested heavily in building requested new features … Additionally, our costs have increased due to increased staffing costs, as well as that we are unable to decrease costs elsewhere in our business to accommodate this overall increase in operating costs.” On contracts: “Our contracts have been annual for some time, and we are now standardising this for all customers.”

The objection window is the striking part. The notice enumerates four things a customer may refuse — “Moving to our new PEPM price model; Increase in your list price (price before any discounts) - if applicable; Moving to an annual contract - if applicable; Changes to our General Terms and Conditions” — with the v5 cohort getting a fifth, “Moving to our new package structure”. Customers had “two weeks from when you receive your subscription notice” to object via a link in the email, and Personio states the consequence plainly: “if we are unable to resolve your objections, this may result in your subscription coming to an end.” That two-week window is the same one written into §12.4 of the General Terms, which lets Personio raise list prices annually “to compensate personnel cost or other cost increases” and gives the customer a right of objection only where the increase exceeds 5%.

The ratchet is asymmetric, and the notice says so. Users can be added at any time, invoiced the following month for the remainder of the term. Reductions “can be requested any time outside your subscription notice period but will not be implemented until your next contract renewal”, and “downgrades in your subscription may result in the reduction or removal of any discounts on your subscription”. Meanwhile the allowance definition widened: it now “will also include any onboarding and on-leave employees”, and Personio recommends “including a 15% buffer in your employee allowance to support any future expansion in employee count” — a documented instruction to over-commit.

Two dated details from the archive that the notice does not mention. The annual-upfront discount doubled: /pricing/ still read “a 5% discount on software services” in its 2024-08-27 09:42 capture and read “a 10% discount” by 2024-09-12, so the incentive to prepay a year doubled in the same release that made annual the default. And the v5 page — but not v6 — mentions a Core Lite plan alongside Core and Core Pro (“Optimise your plan between Core Lite, Core, and Core Pro”) that never appears in the comparison table on the same page and has never appeared on any public Personio pricing page since. Whether Core Lite shipped, and to whom, is unverified.