Nikhil T A

Somewhere between a spreadsheet and a Slack message, I found my thing. I've always been drawn to numbers. Not to report them — to find the thing hiding inside them that changes how someone acts. Ended up sitting between the data, the product, and the people who need to move. Turns out that gap is where most of the interesting problems live. I joined Quince as an intern and stuck around because the problems kept getting harder. Launch timelines slipping. Teams buried in follow-ups. Data that existed but never reached the right person in time to matter. I spent the last year trying to fix that not with more reporting, but by rethinking how information moves through a team. The thing I've learned: most workflow problems aren't data problems. They're design problems. And I care about that distinction more than most people in analytics roles do.