I'm a GTM engineer. I've spent the last four years owning growth, pipeline, and narrative inside early-stage protocols — turning zero-to-one products into ecosystems that compound.

Not as a founder. Not as an investor. As the person who builds the growth system end-to-end: ICP, partner motion, activation loops, instrumentation, and the story that holds it all together.

At LayerEdge, that meant rebuilding the entire GTM stack through the company's hardest pivot — Bitcoin L2 to ZK aggregation infrastructure — writing every external word, running 50+ integrations across a 100+ protocol ecosystem, and rewriting the funnel in real time while the product was still shipping.

Now I'm in Bengaluru, thinking about something I don't think enough people are taking seriously yet:

What does commerce look like when the buyer is an AI?

Not crypto payments for humans. The infrastructure for autonomous economic actors — the identity, the rails, the trust frameworks — for a world where AI agents spend money.

Working inside ZK infrastructure, you develop a specific paranoia about edge assumptions — the things a system takes for granted about whoever's on the other end of it. For two years, every system I worked on assumed a human at the edge. A person with a wallet, a jurisdiction, a liability to bear. ZK proofs, account abstraction, rollup finality — all of it designed for the case where a person decides to sign.

Then language models started acting as agents, and the assumption broke quietly. Not with a warning. Just: one day the entity initiating the transaction might not be a person, and everything downstream of that — identity, accountability, trust — is suddenly load-bearing in ways nobody designed for.

That's not a payments problem. It's a primitives problem. And I haven't been able to think about much else since.

I think this is the most interesting unseized problem at the intersection of Web3 and consumer AI. I'm building a thesis.

If you're thinking about the same thing, I want to talk.