Inam Baig / projects / happen

HealthTech / Consumer

Happen

UK weight loss medication platform, patient facing product experience.

Product management and lead technical consulting.

HealthcareUKin productionFeatured
Next.js
Rails
API

Role

Product Manager · Software Architect

Duration

2024-09 to 2026-06

Company

Happen

Domain

Healthcare · UK

Tech highlights

Next.jsRuby on RailsAPI integrations

Problem

What was hard

Overview

Patients need a trustworthy digital path to regulated weight loss treatment; operators need reliable onboarding and CRM workflows.

Users affected

UK patients and clinical/ops teams.

Why difficult

Regulated healthcare journeys spanning web, CRM, payments, and backend integrations.

Existing limitations

  • Complex onboarding and payments
  • CRM process friction

Constraints

  • UK healthcare context
  • Next.js + Rails ecosystem

Solution

Approach

Overview

Happen web product coordinated with backend APIs, client portal, and affiliate surfaces.

Architecture rationale

Split surfaces for consumer, partners, and ops with shared backend services.

Major components

  • Happen web (Next.js)
  • Backend API
  • Client portal
  • Affiliates

Key capabilities

  • Patient journeys
  • Backend integrations
  • CRM workflow support

Contribution

My contribution

Project outcome

I helped ship a production UK healthcare product at happen.co.uk.

What I personally owned

  • I owned product management across patient and ops journeys
  • I led technical consulting on API architecture, automation, and scalable Next.js/Rails solutions
  • I improved onboarding, payments, and CRM processes

Architecture

Interactive diagram

Zoom, pan, and select nodes to explore components and connections.

Happen spans a Next.js consumer web app, client portal, and Rails affiliates surface on shared Happen backend services. Product consulting covered onboarding, payments, and CRM workflows across those clients.

Loading architecture diagram…

Open in Architecture Lab →

Stack

Technology

Grouped by layer. No skill bar percentages.

Frontend

  • Next.js

Backend

  • Ruby on Rails / Node integrations

Challenges

Engineering challenges

  • Regulated weight loss journeys spanning web, CRM, payments, and partner surfaces

    Why hard

    Patients need a trustworthy path; ops need reliable onboarding and CRM; multiple clients (web, portal, affiliates) share domain logic.

    Solution

    I split consumer, partner, and ops surfaces on shared Happen backend services, and led product plus technical consulting on onboarding, payments, and CRM workflows.

    Result

    Production UK healthcare product at happen.co.uk with a coordinated product family.

Results

Outcomes

Outcomes

  • Live at happen.co.uk

Related

Related projects

Also look at

Want the full picture?

Ask me about Happen, download my CV, or browse the architecture lab.

View CVContact