The short answer
Two founders can run a telehealth brand to around 1,000 active patients if they split the work into growth and operations, contract the clinical and legal roles, and let a platform do the work that is really software: intake, routing a case to a licensed provider in the patient's state, charging after approval, retrying failed cards, pushing pharmacy status to the patient, and handling refills in a portal. The first full-time hire is usually a support lead, somewhere between 300 and 1,000 patients.
The roles that never move to software are the medical director's oversight, judgment calls in support, marketing, and compliance review of what you say in public. No platform removes those, and a founder plan that assumes otherwise is how brands end up in the Reddit post-mortems.
We have no verified salary data for this market, so this post does not quote salaries. Where we give contractor prices, they come from published sources, and every patient-count threshold is our estimate.
The staffing table
| Role | 0 patients (launch) | 300 active patients | 1,000 active patients | Contractor or hire |
|---|---|---|---|---|
| Founder 1: growth | Brand, storefront copy, first audience, LegitScript file | Ads, creative, affiliates, email | Same, managing an agency or freelancers | Founder |
| Founder 2: operations | Entities, pharmacy, processor, vendor contracts | Support, pharmacy exceptions, refunds, reporting | Managing support, finance, compliance calendar | Founder |
| Medical director | Signs protocols, owns the PC in most structures | Chart review, adverse events, protocol updates | Same, likely more states and more review hours | Contractor; from about $799 a month for a director service, $6,000 or more multi-state |
| Prescribing clinicians | Routed by platform or contracted | Same | Same, more states or more hours | Contractor or provider network |
| Healthcare counsel | MSO-PC agreement, policies, consent forms | Ad and claims review on request | Annual review, new states | Contractor, project-based |
| Support | Founder 2 | Founder 2 plus a part-time contractor | First full-time hire | Contractor, then hire |
| Paid media | Founder 1 | Founder 1, maybe a freelancer | Agency or freelancer | Contractor |
| Creative and content | Founder 1 | Freelancer | Freelancer or small retainer | Contractor |
| Bookkeeping and tax | Contractor | Contractor | Contractor | Contractor |
| Engineering | None | None | None, or one part-timer using the API | Contractor if at all |
The engineering row is the one that changes most between a platform brand and a custom build. A self-assembled stack needs at least one engineer from day one and a standing team at volume, which is the argument we made in the build vs buy analysis.
What the platform absorbs
This is the work that used to justify an operations team. On a platform like Turbopills it happens inside the system.
| Work | Who does it without a platform | On a platform |
|---|---|---|
| Intake and eligibility screening | Someone reviews form PDFs and rejects unqualified patients by hand | Conditional intake screens in real time and builds a structured chart |
| Routing a case to a licensed provider in the patient's state | A coordinator matches state to provider license and chases review | State-aware routing assigns it automatically |
| Charging after approval, failed-card retries, refunds | A billing person and a pile of Stripe exceptions | Subscription starts on approval; smart retries; one-click refunds |
| Pharmacy hand-off and status | Faxes, emails and "where is my order" tickets | Orders route to integrated pharmacies with live tracking pushed to the patient |
| Refills and messages | Inbox triage and manual reorders | Branded portal and mobile app with messaging, check-ins and refill automation |
| Patient and order records | Spreadsheets across five tools | One admin console |
Each row is a job description you do not write. It is also the reason our launch timeline post shows the software track collapsing into a few weeks on a platform.
What stays human
Clinical oversight. The medical director is a contractor at almost every brand this size, and the arrangement deserves more attention than it gets. Someone has to sign the protocols the intake enforces, review a sample of charts, own the response when a patient reports a serious side effect, and decide when a protocol changes. Routing software decides who sees a case; it does not decide what good care looks like. Our medical director guide covers sourcing and pricing, and the side-effect triage post covers the workflow the director should sign off.
Support escalations. A portal with live pharmacy status removes the most repetitive tickets. What remains is harder: the patient who was charged and wants to cancel before the shipment, the one whose pharmacy is out of stock, the one whose message is really a clinical question. Those need a person who knows where the administrative line ends and the clinical one begins. AI agents handle more of the first tier every quarter (we covered what works in agentic patient support in production), but escalations stay human.
Marketing. Creative, offer testing, audience building, affiliate relationships. This is the job Founder 1 should spend nearly all of their time on by month three, and the one most likely to be under-resourced because founders spend it fixing operations instead.
Compliance review. Every ad, landing page and email makes a claim. Someone with authority, usually counsel or the medical director, should read new claims before they ship, especially for GLP-1, hormones and peptides, where FDA has sent warning letters to telehealth marketers in three waves since September 2025. A platform can enforce billing and consent rules in the product. It cannot read your Instagram captions.
The three stages, briefly
Zero patients. Both founders are doing paperwork. Founder 2 owns the entity, pharmacy, processor and policy tracks; Founder 1 owns the storefront copy, the LegitScript application and the first audience. Contractors: counsel, medical director, bookkeeper. Nobody else.
Three hundred patients. Support volume starts to matter, and it lands on Founder 2. We plan on the assumption that a mature program's support load scales roughly with active patients and spikes at refill dates, shipping delays and price changes; that is a planning assumption rather than a measured benchmark, and you should replace it with your own tickets-per-100-patients number from month one. When Founder 2 spends more than half the week in the support queue, add a part-time contractor with written macros and an escalation path to the medical director.
One thousand patients. The part-time contractor becomes the first full-time hire, and the founders stop answering tickets. Paid media probably moves to a freelancer or agency. The medical director's hours go up, and if you have expanded states, so does the director fee. This is also where the platform choice gets tested: if billing exceptions or pharmacy status are still producing tickets, the software is not absorbing what it should, and that shows up as a second support hire.
Why support comes before marketing
Founders want the first hire to be growth. We think that is usually wrong. A growth hire at 300 patients brings more patients into a support queue that one founder is already drowning in, and several of the month-two churn triggers we track are service failures: slow answers to side-effect questions, billing friction, support questions left unresolved (the month-two churn post lists them). A support lead protects the revenue you already paid to acquire.
We would change our mind for a brand with a very low ticket rate and a proven channel that only needs more budget and hands. That brand exists. It is rarer than founders think.
Where Turbopills fits
Turbopills is built for exactly this company. The storefront, conditional intake, state-aware provider routing, billing after approval with smart retries, pharmacy routing with live status, the branded portal and mobile app, and an affiliate program run as one system, and the headless GraphQL API is there if you later want a part-time engineer to build on top. What we do not replace: your PC, your medical director, your marketing, your compliance review and the humans who handle escalations.
We are in private beta with hands-on onboarding and limited capacity, and we quote per program. In the demo, ask us to show which of the rows in the table above produce zero tickets on our system, and which still need a person.
FAQ
How many employees does a telehealth startup need? Two founders can run a single-program brand to around 1,000 active patients with contractors for the medical director, counsel, bookkeeping and creative, if a platform handles intake, routing, billing and pharmacy status. The first full-time hire is usually support.
Do I need to hire doctors to start a telehealth company? You need a medical director (usually a contractor who owns the professional corporation) and licensed prescribers in each state you serve, who can be contracted or provided through a network. You do not need to employ them full time at launch.
What does a telehealth medical director cost? Director services advertise from about $799 a month. Nurse practitioners report collaborating physicians at $500 to $1,000 a month, and multi-state oversight can run $6,000 a month or more.
Should I hire marketing or support first? Support, in most cases. Slow answers and billing friction are common month-two churn triggers, and a support lead protects revenue you have already paid to acquire.