All work
Product· Live independent SaaS build

ManeLoom

Salon operations built around a portable Hair Passport

A vertical salon ERP that keeps client history, cut specifications, treatment continuity, and operating workflows in one system. Its differentiator is the Hair Passport: the relationship and service memory stay with the salon, even when a stylist changes.

Role · Product architecture and full-stack engineering

System anatomy

01Vertical SaaS
02Client Memory
03Workflow Automation
04Operational Intelligence
ManeLoom live product interface

Captured from the live product · October 2026

Open live product

The problem

Most salon systems record appointments and bills but lose the knowledge behind repeatable service: guard numbers, formulas, treatment history, reactions, and client preferences. ManeLoom makes that memory an operational asset.

What the system does

Capability with an operating model.

Client CRM with cut cards, treatment schedules, and next-due dates

Appointments, stylist calendars, walk-in queue, and double-booking protection

Billing, Square/Cashfree payments, memberships, and accounting workflows

Inventory consumption, transfers, product tracking, and branch operations

Staff commissions, payroll export, skills, quality, and performance reporting

Marketing, WhatsApp notifications, consent, audit, and role-based tenant access

Architecture

How it fits together.

01

Domain-oriented Django/DRF backend across salon operating modules

02

PostgreSQL-backed tenant, branch, client, appointment, and billing model

03

React/Vite feature application with protected role-aware routes

04

Celery scheduling for reminders and marketing workflows

Key decisions

01

Memory is the wedge

Cut cards and treatment timelines make service repeatable across stylists and protect the salon-client relationship.

02

ERP underneath

The differentiated CRM sits on the appointments, billing, inventory, staff, and accounting workflows used every day.

03

Consent is structural

Client profiles, photos, treatment history, and communications are designed with scoped access and audit.

Explore another system