Repricing a Per-Employee Retainer the Day Headcount Jumps by Forty

A per-employee-per-month HR retainer is closer to a metered subscription than a flat one, since the price scales directly with a number, headcount, that the client doesn't fully control and that can jump for reasons entirely outside the advisory relationship, like an acquisition. Both Stripe Billing and Chargebee support per-unit pricing tied to a quantity, but the mid-cycle update behavior, what happens to the price when that quantity changes partway through a billing period, is where the two platforms actually diverge in practice.

In Stripe Billing, updating a subscription's quantity mid-cycle triggers a proration by default: the client is charged an additional prorated amount for the remaining days in the current cycle at the new headcount, and the next full cycle bills at the new rate going forward. This is accurate and automatic once the quantity update is made, but someone or something has to actually update that quantity when headcount changes, since Stripe has no way of knowing about the acquisition on its own. If your firm doesn't have a live feed from the client's HRIS, that update happens manually, and the accuracy is only as good as how quickly someone catches the change.

Chargebee handles mid-cycle quantity changes similarly, with proration options that are more configurable through its interface, letting a non-technical account manager choose immediate billing, prorated billing, or deferring the change to the next cycle without touching code. For a firm running several per-employee retainers where headcount changes are relatively common, that configurability, and the ability for account managers rather than developers to make the call each time, is often the deciding factor over Stripe Billing's more code-driven proration handling.

Say a client is billed per employee per month for 200 employees, and on the fifteenth of a thirty-day billing cycle, an acquisition brings headcount to 240. In either platform, updating the subscription quantity from 200 to 240 on the fifteenth generates a prorated charge for the additional 40 employees covering the remaining fifteen days of that cycle, and the next full cycle bills at 240 employees. The client sees a modestly larger charge that month and a clearly higher recurring rate going forward, both traceable to a specific, documented headcount change rather than an unexplained price increase.

The billing mechanics work well in both platforms once someone updates the quantity, but neither one monitors a client's actual headcount or flags an acquisition on its own. Build a process, a quarterly headcount confirmation with the client at minimum, or a direct HRIS integration if the volume justifies it, so mid-cycle changes get caught close to when they happen rather than discovered three months later when a client mentions the acquisition in passing and your firm realizes the retainer has been underpriced the whole time.

Some firms, uncomfortable raising a mid-cycle charge, wait until the client's annual renewal to apply a headcount-driven price increase, even when the actual headcount jump happened months earlier. That approach is simpler in the moment but leaves real revenue on the table for however long the gap runs, and it also means the client's contract terms and actual usage were out of sync the whole time, which is a harder conversation to have retroactively than a small prorated charge would have been when the change actually occurred.

The firms that handle headcount-driven repricing smoothly tend to set expectations at the start of the engagement rather than treating each change as a one-off negotiation. State in the engagement letter, in plain terms, how often headcount will be confirmed and how a change flows into the recurring rate, so a client isn't surprised by a mid-cycle prorated charge the first time an acquisition or a round of hiring changes their number. That upfront clarity turns what could feel like an unexpected bill into a routine, expected part of how the retainer works.

Set up headcount-driven repricing with these habits:

• Bill the retainer as a per-employee subscription so a quantity update reprices the client automatically, prorated for the remaining days in the cycle.
• Confirm headcount with the client at least quarterly, or use a direct HRIS feed once the volume of retainers justifies it.
• Update the subscription quantity as soon as you have a reliable headcount, instead of waiting for the annual renewal.
• Apply decreases the same way as increases, so an overpriced retainer doesn't continue after a layoff.
• State in the engagement letter how often headcount is confirmed and how a change flows into the recurring rate.