Operations

From pilot to program: structuring an enterprise telehealth pilot

Most enterprise telehealth pilots that fail do so for reasons that have little to do with patients: the scope was too wide to read, the metrics were set after launch, or the review queue ate the calendar. A well-structured pilot answers one question in 90 days and leaves you on the platform you’ll scale on.

TL;DR

Run an enterprise telehealth pilot for 90 days: about 30 days of review and build, then 60 days live. Scope it to one care category, three to five states and one channel. Fix metrics, targets and data sources before launch, and start security, legal, procurement and clinical review together in week one. Write scale, extend and stop criteria in advance, and pilot on the contract you would scale on. At Lithos pay-as-you-go rates, 600 completed visits cost $28,500.

How should you structure an enterprise telehealth pilot?

Run it for 90 days: 30 days of review and build, then 60 days live, scoped to one category, three to five states and one channel. Fix the metrics before launch, start every internal review in week one, and pilot on the contract you’d scale on. On Lithos pay-as-you-go pricing, 600 completed visits cost $28,500, with no setup or platform fee.

Day 90 should end in one of three answers: scale, extend with a named change, or stop.

ScopePickWhy
CategoryOne, with clear existing demandOne protocol set, one set of messages, one support playbook
StatesThree to five where customers cluster, including one that requires live videoEnough volume, and both async and sync paths get tested
ChannelOne: app, website, benefits portal or in-store QREach extra channel adds design, tracking and support work and splits the data
AudienceExisting customers or employeesPaid acquisition answers a different question
Length90 daysLong enough to see follow-up and support patterns

Write the scope on one page and have the executive sponsor sign it. The 50-state telehealth compliance guide explains how modality rules vary, and which states to launch first gives a scoring model.

Fix the metrics before launch

Set each metric, its target and its data source in week one. A metric with no agreed source gets argued about at day 90.

MetricWhat it tells youWhere to measure
Intake completion rateWhether intake is the right lengthYour analytics plus encounter events
Completed visitsReal usage, and the basis of costEncounter completion webhooks
Prescription rateWhether the audience fits the protocolCompleted encounters with orders
Time from intake to decisionPatient experienceEncounter status timestamps
Follow-up or renewal shareWhether patients stay on therapyFollow-up encounters on the same care plan
Support contacts per 100 visitsOperating loadYour support system
Patient satisfactionWhether it meets your brand standardPost-visit survey
Cost per completed visit, fully loadedWhether the economics workInvoices plus internal cost

Measure from your own systems, using webhook events from the clinical layer, so the pilot’s data model is the one you keep. Prescription rate is a fit metric, never a quota: the clinical lead reviews declines for appropriateness, not conversion. The metrics that tell you a care program is working has illustrative targets.

Start every review in week one

TrackOwnerWhat they needTarget
Security and privacySecurity teamData flow diagram, HIPAA scope, BAA, questionnaire, SOC 2 statusDays 1–25
LegalCounselContract and BAA, your role versus the clinical role, marketing rules, consentsDays 1–25
ProcurementProcurement leadMSA, pricing model, data return on exitDays 1–20
ClinicalClinical leadProtocols, escalation paths, quality reviewDays 5–20
Marketing reviewBrand and legalLaunch copy, claims, channel trackingDays 15–25

Run together, the five reviews are done by day 25. End to end, the same windows take 97 days, longer than the whole pilot.

Ask each vendor for its current attestation status rather than assuming it. Lithos signs a BAA at onboarding and has SOC 2 Type II in progress. See answering the telehealth security questionnaire and the infrastructure RFP checklist.

The 90-day plan

Days 1–30, review and build:

  • Week 1: sign the scope, start the review tracks, get sandbox access and wire up a test flow.
  • Week 2: clinical lead reviews protocols; product designs intake and status messages.
  • Week 3: marketing drafts launch copy; support writes its playbook.
  • Week 4: end-to-end sandbox tests, reviews closed, go or no-go.

On licensed infrastructure the clinical and technical work can be ready in as little as three weeks, though pace varies. Week four is for your internal reviews.

Days 31–60, soft launch to a slice of the audience, such as one email segment or a few stores. Review metrics weekly and fix intake friction first.

