Our Story
Where it all started…
I've worked in marketing for about ten years, and I'm still learning. But the last couple of years genuinely shifted how I think about the work.
For most of my career I did the work — brand, product marketing, growth, SEO, social — at companies like Wix and eBay. Then I spent four years at Polygon, one of the biggest blockchains in the world, valued in the billions. The last two and a half, I led the marketing department.
That's where Vibier started — not as an idea, but as a problem I couldn't solve.
The problem
At our peak we were thirty people marketing six or seven products. Then we shrank to twelve — and the work didn't shrink with us. We were expected to deliver like a team of thirty with a team of twelve, and the answer everyone reached for was the same: use AI, do more with less.
The trouble was, nobody knew how to do it together. Some people on the team had quietly figured out brilliant AI workflows. Others spent hours generating slop that went nowhere. Some were afraid to touch it at all. We had all this intelligence available to us, and no shared way to use it — the knowledge lived in individual heads and individual chat windows, and none of it compounded.
So I built something. A shared system — one place the whole team could work with AI, where the good workflows became everyone's workflows, where the context didn't reset every time someone opened a blank chat box. I built the first version inside Polygon, for my own team.
It worked. And I realized the problem wasn't ours alone. Every marketing team I talk to is living some version of this.
Why Vibier
They've been told to do more with AI by someone who can't tell them how. They have tools that are brilliant in isolation and useless as a team. The intelligence is there — what's missing is the shared brain to hold it.
That's what Vibier is. A marketing team's shared brain, built for the way teams actually work — together, in the tools they already use, with knowledge that compounds instead of evaporating.
I built it because I needed it. Now I'm building it for the teams that need it too.
— Leon