SaaS Product Design — Palash Sarkar's Process for Complex Software Interfaces

SaaS products have a specific design challenge Palash Sarkar has encountered repeatedly: they only grow more complex over time as features accumulate, and a UI that felt clean at launch can become unmanageable within a year without deliberate structural discipline.

Design for the Product's Future Complexity, Not Just Its Launch State

A navigation structure that works cleanly for five features often breaks down at twenty. Palash Sarkar designs information architecture with room to grow — nested navigation patterns, extensible settings structures — rather than optimizing purely for how clean the launch version looks, since that launch-optimized structure is often what causes real pain a year later.

Progressive Complexity for Different User Sophistication

SaaS products serve users ranging from someone using 10% of the feature set to power users relying on advanced functionality daily. Palash Sarkar designs default views that stay simple for typical use, with advanced functionality genuinely accessible rather than hidden — a balance covered from a slightly different angle in his design systems guide.

Empty States and Edge Cases Get Designed, Not Ignored

A SaaS product's empty states — no data yet, a search with zero results, an error condition — get just as much design attention as the fully populated "happy path" screens shown in every pitch deck. These are the states real users hit constantly, and leaving them undesigned is one of the most common gaps between a polished demo and an actually good product.

Key Takeaways

Designing SaaS products well means planning for complexity the product doesn't have yet, serving both new and power users without compromising either, and giving empty states and edge cases the same design attention as the polished happy path. Palash Sarkar's enterprise dashboard work has made this discipline central to his process.