Custom Business Platform · Beauty Industry

Glitz &
Glamour
OS

A fully custom platform built for a US-based nail salon — replacing five disconnected tools with one system that handles bookings, loyalty, wallet passes, CRM, content, analytics, and client communication, all under one brand.

Next.js Prisma + PostgreSQL Apple Wallet API Google Wallet API Resend + SMS Vercel CMS + CRM + Analytics
Project Type
Vertical SaaS-style
operating system
Primary Goal
Replace fragmented tools
with one platform
Business Impact
Better retention, tighter ops,
full business visibility
Project Snapshot
Industry
Beauty / nail salon
Client Location
United States
Project Scope
Full-stack web platform
Role
Design, architecture,
frontend & backend
Focus Areas
Retention, operations,
brand experience
Deployment
Vercel + Supabase

Not a brochure website. Not a basic booking app. A connected system built to run, grow, and retain clients inside one owned platform.

Case Study Positioning Statement
01 · Executive Summary

What this platform actually does

Glitz & Glamour OS was built as a single source of truth for the business. Every touchpoint a client has — finding the salon, booking an appointment, earning rewards, getting reminders — now lives inside one branded product. The owner manages everything from one admin panel.

Customer Lifecycle
End‑to‑end

Discovery, booking, follow-up, rewards, referrals, and reviews — all in one product.

Operations
Unified

Admin dashboard, CRM, bookings, communications, and content publishing — all connected.

Retention Engine
Built‑in

Loyalty cards, milestone rewards, birthday perks, referral links, and wallet-based engagement.

Client Experience
Premium

Branded booking flow, mobile-first account area, and native wallet passes for returning clients.

02 · The Problem

Why the old setup wasn't working

Most small service businesses run on four or five separate tools stitched together with manual effort. That creates friction, lost data, and a weaker client experience.

1

Fragmented tools

Bookings, loyalty, reviews, marketing, and reporting each lived in a separate system with no shared data.

2

Manual overhead

Staff spent time on manual follow-ups and copy-pasting between systems instead of focusing on the client.

3

Weak retention

No single place for clients to see their loyalty progress, past visits, or upcoming appointments under the brand.

4

No real visibility

The owner had no first-party data dashboard. Business decisions relied on disconnected reports from third-party apps.

The solution was to build one connected system from scratch — designed around how this specific business actually runs, not around generic templates.

03 · Architecture

How the system is structured

The platform is built around meaningful business objects — not isolated pages. Every feature connects back to a central data model.

Data foundation

Core data entities include users, admin users, services, bookings, loyalty cards, stamps, reviews, referrals, wallet devices, page views, and notification logs — all connected in one schema.

Access control

Customer sign-in and admin access are separated by design. Clients only see their own data. Admins see everything. No shared login, no role confusion.

Workflow-driven backend

API routes handle booking state transitions, wallet updates, media uploads, review requests, notification dispatch, and analytics — all as platform logic, not one-off scripts.

Primary Stack

Next.js + Prisma + PostgreSQL

A solid foundation for a product that needs public pages, authenticated client areas, admin workflows, structured data, and custom backend behavior — inside one maintainable codebase.

Supporting Integrations

Wallets · Notifications · Cloud storage · Image processing

These integrations move the platform beyond basic CRUD. They give it mobile ecosystem hooks, first-party communication infrastructure, and real content management workflows.

04 · Feature Surfaces

What clients and the owner actually see

The platform surfaces shown below cover the full client and admin experience.

Public website homepage
Booking flow
Client profile
Apple Wallet pass
Google Wallet pass
Loyalty card
Booking confirmation
Referral screen
Services browse
AI chat
05 · Client Experience

Discovery, booking, loyalty, engagement

The client-facing side is designed to convert and keep clients. Every step from finding the salon to becoming a loyal regular is handled inside one brand experience.

01 · Discovery & Trust

Portfolio-first website

The homepage, services page, gallery, and blog work together as an acquisition layer. It's not just presenting services — it's building trust through visuals, clarity, and content.

  • Dynamic homepage with strong first impression
  • Service browsing with pricing and descriptions
  • Gallery showcasing craftsmanship and results
  • Blog engine for local SEO and authority
02 · Conversion

Custom booking funnel

Instead of redirecting clients to a generic third-party scheduler, the platform keeps them inside the brand. That preserves trust and captures richer booking context before the appointment starts.

  • Service and add-on selection
  • Date and time scheduling
  • Inspiration image uploads
  • Policy and waiver acknowledgment
03 · Retention Loop

Profile, loyalty, referrals

Logged-in clients get more than a receipt page. Their account becomes a repeat-visit surface with booking history, loyalty progress, earned perks, and referral mechanics.

  • Past and upcoming appointments
  • Digital loyalty card progress
  • Referral code generation
  • Birthday and milestone reward visibility
04 · Ongoing Engagement

Chat + reviews

The experience doesn't stop after booking. An AI chat layer handles repetitive questions, while the review system turns happy appointments into captured social proof.

  • AI assistant for service and booking queries
  • Secure review request links
  • Support for review media uploads
  • Lower support friction, higher trust
06 · Loyalty & Wallets

