Selected case studies · 2014 - 2025

Systems built to outlast. Still in production.

Four case studies, selected from seventeen years of work, that show how I build and rebuild systems that stay in production.

One I originated from a recurring client question. Another came from a business-model shift. A third was a national programme. The fourth had failed so badly it had to be rebuilt from scratch. Each shipped, scaled, and outlasted the conditions that created it.

Case 01

The Dashboard

An executive analytics platform that plugs into any data source. It became the company's highest recurring-revenue product.

4 phases · Embedded → Standalone → Web → Configurator · 9.5 years
0 → 1 build Solo → 5-person team Platform
Recurring / mo₹27–28L
Widgets700+
Years live9.5
Leadership signal

I originated it from a recurring client question, then built the team to scale it, making the business case for every hire myself and growing front-end recruits into owners of the codebase. The architecture I set let one front-end developer maintain it years after I left.

Read case study
dashboard.intellve.local
Phase IV
The Dashboard
Case 02

MonitoringHub

A SaaS monitoring platform, on web and mobile, and the company's first true subscription product. A major enterprise client moved to it from the paid desktop platform voluntarily, with no sales pitch.

Project revenue → SaaS
0 → 1 build Field research New market
Recurring / mo₹7–8L
In production5 yrs
Company firstSaaS
Leadership signal

When the owners pushed for recurring revenue, I made the case in the early sessions, projects are wells, subscriptions are rivers, to build it from our own domain. Then I did the field research myself, on weekends, and let it reshape the product. I gave up my own mobile-first pitch when web-first proved the better call.

Read case study
monitoringhub.intellve.com
SaaS / Web
MonitoringHub
Case 03

Varanasi Smart City

The software layer for Varanasi's city-wide command centre: eight major systems on one operator platform. Inaugurated by the Prime Minister in 2019, still in production today.

A city of millions.  Secured and managed from one operator surface.
Smart City System of systems Sole UX
Major systems8
Inaugurated byPM of India
In production6+ yrs
Leadership signal

Eight modules, each owned by a different city department with its own workflow, had to feel like one system. I set a single structural pattern, the same table-and-map view across every module, so an operator trained on one could run any of them. That is systems leadership, not screen design.

Read case study
varanasi.smart-city.gov.in
Command Centre
Varanasi Smart City
Case 04

TouchConfig Redesign

The configuration tool was so broken the team had abandoned it. I proposed scrapping it and rebuilding from scratch, and was given the responsibility and ownership.

First version in three months.  Built with a single developer.
Rebuilt from scratch Configuration tool WPF Desktop
Zero rebuild8+ yrs
Screens200+
Layout types3
Leadership signal

I made the case for the rebuild by reframing it as a commercial risk, deploying a broken tool to paying clients would have damaged our credibility, not as a usability complaint. The architecture and modular system I built when I rebuilt it are still running today, unchanged. The right call holds up under time, not just at approval.

Read case study
touchconfig.intellve.local
WPF / Desktop
TouchConfig Redesign