Brivon~4 min read

What we automated stopped where a patient’s appeal began.

A side project, an AI product manager, and a deliberate decision to hold the AI back.

  • Role: Product strategy and design
  • Timeline: Side project
  • Team: Me, with an AI product manager
  • Impact: Not measured yet
  • Platform: Web

Overview

By week two the AI could draft an appeal letter, and I chose not to ship it.

A prior authorization denial arrives as a three-page PDF with one sentence telling a patient their treatment was refused. The 60-day appeal window starts that day. Most patients never find the sentence.

Brivon offers help with those appeals while keeping advocates, who handle one case at a time, from burning out.

Worked with: an AI product manager on requirements and the build; 6 people interviewed.

What I owned

I owned

  • The whole product: strategy, market entry, brand, structure, and every screen
  • The market audit, and the call to enter on insurance denials rather than advocacy generally
  • Phase sequencing, and what automation was allowed to touch in each
  • The trust model: outcomes as patterns, a published acceptance rate, structured ratings
  • Two critique passes, and triaging which findings were real debt

Shared with an AI product manager

  • Requirements and scope, in a loop I spent the first month generating the friction inside
  • The build itself, whose first answers I killed

Research

Advocates and patients each needed to trust the system, so every decision holds automation back.

I audited the market and interviewed 6 people, including patients managing chronic pain. Two advocates stopped mid-sentence in testing when the AI got a case wrong.

Insurers now use AI to deny claims faster than a person could review them. Patients have nothing comparable.

Decision: where to start

I entered on prior authorization appeals because a case is approved or it is not.

I rejected care navigation, billing disputes, and a general health platform. Care navigation had the strongest emotional pull, but its win condition was too diffuse to judge in weeks. A binary outcome also made a success fee possible without a track record.

The cost is a narrow entry point that would make a small business if adjacent workflows never opened.

Decision: what the AI may touch

AI sorts incoming cases and advocates write every appeal.

Phase 0 covers AI-assisted intake and classification, manual advocate work, and a case timeline. I rejected a full copilot that drafts appeals, even with advocate review, though it was reachable by week two.

I accepted the cost: advocates write appeals by hand on a success fee that only pays when cases close. A misclassified denial routes to the wrong template, and a missed deadline can postpone surgery. An advocate who catches the AI wrong twice stops trusting it. Nothing leaves the building without an advocate reading it first. That gate is the product.

Redesign

Advocates get a ranked queue, and patients get profiles that show outcomes against named insurers.

The queue puts a deadline expiring today above a review that can wait until Thursday. The depth-first alternative meant eight context switches across eight cases before the day began. Testing showed advocates also wanted their workload on screen, so I added a session summary.

Profiles lead with patterns such as “15 of 17 denials at this insurer for this condition reversed on first appeal,” not credentials. Patient testimonials would expose people. A tester said the acceptance rate was what separated the product from a directory: “So they’re not just listing everyone.”

A single case: an action-needed banner, the advocate and next session, then three columns for resolved, in progress, and next steps.
The patient side of Phase 0. Status, next action, and outcome tracking on one screen, with two functional colours: amber for anything live, green for anything closed.

Scope

Intake, classification, a case timeline, outcome tracking, and document ingestion shipped. Drafting and monitoring did not.

I cut AI-drafted appeals, proactive deadline monitoring, employer dashboards, and any browsing surface. Each added risk or needed data the pilot would not have.

The brand took three directions. Clinical Authority read like a hospital’s internal tool. Warm Advocacy was called a meditation app. Earned Confidence came from asking what someone looks like when they have done this before and won.

Results

There are no results yet, only a threshold for the pilot.

Phase 0 passes if 70% or more of cases reach a clear outcome signal inside the case lifecycle. I would also watch advocate throughput on a half-automated system. None of this has happened. These are pilot hypotheses, not results.

The documents tab: four PDFs in one undifferentiated list, newest first, each with an uploader and a file size.
The panel the note below is about. A denial letter sits in the same flat list as a pathology report, carrying no sign of which role it plays in the case.

The dangerous parts of the product are still unresolved

I shipped a flat documents panel, although a denial letter at intake and the same letter filed as appeal evidence are different objects. The “How I work” block is one entry, though appeals and billing disputes need different versions.

For the first month I was the only one asking what happens when the AI is wrong. An AI product manager could generate a plausible advocacy workflow in an afternoon. The project ended before I could tell whether the whole team picked that question up.

Sam Cusano