Skip to main content
Home/Blog/Healthcare PE

Best AI OS for Portfolio Margin Expansion

Written by - Samara Strategy TeamLast Updated - September 11, 2026

Margin expansion across a portfolio is a cost-to-serve problem, not a revenue problem. Here's how an AI OS lowers front-office labor cost per visit at every location without touching clinical staffing.

Follow Samara on Google

Set Samara as a preferred source and our research shows up more often in your Google Search results, Top Stories, and AI Overviews.

Make Samara a preferred source

Key Insight

Portfolios running one AI OS across every location cut front-office labor cost per visit by 30-45%, expanding margin percentage even in periods where revenue growth is flat.

Margin Expansion Is a Different Problem Than EBITDA Growth

EBITDA growth can come from adding revenue. Margin expansion has to come from changing the cost structure relative to that revenue — and at the portfolio level, the largest controllable cost-to-serve variable is front-office labor: the staff time spent scheduling, confirming, reminding, and coordinating patients across every location.

This is a margin lever precisely because it scales with site count in a portfolio that hasn't standardized it, and stops scaling with site count in one that has.

Where Portfolio Margins Actually Erode

Front-office headcount grows with location count. Every added site typically needs its own front-desk staffing to handle scheduling and patient communication manually, which caps how much margin improves as the portfolio grows.

Labor cost per visit varies wildly by site. A well-staffed location and an understaffed one produce very different cost-to-serve numbers, and the blended portfolio margin hides which sites are dragging it down.

Overtime and turnover compound the problem. Manual front-office work is repetitive and high-turnover, which means the labor cost per visit at a struggling site tends to get worse over time, not better.

What to Look for in an AI OS

Handles the repetitive front-office volume, not just the exceptions. Scheduling, reminders, and routine patient communication should run automatically at every site, leaving staff for higher-value in-person work.

Cost per visit that holds steady as the portfolio scales. Adding a new location shouldn't require proportionally adding front-office headcount to serve it.

Site-level cost-to-serve visibility. Leadership should be able to see labor cost per visit at every location individually, not estimate it from a blended portfolio number.

Metric Manual front-office labor One AI OS across the portfolio
Front-office labor cost per visit Scales with site count Flat as portfolio scales
Cost-to-serve variance across sites Wide, staffing-dependent Converges toward a common standard
Margin trend as portfolio grows Flat or declining Improving

Frequently Asked Questions

Does this require reducing front-office headcount to see margin improvement?

Most portfolios don't need layoffs to see the margin benefit — existing staff get freed from repetitive coordination work, and the portfolio simply avoids adding proportional headcount as it acquires new locations.

How fast does labor cost per visit typically improve?

Most sites see a measurable drop in front-office labor hours per visit within 30-45 days of deployment, with the full portfolio-wide margin effect visible over two to three quarters as it compounds across every location.

Does this affect clinical staffing or only front-office roles?

Only front-office and administrative coordination — scheduling, intake, reminders, and follow-up. Clinical staffing and care delivery are unaffected.

Healthcare PEHealthcare AIWorkflow Automation

Ready to transform your practice operations?

Join 500+ healthcare leaders deploying specialized AI workforces to drive EBITDA growth.

See a live demo of the Samara AI platform in under 15 minutes.

Samara Assistant

Ask me anything

Welcome to Samara

Tell us who you are to get started