The strongest retention layer

Loyalty here isn't a simple stamp counter. It's a full retention infrastructure with wallet integration, milestone triggers, birthday incentives, and referral mechanics.

Apple Wallet

iPhone clients can add a branded loyalty card directly to Apple Wallet. The system tracks registered devices and pushes updates when loyalty activity changes — no app download needed, no friction.

Google Wallet

Android clients get the same experience through Google Wallet. The business has parity across both major mobile ecosystems, giving every returning client a native-feeling loyalty experience.

Milestone rewards

Structured triggers — like a 10-stamp unlock — make the loyalty card feel meaningful, not decorative. Clients have a real reason to come back.

Birthday incentives

Time-based perks give the business a seasonal touchpoint to re-engage existing clients without needing a separate email tool.

Referral mechanics

Referral links turn satisfied clients into a lightweight acquisition channel. No third-party referral software needed.

Loyalty card — client view
07 · Admin & CRM

The owner's command center

The admin side is where the platform moves beyond a client-facing product. It acts as a complete internal tool suite for operations, communication, and growth.

Bookings & calendar

The owner can view pending appointments, check client reference images, and confirm or manage bookings — all from one screen without switching to a separate scheduling tool.

Customer CRM

Each client has a full internal record: contact details, booking history, private notes, loyalty status, and uploaded reference imagery. Richer context than any generic booking system provides.

Operational visibility

Notification logs, analytics, task tracking, and system observability give the owner more insight into how the business is running than any third-party dashboard would.

Admin dashboard overview
Booking management screen
Customer CRM screen
Services management
Reviews management
08 · Marketing & Growth

Owned acquisition and reputation systems

The platform doesn't just run operations. It also builds acquisition channels the business owns — through content, reviews, and re-engagement.

SEO content engine

An integrated blog gives the business a direct channel for local search traffic, education, and branded content — without needing a separate CMS or marketing tool.

Review generation workflow

After a successful appointment, the owner can send a secure review link to the client. Reputation-building becomes an active process, not something left to chance.

Verified review logic

Review submission is tied back to completed appointments, which supports authenticity and reduces low-trust or fake submissions creeping into the record.

Legacy proof preservation

Older review history can be imported or synchronized, so the business doesn't lose social proof when migrating away from a previous platform.

Content management screen
Analytics dashboard
Notification log
09 · Communications

What makes the platform feel reliable

Communication, logging, and analytics don't show on the surface — but they're what makes a platform feel complete to anyone who actually operates it day to day.

Email + SMS workflows

Booking confirmations, reminders, reschedule notices, cancellations, loyalty milestones, and owner alerts are all built into the platform's core logic — not added via a third-party plugin.

Notification log

Every outbound message attempt is recorded. That makes support easier, issue diagnosis faster, and gives the owner confidence that communications are actually being delivered.

First-party analytics

Page tracking and event data is captured natively. The business has visibility into what clients are doing without depending entirely on Google Analytics or a third-party tool.

Why it matters

Operational maturity

These features signal that the build was designed for real-world operation — not just a polished launch day. They support follow-up, debugging, observability, and iteration over time.

Best supporting screenshot

Analytics or notification log

If you have one especially strong admin screenshot, analytics or notifications work well here — they visually reinforce the "complete system" framing of the case study.

10 · Technical Depth

Why this is a strong portfolio piece

This project shows breadth, systems thinking, and applied business logic — not just frontend skills. Multiple difficult areas are combined into one coherent product.

Auth flows

Social sign-in, email authentication, onboarding, and a clean admin vs. customer separation — done properly with role-based access throughout.

Domain modeling

Bookings, loyalty cards, rewards, CRM records, reviews, referrals, wallet devices, and content objects — all modeled and connected in one schema.

Integration work

Apple Wallet, Google Wallet, email delivery, SMS, image handling, cloud storage, and analytics — real integrations, not placeholder APIs.

Internal tooling

Admin dashboard, CRM, content management, notification log, analytics view, and task tracking — built as a proper internal product, not as an afterthought.

The strongest framing isn't "I built a salon website." It's "I designed and built a custom operating system for a service business — combining bookings, loyalty, wallet passes, CRM, analytics, and growth tools into one unified platform."

Glitz & Glamour OS isn't just a booking website. It's custom digital infrastructure for running, growing, and retaining clients inside a modern beauty business — built and owned by the brand.

11 · Outcome & Positioning

What this case study should leave behind

The main takeaway isn't that the interface looks polished. It's that the product solves the business at the workflow level — acquisition, conversion, operations, retention, and visibility all improve when the stack becomes unified.

Business transformation

The platform moves the business from running on disconnected third-party tools to owning its own tailored digital infrastructure. That's a fundamentally different starting position.

Client trust and retention

Branded flows, wallet convenience, and reward mechanics create a more premium and memorable experience — one that generic booking apps can't replicate.

Signal to future clients

This project communicates system design ability, product judgment, and full-stack execution. It's the kind of work that earns a higher tier of client conversation.

Designed & Developed by
Zeeshan Khan

This case study is published with the full knowledge and consent of the client. All product details, branding, and platform features are shared for portfolio purposes only.