The task
The client runs one-to-one tech support and training for older people. They needed to sell one-off sessions and a support membership online and get every buyer to a booked session without handling each sale by hand.
One detail shaped the whole build: the person who pays is often not the person who needs help. Adult children buy support for their parents.
What I built
- Eight pages on the client's own domain. Home, how it works, about, FAQ, contact and the legal pages (terms, privacy, cookies).
- Two purchase paths from the first screen. "Help for myself" and "Help for someone else", each with its own product page, order form and follow-up emails.
- Four products. A one-off session and a support membership with recurring billing, each in a personal and a gift version.
- Payment through Stripe. Cards, Apple Pay and Google Pay; the membership renews automatically and can be cancelled at any time.
- An email series after every purchase. Booking instructions go out the moment a payment completes, and the following emails lead the buyer to the first session. In the gift flow, the buyer receives instructions to pass on to the person they bought for.
- A renewal reminder 20 days before each rebill, so a membership never renews as a surprise.
- Spam protection. reCAPTCHA on the contact and newsletter forms from launch.
Decisions that mattered
Separate order forms for each path. Personal and gift purchases never mix, and the owner sees from day one which path brings buyers.
The gift flow as its own journey. It is a different situation, so it gets its own product pages, emails and wording rather than an extra checkbox in the personal flow.
Reminders before renewal, not after it. A buyer who knows a charge is coming is less likely to dispute it.
What changed for the owner
Payment links, booking instructions and pre-renewal reminders now go out from the system, not from the owner by hand. The owner's time goes to the sessions themselves.