Selected Work

Three examples of how I approach revenue problems.

These case studies are independent, fictionalized scenarios built to show how I think through analysis, workflow design, and operational strategy in practice.

The organizations and datasets are fictional, but the logic, constraints, and intervention thinking are grounded in real-world revenue cycle and operations experience. Each piece is meant to demonstrate a different dimension of how I work: diagnosis, tool design, and strategic execution.

Analysis

Denial Pattern Analyzer

A diagnostic dashboard for identifying denial clusters, revenue at risk, and operational intervention points.

Built around a fictional multi-specialty group practice with a messy payer mix, this case study uses a synthesized claims dataset to surface denial patterns across credentialing, authorization, eligibility, and modifier-related failure modes.

The goal is not just to visualize denials, but to isolate what is most preventable, where revenue is getting stuck, and which operational changes would matter first.

Tool

Authorization Operations Tracker

A workflow tool for auth visibility, utilization tracking, and expiry risk management.

Built around a fictional pediatric behavioral health practice, this piece addresses the operational mess that happens when services are delivered without clean authorization visibility or reliable vendor queue oversight.

The tool is designed to surface unit utilization, pending vendor status, SLA performance, and expiration risk before they become downstream revenue problems.

Strategy

RCM Turnaround Plan

A 90-day operating plan for scale, org design, and systems decision-making.

Built around a fictional independent practice recently acquired by a PE-backed group, this case study focuses on how to scale revenue operations from 500 to 2,000 claims per month within six months without building chaos into the foundation.

The work centers on sequencing, org design, KPI visibility, and the tradeoffs between building new systems versus configuring what already exists.

Why this format

Because titles alone rarely show how someone actually thinks.

I wanted this work to make that more visible. Each piece is built to reflect a different layer of the job: identifying the problem, designing around the problem, and leading through the problem.