The same foundations, rebuilt too often
Each new SaaS product at Appointy needed the same foundations: authentication, billing, scheduling and staff management. Teams kept rebuilding them, which created duplicate work and inconsistent implementations. The existing scheduling platform already served more than a million users, but pages could take 15 seconds to load. Both problems sat below the individual product features.
A platform teams could reuse
Hariom built Saastack, a modular framework with 232 packages. Its plugin architecture allowed teams to change feature combinations at runtime. A Relay and GraphQL data layer replaced REST, while a command-line scaffolding tool standardized new app creation. A shared component system included support for different languages, currencies and regional formats.
Making variation part of the architecture
Runtime configuration mattered for white-label deployments that needed different capabilities from the same codebase. Code generation reduced repeated integration work across the packages. The Relay compiler checked data contracts during builds, and the platform treated localization as configuration. Hariom also redesigned caching to address the slow page loads at the platform level.
The reported results
The published case reports load times below one second, support for 19 languages and a platform serving 1M+ users. Appointy reused the framework for Google and Telefónica engagements. Hariom managed an eight-engineer team and established coding guidelines. These are results from his role at Appointy, including the enterprise deployments that used its platform.
