Telehealth Buildout · end to end
From idea to first patient,
built to policy.
A telehealth brand is a chain: the offer, the intake (the questionnaire a patient completes before a prescriber decides), the prescriber, the pharmacy, the checkout, the tracking. Most launches buy the links from different vendors and glue them together after. We design and build the chain as one piece, with the ad policies read before the design, and hand it to you running.
Where you are
1 / 3
Takes about two minutes.
- End to end
- Model, intake, design, partners, tracking
- About 12 weeks
- Discovery to launch for an idea-stage build
- Yours from day one
- Code, contracts and accounts in your name
Who this is for
Three starting points, one build.
The funnel asks where you are because the answer decides which weeks of the process you skip, not whether the build fits.
- An idea and a category
- You know what you want to sell and to whom. You need the visit model, the partners, the brand, and a site that takes a patient from ad to prescription without tripping a policy. We build all of it.
- Prescribers or a pharmacy lined up
- One side of the backend exists. We build the other side, the intake that connects the two, and the front end that sells it, without disturbing the contracts you already hold.
- A live brand that needs a rebuild
- The site reads as a pharmacy to a policy reviewer, the intake loses people it should keep, or the tracking tells the ad platforms what condition each patient has. We rebuild on the brand you have while it keeps running.
Pick the model first
The visit model decides everything downstream.
Which partners you need, which states you can sell into, what the checkout looks like, and which ad channels are open all follow from one decision. It gets made in discovery, in writing, before anything is designed.
Async visit and subscription
The patient completes the intake, a licensed prescriber reviews it without a live call (an async visit), and the medication ships from a partner pharmacy on a subscription.
What it needs
State-by-state rules on asynchronous prescribing, prescribers licensed in every state you sell into, a pharmacy that ships there, identity verification, and billing built for refills.
Synchronous video
The patient books a video visit with a clinician, and the prescription or care plan follows the visit.
What it needs
Scheduling against a real prescriber roster, a video platform under a BAA, and an intake that qualifies people before the slot is booked, so clinicians are not paid to say no.
Hybrid clinic and online
A physical clinic adds online visits, refills, or a mail-order program next to in-person care.
What it needs
One patient record across both sides, an intake that routes each person to the right kind of visit, and tracking that credits the ad whether the patient walked in or checked out online.
What we build
Everything between the ad and the prescription.
Seven workstreams, one team, one plan. Nothing is handed off to a vendor you have never met, and nothing ships without the policy read that keeps the ad accounts alive.
Which visit model fits your category and the states you sell into, what the offer costs, and how it renews. Settled in writing before anything is designed, because every later decision hangs on it.
Intake flows and eligibility quizzes written for your brand and your clinical protocol: the questions the prescriber needs, in the order that keeps people moving, with nothing a policy reviewer would flag.
Design from the wordmark to the confirmation screen. Built to load in under two seconds on a phone, and to read as a clinic rather than a pharmacy when a platform reviewer looks at it.
Payment, recurring billing, refills, pauses and cancellations, with the disclosures healthcare subscriptions are held to.
Prescriber network, EHR, pharmacy fulfilment, payments, identity verification and telehealth platform, shortlisted for your model and your states, then connected and tested. Contracts sit in your name.
Server-side tracking with generic event names from the first visit, so a platform learns that a conversion happened and nothing about the condition behind it. Attribution holds through the click-out, the moment a patient leaves your site for a partner's checkout or booking page.
Pages, disclosures and account structure built the way LegitScript, the certification Meta and Google require before prescription drugs can be advertised, reviews them. Certifying becomes a filing, not a rebuild.
Intake flows and quizzes
The intake is the product.
Nobody meets your prescriber first. They meet the quiz. It decides who can be treated, what the platforms think your site is, and how many of the people who clicked ever reach the checkout. That is why it is written for your brand and your protocol, question by question, not copied from a template.
- Eligibility
- The quiz asks exactly what your protocol needs to say yes or no: age, state, history, contraindications. People who cannot be treated find out in the first minute, not after they have paid.
- Policy
- Platforms read your intake pages the way they read your ads. A question phrased as a second-person symptom, or a URL that names a drug, can pull the account into restricted data, the tier where the platform starts throttling what your tracking can send. Every question is checked against the same rules as the creative.
- Conversion
- A template intake asks template questions and loses people at each one. A bespoke flow asks fewer, in your brand's voice, and puts the calendar or the checkout where the momentum is. That difference compounds on every ad dollar you ever spend.
Backend partners
Six contracts, chosen against your model.
The right pharmacy for a five-state async brand is the wrong one for a hybrid clinic, which is why this page lists categories, not names. We shortlist against your states, model and volume, make the introductions, and connect what you sign. Every contract is in your name.
- Prescriber network
- Licensed coverage in the states you sell into, async or video to match the model, and response times you can put in the offer.
- EHR / EMR
- Holds the chart, the visit record and the prescription. Chosen for the API your intake can write to, not for the logo.
- Pharmacy fulfilment
- Ships what you prescribe to the states you serve, compounded or retail, with the licensing to survive a LegitScript review.
- Payments
- A processor that underwrites telehealth knowingly. The wrong one freezes funds the first month the volume looks real.
- Identity verification
- Confirms the patient is who the intake says, the way state telehealth rules require, without losing half of them at the upload step.
- Telehealth platform
- Video, scheduling and messaging under a BAA, where the model includes a live visit.
The process
About twelve weeks, in the open.
The weeks overlap because the work does. Partner contracting and certification review are the two steps outside our control, and when one of them moves the date, you hear it that week, not at the end.
- 01
Weeks 1 to 2
Discovery
Category, states, offer, what already exists, and the rules that apply to each. You get a written model recommendation and a fixed scope at the end of it.
- 02
Weeks 2 to 4
Model and partner selection
The visit model is fixed. Prescriber, EHR, pharmacy, payments and identity partners are shortlisted against your states and volume, introductions made, contracts signed in your name.
- 03
Weeks 3 to 6
Intake and design
The intake and eligibility quiz are written with your clinical lead and reviewed against platform policy. The brand and site are designed screen by screen, and you approve before anything is built.
- 04
Weeks 6 to 10
Build
Site, intake, checkout, subscription and every partner connection built, then walked end to end with test patients until the chain holds.
- 05
Weeks 9 to 12
Certification and tracking
LegitScript filed where the category requires it. Server-side tracking installed and verified event by event. Ad accounts structured before the first dollar of spend.
- 06
Week 12 onward
Launch and first campaigns
Live on the channels open to your category, with attribution from the first click through the intake to the first prescription.
You launch owning all of it.
The code, the design, the intake, the partner contracts, the ad accounts and the tracking are in your name from the first week. If we part ways the day after launch, everything keeps running without us.
Plan a buildoutHanded over at launch
- Model document
- The visit model, states, offer and pricing, with the reasoning that produced each decision.
- Intake and quizzes
- Every question, branch and disqualification, documented, with a policy note on any question a reviewer could read wrong.
- The site
- Design files and code in a repository under your account, from the first commit.
- Partner stack
- Contracts in your name with every backend partner, connected and tested with test patients.
- Tracking
- Server-side delivery live, generic events verified one by one, and a document that says what each event means.
- First campaigns
- Ad accounts structured and the first campaigns live on the channels open to your category.
Buildout questions
Asked on every scoping call.
Do you build on your platform or ours?
Yours. The site lives in a repository under your account, the partner contracts are in your name, and the ad accounts are yours. We build on a modern stack we know well, or on your existing platform when it can be made compliant.
Who owns the code, the design and the intake?
You do, from the first commit. Nothing sits in an account we hold, nothing is licensed back to you, and if we part ways the build keeps running without us.
How long does a buildout take?
About twelve weeks from discovery to launch for an idea-stage build. Partner contracting and certification review are the steps we control least, so they are the ones that move the date, and we say so the week it happens. A rebuild of a live brand is usually shorter because the partners already exist.
What does it cost?
A fixed fee for a fixed scope, quoted in writing after discovery and paid in phases that match the process. There is no figure on this page because a single-state rebuild and a fifty-state async launch are different projects, and a number that has to be caveated is worse than none.
Can you work with our existing pharmacy or prescriber group?
Yes, if they can serve the states you sell into and connect to the intake. We verify both in discovery. If they cannot, we say so and shortlist alternatives next to them, and the decision stays yours.
Do we need LegitScript before launch?
Only to name a prescription drug in ads on Meta or Google. You can launch on the channels that are open while certification is in review, and the site is built so the application is a filing rather than a rebuild.
Will you write the clinical protocol?
No. Your medical director owns the protocol. We turn it into an intake that collects what the prescriber needs, in the order that keeps people moving, and we flag any question a platform reviewer would misread.
What happens after launch?
The build ends at launch, with campaigns live and tracking under them. Ongoing marketing is a separate retainer, scoped like every other engagement. If you take it, the site, the intake and the tracking are already the ones the campaigns need.
Tell us where you are.
Three steps, about two minutes. You hear from the person who would run your discovery within one business day.
Plan a buildout