SILVORYX
A SaaS platform for beauty businesses, in design
SILVORYX is a SaaS platform I am designing for salons, barbers, spas and wellness businesses. A single engine has to serve many businesses while giving each one its own brand, website, services, team, customers and bookings, down to its own domain name. The specification is written; development has not started yet.
- Sheet
- 07 · SILVORYX
- Period
- Oct. 2026 → today
- Status
- In design
- Role
- Product designer · vision, specification, decisions
- Online
- No public link
- Technology
- Multi-tenant · Multi-brand · ADR · Codex · Claude Code · ChatGPT
- Revision
- In design · specified, not developed yet
The project in motion
Transcript
15-second film, no voice or music. Title “SILVORYX”, then a frame draws itself and real screenshots of the project follow inside it; below, the layers I worked on light up. It ends on the project's address.
What the platform has to do
I split the product into 17 epics, from the platform to billing. Each one has its scope, business rules and acceptance criteria. An MVP, user profiles, journeys and a business model complete the specification.
| Domain | What is planned |
|---|---|
| Foundation | Platform, accounts and permissions, client businesses (tenants), admin |
| Business | Locations, staff, services |
| Booking | Scheduling, online booking, customer records, notifications |
| Online presence | One website per business, in its own style, with its own domain name |
| Management | Payments, analytics, billing |
Each business in its own space
- Each business only sees its own data: checks happen on the server, never based on what the browser sends.
- This separation will be tested wherever data flows: database, cache, background jobs, files, domains, exports.
- Each business keeps its identity: colours, logo, website and domain.
- Languages, time zones and currencies are planned from the start.
Specifying before coding
On SILVORYX, I write down the important decisions before the first line of code: architecture, data separation, website publishing, technical choices, accounts and permissions, infrastructure. Six decisions are proposed and waiting to be settled. I have Codex working on engineering, Claude on the visual experience and ChatGPT on technical arbitration, each on its own branch.
| State | Content |
|---|---|
| Developed | Nothing yet: the project only exists as documentation. |
| Specified | 17 epics, security, database, languages, website engine, SEO, technology choices. |
| Proposed | 6 architecture decisions pending. |
| Planned | MVP, launch strategy, visual identity. |
What I take away
- Writing down plainly what is not built yet stops anyone mistaking a specification for a product.
Online
These addresses were responding on Oct 7, 2026.