JSBJJ Kylemore

A full stack project to organize student acquisition and connect the website to the academy's operations. The delivery included registration, authentication, and recurring payments, with a relational database, tracking, and production deployment.

Open project
JSBJJ Kylemore

Responsible for discovery, visual direction, interface architecture, frontend, backend, data modeling, external integrations, tracking events, deployment, and post-launch adjustments.

Responsive institutional website, adult and kids/teens lead capture pages, registration and login, recurring subscriptions, transactional emails, Google Maps, GoCardless, Meta Pixel, PostgreSQL/Prisma, and production deployment.

Next.jsTypeScriptTailwind CSSPostgreSQLPrismaFramer MotionGoogle APIsGoCardless APIVercelCloud deployment

Context

The academy needed more than a brochure site. New student acquisition involved interest, trial, registration, confirmation, and payment, but part of that flow still depended on manual steps. The challenge was to build trust with beginners and families while supporting the operational workflow behind the interface.

Solution

I structured the experience around conversion and clarity: dedicated pages for adults, kids, and teens, consistent CTAs, directed forms, and a visual hierarchy focused on trial and contact. On the backend, I organized registration, authentication, relational data, and recurring payment integration.

Decision: separate product workflows

The project combined a commercial website, registration, and subscriptions. I organized the foundation around separate responsibilities for the public website, registration flows, persistence, and external integrations. This makes each part of the journey from initial interest to payment explicit.

Decision: relational data and integrated payments

I used PostgreSQL with Prisma to persist the core registration data and GoCardless to integrate recurring subscriptions. Transactional emails accompany key steps, and custom Meta Pixel events track funnel actions. These serve different responsibilities: storing product data, connecting payments, and tracking acquisition.

Impact

The result was more mature than a standard institutional website: clear positioning, lead capture, onboarding, connected payments, and structured data. The operation became less dependent on disconnected manual processes and gained better visibility over acquisition, registration, and conversion.