About

For the first five years of my career, I wrote strategies for products other people built.

At PwC, my work was upstream: market analysis, service design, digital transformation roadmaps. The deliverable was a deck, and someone else turned it into a system. That was fine for a while. Then it wasn't.

So I moved closer to the build. I went from strategy into delivery, writing the specs myself (PRDs, screen flows, data models, API contracts) and leading cross-functional teams of engineers, designers, and architects through months of construction. By the end, I owned what shipped, not just what was recommended.

Then a honeymoon trip to Silicon Valley turned into something else. Meeting founders, engineers, and product people, I recognized something I'd been circling for years: I wanted to be where the product is the point, not the engagement. A culture where shipping is the work, where failure makes you the expert for the next attempt, where the thing you build is the argument.

That's what brought me to Duke Fuqua, and what I'm building toward: a product role in the U.S. tech market, applying what I've learned across AI, platforms, and enterprise systems to products that reach further.

Outside of work, I play golf and tennis, and build things with vibe coding tools, this site included. I also write about Big Tech, startups, and Physical AI on Medium.