Telemedicine App Development Cost in 2026: Video, eRx and Licensure

Telemedicine app cost by platform type in 2026

Every telemedicine product has a video call in it, which is why founders tend to price it as "a booking app plus Zoom." That estimate is usually off by a factor of two. What separates a $70k product from a $500k one is who the patients are, how many states the clinicians practice in, whether the app prescribes, and whether it has to live inside a hospital's systems.

The ranges assume an iOS and Android app (cross-platform) plus a provider and admin web app, built by a vendor team with design, QA and project management included. Rates follow what we see in 2026 proposals and match our nearshore rates breakdown: about $45–75 an hour for senior engineers in Central and Eastern Europe or Latin America, $130–200 for a US agency.

This article is the telemedicine slice. If your product is broader (patient portals, RPM, clinical decision support, FDA-regulated software), our healthcare app development cost guide covers the full regulatory tier system, including HIPAA in depth and when software becomes a medical device. Here we focus on what telehealth adds: video, prescribing, licensure and per-visit economics.

Where the money goes in a telehealth visit flow

Follow one patient from "I need to see someone" to "my prescription is at the pharmacy" and price each step. In the estimates we prepare for multi-state platforms, the split usually looks like this:

Two things in that chart matter for budgeting. Video is the largest single step and still under a fifth of the build. And the three orange columns, licensure matching, prescribing and security, are the ones cheap quotes leave out, because none of them show up in a Figma prototype.

Cost driver 1: video, and why minutes are the cheap part

Almost nobody should build telehealth video from scratch in 2026. The serious options are HIPAA-eligible video SDKs from Twilio, Vonage and Zoom, or self-hosted open-source WebRTC. Here's how they compare on price at the time of writing:

Do the math on a busy practice: 2,000 visits a month at 20 minutes with two participants is 80,000 participant minutes, which costs about $250–330 at list price. For a direct-to-consumer startup doing a few hundred visits a month, media costs are lunch money. What actually costs money is the plan tier or contract that comes with a Business Associate Agreement, and the engineering around the call:

• A waiting room that tells the truth. Patients need to know the provider is running late; providers need to see who is ready, who failed the device check and who has been waiting 15 minutes.
• Failure handling. Reconnection after a network drop, switching from Wi-Fi to cellular mid-visit, audio-only fallback, and a way for the provider to call the patient's phone when video fails. In our QA plans for telehealth, connection edge cases take more test time than the happy path.
• Device and permission checks. Camera and microphone permissions on iOS, Android and every major browser, before the visit, not at minute zero.
• In-visit extras. Screen sharing, a third participant (interpreter, caregiver, second clinician), in-call chat and file sharing. Each one adds testing across platforms. Recording usually shouldn't be on by default: it creates PHI you then have to store, protect and retain.

Engineering for a production-ready video module on an SDK typically runs $20k–45k at Central European rates. Self-hosting can add $60k–150k more before it handles real-world networks well, which is why we recommend it only once volume or media requirements justify it.

Cost driver 2: e-prescribing and the 2026 DEA deadline

If your clinicians prescribe, the app needs e-prescribing. Almost every telehealth product does this through a certified partner such as DoseSpot or DrFirst, which connects to the Surescripts network and handles drug databases, pharmacy directories and interaction checks. Building your own Surescripts certification only makes sense for EHR vendors.

Per-prescriber licenses are the recurring part. DoseSpot's own published market estimates put e-prescribing platforms at roughly $500–800 per prescriber per year for small accounts, with controlled-substance prescribing (EPCS) as an extra fee of about $75–135 per prescriber per year. EPCS also brings DEA requirements: the prescribing software must be certified for EPCS, prescribers go through identity proofing, and every controlled-substance prescription is signed with two-factor authentication.

Medicare is more settled for now. The Consolidated Appropriations Act, 2026, signed on February 3, 2026, extended the Medicare telehealth flexibilities (home as originating site, no geographic restrictions, audio-only visits) through December 31, 2027. If you bill Medicare, your product roadmap has about a year of certainty, not five.

Cost driver 3: state licensure and provider operations

Clinicians generally need a license in the state where the patient is physically located during the visit, not where the clinician sits. A platform that serves patients in 30 states needs clinicians licensed across those states, and software that never routes a Texas patient to a provider licensed only in New York.

That rule becomes a surprising amount of product:

• A provider credential model. Licenses per state, DEA registrations per state, board certifications, malpractice coverage, expiry dates and reminders. Admins need to see what's expiring before a provider gets booked into a visit they can't legally do.
• Location checks. Patient state captured at booking and confirmed at visit start, because people travel. Some states also have their own rules on consent, prescribing and the provider-patient relationship.
• Routing and scheduling. Matching the next available eligible provider, balancing load across a network, handling time zones, and showing patients honest availability for their state.
• Payouts and contracts. Many telehealth networks pay contractor clinicians per visit, which means visit tracking, rate tables and payout reports.

The licenses themselves are an operating cost. The Interstate Medical Licensure Compact, which now covers more than 40 states plus DC and Guam, speeds up physician licensing but charges a $700 application fee plus each state's license fee. Nurse practitioners and other professions have their own compacts and rules. Budget the software side at $15k–40k for matching, credentials and admin; budget the licenses in your operating plan.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Retail · Startup700+stores aggregatedMobile application for Grocery shops→Food delivery3.5 moto MVP launchOptimizing and controlling delivery for a Pizzeria Chain→EdTech4 moto a full iOS app on the App StoreA mobile app to develop brain functions→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Estimate your telemedicine app

