Case Study

Mox Multisport Platform

I built and operated a production Next.js platform for a real specialty retail business, combining frontend architecture, product modeling, SEO structure, analytics, lead capture, enriched form metadata, and operational workflows into a customer acquisition system.

Platform overview

A production business system for specialty retail.

Mox Multisport is structured as a premium cycling and triathlon platform offering professional bike fitting, service work, product discovery, dealer positioning, quote workflows, custom bike builds, and high-ticket inquiry funnels.

I built, maintain, and operate the platform across frontend architecture, route structure, product modeling, customer workflows, analytics infrastructure, behavioral tracking, email delivery, deployment, and production iteration.

What I built

Production frontend application for a live specialty retail business
Customer acquisition pipeline for product, fitting, service, and custom build leads
Lead intelligence system with session path, device, referrer, and engagement metadata
Product model for bikes, fittings, service categories, dealer pages, and custom builds
SEO-focused route architecture for local, high-ticket, and product-specific search intent
Conversion-oriented inquiry forms and quote request workflows
Resend email workflows that package customer intent into actionable business context
Analytics tracking for traffic, attribution, engagement, and conversion behavior
Reusable component architecture for product pages, service sections, CTAs, modals, and forms
Mobile-first UX designed around real browsing behavior and customer decision paths
Production deployment, maintenance, and iteration through GitHub and Vercel
AI-assisted documentation and system review workflow for faster architecture refinement

Tech stack

Next.js App RouterReactTypeScriptTailwind CSSVercelGitHubGoogle AnalyticsVercel AnalyticsResendAPI routesFormsEmail workflowsSEO architectureSession metadataBehavioral trackingAI-assisted documentation

Systems architecture

How the platform turns traffic into business context.

The system connects public-facing pages, customer intent signals, form submissions, analytics events, enriched lead emails, and business follow-up into one operational workflow.

Lead intelligence

Form submissions package customer details, subject, source page, device metadata, engagement depth, referral source, and session path.

Product modeling

Bikes, fittings, service categories, dealer pages, product routes, and custom builds are structured as reusable content and interface patterns.

Operational workflow

SEO pages, CTAs, forms, API routes, Resend emails, analytics events, and follow-up context work together as one acquisition system.

Business impact

Turning anonymous traffic into qualified operational leads.

The platform captures customer intent, product interest, referral source, engagement depth, device context, and session path, then packages that information into actionable sales workflows for the business.

Development approach

I maintain and extend this platform through a production workflow built around TypeScript, reusable components, deployment discipline, analytics review, and incremental iteration.

AI-assisted workflow

I use AI-assisted development for planning, documentation, refactoring, code review, system modeling, and architecture reasoning while keeping implementation decisions grounded in production behavior.