SaakhiPay: booking platform for salons and beauty parlours
A beauty services platform connecting customers, salons and referral partners. We built the web platform and the mobile apps, covering discovery, appointment booking, payments, loyalty rewards and partner analytics.
The brief
SaakhiPay is a three-sided platform: customers booking beauty treatments, parlours taking those bookings, and referral partners growing the network. Each group needs a different interface, but all three operate on the same underlying availability and payment data.
What we built
Discovery and booking
Customers browse parlours with ratings and reviews, see real-time availability, and book a slot with confirmation. Appointment booking is unforgiving — a double-booked slot is a real person turned away at a door — so availability handling was the core of the build.
Payments
Secure payment processing with multiple options at the point of booking.
Loyalty and rewards
A customer loyalty programme that rewards repeat bookings, which in a service business is where the margin actually is.
Partner dashboards
Business analytics for parlour partners — bookings, performance and customer patterns — so a salon owner can see the value the platform delivers rather than take it on faith.
Referral tracking
A growth portal with referral attribution, so partners bringing parlours or customers onto the platform can be tracked and paid correctly.
Positioning
The platform is free for customers and monetises through partnerships. That choice shapes the interface: nothing in the customer journey can feel like an upsell, and the commercial mechanics live in the partner-facing side of the product.
Web and mobile across the whole ecosystem
SaakhiPay runs as a multi-app ecosystem and we built all of it: the web platform, the customer app, the parlour-facing app and the growth portal, on one shared backend.
That mattered here more than usual. Availability has to be identical everywhere at once — a slot booked in the customer app must disappear from the parlour's view immediately — and that is far easier to guarantee when one team owns every surface and the API between them.