This calculator gives you two numbers that founders usually see in separate spreadsheets: what the build costs, and what each visit costs to run. It uses the hour ranges we see in our own telehealth estimates and the public list prices of the three video SDKs. Try switching e-prescribing on and adding states first.

Two things usually surprise people. At 1,500 visits a month, video is a few hundred dollars; even at 20,000 visits it stays well below maintenance. Licenses, BAA-tier plans and upkeep are what grow. Switch on EHR integration and the build jumps by six figures, which is why enterprise telehealth is a different business from direct-to-consumer, not a feature upgrade.

Custom, SDK-based or white-label? A 6-question check

Not every telehealth business needs custom software. The quiz follows the questions we ask in a first call to decide between renting a platform, building around SDKs and partners, and building a full platform.

What we see in telehealth estimates and first calls

We've built and reviewed health products including a mental health app and a web and mobile platform for a medical lab. Telemedicine scopes repeat the same budget mistakes:

• The provider side is forgotten. Founders design the patient app in detail and describe the clinician side as "a dashboard." In practice the provider web app, with queues, charting, prescribing, messaging and availability, is often bigger than the patient app. Clinicians use it eight hours a day, so it has to be fast.
• Async is underrated. A questionnaire-first visit reviewed by a clinician costs less to build than polished live video, and clinicians can handle more cases per hour. Several direct-to-consumer models work mostly async with live video as the exception. If your specialty allows it, and state rules on establishing a patient relationship permit it, start there.
• Operations are pushed to "later." Licensure tracking, provider payouts, refunds and no-show handling end up in spreadsheets. That works for 50 visits a week and breaks at 500. We usually scope a thin admin tool from day one.
• Analytics and support tools leak PHI. Session replay, crash reporting and chat widgets capture screens with symptoms and medications. Replacing them with BAA-covered tools late is a common, avoidable cost.
• Bad networks are tested last. The demo runs on office Wi-Fi. Real patients join from a parked car on one bar of LTE. Our internal metric is that only 5% of tasks sent to QA come back to developers, and on telehealth projects that depends on testing network drops, permissions and device matrices in every sprint.

Budget overruns aren't unique to healthcare. A McKinsey and University of Oxford study of more than 5,400 IT projects, published in 2012, found that large IT projects ran 45% over budget on average while delivering less value than planned. Telehealth adds outside gatekeepers you don't control: e-prescribing partner certification, app store review of health claims and, for enterprise products, hospital security reviews. A 15–25% contingency is planning, not padding.

Hidden costs after launch

Telehealth has more usage-based and per-seat costs than most apps. These are the lines that show up after launch:

Why the security line is non-negotiable: IBM's 2025 Cost of a Data Breach report put the average healthcare breach at $7.42 million, the highest of any industry. For a telehealth startup, the more common damage is a payer or health system ending a partnership talk after a security questionnaire.

How to reduce the cost without breaking the product

1. Rent the regulated plumbingUse a HIPAA-eligible video SDK, a certified e-prescribing partner and a clearinghouse instead of building any of them. Put each behind your own service interface. The Twilio Video end-of-life scare in 2023 showed why: teams with a wrapper changed one module, teams without it rewrote their visit flow.
2. Launch async-first if your specialty allows itQuestionnaire visits with clinician review are cheaper to build and to run. Add live video for cases that need it.
3. Start in the states you already coverBuild the licensure model for 50 states, but launch where your clinicians already hold licenses. The matching logic is cheap; licensing clinicians everywhere on day one is not.
4. Responsive web before native appsMany patients join a telehealth visit once or twice. A well-built mobile web flow avoids app store review and download friction. Add native apps when repeat visits or push reminders justify them; cross-platform with React Native or Flutter costs roughly 25–35% less than two native apps.
5. Keep controlled substances out of v1 unless they are the businessEPCS adds cost, identity proofing and regulatory uncertainty past December 2026. If your model doesn't depend on it, add it later.
6. Pay for discoveryA few weeks of business analysis to map the visit flow, PHI touchpoints, partners and state rules before estimating. It's the cheapest way to avoid paying twice for the provider app.

Cuts that look cheap and aren't: consumer-grade video tools without a BAA, a single shared clinician login, skipping the waiting room, recording every visit "just in case," and no audit log of who opened which chart.

Picking a team: rates, time zones and HIPAA

For US buyers the realistic choices are a US onshore agency, a Latin American nearshore vendor, a Central and Eastern European vendor (offshore, with partial overlap) or an Asian vendor. Senior rates in Latin America and CEE are similar, about $45–75 an hour. Latin America shares most of the US working day. Teams in Poland or Cyprus share roughly 2–4 hours with the East Coast on shifted schedules and little with the West Coast. That works well when product decisions happen in a few scheduled calls a week, and less well when your medical director wants to test visit flows live every afternoon Pacific time.

For telehealth specifically, ask any vendor three things: will it sign a BAA if its people could touch PHI, can it build and test with synthetic patient data so engineers never need production access, and has it shipped real-time video to production on both iOS and Android. If you are comparing outside vendors, our list of healthcare mobile app development companies in the USA is a starting point, and our offshore development cost guide covers the rate and overhead math.

FAQ

Where Gilzor fits

We build healthcare software for providers, pharmacies and health-tech companies, including the mobile apps and web apps that telehealth products are made of. We work from Poland and Cyprus, offshore for US clients, with a few shared hours a day with the East Coast.

Send us your visit flow, the states you plan to serve and whether you prescribe. We'll split the estimate into video, prescribing, licensure, compliance and product lines, so you can see what each decision costs before you commit to it.