Medical practice workflow automation — built for independent practices.
I build AI agents and workflow automation for independent medical practices in North Carolina — prior auth, intake and scheduling, documentation, and the hand-offs between the five tools your staff carries the work across. Built around your compliance requirements, running on your infrastructure, owned by you. Every engagement starts with a one-week, $4,500 operations audit that shows where the hours are leaking before you spend a dollar on a build.
To be clear about who this is for: if you run a hospital system, the enterprise vendors are built for you. If you own or manage a practice, keep reading.
Charlotte, NC · On-site across the state or remote · You own everything built
Four leaks every practice knows. Four systems that plug them.
Prior-auth orchestration that drafts, submits, and tracks instead of just templating, intake automation that fills the schedule without the phone tag, and document agents built around your compliance requirements — one system, not a sixth tool.
It's the same workflow-automation approach I use everywhere — pointed at a practice.
Prior auth is a part-time job stapled to every clinical role.
Prior-auth orchestration
A system that drafts, submits, and tracks — not another template library. It pulls what it needs from your records, prepares the submission, files it, and watches the status. Your staff steps in when a payer pushes back, not before.
Intake and scheduling run on phone tag and voicemail.
Intake & scheduling automation
Forms collected before the visit, confirmations sent without a human dialing, cancellations backfilled from the waitlist instead of sitting empty. The schedule fills itself; your front desk greets patients instead of chasing them.
Documentation and coding pile up after close.
Documentation & coding support
Draft notes and suggested codes assembled by the system, reviewed and approved by your clinicians. The after-close pile stops being a second shift.
Five point-solution tools, and staff still carry the workflow between them.
Consolidation
One system that carries the workflow across the tools you already own — EHR, scheduling, billing, phones — so your staff stops being the integration layer. Not a sixth tool. The connective tissue between the five you have.
Nearly two hours of paperwork for every hour of care.
That time is payroll. It's your most expensive clinical people doing data entry, and your front desk running the same status check forty times a week. The audit's job is to put a dollar figure on it for your practice — it's the size of the leak, not a promise.
of physician and staff time per physician, per week, on prior authorization alone.
of a physician's office day goes to EHR and desk work — 27% goes to patients.
The hospital systems have armies for this. Your practice has a front desk.
Healthcare AI vendors build for hospital systems: enterprise contracts, long implementations, an IT department on the receiving end. Independent practices get point tools instead — each one solves a sliver, and your staff carries the workflow between them. I work the other side of that gap — for the practice owner and the practice manager, not hospital IT.
And because it's patient data, the rules aren't negotiable: everything runs on your infrastructure, under permissions you set — you decide per system what the automation can read, what it can write, and what's off-limits — and every action can be logged. Built around your compliance requirements from day one, not retrofitted after.
This page is the medical vertical of my North Carolina work — the hub covers manufacturers and contractors too.
Where the engineering rigor comes from.
I'll be straight: my production systems to date run in reverse logistics and enterprise finance, not clinics. What transfers is the engineering — agent systems real teams use every day, and data-integrity discipline at a scale where mistakes are expensive. The workflow shapes are the same ones leaking hours in your practice: intake queues, status tracking, document assembly, systems that don't talk.
A mid-market reverse logistics-tech company put 50+ internal users on the MCP server and agents I built — Python on Google Cloud, live in their inventory and truckload workflows. Read the MCP server case study →
For a top-five U.S. bank, I ran forensic data-quality and integrity work at enterprise scale — migration testing and validation that protected integrity benchmarks while systems moved underneath. Read the trade-data migration case study →
For a multi-brand field-services group, I built 14 field and back-office applications — the finance automation alone recovered 18 hours of team capacity a week. How the nine-brand automation layer was built →
Built for practice owners — not hospital IT departments.
A fit if you're…
- An independent practice — one location or a few — where the owner or practice manager can act on a plan
- Real patient volume moving through manual intake, prior auth, and after-close documentation
- More admin hours than headcount, and no appetite to hire another seat just to push paperwork
- Five tools that don't talk, and staff who carry the workflow between them
Skip it if…
- You're a hospital system with an IT department — the enterprise vendors are built for you
- You want a tool recommendation, not a look at your actual workflow
- You want a big-logo vendor to check a procurement box. This is a small, senior practice
Run a plant or a project office instead? The same work exists for manufacturers and contractors.
What practice owners want to know first.
What does medical practice automation cost?
Every engagement starts with a $4,500 operations audit — fixed price, one week, and if it doesn't surface savings worth more than its cost, you don't pay. Build sprints are fixed-scope from $45,000, with the audit fee credited toward your first build. Ongoing work runs from $8,500/month, month to month. The audit prices the leak before you spend a dollar on the fix.
Will it work with our EHR?
If it has an API or an export, yes. Most EHRs — and the scheduling, billing, and fax tools around them — expose more than practices realize, and nothing gets ripped out or replaced. Confirming exactly what your systems will support is part of the audit, before you commit to any build.
How do you handle patient data and compliance?
Everything is built around your compliance requirements and runs on your infrastructure, under your permissions. You decide per system what the automation can read, what it can write, and what's off-limits — and every action can be logged. I'm not selling a boxed product; I build your system to your rules, and your compliance requirements shape the design from day one.
Who maintains the system after it's built?
You own everything — code, infrastructure, and documentation. Your team gets trained on operating it, and support is available without being mandatory. Practices that want ongoing building and upkeep use the fractional arrangement, from $8,500/month, month to month. Nothing is held hostage to a retainer.
Our front-desk staff isn't technical. Will they actually use it?
That's the design constraint, not an obstacle. These systems sit inside how your staff already works — the schedule fills itself, the prior auth drafts itself, the note shows up ready for review. If your team needs a manual, I built the wrong thing. Success is measured in admin hours removed, not another login added.
Start smaller
Where's the busywork? One hour, $300, credited in full.
Before a week-long audit: one hour on a call with you and whoever runs the spreadsheets. We walk the way work moves through your business, name the leak worth fixing first, and you leave with a written list of what to fix, in order. Yours to act on with anyone.
The $300 is invoiced before the hour and comes off the $4,500 operations audit or an agent's first month in full. Book the 15-minute call first: it sets the hour and the invoice.
The 15-minute call itself is free.
A note from Nick
From one North Carolina business to another.
Patients trust your practice with their health, and your front desk is the first person they meet. Every hour that desk spends on paperwork is an hour it can't spend on them.
I build the work around the visit: scheduling, reminders, intake, and prior-auth paperwork. Clinical judgment stays with your clinicians, and every draft note or code waits for their sign-off. I run a small business here in Charlotte, and I build for practice owners, not hospital IT departments.
On the call, I'll ask your practice manager where the day goes. That answer is where the plan starts. If the numbers don't work for your practice, I'll say so.
Nick George · Charlotte, NC
What a client said
“Nicholas delivered exactly what we wanted on time, and on budget. The end result was better than what we originally had in mind.”
AI training from
NVIDIA · Google · Microsoft · AWS
5 credentials, each with a public verify link. Check them →
13 hours a week per physician go to prior authorization. Every week.
Start with the leak, not the software.
One week, $4,500. I sit with your front desk and your practice manager, map where the hours go, and hand you a build roadmap ranked by ROI. The fee is credited toward your first build — and if the audit doesn't surface savings worth more than its cost, you don't pay.