Team Culture
Own the outcome, lead with empathy, and turn complex change into calm, measurable wins.
How we work
Own the outcome
You’re empowered to make calls, clear blockers, and ship work that moves the needle. We care about results, not theatrics.Move fast, stay clear
Short meetings. Crisp written updates. Simple trackers. Clients know what’s happening and why.High EQ in high-change moments
Big system changes are stressful. We lead with empathy, listen first, and keep energy positive.Design at the intersections
You’ll connect PMS, RCM, finance, HR, and analytics. We think across teams, not in silos.Document so it sticks
Playbooks, workflows, and training that hold up after we’re gone. If it isn’t documented, it isn’t done.Partner, don’t preach
We work alongside internal leaders and field teams. Respect existing relationships and build trust as you go.Be practical about cost
We deliver senior leadership without adding permanent headcount. That means focus, rigor, and smart trade-offs.
What you’ll do here
Lead implementations of practice management and analytics tools from kickoff to adoption
Map current workflows, design better ones, and align stakeholders across ops, finance, RCM, and clinics
Build reporting that leaders can trust and teach teams how to use it
Spot the land mines early and protect data quality, collections, and patient experience
Translate technical detail into clear guidance for CFOs, controllers, RCM leads, regional and office managers
What success looks like
Measurable improvements in efficiency and reporting accuracy
Confident end users who can run the process without us
Clean documentation and training materials others can follow
Fewer escalations and faster decisions because your communication is simple and timely
What you’ll love
Autonomy with support: Real ownership, plus senior teammates who jump in when needed
Variety: Every DSO is different. You’ll learn fast and keep sharpening your toolkit
Visible impact: Your work shows up in better workflows, better numbers, and happier teams
What might not be a fit
You prefer long discovery cycles without shipping
You avoid documentation or don’t enjoy cross-functional problem solving
You struggle to stay steady and positive during change