NEW YORK METRO
next interesting problem.
Worked with:
(Impact)
75%
27%
Increase in collection efficiency at L&T Finance
5x
Revenue growth at Nata Ace Tutorial
Selected work
(04)
People I've worked with
(REFERENCES)
Simple Design, Big Impact.
I've designed buildings, software, and a course for teenagers. 9 industries later, the job hasn't changed: take something tangled and make it obvious.
(about me)
Architectural sites taught me the order. Systems first, screens after. Being wrong on a site sets in concrete. In software you can be wrong on a Tuesday and fix it by Thursday. Teaching taught me the rest. Fifteen-year-olds don't accept "trust me, it's cleaner," and honestly, neither should anyone else.
Beyond the work?
Singing, trekking, and cooking that takes longer than it should. Chai (tea) twice a day, no exceptions.Evening walks with the Manhattan skyline across the water.
How do I start with a blank brief?
On paper. I sketch, photograph the page, and hand it to Claude to turn into screens. A blank prompt is a bad place to think. A blank page isn't.
How do I know it's the right problem?
I go and watch. At Vodafone Idea, an engineer read a job order on a phone in direct sun with one hand free. The back office read the same record on a desktop with time to spare. Same data, two different products.
How do I use AI day to day?
At every stage. Research in Perplexity, ideation in ChatGPT, paper sketches into Claude for wireframes, Replit or Lovable for prototypes, Claude over MCP for production Figma. First drafts went from four hours to under thirty minutes.
What do I reject from what AI gives me?
Most of the first pass. It writes for the happy path, hands back the pattern it has seen most often, and makes it look finished. So I keep the structure, throw out the copy, and rebuild the states it skipped. The edit is the work.
When do I stop trusting AI?
The moment I cannot check its work. It is fast at making something look finished, and looking finished is not the same as being right. The copy, the data logic, the states nobody demos, I verify all of it. The AI tool I built at Pace only earned that claim after real students tested it. Task time, 18 minutes to 7.
(PROCESS)
