I'm a practicing nurse anesthetist who designs and builds automation and software for independent healthcare practices. I've worked the clinical side of the desk for years — so the systems I build fit how a practice actually runs on a busy Tuesday, not how it looks in a sales deck.
Missed-call text-back, review generation, appointment confirmations, patient reactivation — the revenue-adjacent workflows that leak money when they depend on a busy front desk.
Mapping where staff hours actually go, then wiring the repetitive parts — intake, follow-up, scheduling handoffs — to run in the background against the tools a practice already uses.
Consent-tracked SMS pipelines, feedback analysis, and review flows built for healthcare's rules — TCPA-compliant messaging with audit trails, not a generic marketing blaster.
When off-the-shelf doesn't fit: multi-tenant backends, internal dashboards, and operational tooling — built lean, deployed fast, owned by the practice.
Every automation vendor claims to "understand healthcare." I administer anesthesia in it — patient flow, staff bandwidth, the gap between a workflow that looks fine on paper and one that survives a full schedule.
And I build the systems myself. No handing your practice to an offshore dev team, no reselling white-label software. The person who scopes the problem is the person who ships the fix.
Active CRNA — inside hospital and surgical operations every week, not consulting from memory.
Scheduling friction, front-desk load, follow-up lapses — I've watched where the hours and revenue actually go.
From Postgres schema to Twilio compliance registration to the n8n workflows in between.
No moonshot pitches. Systems get scoped against a measurable outcome and shipped in weeks.
Schematics of production systems I've designed and built. Client identities stay private by default — the architecture speaks for itself.
Every missed call gets an instant, compliant text within seconds — opening a two-way thread that books the patient before they dial the next practice on Google. Consent captured and logged on every send.
The foundation under every client deployment: one hardened backend where each practice's patients, SMS consent records, and audit trail live behind row-level security — isolation enforced by the database, not by good intentions.
I run my own 1099 anesthesia practice on systems I built: monthly invoicing generated from templates, mileage and deduction tracking computed automatically, output filed and drafted for review — never auto-sent. I'm my own first client.
Screenshots & case detail available on a call — client data stays out of public pages.
I've spent my career inside operating rooms — administering anesthesia across DFW hospital systems and surgical specialties since 2020. Anesthesia is a systems discipline: monitor everything, anticipate failure, act before the problem compounds. That mindset didn't stay in the OR.
Between cases I taught myself to build — databases, automation pipelines, compliant messaging infrastructure — and turned it into Solitude Enterprise, where I build the operational systems independent practices can't get from enterprise vendors and can't staff internally.
I run everything as an operator: my own contracting practice, my own billing systems, my own company. If I recommend a system, it's because I'd run it myself — and usually already do.
— Sean
One working session. Bring the workflow that annoys you most — I'll tell you honestly whether it's worth automating, what it would take, and what I'd build first.