Days 61–90, full pilot audience, scope frozen: no new states or categories. Results against day-one targets by day 85; decision meeting on day 90.

Review and buildSoft launchFull pilot audienceScope signedreviews startClinical + tech readyas little as 3 weeksGo / no-goreviews closedFull audiencescope frozenResults invs day-one targetsDecisionscale · extend · stopday 0 to day 90 · no new states or categories once the full audience opens
A 90-day pilot: 30 days of review and build, 30 days of soft launch to a slice of the audience, then 30 days at full pilot audience with the scope frozen. Results are assembled against day-one targets by day 85, and day 90 ends in scale, extend or stop.

Write the scale, extend and stop criteria up front

  • Scale if completed visits, completion and satisfaction hit target, cost per visit is in range, and no compliance or clinical-quality issue is open.
  • Extend for 30 to 60 days with one named change if demand is there but a metric missed for a clear reason: a long intake, a weak channel, a state mix heavy on video.
  • Stop if demand is below threshold after a fair test. On pricing that scales with use, a clean stop is cheap.

Four things blur the result: adding a state or category mid-pilot, buying a launch burst of paid traffic, counting signups instead of completed visits, and leaving support untracked.

What does an enterprise telehealth pilot cost?

Assume 600 completed visits over the 60 live days, about 300 a month. That stays in the first pay-as-you-go band.

At pay-as-you-go rates, 540 async visits at $45 ($24,300) and 60 live video visits at $70 ($4,200) come to $28,500 for the pilot’s 600 visits.

There are no minimums, so if demand comes in at half, so does the cost. Add usage-based add-ons only if needed (benefits checks or prior authorization for branded medications), plus your team and marketing. Medication passes through at pharmacy cost, with a small flat fee on mail-order orders.

Send us your category, candidate states and expected volume, and we’ll draft a one-page pilot scope and cost estimate with you on a call. Book a call.

Pilot on what you’ll scale on

When you scaleOn a temporary pilot setupOn Lithos
ContractRe-run procurement and legalSame agreement
IntegrationRebuildSame API, data model and webhooks from the sandbox
New statesRe-check coverage state by stateOpen them; licensure and compliance are handled
New categories and channelsNew vendorsSame care plan model and intake
PriceRenegotiateRates fall with volume: $40/$60 from 500 visits, $30/$50 from 1,000, $25/$40 from 2,500, each band at its own rate; or a flat committed rate from month one

For category detail, see telehealth for retail and pharmacy chains and adding prescription care to a consumer brand.

Lithos puts licensed providers, protocols, prescribing and pharmacy routing, and state-by-state compliance behind one API, under your own brand, so a pilot runs on the same integration and contract as the program it becomes. You keep pricing, patients and revenue; the sandbox is free and you pay per completed visit. On a call we’ll scope your pilot, commit to a launch date and start on your security questionnaire. Book a call or get sandbox access.

Frequently asked questions

How long should an enterprise telehealth pilot run?

Ninety days is a practical default: about 30 days for review and build, then 60 days live. That is long enough to see follow-up and support patterns in most categories, and short enough to hold executive attention.

What should a telehealth pilot measure?

Completed visits, intake completion, prescription rate, time to decision, renewal share, support contacts per 100 visits, satisfaction and fully loaded cost per completed visit. Agree each target and data source before launch, or the numbers will be argued about at day 90.

How many states should a telehealth pilot cover?

Three to five is usually enough. Choose states where your customers are concentrated, and include at least one that requires a live video visit for your category so the pilot tests both the asynchronous and synchronous paths.

How much does a telehealth pilot cost?

On per-visit pricing with no minimums, the clinical cost scales with use. At Lithos pay-as-you-go rates of $45 per asynchronous visit and $70 per live video visit, 540 async and 60 video visits cost $28,500. Add your internal team, marketing and any usage-based add-ons for the full number.

How do you scale a telehealth pilot without re-platforming?

Pilot on the same infrastructure, contract and integration you would use at scale. Scaling then means opening more states, adding categories and channels, and moving into a lower per-visit price band, without repeating procurement or rebuilding the integration.

Get started

Put a medical practice behind your product

Book a call and we'll scope your program together, or get free sandbox access and start building.

Book a call Get sandbox access

Free to startNo setup or platform fees