Mark Lauren — From Platform Architect to CTO
My work with Mark Lauren began as a platform build and evolved into long-term technical leadership.
I first partnered with Mark while serving as Director of Technology at Brave People, where I led the architecture and development of his original digital subscription platform. In 2023, I began working with Mark directly and stepped into the role of CTO, taking responsibility for day-to-day technical operations and the platform's long-term direction.
What began as a system build became platform stewardship — architecting the foundation, operating it as a live business system, and guiding its continued evolution.
The Business Problem
Mark Lauren's training content had grown over more than a decade. Books, DVDs, PDFs, and video programs existed across multiple formats and delivery systems.
The material itself was strong. The structure around it was not.
Users navigated a fragmented collection of products rather than a cohesive training experience. The business lacked a durable subscription platform. Content delivery had to work reliably across devices and global network conditions. And the digital product did little to support consistent engagement.
The real task was transforming media into a usable digital system.
Building the Original Platform
At Brave People, I led the architecture and development of the first platform designed to unify Mark's training ecosystem. The goal was to create a structured experience where users could access programs, complete workouts, and maintain consistency over time.
The decision to build as a progressive web application was deliberate. It avoided app-store friction, simplified distribution, and ensured reliable cross-device access for a global user base.
Platform Architecture
- —React-based progressive web application
- —Structured content model for training programs
- —Stripe-powered subscription billing
- —JW Player video delivery with global CDN
- —Intercom for integrated communication and support
Encouraging Consistency
Training platforms succeed when users stay consistent. One product decision played a key role in retention: lightweight gamification. The system introduced simple mechanics that reinforced completion and progress.
The goal was not competition. It was accountability. Small signals of progress helped users maintain momentum and return to the platform regularly.
Gamification Mechanics
- —Points for completed workouts
- —Streak tracking
- —Milestone rewards
- —Leaderboards and progress visibility
Transition to CTO
In 2023, the relationship shifted from project delivery to direct technical leadership. I began working with Mark directly and stepped into the role of CTO, taking responsibility for the platform as a live operational system rather than a finished product.
This phase marked a fundamental change in the work. The focus moved from launching software to sustaining and evolving a digital business.
CTO Responsibilities
- —Day-to-day technical operations
- —Infrastructure and hosting oversight
- —Platform reliability and security
- —Product planning and technical direction
- —Vendor and systems stewardship
- —Continuity across subscriptions, billing, and support
Operating a Live Digital Platform
Launching a platform is only the beginning. Operating it is where most of the real work happens.
The Mark Lauren ecosystem spans multiple interconnected systems: content management, subscriptions, mobile distribution, community platforms, analytics, and support tooling. Each component must work together without disrupting the customer experience.
My role has involved maintaining coherence across this environment — resolving customer-impacting issues, preserving access to legacy products, managing vendor integrations, and guiding modernization without breaking existing workflows. Much of this work is invisible to users. But it is what allows a live digital platform to remain stable while it continues to grow.
Stability is not accidental. It is the result of continuous technical stewardship.
Building the Next Generation — Hooya!
While operating the existing platform, a major focus has also been building forward. Hooya! is a workout library and exercise timer built from scratch — moving the product beyond passive content delivery toward a more interactive training experience.
Designing Hooya! required translating training methodology into software architecture. The stack was chosen deliberately: React and TypeScript for a maintainable component-based frontend, Supabase for auth, database, and storage, and BunnyCDN for performant media delivery. TanStack Query handles all data fetching and caching, keeping the UI in sync with the backend without unnecessary complexity.
The application separates public and admin routes via React Router, with context-based state management for auth and admin roles. Zod handles runtime validation on forms where data integrity matters most. The goal was not simply to ship a feature — it was to build a solid, extensible foundation for the next phase of the platform.
Hooya! Capabilities
- —Structured reusable exercise library
- —Session-based workout flows with timer
- —Role-based access for public and admin users
- —Media storage and delivery via BunnyCDN
- —Form validation with Zod
Architecture Decisions
- —Supabase for auth, database, and serverless functions
- —TanStack Query for data fetching and cache management
- —Context-based state for auth and admin roles
- —shadcn/ui and Radix UI for accessible components
- —Vite for fast development and optimised builds
Outcomes
Business
- —Profitable in under a year
- —Full investment recovered
- —Platform growth to 10,000+ users
Technical
- —Unified subscription platform
- —Scalable training content delivery
- —Next-generation product — Hooya!
Leadership
- —Transition from external technical lead to CTO
- —Long-term technical stewardship
- —Continued product evolution
My Role
Across this work, my role has included:
- —Platform architecture
- —Product development leadership
- —Infrastructure and vendor stewardship
- —Operational continuity
- —Platform modernization
- —CTO-level technical direction
I built the original foundation, then became responsible for helping the business run on top of it — and guiding the platform into its next phase.