DEEP DIVE
🛠️ What the Vendor Hall is Really Selling You
Most practice managers do not leave a conference thinking, "I need another platform." They leave thinking, "Maybe this one finally fixes the thing that keeps breaking."
That is what the vendor hall is really selling. Not software. Relief.
Relief from denials, prior auth, charting, eligibility, no-shows, patient collections, staffing gaps, and the low-grade daily drag of running an independent practice. Some of those tools are useful. Some are genuinely impressive. The problem is that almost every booth uses the same shape of promise: a percentage, a dashboard, a case study, and a line about AI.
The owner job is not to become cynical. It is to become harder to impress.
Start with the broken workflow
The weakest buying process starts with a category: "We need an AI scribe," or "We need a denial tool," or "We need better automation."
The stronger process starts with a sentence: "Our MAs spend 90 minutes a day chasing missing prior-auth documentation," or "Our top 3 denial reasons have not changed in 6 months," or "Providers are closing charts 3 days late, and charge lag is following them."
That sentence does 2 things. It makes the vendor prove fit against a real workflow, and it gives you something to measure after launch. Without it, the demo becomes the standard. And demos are built to make the tool look inevitable.
The claims to slow down
The first claim is the guaranteed lift percentage. If a vendor says revenue goes up 15%, ask what moved. Did visits increase? Did documentation improve? Did coding levels shift? Did denials fall? Did collections rise, or did charges rise while payer pushback waited a few months to show up?
That distinction matters. One JAMA analysis of ambient AI scribes found E/M revenue increased by $167.37 per clinician per month. Useful, but not magic. Scribe tools can cost $39 to more than $700 per provider per month, so the ROI depends on the price, the workflow, and whether saved time becomes billable capacity or simply a less miserable evening.
The second claim is "fully automated." In revenue cycle, that phrase usually means "automated until the expensive exception." Prior auth, coding judgment, medical necessity, appeals, and payer disputes still need a human checkpoint somewhere. Ask where the tool stops, who owns the exception queue, and what happens when the payer disagrees.
The third claim is the benchmark. National averages are helpful for context, but your baseline is the buying tool. A vendor's benchmark does not know your payer mix, provider mix, procedure mix, locations, templates, or denial history. Before buying anything, lock down your own KPIs. These are the 4 metrics dermatology practices should monitor before a vendor gets to define success for you.
The fourth claim is the complete platform. Most platforms are strong where they started and thinnest where they expanded last. A scribe company that added billing built the billing last. A billing company that added charting built the charting last. A scheduling tool that added everything built everything last.
That is not a knock on anyone. It is how software gets built. But it means the module you need most may be the one with the least mileage on it, and the demo will not tell you which is which, because the demo is built to look uniform.
Ask a simple question: which part of this product has been in production the longest, and which part shipped most recently? Then ask how many practices are live on the newest part, not the platform overall. Those are different numbers and vendors rarely volunteer the second one.
The dermatology trap
Dermatology is especially easy to over-promise because the workflow is so procedure-heavy. A small change in modifier use, same-day E/M capture, biopsy documentation, or prior-auth handling can look like a huge opportunity.
It can be. But the payer gets a vote.
If a tool promises lift from higher E/M levels or cleaner same-day procedure billing, ask to see the effect in collections 6 months later, not charges in month 1. Coding mix is not the same as cash. We have seen the other side of this in the downcoding playbook for dermatology: the claim may go out clean, then come back reduced, denied, or flagged for records.
That does not make the tool bad. It means the proof has to follow the money all the way through.
What good buying looks like
Good buying is boring at the start. It names the workflow, the owner, the baseline, and the recheck date before the demo.
For a scribe, that might be chart closure time, charge lag, provider after-hours work, and visits per clinical hour. For a denial tool, it might be denial rate by payer, dollars in top denial categories, appeal overturn rate, and time from denial to action. For patient collections, it might be statement cycle time, card-on-file adoption, patient balance aging, and payment rate after first statement.
Then make the demo run on your world. Give the vendor 20 recent denials, 5 messy prior-auth cases, or a sample of de-identified charting scenarios. Ask them to show what the tool does, what the team still does, and what the practice manager sees when something breaks.
The best vendor will not flinch at that. The weaker one will keep pulling you back to the standard deck.
Takeaways
1. Write the problem before you book the demo. One sentence is enough: the workflow, the owner, the metric, and the cost of leaving it alone. If the vendor cannot map to that sentence, the tool is already drifting.
2. Make the vendor prove the claim on your data, and check the references against your configuration. Size and specialty are the easy filters. The harder one is how you actually plan to use the thing. If you intend to use the module that shipped last quarter and every reference uses the one that shipped three years ago, the reference tells you very little. Ask directly whether there is a practice live today using this the way you intend to use it, and whether you can talk to them. And if the reference list leans on the founder's own practice, treat that as a demo rather than a reference. Founders can walk down the hall to engineering. You cannot.
3. Read the exit before you sign the entrance. Morgan Lewis's current guidance on AI-enabled outsourcing points in the same direction: watch term length, auto-renewals, termination rights, data return, and governance. The unglamorous contract terms matter most when the shiny workflow fails.
The unglamorous contract terms matter most when the shiny workflow fails.
The vendor hall is useful if you treat it like research, not shopping. Bring your baseline, ask boring questions, and make the tool prove itself against the practice you actually run.
UPCOMING EVENTS + REMINDERS
📆 Mark your calendars:
MGMA Annual Conference - September 27-30, 2026. MGMA’s annual practice-management conference is in San Antonio, with programming for medical group operations, finance, technology, and leadership.
Fall Clinical Dermatology Conference - October 8-11, 2026. Fall Clinical runs at the Wynn Las Vegas, with medical, surgical, and cosmetic dermatology updates across four days. Ashwin will be there – reach out if you plan to attend!
ASDS Annual Meeting - November 5-8, 2026. ASDS heads to San Diego for dermatologic surgery education, procedural innovation, and networking. Clarity will be there. Reach out if you plan to attend!
Until next week,
The Practice Layer, powered by Clarity RCM


Built by the people who do this every day.
Clarity RCM manages revenue cycle for 200+ dermatology practices across 44 states. It's all we do. See how we work.

