Build the funnel. Keep the guardrails.

Ship fast

From idea to a live funnel in an afternoon

Start from the corpus, not a blank page. Every one of our certified questionnaires is already wrapped as a ready-to-run funnel — pick one, edit the copy, set your theme, and publish. The clinical screens are built and approved before you arrive.

• →Template picker: the full certified questionnaire corpus, each wrapped as a working funnel
• →Form-based editor: rewrite copy, set theme, reorder steps, wire the checkout handoff
• →Publish is a licensure act — it records a clinical-plane hash and the provider who approved it

The two-plane moat

AI drafts. A licensed provider signs.

Describe your program and the AI matches it to a certified questionnaire, then writes the landing copy, the outcome page, and the theme — the presentation plane, which AI is free to author. The clinical plane — the medical questions, the disqualifiers, the consent — comes only from our certified corpus. AI never writes a live clinical screen. A licensed provider approves before anything publishes.

• →Presentation plane (marketing copy, theme, quiz, A/B variants): AI and the clinic author freely
• →Clinical plane (questions, disqualifiers, consent): drawn only from the certified corpus
• →Need a product the corpus doesn't cover? AI drafts a full questionnaire in the certified schema, a deterministic validator gates it, and a provider approves it before it can go live
• →Every publish produces a flow approval certificate — the clinical-plane hash and the provider who signed

PathwAI lets AI write every step. We don't. That difference is the certificate — and the E&O conversation it earns you.

Distribution

A hosted page or one line in your store

Every published flow ships two ways: a hosted URL you can point an ad straight at, and a self-contained embed you drop into the store you already run. Both are served from our BAA-covered API — never from a static host — because the moment a patient answers a medical question, that page is handling health data.

• →Hosted page at a neolife URL — served from the BAA-covered API
• →One-line embed: a self-contained flow.js you paste into Shopify, WordPress, or a custom storefront
• →Checkout is a handoff to your own store, carrying the certificate token — neolife never touches patient money

Your brand

It looks like your clinic, because it is

Theme every flow with your own colors, type, and voice through a set of CSS variables. Patients see one continuous brand from the first quiz question to the tracking email — no seams, no third-party logo in the way of the sale.

• →Brand theme tokens drive the whole rendered funnel
• →Edit copy on every step — landing, questions, outcome
• →White-label available on Scale and above

Measurement

Analytics that cannot leak PHI — by schema, not by policy

See views, sessions, qualified and disqualified counts, and where patients drop off, step by step. The funnel stats are PHI-free by construction: the schema simply has no field to hold a health answer, so there is nothing to leak. Not a policy you have to trust — a shape the data can't take.

• →Per-step drop-off, qualify and disqualify rates, session counts
• →PHI-free by construction — the schema carries no clinical detail
• →PHI-free event beacons, so measurement never becomes a liability

Optimization

A/B test the pitch, not the protocol

Run experiments on the presentation plane — headlines, imagery, the marketing quiz — with deterministic, sticky, server-side assignment. Variants can't touch the clinical questions, so the certificate is identical across every arm. You optimize the funnel without ever changing what a patient is actually asked.

• →Presentation-plane experiments only — the clinical plane is frozen across arms
• →Sticky server-side assignment; live control-vs-variant qualify rates
• →Same certificate on every variant, because the medicine never changed

Integrations

Send the signal, never the symptom

Flows talks to your ad stack and your CRM, but what it sends is governed by the same two-plane discipline. Ad pixels get hashed identifiers and a closed-vocabulary event — never an email, never a health detail. First-party CRMs, running under your own BAA, get the lead's name and a neutral funnel label — never clinical detail.

Hosting

Run it from your own domain

Point start.yourclinic.com at your funnel. Add the domain, drop in the CNAME and TXT records we hand you, and verification polls until it's live. Patients never leave your brand.

• →Custom domains via Cloudflare for SaaS
• →CNAME + TXT handed to you; verification polls automatically
• →Available on Growth and above

Attribution

The one attribution nobody else can offer

Every lead a funnel captures merges into a unified contact keyed on a PHI-free hash. When that contact is approved and becomes a patient, the thread holds — so you can see an ad click turn into a shipped medication. That line only exists if you own both the funnel and the fulfillment rail. We do.

• →Leads stitch into one Contact on a PHI-free email hash (email and name encrypted at rest)
• →Contact links to a Patient after approval — funnel-to-fulfillment attribution end to end
• →A Contacts view and a per-contact journey, from first click to tracking number

The wedge

PathwAI gets the patient to your door. We get the medication to theirs.

A funnel builder that stops at checkout is only half the job. Flows carries the patient through the certified intake, the provider approval, and the pharmacy routing your clinic already runs — one system, one certificate, one thread of attribution.

• →A BAA at every paid tier — not reserved for Enterprise
• →Pricing published on the page — not "contact sales"
• →Bundled into the tiers you already have — the builder just manufactures the routed orders your meter already counts
• →Gate the prescription, not the cart