Case study

Custom patient portal, cancellation save path, and payments that stop leaking.

Same three-brand GLP-1 group. Patients on monthly and multi-month subscriptions. Stock platform portal, cancellations by email to support, no referral, nothing sold after checkout.

2

Brands on one portal

5

Systems launched

100%

Payments checked after the charge

1

Cancel path, measured

24/7

Recovery running

Under NDA. Brand and revenue stay out. Scope and scale do not.

The problem

Where the money was leaving

Portal, cart, save path and recovery backend all sync with the care team's system and the lifecycle email tool the client already used.

A patient who paid in full and left in month two never reached margin.

The stock portal could not tell them when their box ships, so they emailed support, and support was the only cancel path, so every cancel was a lost conversation.

Nothing was sold to an existing patient. On the money side, some payments cleared while the record behind them failed, so earned revenue turned into refunds and tickets.

What we launched

Shipped, then tested

Custom patient portal

Both brands, one codebase, synced to the care team's system.

Portal cart

Payment built in, so every later purchase happens in the portal.

Cancellation save path

Every cancel is a decision the patient makes after seeing an offer. Measured like everything else.

Referral program

Tracked to the charge, not the click.

Payment recovery

Catches payments whose paperwork failed and fixes them before the patient notices.

Memberships in sync

Discounts, memberships and cancellations follow the payment record automatically.

Lifecycle email and SMS

Wired to real patient events: paid, shipped, refill due, cancel requested.

Admin analytics

A before/after on every retention change, same as acquisition.

The result

What changed

The second purchase and the cancel conversation both moved into a system we control and measure.

Payments that used to end as refunds and support tickets are recovered automatically.

Every retention change ships as a test with a before/after, same as acquisition.

Duration. Ongoing. Portal first, then cart and save path, recovery backend still growing.

2

Brands on one portal

5

Systems launched

FAQ

Asked on the scope call

Is this only checkout, or the money after the first order?+

Both. Upsell pages after checkout raise what the first order is worth, and the portal is where refills, doses and the clinician thread live, which is what decides whether someone is still paying in month three. Same system, same tests.

Does the portal actually make money?+

It is where the second, third and twelfth payments come from. A refill someone can approve in two taps, a dose change that does not need a phone call, and a relevant offer in the place a patient already trusts are worth more over a year than anything on the landing page.

Can we cancel?+

The audit is one time, a build is fixed scope at a fixed price, the retainer is month to month. Stop any of it and the pages keep running and keep charging, because the code, the repo and the deploy are yours. The only thing you lose is the next test.

Book a scope call

More patients. Each one worth more.

Book a scope call