Studio

Build the whole brand without writing code

Pages, theme, intake flow and catalog — authored visually, versioned like code, published to production in one click.

Why Studio

From idea to launch, faster.

Bring your storefront, patient intake, branding, and treatments together in one connected workspace. Create, customize, and launch new experiences without juggling tools or waiting on developers.

Sites and pages

Marketing pages, product pages, a 404, and the patient-facing storefront. Build from a template or from a blank canvas.

Intake flows

The questionnaire, the branching, the clinical assessment and the checkout, drawn as a graph.

Themes

Colour, type, spacing, radius, shadow and motion as tokens. Change one, and every page and flow that uses it follows.

Catalog

Products, pricing, offers and fulfillment, wired to the pharmacy network that fills them.

Site templates

Start from a template with its pages, theme and intake already wired together, then make it yours.

Shared layouts

Headers, footers and navigation live as layouts, reused by every page and flow that needs them.

Asset library

Upload or generate imagery once and reuse it across pages, products and flows.

Every brand in one place

Run several sites from one workspace, each with its own theme, catalog and intake flow.

Themes

Your brand, everywhere.

Create a look that's uniquely yours. Set your colors, typography, and visual style once, and watch it come to life across your entire telehealth experience—from your storefront to patient intake and checkout.

A component library, not a blank text box

Around 97 components across layout, media, text, actions, display, disclosure, inputs, selection, overlays, checkout, cart, catalog and product — plus a custom-code block for anything they don't cover.

  • Ready-made bands like heroes, pricing, FAQs

  • Usage tracking shows exactly which sites, pages and flows consume a theme before you change it.

  • Start from brand basics — a logo and a couple of colours — and Studio derives a full, consistent token set.

  • Draft and publish are separate. Every page keeps its version history, so you can preview a change, publish it, and roll back to any earlier version.

  • Preview bundles render the real page before it goes live — not an approximation.

Intake flows

Draw the intake, don't code it

Nodes, steps and transitions on a canvas. Branch on any answer, drop in a clinical assessment, collect files and ID photos, and hand off to checkout — without a developer.

Reuse what you built

Duplicate a step, copy a whole flow between sites, or paste a chain of steps you've already built.

Validated before publish

Validate and compile before you publish: the flow is checked as a graph, so a dead end or an orphan step is caught at build time, not by a patient.

A/B test entry paths

A/B test entry paths and aggregate the results into one experiment.

Configure, don't code

Custom fields, medical-assessment placement and OTP requirements are configuration, not code changes.

Publish

Go live, then see where patients drop

Assign a domain, run the launch plan, and publish. Afterwards, flow conversion, per-step metrics and experiment reports tell you which question is costing you patients.

Domain, launch plan, publish

Assign your domain, work through the launch plan, and publish when every step is green. Drafts stay private until you do.

Experiments on every flow

Run a variant of a question or a step, and read the experiment report to see which version keeps more patients moving.

Imagine it. Build it. Launch it.

Bring your telehealth brand to life with AI-powered creation tools. From storefronts to patient intake, build and launch connected experiences faster than ever.