How to Start a Telehealth Business: Model, Budget, Technology and Launch Plan
Key Takeaways
Licensure follows the patient’s location at the time of the visit, not your headquarters. Launch in one or two states and expand after legal review, not after demand.
Medicare telehealth flexibilities run through December 31, 2027 under the Consolidated Appropriations Act, 2026. DEA controlled-substance prescribing flexibilities expire a year earlier, on December 31, 2026.
A cash-pay pilot on an existing platform can launch for $60K–$150K. A multi-state insurance-based build with EHR and pharmacy integrations runs $250K–$700K.
A “HIPAA-compliant” video vendor does not make your business compliant. You still own the risk analysis, BAAs, access controls, training and incident response.
Do not build the revenue model on a temporary federal exception. The prescribing flexibility has been extended four times and still has no permanent rule behind it.
Starting a telehealth business is not the same project as launching a video-calling app. The actual visit may be only about 15% of the work. The rest involves attracting the right patients, hiring or contracting licensed clinicians in the correct states, protecting health information, collecting payments, and managing everything that happens before and after the appointment.
But doing it in that order can become expensive.
First, decide on the care model and operating requirements. From there, the platform, budget, and launch plan become much easier to define. It also helps prevent you from building a patient journey that you cannot legally deliver, which is the most common reason a telemedicine app development project gets rescoped.
This guide covers the sequence for a US telehealth business. It is not legal or billing advice, and state boards, professional rules, and payer policy need confirming for your specific model.
What Does It Take to Start a Telehealth Business?
Six things have to be true before the first paid visit. This includes a defined care model, clinicians licensed where your patients are, a documented patient journey with escalation paths, a working payment mechanism, a HIPAA program covering the actual data flow, and a platform that supports all of the above. Everything below is how you get each one.
The difference between telemedicine and telehealth matters more than it sounds, because it determines which regulations and reimbursement rules apply to what you are selling.
Pick a Narrow Care Model Before You Start a Telehealth Business
“Telehealth for everyone” is not a starting position. Define the patient, the problem and the clinical service.
Working examples:
- Follow-up care for an existing specialty practice
- Virtual behavioral-health visits
- Chronic-condition monitoring and coaching
- Employer-sponsored episodic care
- Cash-pay consultations in one specialty
- Hybrid care combining remote visits with partner locations
The narrower the first model, the easier it is define clinician requirements, visit length, intake questions, escalation rules, and marketing. It also gives patients a clear reason to choose you instead of a national brand with a much bigger budget.
Write a single sentence: “We help [specific patient] get [specific service] through [care pathway] in [initial states], paid for by [payer or patient].” If the team cannot agree on that sentence, it is too early to build anything.
Behavioral health is a common first wedge, and the build-versus-buy decision for behavioral health software plays out differently there than in general medical care because of documentation and consent requirements.
Decide Who Delivers Telehealth Care and in Which States
Licensure generally follows the patient’s location at the time of the visit, not your company’s address or the clinician’s home state. HHS describes several routes for practicing across state lines including full licensure, temporary-practice laws, reciprocity, interstate compacts and telehealth registration. It also advises verifying patient location before the appointment starts.
Build a state-by-state launch matrix covering:
- Professional licenses required per clinician type
- Corporate-practice-of-medicine and entity structuring rules
- Telehealth registration requirements
- Consent and documentation requirements
- Prescribing restrictions
- Malpractice coverage
- Rules for establishing the clinician-patient relationship
- Referral path for patients needing in-person or emergency care
Starting in two states is better than trying to launch in all fifty. Expand only after completing the legal and operational review for each new state, rather than responding to demand from a state you have not yet cleared. Start with the HHS cross-state licensing overview and confirm specifics with the relevant boards and counsel.
Map the Full Telehealth Patient Journey
Map everything from first website visit to follow-up:
- Patient finds the service and checks whether it fits their situation.
- Patient creates an account, verifies identity and location.
- Intake collects symptoms, history, consent, insurance or payment.
- The system routes the case to an appropriate clinician.
- The visit happens, with a documented fallback for technical failure.
- Clinician documents the encounter and issues orders or prescriptions.
- Patient gets instructions, receipts and follow-up tasks.
- The team handles messages, results, escalations and refunds.
For each step, name the owner and the failure path. What happens when the patient is in an unsupported state? Reports emergency symptoms mid-intake? Cannot get video working? Needs a physical exam? These answers shape both the business operations and the software. Skipping them is one of the main reasons a launch can get delayed by two months.
Choose How Your Telehealth Business Gets Paid
The revenue model drives most product decisions.
Cash pay simplifies early billing but demands transparent pricing, clear cancellation and refund policy, receipts and an explicit scope of what a visit includes. Demand has to be strong enough that people pay directly.
Insurance reimbursement widens access and adds credentialing, eligibility checks, coding, claims, denials and payer-specific rules. Coverage for a clinical service does not mean every delivery method, provider type or patient location gets reimbursed.
Employer or organization contracts offer predictable revenue against expectations for reporting, service levels, security review and integration. Define exactly what the customer can see without compromising patient privacy.
Subscription or membership supports ongoing care, but the offer has to be precise about clinical access, response times, renewals and what gets billed separately. Recurring billing, entitlement logic and plan changes push this closer to SaaS development than to a visit based product. Check state and payer implications before launch.
Medicare policy has moved recently. The Consolidated Appropriations Act, 2026 extended many Medicare telehealth flexibilities through December 31, 2027, including home as an originating site and audio-only delivery for non-behavioral services, while several behavioral-health provisions are permanent. Confirm current rules through HHS telehealth policy updates and your payers before building a forecast on them.
Define the Minimum Safe Telehealth Clinical Operation
An MVP is not permission to skip clinical safeguards. Before the first paid visit, establish:
- Patient identity and location verification
- Informed consent and privacy notices
- Inclusion and exclusion criteria for the service
- Emergency and escalation protocols
- Documentation standards
- Prescription, laboratory and referral workflows
- Coverage when a clinician is unavailable
- Response-time commitments for patient messages
- Quality review and incident reporting
Bring a clinical leader into product decisions early. Workflows that look efficient to an engineering team are regularly unsafe or unworkable in real care, and finding that out during the pilot is expensive.
Should Your Telehealth Business Buy a Platform or Build Custom Software?
An established platform is usually the fastest way to test a standard care model, bundling scheduling, video, intake, documentation and payment. Check the contract terms, export options, integrations and whether it supports your states and workflows before committing.
Custom software makes sense when the workflow itself is differentiated, several systems need to behave as one, or the off-the-shelf product generates too much manual work. Hybrid is the common answer when proven services for video, identity, payments and messaging, with the patient and staff experience are built around them.
Compare on:
- Fit with the clinical workflow
- Willingness to sign an appropriate BAA
- Access controls and audit logs
- Data ownership and export
- EHR, laboratory, pharmacy and payment integrations
- Reliability and support terms
- Configuration limits
- Total cost at your expected visit volume
The build-versus-buy trade-off for custom healthcare software covers the commercial side of this in more depth. Whichever way it lands, a healthcare app development company that has already shipped into your states will spot the licensure and consent branches before they become rework. When the business focuses on recurring virtual care and offers a different patient experience, a telemedicine platform built around your own operations is usually a better choice than trying to push a generic product beyond what it can handle.
Build HIPAA Compliance Into Telehealth Operations
HHS states that telehealth services provided by covered healthcare providers and health plans must comply with the HIPAA Rules, that these organizations must use technology vendors that comply, and that business associate agreements are required for the remote communication service where applicable.
In practice that means:
- A security risk analysis based on your actual data flow, not a template
- Role-based access and unique user accounts
- Encryption and secure configuration, verified rather than assumed
- Logs for access and significant actions
- Vendor and subcontractor review, including subprocessors
- Backup, downtime and incident response procedures
- Workforce training with records
- Patient guidance for private, secure visits
If the service will also operate in the UK or Canada, the wider healthcare app compliance picture adds GDPR and UKCA obligations on top of HIPAA.
A vendor’s compliance badge is not your compliance program. You remain responsible for how the product is configured and used. Review the HHS guidance on telehealth technology and involve qualified compliance counsel.
The engineering side of this is covered in more detail in how to build a HIPAA-compliant app, and Tech Exactly’s HIPAA-compliant therapy platform shows what the controls look like in a live behavioral health service.
Treat Telehealth Prescribing as Its Own Workstream
If the service includes prescribing, map federal and state requirements, clinical protocols, pharmacy connectivity, identity checks and monitoring obligations before launch. Controlled substances need particular care.
DEA and HHS issued a fourth temporary extension of the pandemic-era telemedicine flexibilities for prescribing controlled medications, which runs through December 31, 2026. This is only a temporary extension and does not remove the need for a legitimate medical purpose, proper DEA registration, professional licensing, or compliance with state laws.
The proposed Special Registration for Telemedicine framework has not been finalized. Verify the current position through HHS controlled-substance telehealth guidance before offering the service.
If the business model only works while this temporary exception remains in place, there is a clear deadline attached to the model. Build the backup plan now. GLP-1 prescribing is the sharpest current example, and building a GLP-1 telehealth platform carries a distinct set of clinical, supply, and compliance constraints on top of the general rules.
What It Costs to Start a Telehealth Business
Instead of asking for one overall “telehealth app cost,” break the budget into separate layers.
| Layer | What it covers | Typical US range |
|---|---|---|
| Business and clinical setup | Entity, legal and regulatory review, licensing, credentialing, insurance, policies | $25K–$90K |
| Technology (configured platform) | Subscriptions, configuration, light integration, security review | $35K–$90K |
| Technology (custom build) | Product development, integrations, cloud, security testing, monitoring | $150K–$450K |
| Operations (year one) | Clinician compensation, scheduling and support staff, billing, quality review | $120K–$400K |
| Patient acquisition | Website, content, paid acquisition, partnerships, positioning tests | $40K–$150K |
| Contingency | Licensing delays, credentialing, integration change, slow ramp | 15–20% of total |
A configured-platform cash-pay pilot in one or two states will realistically cost around $60K–$150K before the first visit. A multi-state, insurance-based service with EHR, lab, and pharmacy integrations can cost $250K–$700K.
The main comparison should be the total cost of delivering the care model, not just the cost of the video software. For a breakdown by product type and complexity, the healthcare app development cost tiers are a useful cross-check.
Launch Your Telehealth Business With a Controlled Pilot
Start with a limited pilot by restricting the geography, number of clinicians, patient group, and visit type. Keeping the scope small makes it easier to spot problems before they are hidden by growth.
Before the pilot, run representative test cases including unsupported locations, failed payments, dropped calls, urgent symptoms, prescription exceptions, data corrections, and records requests. Train staff on the actual escalation paths, not the documented ideal.
During the pilot, review operational signals daily, including visit completion, wait time, technical failures, booking-to-visit conversion, clinician utilization, support contacts, and any safety or privacy incident.
Before expanding, confirm three things. Patient acquisition cost is sustainable. Clinicians can deliver at the expected quality and pace. Follow-up work is not accumulating in somebody’s inbox off-system. Then expand one dimension at a time: a state, a visit type, or a channel.
A realistic 90-day sequence puts validation, state selection, and unit economics in days 1–30; platform configuration or build, vendor and security review, policy preparation, and clinician recruitment in days 31–60; and training, end-to-end simulation, and a limited pilot in days 61–90. Licensing, credentialing and custom integrations regularly push those dates. The sequence holds even when the calendar does not.
A telehealth company is a healthcare delivery business with software supporting it. If the business model, licensing, clinical operations, and economics are clearly defined before starting a large software build, the technology decisions become much easier.
Frequently Asked Questions
Not at the initial stage.A standard care model can usually be piloted on an existing platform. Custom software earns its cost when the workflow, integrations or patient experience creates a real advantage.
No, not automatically. Requirements vary by state and profession, and may involve full licenses, compacts, reciprocity or telehealth registration. Verify the patient's location and the relevant board rules before delivering care.
No, it doesn't. You still need contracts, policies, access controls, a risk analysis, training, incident procedures and secure workflows around the tool. The vendor covers its product, not your operation.
A small cash-pay pilot can be ready for its first visit in around 90 days. A multi-state telehealth platform that works with insurance usually takes about 6–12 months. In these cases, licensing and payer credentialing often take longer than the actual software development.
It should include service eligibility screening, identity and location verification, consent, scheduling, the visit, documentation, payment or billing, follow-up and escalation. The exact scope follows the clinical model.
A configured platform cash-pay pilot in one or two states costs around $60K–$150K to first visit. A multi-state insurance based build with EHR and pharmacy integrations costs$250K–$700K.
