Insights

Plain answers to the questions vendors avoid

Written by the people doing the work, about the parts that go wrong. If an answer is unflattering to us, that is usually a sign it is worth publishing.

Prior auth

July 28, 2026

6 minute read

What actually breaks when you automate prior authorization

Eight years of running one of these programs, and a list of the five things that break. Four of the five are organizational rather than technical, which is the part most pitches leave out.

Read it →

In the queue

One new piece a month is the cadence we can hold in a bad month. Next three, in order:

Appealing faster versus denying less, which one to fund first, and when appealing faster is genuinely the right call.
When you should not automate a workflow, four situations where the honest recommendation is to fix the process or leave it alone.
Automating work that depends on judgment, case assignment and subspecialty routing, and where the line actually sits.

If one of those is the question you have today, ask us directly rather than waiting for it to publish.

How we write these

The Editorial Rule

Every section stands alone

Lift any section out of the page and it still answers a question completely. No “as discussed above.”

Every number carries a date

A figure without a measurement window and a baseline is decoration. If we cannot source it, it does not go in.

Unflattering answers stay in

Where the honest answer costs us the sale in the short run, we give it anyway. Those are the pieces people forward.

Next step

Ask Us The Version That Applies To You

These are general answers. Thirty minutes on your actual workflow produces a specific one, in writing, whether or not we end up working together.

Book a teardown