PMPM shows up everywhere in health plan conversations, vendor pricing pages, actuarial reports, benchmarking decks, and it’s usually used correctly but rarely explained. Here’s the plain version.
What PMPM means
PMPM stands for Per Member Per Month. It’s a normalized way to express a cost, total spend divided down to a single, comparable unit: one member, one month. The formula is simple:
PMPM = Total Cost ÷ Member Months
The part that trips people up is “member months,” which isn’t the same as your current headcount. A member month is one member enrolled for one month. If your plan has 1,000 members enrolled for all twelve months of the year, that’s 12,000 member months, not 1,000. If membership fluctuates during the year, you add up the actual enrolled count in each month across the period.
A worked example
Say a plan spends $1.2 million over a year and averages about 1,000 members enrolled throughout that year.
Member months = 1,000 members × 12 months = 12,000 member months
PMPM = $1,200,000 ÷ 12,000 = $100 PMPM
That’s it. A plan running $1.2M a year with roughly 1,000 members costs $100 per member per month, a single number you can hold up against a benchmark, a budget, or a competitor’s number, regardless of how big or small either plan is.
Why PMPM instead of just “total cost”
Total cost tells you almost nothing on its own. A plan spending $2 million a year could be running lean on 25,000 members or running hot on 8,000. You can’t tell which without normalizing for size. PMPM strips out the size variable so you’re comparing rate, not scale. That’s what makes it useful for four different jobs:
- Budgeting. Once you know your PMPM trend, you can project next year’s cost against expected membership instead of guessing at a lump sum.
- Vendor and software pricing. A platform priced PMPM tells you the exact incremental cost of your next enrolled member, before you sign anything.
- Benchmarking. PMPM lets you compare your plan’s cost against industry, regional, or peer-group benchmarks that have nothing to do with your specific headcount.
- Trend analysis. Tracking PMPM over time shows whether your cost per person is rising, separate from whether your total spend rose just because you added members.
PMPM vs. PEPM, and why they’re never the same number
PEPM (Per Employee Per Month) is PMPM’s close cousin, and the two get mixed up constantly. The difference is who’s in the denominator: PMPM counts every covered member, employees plus every enrolled spouse and dependent. PEPM counts only employees (or subscribers), the person actually on payroll or holding the policy, full stop.
Because a PEPM denominator is always smaller than a PMPM denominator for the same population, you’re dividing the same total cost by fewer people, PEPM is always a higher number than PMPM for the same plan. If that same $1.2M plan has 1,000 members but only 400 of them are the actual employees (the rest are spouses and kids), the PEPM math is $1,200,000 ÷ (400 × 12) = $1,200,000 ÷ 4,800 = $250 PEPM, two and a half times the $100 PMPM figure, for identical total spend.
This is exactly why vendors pick whichever framing suits the pitch. A software vendor selling on “affordability” often quotes PMPM, because it looks smaller against a large member count. A vendor selling to HR against a headcount-based budget might quote PEPM, because that’s the number that maps to the org chart. Neither number is wrong, they’re answering different questions, but you need to know which one you’re being quoted before you compare it to anything else.
When a PMPM rate has tiers, ask how the tiers are applied
Plenty of vendors publish a PMPM that comes down as you grow. Far fewer are clear about how the lower rate gets applied, and the difference is worth real money.
There are two ways to do it.
Cliff pricing re-rates your entire population the moment you cross a threshold. Everyone moves to the new rate, including the members you already had.
Marginal pricing works the way tax brackets do. Each rate applies only to the members inside its own band. Your first 2,500 stay on the first rate no matter how large you eventually get.
Cliff pricing sounds like the more generous of the two. It produces strange results at the boundary. Take a platform charging a flat $3,500 platform fee, $5.00 PMPM up to 2,500 members and $3.25 PMPM above that. On cliff pricing:
- 2,500 members: $3,500 + (2,500 × $5.00) = $16,000 a month
- 2,501 members: $3,500 + (2,501 × $3.25) = $11,628.25 a month
Enrolling one more member cut the bill by $4,371.75. Nobody designs that on purpose. It is what happens when a rate change reaches backwards over members who were already being billed at the old rate, and it turns a number that should be a simple headcount into something both sides have a reason to manage.
Marginal pricing removes the effect entirely. Those same 2,501 members bill as 2,500 at $5.00 plus one at $3.25, which comes to $16,003.25. That is $3.25 more than the member before it, which is exactly what that member costs. Every additional member raises the bill by that member’s band rate, never by more and never by less.
So when a vendor quotes you a tiered PMPM, one short question separates the two: when I cross a threshold, does the new rate apply to everyone, or only to the members above it? If the answer is not immediate and plain, model your own bill at a few counts either side of each threshold before you sign anything. The boundary is where a pricing structure tells you what it really is.
The angle that actually matters when you’re buying software
Here’s the part worth sitting with if you’re evaluating a claims platform, not just reading about pricing units. A platform priced PMPM scales with your membership. A platform that also charges per-claim fees scales with your utilization. Those are genuinely different risk profiles, not two flavors of the same thing.
Membership growth is usually a good outcome, you’re growing, and a PMPM-only cost grows predictably alongside it. Utilization is a different animal: a rough flu season, a plan year with more surgeries, a team that finally clears its claim backlog, none of those are things you want to be financially punished for. A vendor charging per claim is charging you more in exactly the months your team is doing its job well or your members need more care. That’s a cost structure indexed to the wrong variable.
Claimaro is priced base plus PMPM, from $3,500/month + $5.00 down to $2.00 PMPM, with zero per-claim fees, ever. Your platform cost tracks your membership, the number you actually control and plan around, not your claim volume, the number you don’t. The ladder is marginal and published in full, so crossing 2,500 or 10,000 members lowers the rate on your next members without repricing the ones you already had.
See your own number
Benchmarks are useful, but your plan’s actual PMPM is what decides your budget. Run your member count through the calculator to see what a PMPM-plus-zero-per-claim model costs against your current stack, or read the full breakdown of what TPA software costs in 2026 for how PMPM fits into the rest of the pricing picture.