Complex day at Headway

Settle reversed denials without paying a clinician twice

Published Oct 22, 2026

You’re the software engineer. Your team is in the room.

The setting

is a marketplace and software platform that connects patients, health insurers and independent providers of mental health care across the United States. is the software therapists and psychiatric prescribers use to accept insurance and run their practice.

Retroactive payer payments collide with records built around the original denial.

Correcting eligible clinician payments protects reimbursement, while preserving final payer outcomes protects the ledger.

Who you’d be doing this for

“I saw a payment come through, then the claim still showed denied when I checked after my session.”

Anwar Wattana · Licensed Clinical Social Worker · a character in this brief

Runs a solo outpatient practice and relies on payment management to understand reimbursement for completed sessions.

What is at stake

A payer reversal has left 4,200 psychotherapy claims with conflicting denial and payment records. You must weigh fast corrected reimbursement against a one-way payment release that cannot create duplicate balances.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • speed of corrected reimbursement vs duplicate-payment control
  • payer reprocessing vs final ledger state
  • automation scale vs claim-level verification
  • provider clarity vs unresolved documentation exceptions

Why Headway

The claims platform connects provider reimbursement to payer and clearinghouse responses, so a duplicate or missing settlement reaches a clinician's practice directly.

Written with these in mind

systems-minded fullstack engineerpayments or claims engineerreliability-focused product engineer

Not your kind of problem? 104 more at Headway, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Headway. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

Reporting read before this brief was written

The pieces closest to the situation in this brief.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about money moving incorrectly, late, or twice.

The same setting, from another role

Each is set around Headway’s Headway for Providers, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make the background systems nobody sees behave dependably even under heavy, high-volume real-world load.