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
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.
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.
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.
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.
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.
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 staff time per physician, per week, on prior authorization alone.
of admin work for every hour of patient care in independent practices — before anyone sees a patient.
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.
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.
For a mid-market reverse logistics-tech company, I built the MCP server and agent tooling their internal teams use every day — Python on Google Cloud, wired into live inventory and truckload workflows, supporting 50+ internal users.
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.
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.
Run a plant or a project office instead? The same work exists for manufacturers and contractors.
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.
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.
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.
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.
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.
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.