Beta Next.js · PayPal

Health Platform.

I’m building a platform for a client in the health sector, and the first stages are live.

The problem
The client had the content and the participants, but no tool that fit. People paid by bank transfer and got access through an email link that often never arrived.
The solution
Booking, payment, a weekly programme with exercise videos and a private group now sit in one place, behind one login.
How I built it
I built the platform with my AI team, one stage at a time, and the client signed off each stage. In our conversations, the planned weekly app grew into a platform for several health topics.
The health platform on day 4 of back week: the week from Monday to Sunday at the top, then today’s session with an exercise video, a group call at 2 pm and the week overview with the PayPal booking.

How a health programme moves online.

People who offer health coaching, nutrition advice or exercise programmes often run them through Facebook groups, the odd newsletter and weekly plans as PDFs. That works while there are only a few participants, but it can’t keep up with more. Payment is a manual bank transfer, and access comes through an email link that often doesn’t arrive.

For the client this was a constant problem. She has the content and the customers, but no tool that fits. Off-the-shelf platforms like Kajabi are too big and too expensive for a German practice with 50–80 participants per season.

Booking, programme and group now sit in one place.

The platform takes the booking through PayPal and then unlocks the weekly programme, with a plan, exercise videos and daily reminders. On top of that there is a private chat for participants and a check-in at the end of each week. Everything is in one place, behind one login.

The first two stages are built and live. More are coming, and the client signs off each one. Along the way, the planned weekly app has become a platform for several health topics. It grew out of conversations with the client.

/ tech decisions

Three decisions that mattered.

Payment

PayPal, because the audience knows it

Most participants are over 50 and are used to paying online with PayPal. Stripe, another payment provider, would have been more elegant technically. Here it matters more that as many people as possible finish their booking (the conversion rate) than how pleasant it is to develop.

Sign-in

Email and password, no login link

The users know signing in with an email and a password. A login link sent by email (a magic link) doesn’t suit them: it lands in spam and looks dodgy. A cookie whose timer restarts with every visit keeps people signed in for 30 days after their last visit.

Content

Weekly plans as text files in the project

The client maintains her content herself, in clearly structured Markdown files. That is plain text with a few symbols for headings and lists. There is no need for a CMS or Notion. Every change is recorded in git, and each upload puts the site live again.

On request Status   Beta · users give feedback

/ other apps