A few months ago a visit to a specialist's office turned into the kind of administrative mess that most people quietly eat. A claim got handled wrong, the coverage I thought I had did not show up the way I expected, and I was suddenly on the hook for a bill that did not match my understanding of my own plan.
I want to be careful here: this post is not about my health. The medical part is boring and private, and it stays that way. This is about the bureaucracy that wraps around the medical part — the denials, the Explanation-of-Benefits letters written in a language no human speaks, the phone trees, the "we'll have to escalate that." That part is universal. And it is exactly the kind of fight AI is quietly very good at.
If this ends the way I think it should, it saves me over $600. But honestly, the money is not the most interesting thing about this story.
Why Everyone Gives Up
Here is the dirty secret of insurance disputes: the process is designed to be exhausting.
Not maliciously, necessarily. But the friction is the feature. Every denied claim is a bet that you will not have the time, energy, or stomach to push back. Most of the time, that bet pays off. You get the letter, you do not understand the letter, you call the number, you sit on hold, you get transferred, you give up. The bill stands.
I almost did the same thing. I am a reasonably persistent person, I run operations for a living, and even I looked at that stack of paperwork and felt the pull to just pay it and move on. The activation energy to fight it correctly — reading the policy, understanding my actual rights, building a paper trail, writing it all up in a way an institution has to respond to — felt like more than the $600 was worth in pure hours.
That is the trap. The cost of fighting is mostly your time and attention. And the system knows your time is expensive.
Bureaucracy wins by making persistence expensive. AI makes persistence cheap. That single shift is enough to change who wins these fights.
What Claude Actually Did
I did not ask Claude to "handle my insurance." That is not how this works, and it is not how I work. I treated it the way I treat AI on everything — as leverage on the parts that are slow and opaque, while I keep the judgment.
A few concrete things it did:
- Translated the dense language.: I pasted in the relevant policy sections and the EOB and asked Claude to explain, in plain English, what each line actually meant and where the gap was between what I was billed and what my plan said. The jargon stopped being a wall.
- Built the timeline.: Every call, every letter, every date got organized into a clean chronological record — who said what, when. That paper trail is the entire ballgame in a dispute, and it is the thing people never keep.
- Identified my actual rights.: Not legal advice — I want to be clear about that — but a clear-eyed read of what protections and appeal steps existed for a situation like mine, so I knew what I was entitled to ask for instead of guessing.
- Drafted the appeal, then the complaint.: When the internal appeal stalled, we drafted a formal complaint to my state's department of insurance — the regulator that oversees insurers. Structured, factual, dated, attached to the timeline. The kind of document that is hard to ignore.
None of these are things I could not have done alone. They are things I would not have done alone, because each one is a small wall of friction, and stacked together they are the reason people quit.
AI did not replace my effort. It removed the part of the effort that has nothing to do with being right — the formatting, the translating, the organizing — so the only thing left was showing up.
The Regulator Step Most People Skip
Here is the part I did not fully appreciate until I was in it: you are not stuck with your insurer's decision.
Insurers have an internal appeals process, and you should use it. But above that sits a state regulator — a department of insurance — whose job is to take complaints from people exactly like me. Almost nobody uses it, partly because almost nobody knows it exists, and partly because "file a formal complaint with a state agency" sounds like a thing that requires a lawyer.
It does not. It requires a clear story, a clean timeline, and the patience to write it down correctly. That last part is precisely where AI changes the math. Drafting a structured regulatory complaint used to be an afternoon of dread. With Claude it was a focused hour of me directing and editing while the machine handled the scaffolding.
The filing is in. I do not know yet how it resolves. It may go my way, it may not. But it is filed — and it would not be, without the tooling that made the persistence cheap enough to be worth it.
What This Means If You're Not Technical
I am not a lawyer and I am not a coder. I am an operator who has learned that most "I can't deal with this" problems are really "the homework gap is too wide" problems. Insurance is the perfect example. The fight is not hard. The fight is tedious. And tedium is exactly what you should be handing to AI.
The mental model I keep coming back to: AI does not make you right. If your claim is genuinely not covered, no amount of clever drafting changes that. But when you are right, and you are being worn down by process, AI levels the asymmetry. It lets one person with a legitimate grievance match the institutional patience of an organization built to outlast you.
For the price of an hour and some attention, I turned a bill I almost paid into an open case with a regulator. Win or lose, that is a different relationship with the system than the one most of us settle for.
If you have ever stared at a denial letter and just given up — I get it. I almost did too. But the calculus has changed. The next time you get one, try treating it as a project instead of a verdict.
I would genuinely love to hear if anyone else has used AI to push back on something bureaucratic — insurance, a billing error, a benefits appeal, anything. Drop it in the comments. And if you want to talk through how to approach a fight like this, reach out through the contact page. These are some of my favorite conversations to have.
Comments
Leave a comment
AI SEO Is the New Visibility Game. Here's How I Picked a Tool For It.
People are asking AI instead of Googling. That quietly rewrites the rules of being found. Here's how I evaluated Profound versus Athena for work — and why we went with Athena.
I Tried the Big AI Note-Takers. I Keep Coming Back to Granola.
I ran the major AI meeting-notes tools through real work — including a head-to-head with the Gemini note-taker built into Google Meet. One quietly won. Here is why Granola earned the spot.
Opus 4.8 Is My Daily Driver. Then Fable Cracked a Problem It Couldn't.
Claude Opus 4.8 is a real step up and my everyday workhorse. But the first time I handed a sprawling, multi-step problem to Fable — a long-horizon model — I saw where this is actually going.