
Feb 18, 2026
IN /
AI technology
3 min read
What running a telehealth company taught me about automating operations
Lessons from building and running ElevatedHealth — where the bottlenecks actually were, and which ones AI could genuinely remove.

Konrad Sudyka
AI Automation Consultant
The bottleneck in a telehealth business is almost never the clinical work. It is everything that has to happen before and after the visit — intake, eligibility, documentation, follow-up. That is where automation earns its keep.

The work around the visit is the real work
When we were running ElevatedHealth, clinicians were never the constraint. The constraint was everything wrapped around the appointment: collecting intake information, verifying insurance eligibility, matching a patient to a licensed provider in the right state, chasing documentation, and following up afterward. Each of those steps was small. Together they decided how many patients we could actually serve in a week.
The instinct is to buy a tool for each of those steps. What actually worked was mapping the full path a patient takes, finding the handoffs where information had to be re-entered or waited on, and automating those specific joins. The tools mattered far less than knowing which twenty minutes of the process were costing us a day.
Automate the handoff, not the judgment
The steps worth automating in healthcare operations are the ones with a clear right answer: pulling eligibility from a payer, routing a patient to a provider licensed in their state, generating a follow-up task when a result lands, flagging an incomplete chart before it becomes a billing problem. These are rules, not judgment calls, and a system executes them the same way every time.
The steps that involve clinical judgment stay with clinicians. The goal is not to make software practice medicine. It is to make sure that by the time a clinician opens a chart, everything that could have been prepared already has been.
What I look for now
When I work with a company today, the first question is never which model or platform to use. It is where work stops moving. Usually that is a queue nobody owns, a spreadsheet acting as a database, or a step where someone re-types information a system already has. Those are the places automation pays for itself quickly and visibly.
Running the business first is what makes this obvious. You learn quickly which problems are worth solving with software and which are just the cost of doing the work.

Feb 18, 2026
IN /
AI technology
3 min read
What running a telehealth company taught me about automating operations
Lessons from building and running ElevatedHealth — where the bottlenecks actually were, and which ones AI could genuinely remove.

Konrad Sudyka
AI Automation Consultant
The bottleneck in a telehealth business is almost never the clinical work. It is everything that has to happen before and after the visit — intake, eligibility, documentation, follow-up. That is where automation earns its keep.

The work around the visit is the real work
When we were running ElevatedHealth, clinicians were never the constraint. The constraint was everything wrapped around the appointment: collecting intake information, verifying insurance eligibility, matching a patient to a licensed provider in the right state, chasing documentation, and following up afterward. Each of those steps was small. Together they decided how many patients we could actually serve in a week.
The instinct is to buy a tool for each of those steps. What actually worked was mapping the full path a patient takes, finding the handoffs where information had to be re-entered or waited on, and automating those specific joins. The tools mattered far less than knowing which twenty minutes of the process were costing us a day.
Automate the handoff, not the judgment
The steps worth automating in healthcare operations are the ones with a clear right answer: pulling eligibility from a payer, routing a patient to a provider licensed in their state, generating a follow-up task when a result lands, flagging an incomplete chart before it becomes a billing problem. These are rules, not judgment calls, and a system executes them the same way every time.
The steps that involve clinical judgment stay with clinicians. The goal is not to make software practice medicine. It is to make sure that by the time a clinician opens a chart, everything that could have been prepared already has been.
What I look for now
When I work with a company today, the first question is never which model or platform to use. It is where work stops moving. Usually that is a queue nobody owns, a spreadsheet acting as a database, or a step where someone re-types information a system already has. Those are the places automation pays for itself quickly and visibly.
Running the business first is what makes this obvious. You learn quickly which problems are worth solving with software and which are just the cost of doing the work.

Feb 18, 2026
IN /
AI technology
3 min read
What running a telehealth company taught me about automating operations
Lessons from building and running ElevatedHealth — where the bottlenecks actually were, and which ones AI could genuinely remove.

Konrad Sudyka
AI Automation Consultant
The bottleneck in a telehealth business is almost never the clinical work. It is everything that has to happen before and after the visit — intake, eligibility, documentation, follow-up. That is where automation earns its keep.

