Director of Revenue Cycle Management · Behavioral Health & SUD

The revenue cycle,
re-engineered as an operating system.

I take chaotic behavioral-health billing operations and turn them into predictable, high-margin revenue engines — through workflow design, KPI accountability, process control, and now AI-driven automation. This is a living map of that system.

Click any node to step inside the operation
100+
Facilities scaled
$120M+
A/R under management
32days
Avg A/R · down from 60+
98%+
Clean claim rate
70
Team members led
<10%
Denial rate sustained
The Operating System

Every claim follows one tree.

From admission to resolution, each claim travels a single trunk — then branches at the payer's decision into paid, worked, or closed. Tap any node for the high-level view of how it works and the numbers I hold it to.

▸ Tap any node for the high-level view — the detailed playbook stays internal
Executive Profile

An operator who builds systems — not just a resume.

Revenue Cycle Operations executive with 8+ years building RCM infrastructure from the ground up across behavioral health and substance-use-disorder care. I specialize in the messy middle — where payer complexity, clinical documentation, and cash flow collide — and I turn it into something measurable, controllable, and fast.

I've been the trusted advisor to CEOs and ownership groups through rapid growth, designed the data systems leadership runs on, and led teams of up to 70 across the full cycle: VOB, UR, billing, denials, appeals, negotiations, and posting. Now I'm integrating agentic AI and automation into RCM operations to accelerate performance without sacrificing accuracy, compliance, or human accountability.

// career trajectory
role = "Director of RCM"
scope = 100+ facilities · 70 staff
domain = ["behavioral health","SUD","mental health"]
reports_to = ownership / C-suite
superpower = "complex → simple → scalable"
RCM & Revenue Operations
Technology & Systems
Leadership & Operations
Revenue Cycle Command Center

The view I run the operation from.

Not a payer report — the internal oversight layer I built to grade every department and facility, watch AR composition, and catch stalled claims before they age into write-offs. This is how 70 people across 11 teams stay accountable to one number. Sample data; live interactions.

RCM Command Center
WMQ 5.20.26 · vs prior weekly snapshot
8.1% past due
26,296 claims · $127.4M
Facility
Level of Care
Period

Overall Grade

Weighted health across all teams
B
92%

AR Balance by Department sorted by past-due %

Each bar = on-track / warning / past-due composition

Facility Performance by charge volume

Top facilities · graded on past-due pressure

Period Comparison

This snapshot vs. the prior weekly snapshot
MetricCurrentPriorΔ

⚠ Stalled Claims Alert

Top statuses by avg days over their SOP threshold
SOP / Process Library

A standardized playbook behind every claim.

Each claim status maps to an owning team, a defined touch cadence, and an escalation path — the standardized system I built so dozens of people across many teams act as one. A few are featured in full below; the complete decision trees and processes live in the internal playbook.

Featured statuses — full detail
The full status framework

Owning team and cadence shown for context. Definitions and processes are proprietary — open a featured status above to see the depth behind each one.

Leadership & Impact

Leading across departments, vendors, and the C-suite.

60+ → 32
Avg A/R days cut nearly in half across the portfolio
$120M+
A/R managed across 100+ behavioral health & SUD sites
98%+
Clean claim rate achieved and sustained at scale
5
RCM roles climbed — VOB to Director — building the function up
Projects · Automation · AI

Modern infrastructure for a traditional discipline.

RCM has run on manual follow-up and brittle spreadsheets for decades. I'm rebuilding the foundation — data pipelines, dashboards, and agentic automation — so the human team spends its time on judgment, not on data entry.

// A pipeline I built from scratch

CollaborateMD WebAPI
Python sync · nightly
PostgreSQL warehouse
FastAPI service layer
React client dashboards

"Automation in RCM should remove the keystrokes, not the accountability. Every agent I deploy leaves an audit trail, a human checkpoint, and a number I can defend to ownership."

Let's talk

I build the revenue engine. Let's see what yours could do.

Open to RCM leadership roles, fractional/consulting engagements, and conversations with behavioral-health ownership groups navigating growth, payer complexity, or operational transformation.