LIFEYA — Salon Operating System

The author states that LIFEYA is a self-developed SaaS platform for beauty businesses, built as a personal project to support their wife’s salon and later expanded into a full operating system. The description indicates it includes features like booking, CRM, finance, team management, and multi-salon support. It was submitted to the OpenAI 2026 hackathon by a single developer using AI tools such as GPT-5.6 and Codex.

The platform is described as being in active use, with continuous improvement underway, but no evidence of revenue, customers, or traction beyond self-reporting.

The description states that LIFEYA is an all-in-one SaaS platform for beauty businesses. It includes:

• Smart appointment scheduling
• Online booking websites
• Client CRM
• Finance and reporting
• Team management
• Services & pricing
• Staff permissions
• Multi-salon management
• Analytics
• Data export and backup tools

It was built as a full-stack web application using technologies such as Next.js, React, Node.js, PostgreSQL, Supabase, and AI tools like GPT-5.6 and Codex.

Not evidenced: The actual functionality or UI of the platform; whether it is live or accessible to users beyond the founder’s network.

The author claims that LIFEYA began as a personal gift for one salon owner and evolved into a complete operating system for multiple salons. It positions itself as an integrated solution for managing all aspects of beauty business operations, from client booking to financial reporting.

It also states that the platform supports multi-salon management and is designed with scalability in mind.

The author notes that the platform was built during OpenAI Build Week and used AI tools extensively to improve development speed and solve complex engineering problems.

Not evidenced: How the product differentiates from existing solutions; whether it has a competitive advantage or unique value proposition beyond being custom-built for salons.

The description states that LIFEYA targets salon owners, beauty professionals, and multi-location businesses. It is positioned specifically for "beauty businesses" and includes features tailored to those needs.

Not evidenced: Specific customer segments; whether the platform addresses different types of beauty businesses (e.g., nail salons, spas, hairdressers); how many customers exist or what their size or geographic distribution might be.

The description does not provide any information about pricing models, monetization strategies, or revenue streams. It only mentions that the platform is a SaaS offering with features like finance and reporting.

Not evidenced: How the product will generate revenue; if there are paid tiers, subscriptions, or usage-based charges.

The platform was built using modern web technologies including Next.js, React, Node.js, PostgreSQL, Supabase, and TailwindCSS. It uses AI tools such as GPT-5.6 and Codex for development assistance.

It is described as a full-stack application designed with scalability in mind and includes multi-salon architecture and RBAC (Role-Based Access Control).

Not evidenced: Deployment environment or infrastructure details; whether the platform has been tested at scale; how performance or reliability are measured.

The author states that LIFEYA is actively used, continuously improved, and prepared for expansion to additional salons. It was submitted to a hackathon and is described as having evolved from a personal project into a full platform.

Not evidenced: Customer base; user engagement metrics; revenue data; adoption rate or retention figures; whether the product has moved past MVP stage.

The description does not mention competitors or how LIFEYA compares to existing salon management systems. It implies that generic booking platforms were inadequate for salon owners, but does not name specific alternatives.

Not evidenced: Market landscape; competitive positioning; differentiation from other tools in the space.

• The platform is described as a single-developer project with no evidence of team expansion or external validation.
• There is no mention of customer feedback, user testing, or product-market fit beyond personal use.
• No financial data, revenue, or traction metrics are provided.
• The author’s own account suggests the product was built primarily for personal use and later generalized — this raises questions about early-stage market validation.

Inference: If LIFEYA is only used by the founder's wife and a few other salons, it may not yet have achieved meaningful market traction or proven scalability.

1. What is the current number of active users or salons using LIFEYA?
2. How do you plan to monetize the platform? Are there any existing paying customers?
3. What specific problems in the salon management space are you solving that other platforms don’t?
4. Have you conducted any user research or interviews with salon owners outside your personal network?
5. What is the timeline for scaling beyond the initial set of users?
6. How do you intend to handle data privacy and compliance (e.g., GDPR, CCPA)?
7. Are there any technical limitations or bottlenecks currently in place that could hinder growth?