Product builder · New to San Francisco

I turn hard, technical systems into products people can actually use.

Product manager × forward-deployed builder × product engineer. Currently building agent commerce at Visa.

If the problem sits between users, product, and a messy technical system, that is usually where I’m most useful.

Best fit0→1 productForward-deployed workTechnical systemsClose to users

Selected proof · newest first

The work compounds.

Each chapter left behind a capability, a constraint, or a better question. Pick one to see the proof and what moved forward.

NowCurrent work

Discovery was missing from agent payments.

ProductRank connected product knowledge to agent action. That work led me to Visa, where I now work on agent commerce across card and stablecoin rails.

What this proves
Product strategy · forward deployment · systems implementation
What carried forward
Markets + identity + discovery + authorization + money
Public-safe system sketchNot product UI
01DiscoverKnow what exists
02DecideCompare and qualify
03AuthorizeIdentity and policy
04PayCard or stablecoin
05ProveReceipt and reconcile
The product is the whole path—not the payment at the end.

The part that isn’t on LinkedIn

None of this was the plan.

I have no fucking clue what I’m doing. I’ve just gotten comfortable moving before the whole path makes sense.

I’m from the north suburbs of Chicago. Building things with computers did not feel like a creative life that was available to me. I left an early job to chase an ICO. It failed. I ran out of money and fell into technical recruiting because I would take any job.

I kept moving while I figured it out: Chicago to Arizona and a nomadic stretch, back to Chicago, then New York, and now San Francisco. In between there was time in places like Barcelona, Mexico City, Paris, and elsewhere. I’m new here again—which feels pretty consistent with the rest of the story.

Recruiting became an accidental education—from Rails startups to high-frequency trading and distributed systems—then a route into ConsenSys and the Ethereum ecosystem. Peeple Work gave me enough independence to recruit for a living and build products everywhere else.

Software became the biggest public stage I could afford. An idea can become an experience, travel without me, and reach anyone with an internet connection. It does not have to save the world. Making one corner of it three percent better is enough reason to keep going.

01

Get close

The useful product gap usually appears after living with the system, the user, and the ugly edge cases.

02

Make it real

A strategy becomes valuable when somebody can use it. I like owning the uncomfortable distance between idea and operation.

03

Keep the miss

Failed ventures, regulatory limits, and wrong turns are part of the capability—not embarrassing edits to remove later.