After 18 months of investment, Fairbank’s app was stuck in limbo — broken API integrations, an outdated stack, low stability, and a backlog that the product manager couldn’t push through. Leadership was losing confidence, and the choice seemed to be either rewrite everything or abandon the effort.

• →Deployed a focused 4-person strike team to own the frontend and supporting architecture.
• →Rebuilt the frontend with production-grade security and stability in mind.
• →Partnered closely with the product manager to break the backlog bottleneck and prioritize what truly mattered.
• →Shipped 4–5 high-quality features every week, consistently, for 4 months.
• →Anticipated UX needs and added thoughtful touches like Lottie animations and interaction details that made the app feel alive.
• →Cleaned up integrations and tightened the system until reliability reached 100%.

• App stability improved from ~40% to near 100%.
• Leadership regained confidence in both the product and the roadmap.
• The product finally launched after being stuck for over a year.
• The team experienced a new baseline for feature velocity and quality.

Raedan was moving from sub-broker to full broker status with NSE/BSE, but their existing network path led to severe order execution slippage. Orders were placed quickly, but landed deep in the queue due to latency. At their volumes, this made certain trades too risky to attempt.

• →Performed a first-principles analysis of their trading network and operational flows.
• →Architected a new low-latency trading network optimized for direct exchange connectivity.
• →Got single-hop leased lines from NSE and BSE, working closely with Sify and Tata Telecom.
• →Designed an isolated, dedicated trading LAN separated from general internet traffic to avoid collisions and noise.
• →Optimized network parameters and routing to achieve deterministic, ultra-fast packet paths.

• Achieved latency in the 2–10ms range for critical trading flows.
• Effectively eliminated execution slippage caused by network issues.
• Gave Raedan the confidence to take higher-volume, higher-risk trades.
• Turned their infrastructure into a competitive asset instead of a hidden liability.

Smoothline was a boutique, founder-driven operation that suddenly landed on the global map after acquiring a key patent. The entire business ran from the founder’s head — orders, batches, stock, dispatches, client-specific variants — across multiple factories. As demand exploded, this model became impossible to sustain.

• →Immersed ourselves in their real-world operations across three factories and one central hub.
• →Mapped the implicit logic in the founder’s head into explicit, structured workflows.
• →Built a cloud-based order and stock management system in 2014, when cloud adoption in India was still rare.
• →Evolved the system into a full custom ERP — with alias mapping, partial dispatch flows, multi-factory coordination, and per-role interfaces.
• →Implemented audit trails, role-based security, and rich reporting for full traceability.

• Transformed the company from founder-run chaos into a process-driven, scalable operation.
• Achieved company-wide adoption — rare for any ERP rollout.
• Gave the leadership confidence to focus on strategy instead of firefighting operations.
• Enabled fast analysis of batches, dispatches, and cross-factory flows with a few clicks.

The client needed a gentle but powerful way to introduce web-based tools to the entire organization. Traditional task tools felt dry and were unlikely to drive adoption or excitement.

• →Designed a task management system that felt more like a game than a form.
• →Introduced points for task completion, badges for behaviors like early logins or staying late, and visible leaderboards.
• →Built a points store where employees could redeem rewards like company merchandise, chocolates, and bouquets.
• →Allowed approvers to send tasks for rework, reducing points and encouraging real quality.
• →Kept the UI simple enough that anyone in the company could use it without friction.

• Employees raced to claim and complete tasks to climb the leaderboard.
• The system became the informal heartbeat of internal productivity.
• The company adopted web-based tools with enthusiasm instead of resistance.
• Leadership gained better visibility into ownership and throughput.

The client needed a conversational assistant that could handle Indian multilingual realities — mixed languages, code-switching, and different scripts — while strictly adhering to security and compliance rules. Customer data couldn’t be stored at rest, and responses had to be generated on-the-fly via secure APIs.

• →Designed a conversational architecture using RASA at its core.
• →Built a translation-aware middleware layer using Google Translate APIs and custom handling for mixed-language input.
• →Integrated secure backend APIs that fetched customer data in real time, without persisting it.
• →Orchestrated the flow from user → translation → intent → data fetch → response in a way that respected both latency and compliance.
• →Tested against real-world, messy language inputs rather than only idealized queries.

• Delivered one of the earliest multilingual banking assistants in India.
• Enabled customers to engage in natural, mixed-language conversations.
• Met strict compliance requirements by ensuring customer data was never stored at rest.
• Gave the bank a modern, differentiated support channel before LLMs became mainstream.

Cloud teams were spinning up servers and services at a rapid pace. Months later, no one remembered who owned what, which environments were still needed, or how much each piece cost. Terraform offered control, but not the kind of human-readable visibility leadership needed.

• →Designed a web-based platform that visualized servers and services as a clear, explorable map.
• →Attached ownership, purpose, and contact details to each resource.
• →Surfaced cost data so teams could see the financial impact of infrastructure choices.
• →Allowed grouping by team, project, and cost center to match real organizational structures.
• →Extended the mindset of infrastructure-as-code into infrastructure-as-clarity.

• Gave teams immediate visibility into what they were running and why.
• Reduced waste by making forgotten or unnecessary servers obvious.
• Helped organizations have better conversations about cost versus value.
• Became a foundation for more disciplined cloud governance practices.