Relentless Health Value · 2026-07-01 · 14 min
Key moments - from our scoring
Substance score
55 / 100
Five dimensions, 20 points each
Claire Brockbank, newly appointed director of the 32BJ Health Fund, distinguishes between ASO (Administrative Services Only) vendors owned by insurance carriers and independent TPAs (Third Party Administrators) in this AMA episode. An ASO is essentially a TPA owned by a major insurance carrier that processes claims and administers networks for self-funded employers while the carrier bears no risk - but it comes bundled with the carrier's existing network and built-in incentive misalignments. A TPA, by contrast, is a standalone administrator with no insurance operations, no proprietary networks, and aligned incentives: what you pay for is what you get. The critical difference for employers seeking transparency and control: ASOs make carve-outs, direct contracting, and custom audits difficult because their infrastructure is baked into an insured model, while TPAs - typically built on modern technology stacks rather than legacy systems - enable employers to bring their own networks, implement pre-authorization audits via API, and execute strategic clinical initiatives like removing unsafe providers. Research shows self-funded employers using ASOs pay 4.7% higher rates than their insured counterparts due to cross-subsidy dynamics. This episode is essential for benefits consultants, self-funded employers, and plan sponsors evaluating administrative partnerships.
An ASO is a third-party administrator owned by an insurance carrier that comes with the carrier's network and services, while a TPA is an independent administrator with no insurance operations, no proprietary network, and incentives aligned purely with the employer's goals rather than the carrier's profit margins across multiple business lines.
ASOs often cross-subsidize their insured book of business by charging self-funded employers higher rates; research cited in the episode shows self-funded employers working with ASOs pay on average 4.7% more than insured customers for the same services because the carrier needs the math to average out across all business lines.
Direct contracts and carve-outs are much easier with a TPA because they are built on modern, flexible technology; ASOs often have legacy systems and infrastructure constraints that make customization difficult or require 18+ months to implement changes.
TPAs are newer market entrants built on modern technology as their core competency, while ASOs inherit legacy systems from large insurance carriers; this makes TPAs more nimble, faster to integrate with APIs for auditing, and better equipped to support strategic clinical initiatives like provider carve-outs.
ASOs balance their incentives across insured and self-funded business lines, sometimes pricing self-funded claims higher to keep their insured business competitive; TPAs have only one client - the employer - so their financial success depends entirely on accurate, efficient claims processing aligned with the employer's interests.
Our reviewer’s read on each dimension, with quotes from the episode.
Within the ~8-10 minutes of actual conversation (after generous intro/outro/sponsor padding), the episode delivers a handful of genuinely useful distinctions - network ownership, incentive misalignment mechanics, and technology legacy gaps - but the topic itself is a primer-level explainer rather than a dense idea-rich exchange.
What you pay for is what you get. When you do that with an ASO, you have to understand that the ASO your one piece of their puzzle.
TPAs are typically a slightly newer entrant in the market, and they are often built because technology is their bread and butter.
The ASO-vs-TPA distinction is well-known terrain in self-funded benefits circles; the episode organises it clearly but offers little that is contrarian or first-principles beyond the incentive-misalignment mechanism, which is articulated usefully but not originally.
So if they have to negotiate a contract with a provider and they can pay Stacey a hundred dollars for the service on behalf of their insured business where they have a profit margin, but the provider says, but overall, I wanna get paid an average of 140 for my services.
it becomes really important if you're doing a TPA that you read that contract carefully and that you know what they will and won't do
Claire Brockbank is the director of a major union health fund (32BJ) who is actively mid-implementation of a TPA switch effective January 1 - she is a genuine practitioner reporting from live experience, not a thought-leader theorising.
We went with a TPA effective one one this year, and we've thrown two massive direct contracts at them.
We're certainly finding that with the implementation we've been doing.
The episode includes one solid data point (4.7% premium premium cited via Luke Prettol), a real-world audit-clause abuse example (25% clawback), and a live go-live reference, but most supporting evidence is callbacks to other episodes rather than data Claire herself presents.
Luke Prettol referenced a study that showed that self-insured employers, if they are working with an ASO pay on average of something like 4.7% more.
some TPA was like, sure, go audit your own claims. But then we still get 25% of whatever you collect
The host synthesises well - summarising back, adding external evidence (Prettol, Carleson, Noel), and introducing a useful counterpoint on TPA contract abuses - but there are no genuinely probing follow-ups and no real moment of productive disagreement or challenge to Claire's framing.
So it's kind of like exactly like you just teed up. I'm a carrier, I have a fully insured business line. If I go with an ASO, I'm gonna get everything you'd get with a fully insured model subtracting the risk.
But to your exact point, if you have a TPA that knows how to API, this is not an issue. If you get someone still on COBOL with 17 different manual processes, it's just, it becomes problematic.
Computed from the transcript - who did the talking, and the words that came up most.
The ASO vs. TPA Decision That Quietly Costs Self-Funded Employers More What's the real difference between an ASO and a TPA - and why does it matter that self-insured employers working with an ASO pay, by one referenced estimate, about 4.7% more than the insured book of business for the same care? In this Ask Me Anything, Stacey Richter puts a listener question from Dr. Alex Sommers, MD, ABEM, DipABLM, president of Astia Health, to Claire Brockbank, newly appointed director of the 32BJ Health Fund, who breaks down how ASO and TPA models diverge on ownership, networks, and incentives.
Transcribed and scored by The B2B Podcast Index.
This file was generated by Descript Episode 518. Today we're gonna do an ask me anything. How do you explain the difference between an ASO administrative services only vendor and a TPA, a third party administrator? Hmm.
Today I'm speaking with Claire Brockbank. American Healthcare Entrepreneurs and Executives You Want to Know, Talking. Relentlessly Seeking Value. Hi.
I am Alex Sommers. I'm president of Astia Health, an advanced direct primary care organization, an emergency medicine and lifestyle medicine physician, as well as a licensed employer health plan advisor from Wisconsin. I'm curious how you explain the difference in the real world between a carrier administrative services only arrangement and an independent third party administrator model to an employer looking for more transparency, cost control, and clinical risk strategy for their health plan.
What a great, ask me anything from Dr. Alex Sommers, and let me tell you if I do say so myself, I got the perfect person to answer this question. The one and only Claire Brockbank, the recently appointed new director of the 32BJ Health Fund. Before we get to Claire's answer.
However, let me just again thank Dr. Sommers for the question, which is especially relevant since Dr. Sommers, as he just mentioned, is president of Astia Health, which is an advanced primary care practice that's physician led and they help employers get their plan members, the kind of proactive whole person, primary care, and also proactive clinical risk management that we talk about over and over and over again on this show. Listen to the episode most recently, I would suggest with Patrick Nelli.
I mean advanced primary care and the data necessary to actually do proactive clinical risk management, that is what is needed as a foundation to build a health plan that bends medical and pharmacy trend below inflation and members actually becoming healthier as an investment to that end in this model. So yes, when laying this advanced primary care foundation access to data as just one example really matters. Read that series of posts recently by Kimberly Carleson to underline this point.
I say all this to say Claire's response to what is an ASO versus a TPA, and her thoughts on the whole ASO versus TPA decision are really insightful news you can use to explain to employers the difference in the best way possible. And yeah, all of this can be very foundational for anybody who's really trying to figure out how to get their health plan back on track. This podcast is sponsored by Aventria Health Group with an assist by Payerset. Hi, I'm Jerry DiMaso, CEO, and co-founder of Payerset.
Relentless Health Value is one of the best resources out there for understanding how healthcare really works, and it's actually required listening for anybody that comes on board at Payerset. Stacey gets into the real mechanics of healthcare pricing and what it takes to fix this system. If you care about making healthcare more affordable and transparent, this is the show to tune into. I highly recommend signing up for the weekly newsletter.
It's a great resource because it includes all the links mentioned in the show, plus a full transcription of Stacey's intro. Please be sure to follow the podcast on Apple Podcasts or Spotify and forward this episode to someone who should be listening. And here is Claire Brockbank answering the question, how best to explain to an employer the difference between what is an ASO and what is a TPA? Claire Brockbank, welcome to Relentless Health Value.
Hi Stacey. Thanks for having me. I am so pleased to have you here to answer this age old question because I think a lot of times people say administrative services only, and I don't know, like I've always had in my head, if it's like administrative services only as a TPA that's owned by a carrier. Straighten us out here.
So that is kind of true. It's a TPA that's owned by one of the big insurance carriers. Those carriers have insured business, they have all sorts of other product lines, but they sell to self-insured employers like 32BJ Health Fund, the option of having them process claims, administer a network, do any one of a number of different services that they also provide to their fully insured business. What you're not paying for when you do that is any of the risk bearing part of being an insurance company.
So that's an ASO. A TPA, third party administrator, does many of the same things. So in the end, both of those entities function to pay claims, manage some of the administrative parts of care covering your employees. However, a TPA, that's all they do.
So TPA functions to process claims, manage other aspects of the administrative process, whether that's payment review, prior authorization, maybe some claims, high cost claims management, those kind of things. But they don't have insurance companies. They don't have their own networks, typically, they have no other side hustles, if you will, other than serving you the self-funded employer. So if I'm kind of distilling this down to the lowest common denominator, what I'm hearing is an ASO is gonna come complete with its own network and all of those trimmings that go along with that, whereas a TPA is like a third party administrator, so it could rent a network or something like that.
But it's a third party to that network. Like it's not, it doesn't own its own network. It doesn't own its own network, which means you can bring your own network. An ASO, it's very difficult to bring your own network, so you're sort of buying their network.
So for employers who want to do carve outs or direct contract or their own audits or a lot of the things that we've talked about, Stacey, the the rights associated with your administrative relationships, that is harder to do sometimes with an ASO because that's already baked in into their model. Got it. So it's kind of like exactly like you just teed up. I'm a carrier, I have a fully insured business line.
If I go with an ASO, I'm gonna get everything you'd get with a fully insured model subtracting the risk. Yes, along with some of the misaligned incentives. Ah. So the other thing that happens is that when you contract with a TPA.
Your incentives are pretty much the same as theirs. You want your claims processed accurately. You want them processed quickly. You set the rules in terms of how fast you pay, what you're prior authorizing, et cetera, but it's really a partnership between you and the TPA.
What you pay for is what you get. When you do that with an ASO, you have to understand that the ASO your one piece of their puzzle. And so if they have to negotiate a contract with a provider and they can pay Stacey a hundred dollars for the service on behalf of their insured business where they have a profit margin, but the provider says, but overall, I wanna get paid an average of 140 for my services. Then they can say, well, we'll charge Claire the self-funded employer, maybe a little bit more so that we can pay us on the insured side a little bit less, and it might average out.
So their incentives are not so aligned, and we see this, right? We see this in the evidence and in the literature that in fact, self-funded employers, remarkably, you've done it in your podcast, sometimes pay higher rates than the insured book of business. Yeah. In fact, Luke Prettol referenced a study that showed that self-insured employers, if they are working with an ASO pay on average of something like 4.
7% more. And that's where that comes from. Because the ASO is trying to make the math work so that on average a provider organization can get paid its ask. Yes.
So your incentives are just not always aligned.. Yeah, I mean you have heard of course also horror stories about some TPAs where there, I just saw Kimberly Carleson posted something the other day about how some TPA was like, sure, go audit your own claims. But then we still get 25% of whatever you collect, you know? So there's still funny stuff going on, right?
But at least on its face. If we go back to first principles, if you're working with someone who is a third party TPA, there is the potential that incentives are aligned. Whereas if you're working with an ASO, just you know, again, first principles, there are some implicit misalignments that you're going to have to deal with. Just like right outta the gate.
Yes. So then it becomes really important if you're doing a TPA that you read that contract carefully and that you know what they will and won't do, of course. Yeah, referenced the earlier podcast with Claire Brockbank, where we discuss contracts. Exactly, The other thing that we often see, not always, but many of the BUCAs have merged and grown over the years, and they have a lot of legacy systems, right?
They have old systems. They've been around for a really long time. And so many times the things that you wanna do, you find they might even want to do them with you, but their legacy system will take 18 months to fix to try to figure out how to do it. TPAs are typically a slightly newer entrant in the market, and they are often built because technology is their bread and butter.
It is not risk bearing, it is not insurance regulation. It is not building networks, right? It is managing this so often what we found was that their technology is much better, more streamlined, and therefore a little bit faster. So that if you wanna be nimble in the marketplace, you're more likely to get that with a TPA.
We're certainly finding that with the implementation we've been doing. We went with a TPA effective one one this year, and we've thrown two massive direct contracts at them. And their ability to pivot and to do that is in large part because they have invested in very good technology. And so that's often a difference.
Not universally, but it is a generalism that I think is fair to say. Yeah, that's a really interesting point that you just made, that if there is some kind of carve out, first of all, they can just, they can do it to begin with. Like I was just talking to someone who had identified 40 very, very unsafe physicians. Really bad doing very bad things and they couldn't figure out how to cut 'em out of the network with their ASO for, yeah, for probably all kinds of reasons.
But if they had been working with the TPA, that to your point, probably wouldn't have been an issue. Doing direct contracts wouldn't have been an issue. We had Mark Noel on the pod from ClaimInsight, who was really able to hook up some pre-audit and, you know, and, and basically what he said is, I just get an API and I can easily hook it up with a TPA. You know, so the employers themselves on the backend don't have to be doing all kinds of crazy stuff dealing with all this technology, just hook it up with the TPA.
But to your exact point, if you have a TPA that knows how to API, this is not an issue. If you get someone still on COBOL with 17 different manual processes, it's just, it becomes problematic. Yes, it's a huge difference, and we have seen it in action in this last five months. Time and time again.
Claire Brockbank, thank you so much for clarifying this Ask Me Anything, this is this, this AMA is a FAQ, right? Like how often does it come up where either someone makes something up for, what's the difference between, as I apparently have been doing for years? Um, what's the difference between an ASO or a TPA and or uses these terms sort of interchangeably and clearly they are not synonyms. Claire Brockbank, thank you so much for being on Relentless Health Value today.
You are so very, very welcome, Stacey. Happy to help. Hi, this is Tom Nash, editor and producer of the Relentless Health Value Podcast. I bet you're wondering, how can I help Relentless Health Value?
Well, that's pretty easy. Have you signed up for the newsletter? The newsletter is great. It tells you when each episode's coming out.
It gives you an introduction to the episode with all the mention links. And a way to click through and listen to the podcast. But there's more ways to help. You can always go over to LinkedIn.
Are you following the page? You should be. There's great conversations each week on all the episodes. So go to LinkedIn, find the Relentless Health Value page and follow us.
Have you ever left a review for us on Apple Podcast or Spotify? That would help greatly? While you're doing that, be sure you're following the podcast so you get notified each week inside of Apple Podcasts or Spotify. Okay, so you've done all those things already.
Another thing you could do, you could head over to our website and donate to the Tip Jar, maybe become a sustaining member. In many ways, Relentless Health runs like an unofficial nonprofit, a very, very nonprofit. So anything that you give would help us pay the bills. Thanks so much for listening.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.