Why FM classification pricing has to flex with volume

Quick answer: No, a facilities management classification engagement should not be priced as a flat annual fee. Monthly spend-line volume on the same contract can swing from around 500 lines to 20,000 depending on where the client sits in its project cycle. A model priced per line, with a rate that flexes to actual volume, absorbs that swing without a renegotiation, because classifying the next line costs the pipeline almost nothing either way.

On this page: FM spend volume swings by design · Flat fees assume spend that never moves · Why usage-based pricing fits FM · What a volume-flexible engagement looks like · FAQ

FM spend volume swings by design

I run delivery on most of our projects and I am the person clients call when something changes, so I am the one who watches this happen month to month. The pattern is consistent enough that I no longer treat it as unusual: a client's monthly spend-line volume on the same contract, the same sites, the same categories, can move from roughly 500 lines in a quiet month to 20,000 in a busy one.

The swing is not noise. It tracks the project cycle. A quiet month is business as usual: routine planned maintenance, a handful of reactive callouts, the usual supplier invoices. A busy month is a refurbishment landing, a new site coming onto the contract, or a portfolio-wide asset survey feeding a head-office mandate. Facilities teams already plan around this shape of spend. Capital works, seasonal shutdowns, and equipment replacement programmes concentrate cost and activity into short windows rather than spreading it evenly across the year, and the same concentration shows up in the transaction data underneath it.

What makes this a pricing problem rather than just an operational one is that classification and data quality work scales with the same line volume. Twenty times the lines is, roughly, twenty times the classification work in that month. An engagement priced to one snapshot of that volume, whichever month it happened to be sized on, is wrong for most of the months that follow.

Flat fees assume spend that never moves

A flat engagement fee is a bet that this month looks like next month. For a lot of professional services work, that bet is reasonable. It falls apart for FM because the underlying workload is not level, it is lumpy, and the size of the lump is set by the client's project calendar, not by anything we control.

Price the fee off a quiet month and the volume months overwhelm it. Reviews queue up, confidence scores get rushed, and the client feels the engagement thinning out exactly when a refurbishment or a new-site onboarding is the moment they most need the data to hold up. Price the fee off a busy month instead, and the client is paying for twenty thousand lines of capacity through the eight months a year they are sending five hundred. Neither number is dishonest. Both are wrong for most of the contract.

The usual patch is a scope renegotiation: the vendor comes back mid-contract asking for more money once the busy month lands, or the client tries to claw money back once it passes. Both conversations are avoidable, and both cost more in account management time than the volume swing itself would cost to simply price for.

Why usage-based pricing fits FM

The reason this is fixable for FM specifically, and not just a nice idea, is how the underlying classification work is built. Our pipeline classifies against a constrained taxonomy, applies the client's own rules, and routes only the lines it is genuinely unsure about to a person. That means the cost of running one more line through the pipeline, once the taxonomy and rules are set up, sits close to zero. It is nothing like the economics of a person manually reviewing spend, where every extra line is another chunk of someone's week.

That is the mechanism, not just the marketing line: a pipeline with near-zero marginal cost per line can price per line without the margin collapsing in a heavy month, because a heavy month is not disproportionately more expensive to deliver. A person-day-rate engagement cannot make the same offer, because a heavy month genuinely is more days.

Pearstop prices FM classification engagements to move with the client's own volume rather than a number fixed at kickoff, so a refurbishment month costs more than a quiet one and a quiet month costs less, for FM teams whose spend does not arrive at a level pace.

Set up correctly, this also removes the incentive problem that flat fees create on both sides. A client on a flat fee has a reason to under-report scope to keep the number down. A vendor on a flat fee has a reason to slow-walk a busy month rather than absorb the cost of it. A model that flexes with actual volume removes both incentives, because the price already reflects what is coming through, whatever that turns out to be.

What a volume-flexible engagement looks like

In practice this is a banded per-line rate rather than a single number: a rate per line within a normal range, and a lower marginal rate once volume in a given month clears a threshold, reflecting the fact that the pipeline gets more efficient, not less, at higher volume. There is no separate change order when a refurbishment lands. The invoice for that month is simply higher, sized to what actually ran through the pipeline, and the client has seen that shape coming because the same thing happened during their last onboarding.

I sit in the monthly review with most of our clients, so I am usually the first person to see the volume moving before it shows up on an invoice. A client bringing on a new site tells me two months out, not because the contract requires it but because they want the classification and the reporting ready when the site goes live. A rising line count is a signal I plan the month around, not a bill I hope survives.

The other side of this matters just as much: a genuinely quiet month should cost less to run, not the same as every other month. On a flat fee, a quiet month is where the client's spend quietly subsidises the vendor's margin. On a volume-based model, a quiet month simply looks like a quiet month on the invoice too. That is the pragmatic case for this pricing shape as much as anything else. It matches what the client is actually asking for, which is fewer surprises and a number that tracks reality, not an elegant contract structure for its own sake.

Frequently asked questions

Why does facilities management spend volume vary so much month to month?

FM spend is project-driven, not level. Routine planned maintenance and standard supplier invoices produce a steady baseline, but a refurbishment, a new site onboarding, or a portfolio-wide asset survey concentrates a large volume of transactions into a short window. The same client can generate a few hundred spend lines in a quiet month and tens of thousands in a month with active capital works.

Why does a flat-fee classification engagement not work for FM clients?

A flat fee prices the engagement to one assumed volume, usually whatever the contract was sized on at kickoff. When actual monthly volume runs far above that number, delivery quality slips under the extra load. When it runs far below, the client pays for capacity it does not use. FM volume swings by design, so a flat fee is wrong for most months in the contract.

How does Pearstop price a facilities management classification engagement?

Pearstop prices per line rather than as a fixed annual fee, so a heavy month with a refurbishment or new-site onboarding costs more and a quiet month costs less, matched to volume actually run through the pipeline. This works because the pipeline's cost per additional line stays close to zero once the taxonomy and client rules are set up, unlike a day-rate engagement where every extra line is more time.

What is usage-based pricing and how does it differ from a fixed fee?

Usage-based pricing ties the price to measurable consumption, such as the number of lines processed in a given period, rather than charging one fixed amount regardless of volume. A fixed fee gives predictable billing but assumes a workload that does not move much month to month. Usage-based pricing gives up some of that predictability in exchange for a price that tracks what was actually delivered.

Does a volume-based pricing model mean costs are unpredictable for the client?

Not in practice, because FM clients generally know their own project calendar well before the spend lands. A client planning a refurbishment or bringing on a new site can see the volume increase coming months ahead and plan the month's cost around it, which is a more accurate kind of predictability than a flat number that ignores the same information.

Rae Thomas

Director of Operations, Pearstop

Rae heads up operations at Pearstop, in both the traditional and non-traditional sense. She's as committed to the internal success of the business as she is to the value clients get out of it, which is why she leads delivery on most projects and is the main point of contact for clients throughout.

LinkedIn →