Re-engaged a Tier-1 carrier. Shipped four new modules.
Re-opened Air India Cargo, structured an IATA GSS licensing deal, launched CargoIntel · DataGuard · CapacityIQ · CPS CoPilot. +20% users, +15% MAU.
I'm Nayan Chatterjee - Associate Principal PM at Unisys, opinionated about air cargo, branch banking, and the difference between roadmaps and wish lists. Probably in that order.

I lead a 5-person product team - two GTM leads, two senior PMs, one associate PM - and work day-to-day with a 40-50 person design and engineering org at Unisys. It's a lot of calendars, but the shipping keeps it honest.
I started in engineering at Cognizant, building analytics for banks and insurers - learned how a thing actually gets shipped, then crossed into product where everything else is just storytelling on top of operations.
HSBC taught me regulated industries at scale. Morpheus taught me consumer edtech in a hurry. Unisys taught me that even cargo manifests and teller screens have a brand voice (it's "trust, but compliant").
Now I own three enterprise product lines - CPS, Failed Milestone dashboard, and UBB - serving Tier-1 airlines and building societies across UK, LATAM, and APAC.
The bit your recruiter wants: 9+ years across SaaS, banking, and cargo. Roadmaps, GTM, regulatory delivery (KYC/AML, PCI DSS, IATA ONE Record). I personally write the frontend code for every prototype I ship - production-ready, API-wired, just needs the backend plugged in.
Numbers attached. Case studies available on request.
Re-opened Air India Cargo, structured an IATA GSS licensing deal, launched CargoIntel · DataGuard · CapacityIQ · CPS CoPilot. +20% users, +15% MAU.
Owned Failed Milestone dashboard roadmap for Air Canada & American Airlines. Drove Cargo iQ Spec V7.0 readiness across 23 impact areas. Zero P0s, three quarters running.
Authored the 2026–2029 strategic roadmap for a retail branch platform. $2M+ pension-fund POC. 86+ teller transactions, KYC/AML and PCI DSS embedded in release cycle.
Launched a NEET/IIT prep platform, designed a personalization algorithm that cut test anxiety 30%, shipped an Android OMR checker that took 40% off grading time.
Two quarters. Subs up 60%, churn down 15%. Illustrative shape, exact figures on request.
Designed and built a three-app cargo booking prototype for a regional US cargo carrier. A self-service drop-off kiosk for walk-in shippers, a carrier acceptance desk for the counter team, and a CPS portal stitching it together. I wrote a 40-point requirement spec, then shipped three working React prototypes on Lovable, API-wired and ready for the backend to plug in. Same pattern as everything else here: spec, working prototype, pressure-test with engineering, then commit the build. De-risk the bet before you scale it.
I wrote the spec, built all three working React prototypes, and pressure-tested the flows with the engineering lead before the team committed the backend build. Front end first, de-risked, then scale.
De-risk the bet before you scale it. Same guardrails, every client.
Enterprise product work lives under NDA. So here's the shape of it, with the sensitive parts pulled. Everything below is real work, redacted on purpose.
Product spec · air cargo · 40 requirements · client redacted
Delivery dashboard · Tier-1 carrier · figures under NDA
4-year platform roadmap · branch banking · names withheld
Want the unredacted version? Bring a real brief and an NDA. Link at the bottom.
Working prototypes. Click through any of them.
An end-to-end agentic AI roadmap I'm authoring right now - the blueprint for how we'll deliver client implementations going forward. Twelve+ task-specific agents on a shared, governed platform: status reports, change impact, requirements, code, tests, triage. Same five-step pattern, reused. Same guardrails, every time.
No "quick chat to pick your brain." No "exposure." Bring a problem and I'll bring an opinion - and probably a 90-day plan.