The work around the visit is the real work
When we were running ElevatedHealth, clinicians were never the constraint. The constraint was everything wrapped around the appointment: collecting intake information, verifying insurance eligibility, matching a patient to a licensed provider in the right state, chasing documentation, and following up afterward. Each of those steps was small. Together they decided how many patients we could actually serve in a week.
The instinct is to buy a tool for each of those steps. What actually worked was mapping the full path a patient takes, finding the handoffs where information had to be re-entered or waited on, and automating those specific joins. The tools mattered far less than knowing which twenty minutes of the process were costing us a day.
Automate the handoff, not the judgment
The steps worth automating in healthcare operations are the ones with a clear right answer: pulling eligibility from a payer, routing a patient to a provider licensed in their state, generating a follow-up task when a result lands, flagging an incomplete chart before it becomes a billing problem. These are rules, not judgment calls, and a system executes them the same way every time.
The steps that involve clinical judgment stay with clinicians. The goal is not to make software practice medicine. It is to make sure that by the time a clinician opens a chart, everything that could have been prepared already has been.
What I look for now
When I work with a company today, the first question is never which model or platform to use. It is where work stops moving. Usually that is a queue nobody owns, a spreadsheet acting as a database, or a step where someone re-types information a system already has. Those are the places automation pays for itself quickly and visibly.
Running the business first is what makes this obvious. You learn quickly which problems are worth solving with software and which are just the cost of doing the work.

Feb 18, 2026
IN /
AI technology
3 min read
What running a telehealth company taught me about automating operations
Lessons from building and running ElevatedHealth — where the bottlenecks actually were, and which ones AI could genuinely remove.

Konrad Sudyka
AI Automation Consultant
The bottleneck in a telehealth business is almost never the clinical work. It is everything that has to happen before and after the visit — intake, eligibility, documentation, follow-up. That is where automation earns its keep.

The work around the visit is the real work
When we were running ElevatedHealth, clinicians were never the constraint. The constraint was everything wrapped around the appointment: collecting intake information, verifying insurance eligibility, matching a patient to a licensed provider in the right state, chasing documentation, and following up afterward. Each of those steps was small. Together they decided how many patients we could actually serve in a week.
The instinct is to buy a tool for each of those steps. What actually worked was mapping the full path a patient takes, finding the handoffs where information had to be re-entered or waited on, and automating those specific joins. The tools mattered far less than knowing which twenty minutes of the process were costing us a day.
Automate the handoff, not the judgment
The steps worth automating in healthcare operations are the ones with a clear right answer: pulling eligibility from a payer, routing a patient to a provider licensed in their state, generating a follow-up task when a result lands, flagging an incomplete chart before it becomes a billing problem. These are rules, not judgment calls, and a system executes them the same way every time.
The steps that involve clinical judgment stay with clinicians. The goal is not to make software practice medicine. It is to make sure that by the time a clinician opens a chart, everything that could have been prepared already has been.
What I look for now
When I work with a company today, the first question is never which model or platform to use. It is where work stops moving. Usually that is a queue nobody owns, a spreadsheet acting as a database, or a step where someone re-types information a system already has. Those are the places automation pays for itself quickly and visibly.
Running the business first is what makes this obvious. You learn quickly which problems are worth solving with software and which are just the cost of doing the work.
(qtf® — 11)
Insights & Research
More articles
More articles
More articles
Notes on AI systems, architecture decisions,
and lessons from real deployments.
No hype. Just systems
Clarity beats automation
Decisions over demos
Designed for messy reality
Systems that hold under pressure

(qtf® — 15)
OUR PRINCIPLES
Book a
free call
We design AI systems that improve real work —
not just demonstrate technology.
We design AI systems that improve
real work — not just demonstrate technology.
We’ll review your
workflows, identify
where AI can create
impact, and outline
a clear path forward.
We’ll review your workflows, identify AI opportunities, and outline a clear path forward.
We’ll review your workflows, identify where AI can create impact, and outline
a clear path forward.
No preparation needed — we’ll guide the conversation
and focus on what matters.
No preparation needed — we’ll guide the conversation and focus on what matters.




40+ clients
4.9/5
1.5k reviews on Clutch
1.5k reviews








