Skip to content
KayD
All work

Case study

Uniguru Operations Platform

The internal operations and CRM platform of Uniguru, a UK study-abroad consultancy: leads, admissions, partners, staff and compliance in one system.

Visit the site
Uniguru Operations Platform screenshot

Context

Staff work their leads, students and partners from one place, leadership has its own dashboards, and students and partner agents each get a portal.

It is a Next.js App Router application on Supabase: Postgres with row-level security, Auth and Storage. Every user has a system role, roles map to permission groups, and each route and server action checks the permissions it needs.

Background work runs as scheduled jobs on Vercel, with a GitHub Actions fallback for the SLA clock. The codebase is covered by Vitest unit tests and Playwright end-to-end tests.

Abstract illustration of leads, documents, roles and scheduled checks flowing through one connected system
Illustration, not a screenshot of the product.

System map

  1. People

    • Staff
    • Leadership
    • Students
    • Partner agents

  2. Interfaces

    • Staff workspace
    • Leadership dashboards
    • Student portal
    • Partner portal
    • Companion mobile app

  3. Services

    • Permission checks on every route and server action
    • Public lead-capture API
    • Versioned mobile API with push notifications
    • Scheduled SLA jobs, GitHub Actions fallback

  4. Data

    • Supabase Postgres with row-level security
    • Supabase Auth
    • Supabase Storage
Drawn from the documented facts of the project, top layer first.

The challenge

Uniguru, a study-abroad consultancy, needed one system for its lead pipeline, a staged admissions process, its partner agents and staff oversight, replacing an older system whose partner records had to be carried over.

Decisions

  1. Access is permission based: every user has a system role, roles map to permission groups, and each route and server action checks the permissions it needs.
  2. SLA clocks run as scheduled jobs on Vercel and record breaches, with a GitHub Actions fallback for the clock.
  3. A public lead API feeds the platform from the marketing site, with spam protection and deduplication.
  4. A versioned mobile API serves the student and partner app.

What it covers

  • CRM lead pipeline with stages, SLA queues, follow-ups and consultations
  • Student case management: applications, documents, visa, payments and deadlines
  • Permission-based access: system roles, permission groups and per-route checks
  • SLA monitoring that records compliance breaches on a schedule
  • Click-to-call softphone with call-log sync
  • Public lead-capture API with spam protection and deduplication
  • Mobile REST API with push notifications for the companion app
  • Task boards, an independent auditor module and a knowledge hub
  • Student and partner portals

My part

I am the main developer of the operations platform of Uniguru, a UK study-abroad consultancy.

Outcome

In production.