01
Unstructured services
Price, duration, images, and service details are scattered across posts, highlights, and messages.
Case study
Gloss Link
SaaS for beauty services, booking, and business operations
A SaaS case study for beauty professionals who need to showcase services, accept booking requests, organize their team, track Pix deposits, and manage subscriptions and administration in their own platform.
Public profileSchedulingServicesPix depositsTeamSubscriptionsAdmin
This private system is shown through interface screenshots, workflow details, and fictional data to protect business rules and sensitive information.
Shows
A working booking dashboard
Bookings, incoming requests, and statuses appear together so the team can manage the day.
Solves
Less improvisation in WhatsApp
Services, Pix deposits, and booking requests move beyond manual conversations into a clear dashboard workflow.
Why it matters
A foundation for SaaS
The product already separates the public experience, booking calendar, team, tenants, and administration so it can grow as a platform.
Challenge
Instagram and WhatsApp cannot manage the entire booking operation
Instagram and WhatsApp can drive sales, but they do not provide the structure needed for bookings, Pix deposits, team access, permissions, and recurring operations.
02
Manual booking
Available times, Pix deposits, and confirmations depend on back-and-forth messages and constant checking.
03
Limited team controls
Professionals, permissions, and calendars can grow without a clear operational structure.
04
No SaaS administration
Selling the tool as a product requires tenant, subscription, log, and support controls.
Solution
One platform to showcase services, manage bookings, and run multiple tenants
Gloss Link connects a public page, service catalog, booking calendar, and internal dashboard in a SaaS workflow.
01
A client opens the public page
The page brings the profile, services, availability, and booking CTA into one simple experience.
02
They choose a service and professional
Price, duration, and images answer common questions before the client reaches out.
03
They request a time
The calendar organizes availability and records the booking request in the dashboard.
04
The team manages the request
The internal dashboard brings together Pix deposit status, bookings, permissions, and follow-up.
Product screens
A booking dashboard and public catalog built for day-to-day operations
The screens below show the public experience and internal dashboard with fictional data. No real professionals, customers, or metrics are displayed.
Booking dashboard
Turns requests from the public page into an operational workflow with a calendar and clear statuses.
- Centralizes incoming times, confirmations, and follow-up.
- Helps the team track Pix deposits, status, and ownership.
- Moves booking beyond improvised coordination across Instagram, WhatsApp, and notes.
Public service catalog
Presents services, prices, images, and a booking CTA in one branded link, answering common questions before a client books.
- Works as a more operational alternative to a standard link-in-bio.
- Each service includes enough information to support the client's decision.
- Connects public interest directly to the internal booking dashboard.
Features
A public page, online booking, Pix deposits, team tools, and multi-tenant SaaS
Gloss Link combines a public storefront, booking calendar, team access, subscriptions, and administration to support the full sales cycle for beauty professionals.
Public page
Services, positioning, and a clear booking CTA in one link
The public page works like a focused link-in-bio, but is designed to move visitors toward services and booking.
01
Profile and positioning
Space to introduce the professional, explain what sets the business apart, and share important channels.
02
Featured services
Each service can include an image, price, duration, and description to make the choice easier.
Booking and services
Online booking with service, duration, price, and image
Bookings and services are the operational core of Gloss Link, connecting the public experience with the internal dashboard.
01
Guided selection
Clients understand the service before requesting a time, reducing repetitive questions.
02
Team dashboard
The team tracks requests, booking status, manual Pix deposits, and each professional's calendar.
Pix deposits
Manual tracking for a payment step already used by the business
Manual Pix deposit tracking supports businesses that still reconcile payments outside the system but need the status recorded in their dashboard.
01
Deposit status
The team marks a payment as received, pending, or under review without relying on an external spreadsheet.
02
Booking status
Pix deposit status stays connected to the booking, supporting confirmation and day-to-day organization.
SaaS, tenants, and teams
Multi-tenant architecture with team permissions and logs
As a SaaS product, the platform must separate each business, team, service catalog, and calendar as it grows.
01
Business-level separation
Each tenant has its own team, services, public page, booking calendar, and settings.
02
Administrative dashboard
An internal area manages subscriptions, accounts, logs, plans, and overall SaaS visibility.
03
Team permissions
Roles control who can change services, bookings, Pix deposit status, and settings.
04
Operational logs
Records help the team understand changes, support requests, and important events across the platform.
Subscriptions and admin
AbacatePay subscriptions and a dashboard for managing the platform
The administrative layer supports plans, subscriptions, tenants, customer support, and operational visibility.
01
Subscriptions
AbacatePay integration supports commercial access, billing, and tenant status.
02
SaaS administration
The dashboard brings together accounts, logs, plans, support, and operational decisions for the platform.
Security and LGPD
Separated access, operational logs, and careful handling of personal data
The case study involves end-customer data, bookings, and business accounts. The public demo therefore uses fictional data and demonstration screenshots.
01
Privacy-aware data flow
Data collection is limited to what is needed for booking, communication, and business operations.
02
Access control
Authentication, roles, and tenant rules reduce the risk of access across separate businesses.
03
Fictional case study data
The portfolio uses demo professionals, services, and bookings to protect real information.
04
Observability
Logs and monitoring help investigate failures and keep the platform operational.
Tech stack
Technology for a SaaS booking and commerce workflow
The stack supports the public page, booking, internal dashboard, tenants, payments, logs, and security.
Tech stack overview
The technology supports the day-to-day product experience, data, integrations, security, logs, and automation.
Next.jsReactTypeScriptNestJSSupabasePostgreSQLRLSSentryAbacatePay
01
Fast public page
A responsive interface presents services and guides clients toward booking.
02
Multi-tenant foundation
Data is separated by business, team, permissions, services, and booking calendar.
03
Payments and subscriptions
AbacatePay supports subscription management and the commercial foundation of the SaaS.
04
Logs and security
RLS, monitoring, and sound security practices support operations and troubleshooting.
Next step
Want to build a SaaS product or improve your booking operation?
If you need to turn bookings, a public service page, team management, or subscriptions into a SaaS platform, message me to discuss the scope and first workflows.