Founding Product Marketing Manager · Paris · 2019–2020
Globcoin: explaining a fifteen-currency basket to people who'd never heard of purchasing power parity
The situation
Every competitor stablecoin could be explained in four words: one coin, one dollar. Ours needed a paragraph about GDP weighting before it made sense.
Globcoin's GLX launched at Davos in January 2019, pegged not to a single currency but to a basket of the world's fifteen largest, plus gold, weighted by GDP and adjusted for purchasing power parity. Linked to roughly 85% of the world economy rather than to any one government's monetary policy.
It was a genuinely better answer to the question stablecoins exist to answer. It was also substantially harder to say.
When I arrived
When I left
A basket mechanism nobody understood
A consequence anyone could act on
One market
Five international markets
Blockchain-first language
Customer-first messaging and education
No launch support in regulated markets
Compliance-aligned launches and exchange partnerships
What I built
Product marketing for blockchain financial products across five international markets. Localized go-to-market, partnerships and community growth. Customer-first messaging and educational content translating the basket mechanics into something a non-specialist could act on. Launch support with Product and Compliance in regulated crypto markets, plus exchange partnership and wallet adoption material.
The judgment call
Leading with the consequence, not the mechanism.
The product's differentiation was also the reason nobody understood it. The instinct in that position is to simplify until it sounds like the competitor, which throws away the only thing you have.
What worked was inverting the order. Not how the basket is weighted, but what it means to hold money that isn't a bet on a single country. The mechanism became the proof rather than the pitch.
That's a pattern I've used ever since on technical products: the thing that makes you different is usually a mechanism, and mechanisms don't sell. Consequences do. The mechanism's job is to make the consequence believable once someone already wants it.
Frameworks installed