I've been exactly where you are, and I didn't know the answer either

I'm Diego. I build B2B platforms in regulated industries where mistakes are expensive: payments, telecom, and HR and payroll. I trained as a computer engineer and I'm still hands-on.

Most recently, as General Manager at Toptal, I ran a global payroll venture (invoicing, FX and global payouts) and led the team's move to agentic engineering with human review. Before that I led Twilio's Phone Numbers business, a $230M-a-year platform with 8 PMs and 60+ engineers and designers across four continents, covering identity, KYC and KYB, access control, compliance and data residency. Earlier, I co-founded a VC-backed accounting startup in Latin America and ran product until it was acquired.

Most product writing is a thesis with a story attached to it. I want the opposite: the situation, in order, including the part where my first read was wrong, and then one clean sentence about the mechanism that survived.

Readers aren't hiring the person who was always right. They're hiring the person who can be trusted to navigate not-knowing. That is the actual job of a product leader, and it is the only thing I know how to demonstrate in public.

Bogota, mostly. Working with teams across LatAm, the US, and Europe, which means half my career has been spent translating disagreement between cultures that price it very differently. Most pieces are in English.

B2B platforms and APIs, payments, identity and compliance, strategy, product operations, team leadership, platform modernization, first days in a new role, and agentic engineering. I'm less useful on consumer products and growth, and I'll say so.