The product problem
Small beauty businesses often run appointments through messages, remember client context manually, and maintain a separate website that becomes outdated. Every new tool adds another place to synchronize.
← All product work
Product case / 02
Randevu
One operating system for bookings, clients, schedules, and a business website.
A complete SaaS product for salons, barbershops, and solo specialists — built solo from product logic to the production system.
Created end to end by the founder of R&D Club.
Visit live product01 / Product thesis
A complete SaaS product for salons, barbershops, and solo specialists — built solo from product logic to the production system.
What we built
R&D Club turned booking, staff availability, client history, service data, and a customer-facing website into one product. A business updates information once; clients see current services and book available time without calls or message ping-pong.
04 / Product capabilities
Product capabilities
24/7 booking
Clients choose services and available time without waiting for a reply.
Client context
Visit history and notes stay attached to the relationship, not to someone's memory.
Predictable schedules
Availability, working hours, and days off prevent booking conflicts.
Website from data
The customer site always reflects the current services, prices, hours, and location.
05 / System shape
System shape
The important architecture is the product model: services, employees, schedules, clients, and public pages share the same source of truth. Internationalization and solo/team modes are built into that model instead of being bolted on as separate products.
SaaSCRMOnline bookingSchedulingi18n
06 / Interface evidence
Interface evidence
Have a product that needs research-grade engineering?
hello@rnd.club