Case study 01

JAXIS StatLab

A statistics service for students and researchers in the Philippines: a public website to send a study, and a workspace where clients, analysts, reviewers and finance work through it together.

Role
Designer & Full-Stack Developer
Timeline
Jul 2026 – Present
Status
Live in production
Built with
Next.js, React, TypeScript
jaxis-statlab.com
JAXIS StatLab website
  • 6user roles, each with its own view
  • 9steps every study moves through
  • 2analysts check every result
  • 3parts: website, app, design system
Overview

What it is

JAXIS StatLab runs statistical analysis for thesis groups and researchers. A client sends their data, gets a fixed price, pays by GCash or bank transfer, and receives clear tables and plain-English write-ups that a second analyst has checked. I designed and built the whole product: the public website, the workspace app where every role does its part, and the design system both share. Besides the core workflow, the app covers chat between clients and analysts, defense practice sessions, revisions and refunds, notifications, and reports.

The challenge

Many hands, one study

A statistics service involves many hands: the client, the analyst, a reviewer and whoever handles money. Done over chat and spreadsheets, things slip.

  1. 01

    Files and revisions get lost. Datasets, drafts and change requests end up spread across chats and email.

  2. 02

    Everyone sees everything. Without separate views, a client could get results before review or before paying.

  3. 03

    Pricing and payouts take time. Rush fees, package tiers and each person's share were worked out by hand.

What I built

One workspace for everyone

One workspace where each study moves through fixed steps and each role only sees and does its own part.

  • A 9-step workflow from request to payout. A study can't skip a step.

  • A separate view for each role, so people only see their own part of the work.

  • Results are released only after review is done and the final payment is in.

How a study moves

9 steps, in order

Every study follows the same path, and the app won't let one skip a step.

  1. 1Request
  2. 2Quote
  3. 3Payment
  4. 4Assignment
  5. 5Analysis
  6. 6Review
  7. 7Delivery
  8. 8Revisions
  9. 9Archive & payout
Who uses it

6 roles, 6 views

Each role signs in to its own view and only does its own part.

  • Client

    Sends a study, approves the quote, pays and gets the results.

  • Statistician

    Runs the analysis and writes up the results in plain English.

  • Reviewer

    Checks the work before anything reaches the client.

  • Finance

    Confirms payments and pays the team.

  • Admin

    Looks after accounts and day-to-day settings.

  • Leadership

    Sees how the business is doing as a whole.

Under the hood

How it's built

  • 01

    One codebase, three parts

    The public website, the workspace app and a shared design system are built together, so a change to a button reaches both apps at once.

  • 02

    Careful with money

    Payments and payouts either complete in full or not at all, so nothing is half-saved or counted twice.

  • 03

    Each role, its own access

    People only see and do what their role allows.

  • 04

    Private by default

    Client data and files stay private and are shared only with the people working on that study.

  • 05

    Pages arrive filled in

    Pages load their data before they reach the browser, so dashboards show up ready instead of loading.

  • 06

    A website that explains

    The public site explains the service in plain English, with pricing, scroll animations and pages written for people searching for thesis help.

Tools

What it runs on

  • Next.jsBoth apps
  • ReactUser interface
  • TypeScriptAcross the codebase
  • Tailwind CSSShared design system
  • PostgreSQLDatabase
  • GSAPWebsite animations

Have a project like this in mind?

Tell me what you're building. I'll reply with how I'd approach it and what it would take.

All Rights Reserved© 2026 Barth Serceña
Local Time
--:--:--, UTC+8