Stacks AI Studio Let's Talk

Stacks AI Studio / Medical Practices

AI for Medical Practices

"I feel behind on AI, and there is no chance I can catch up." If that is the sentence in your head, you are exactly who I work with. I am not selling software or theory-based advice. I run my own ten person managed services business on Claude, I know the value it adds every week, and now I help owners do the same inside medical practices like yours: your team trained, jobs automated, hours saved. Saying yes to starting puts you ahead of many of your competitors.

Book A 15 Minute Call See five automations we could build
Line drawing of a coiled stethoscope
5.5 hours hours back per person, weekly

Experience, Not Theory

That is our first four automations at Stacks, across a ten person team. We took on more clients, and gross margin went from 26% to 56% in twelve months. AI was not the only driver. It was the biggest one. It also set a new standard for what my team sends out: the same bar for research, formatting, and finish on everything that leaves the building, no shortcuts.

Casey Templeton, Founder of Stacks. Nashville.

"In one week I went from a two-hour session with Casey to a brand new marketing site and firing the marketing firm I'd used for two years. If Casey wants to work with you, don't be a dummy. Just do it."
Mike Kelly, CEO, TeamOnUP

The Week

Your Week. I Know It.

Five jobs that eat the day. This is the work an automation goes after first.

A prior auth lands before the visit ends. Somebody digs the chart for what the payer wants.

The patient leaves with a generic printout. The phone rings Thursday asking what it meant.

The same denial reason shows up twice. Nobody catches the pattern until days in AR climb.

The EHR inbox fills with messages and forms. The pile gets worked at nine at night.

The owner rebuilds the same monthly numbers. Payer mix and no shows get typed twice.

48 percent of leaders name denials and appeals their top revenue leak.

Denials are the leak, and the same reason repeats until somebody reads the last ten side by side.

Source: MGMA, July 2026.

The First Step

Two Sessions. Two Hours Each.

For most medical practices, this is the first step. Homework first, then two sessions, two hours each. In person if you are near Nashville, or over Zoom. $1,950.

For the math: one person at $25 an hour who gets two hours a week back is worth about $2,600 a year. If the first automation does that for one employee, it pays for itself with room to spare. And if after our first session you do not see a job worth automating, you pay nothing.

An automation is a repeated piece of work you teach Claude once. Your team runs it every day, you own it and tune it, and it carries the work to 80 percent so your people finish the 20 that needs their judgment.

Book A 15 Minute Call

"Casey taught me how to actually put AI to work. I generate quotes faster, my workflow is smoother, and I'm making more money because of it. One of the best investments I've made in my business."
David Pledge, Construction Sales Lead

01

Homework

Before we ever meet, you pull real examples of the work that eats your week: actual documents, actual messages, nothing cleaned up for me.

02

Session One

Two hours. We map how your practice actually runs, get Claude set up for your team, and train you on how to operate it.

03

Session Two

Two hours. We start building your first automations and put together the training your team needs to run Claude every day.

04

What You Leave With

Claude running for your team, your people trained on it, and one job automated and in use.

Five Automations We Could Build In Your Practice.

One page, no obligation. Proof of what we could build together, before we ever talk.

One email with the PDF. No newsletter, no drip campaign.

43 percent

expect to automate insurance pre-auth within the year.

Source: American Medical Association, March 2026.

HIPAA makes Stacks a business associate the moment an automation touches patient information, so the BAA gets signed before any of that starts.

The Stack

Claude Sits In The Middle.

It works with the tools you already run. It reads from your EHR, your practice management system, your payer portals, and your books, and writes back where it can.

Start with one connection, not all of them. The first automation usually needs one export from one system, and that is the whole first step. Once it earns its keep, the next system comes in, then the one after that. Every automation gets sharper as it goes, because Claude stops reading one screen and starts seeing the whole practice.

Claude Patient records Scheduling Billing and claims Payer portals Patient messaging

The Numbers

The Numbers Practices Are Seeing.

That feeling of being behind is not in your head. Medical practices are adopting fast, and the paperwork between the patient and the payer is still where the week goes.

83 percent

Medical groups using AI in visits

Source: MGMA, August 2026.

13 hours

Hours a week on prior authorizations

Source: American Medical Association, December 2025.

Questions

Questions, Answered.

I feel like I am already behind on AI. Is it too late?

No, and you are not as far behind as you think. The owners who feel furthest behind often move fastest once they start, because they have not spent a year on tools that did not stick. You do not need a strategy, a budget cycle, or a technical person on staff. You need four hours and one job that is costing you time every week. That is the whole first step.

Will this replace my staff?

No, and that is the whole design. An automation carries a job to 80 percent quickly and your employee takes the final 20 percent over the finish line. Efficiency goes up for everyone, the practice grows without the headcount it used to need, margins grow with it, and your team spends its time on patients instead of paperwork.

Will it work with the software we already run?

Usually, whether that is athenahealth, eClinicalWorks, Elation, DrChrono, or Epic. Some systems give me an API, some give me a nightly export, and a few give me nothing but a screen to copy from. I tell you which one you have before I scope anything.

We already use an ambient scribe. Is this the same thing?

No. That tool writes the note in the room. Ambient scribes listen to the visit and draft the documentation, and that is a real job done well. What I build starts after the note: the prior auth packet, the summary the patient reads at home, the denial that needs a second look. The two sit fine side by side.

Does any of this touch diagnosis or coding?

No. Everything I build is admin. An automation assembles what the payer asks for, drafts what the patient reads, and organizes what came back denied. It does not diagnose, pick an E and M level, or decide medical necessity. Those calls stay with the clinician, and the review step is part of the automation.

What happens to patient information?

Stacks signs a BAA before any automation touches PHI. Where a job can be done on de-identified data, I do it that way. Where it cannot, the data path is written down and you approve it before the automation runs on anything real. Your EHR stays the system of record.

How long before we see something working?

The first automation runs in weeks, not quarters. The two sessions scope it, I build it against your real charts and denials, and your team uses it while I refine it. One automation in production beats five in a plan.

Who owns what you build?

You own the automations and the documentation. They live in your account, written in plain language, so your team can read them and change them. If you stop working with me, nothing walks out the door.

What if we get to the end and nothing is worth automating?

Then you pay nothing. If after our first session you do not see a job worth automating, the engagement ends there and there is no charge. The first session either surfaces a job worth the money or it does not, and that risk is mine, not yours.

Why $1,950?

Because the format is small on purpose. Homework, two working sessions of two hours each, and the setup work around them. For the math: one person at $25 an hour who gets two hours a week back is worth about $2,600 a year. If the first automation does that for one employee, it has paid for itself with room to spare. Every number in that sentence is yours to check.

Casey Templeton, founder of Stacks

Who You Will Be Working With

Casey Templeton.

Founder of Stacks, a ten person business in Nashville that runs on Claude. Both sessions are with him directly, and every message from this page lands in his inbox, not a queue.

Start Here

Start With A Conversation Between Two Small Business Owners.

Tell me about your practice. I take on two or three of these engagements a month. Every message comes to me and I answer it myself. The first conversation costs nothing.

Book A 15 Minute Call
"A fear of not understanding AI had kept me from diving in. Casey's coaching changed that. It opened my eyes to a sea of possibilities and left me more confident to explore. Come open-minded, and see where your imagination takes you."
John Conger, Sports Coaching Professional

I reply to every message. No newsletter, no drip campaign.

I reply to every message. No newsletter, no drip campaign.