Ask three vendors what their claims administration platform costs and you’ll get three answers that aren’t comparable, because the price of running a TPA isn’t one number. It’s a stack of them, and a couple of the biggest ones don’t show up until you’re already committed. Here’s the honest breakdown for 2026.

A quick note on scope: these are published industry benchmark ranges for the software, the platforms that administer a plan. What it takes to stand up the TPA itself, and the licensing and bonding behind it, is a separate conversation for your own advisors. This is about the technology bill.

The five things you’re actually paying for

1. Setup / implementation. A one-time build-out. Mid-market claims platforms run $25,000 to $150,000; enterprise payer systems run $500,000 to $3 million. This is where a legacy migration and configuration project lives, and it’s why so many TPAs can’t afford to say yes to a small new client.

2. Base platform fee. A monthly floor whether you process one claim or a million. On mid-market systems this alone is often $10,000 to $20,000+ a month before anything usage-based.

3. PMPM (per-member-per-month). A charge on every covered member, typically $2 to $6 on mid-market platforms, $8 to $10 on enterprise ones.

4. Per-claim fees, the one that compounds. Many platforms bill $0.50 to $2 for every claim processed. Read that again: the more claims your team works, the more you pay. It’s a fee that grows with your throughput, a tax on doing the job well, and it’s the line item most likely to be quietly larger than you budgeted.

5. The other six vendors. The claims payer is one system. Enrollment (Employee Navigator, bswift), a clearinghouse, a member portal, billing and payments, a CRM, and a communications platform are five or six more, each with its own setup, per-seat, and per-transaction fees, and its own integration to maintain.

Add it up and a mid-market TPA stack lands somewhere around $11,000 to $78,000 a month all-in, on top of the setup, most of it fixed, and the fastest-growing part indexed to your own success.

Why the per-claim fee matters more than it looks

Every other cost is roughly predictable. The per-claim fee is the one that punishes exactly the thing you want more of. A clean adjudication month, a growing client, a team clearing its queue, each one raises the bill. Over a few years it often becomes one of the largest lines in the stack, and it’s structurally backwards: your software vendor’s revenue goes up when your operational performance goes up.

That’s the number worth pressing every vendor on. Ask for the per-claim, per-member, and per-feed fees in writing, and model them at the volume you actually expect, not the volume in the demo.

The all-in-one math

Claimaro prices differently on purpose. One platform, claims adjudication, X12 EDI, enrollment, billing, member and provider portals, CRM, and communications, with TPA pricing quoted for your book and zero per-claim fees, ever. Your claim volume can double and the platform cost doesn’t move. Against a stack of six or seven vendors with a claims payer that bills per transaction, most TPAs see a six-figure year-one difference. The point isn’t just that it’s less, it’s that it’s legible, and it doesn’t get more expensive every time your book grows.

And it’s built to keep consolidating. ACA 1094 and 1095 reporting is already built into the platform, switched on per account, so it isn’t vendor number eight down the line. That’s the direction worth buying toward: fewer systems, not more.

See your own number

Benchmarks are a starting point; your plan design and member count are what actually decide it. Run your numbers in the calculator to size Claimaro against a multi-vendor stack, then book a walkthrough, and if you want the full picture of the systems a TPA is paying for, here’s the seven-system software stack it takes to run one.