Platform Margin Starts With SG&A, Not the Clinic Floor
Portfolio margin is about cost-to-serve at the clinic level. Platform margin is a different number: SG&A as a percentage of consolidated revenue at the corporate layer — operations, reporting, compliance, and vendor management overhead. It's the number investors watch most closely at exit, because it's the clearest signal of whether the platform actually operates as one business or as a loose federation of acquisitions.
The uncomfortable pattern in healthcare roll-ups is that SG&A often grows faster than revenue during the acquisition phase, because each new site adds coordination and reporting burden that gets absorbed by adding corporate staff rather than by better systems.
Where Platform SG&A Creeps
Reporting and compliance overhead scales with site count. Compiling performance data and audit-ready compliance documentation manually across a growing portfolio requires proportionally more corporate staff.
Vendor sprawl adds cost without adding standardization. Each acquisition often arrives with its own scheduling, reminder, and reputation tools, and consolidating them takes ongoing corporate effort rather than happening automatically.
Operations management doesn't scale linearly by default. Without a shared operating layer, supporting more locations requires proportionally more corporate operations headcount.
What to Look for in an AI OS
Consolidated, automated reporting. Corporate should get live, portfolio-wide performance and compliance data without a team manually compiling it every month.
One platform replacing the fragmented vendor stack. Consolidating scheduling, reminders, and patient communication onto one system reduces both vendor cost and the corporate effort spent managing multiple contracts.
SG&A that grows slower than revenue. The right AI OS should let the corporate layer support a larger platform without proportional headcount growth, which is what actually expands margin.
| Metric | Manual platform operations | One AI OS across the platform |
|---|---|---|
| SG&A growth vs. revenue growth | Often exceeds 1:1 during scale-up | Consistently below 1:1 |
| Vendor consolidation | Ongoing manual effort | Standardized on one system |
| Corporate reporting overhead | Scales with site count | Largely fixed |
Frequently Asked Questions
How does an AI OS reduce SG&A specifically, rather than just shifting cost elsewhere?
By automating the reporting, compliance documentation, and vendor coordination work that would otherwise require additional corporate headcount as the platform adds locations — the cost is eliminated, not relocated.
Does this matter more at exit, or during the hold period?
Both. A lower and more stable SG&A ratio improves EBITDA during the hold period and presents a cleaner, more credible margin story to buyers during diligence at exit.
How does this connect to compliance documentation for diligence?
The same shared operating layer that reduces reporting overhead also centralizes BAAs, audit logs, and security documentation across every location, which is typically the first thing a buyer's counsel asks for.