Tetrium
A payments aggregator I co-founded. I built the frontend and co-designed the API. We demoed it to GlideSwipe, and they ended up hiring both of us.
- Role
- Co-founder · product and UX lead
- Period
- Feb 2025 – Oct 2025
- Type
- Startup
The short version
Two of us, starting from nothing. I owned the frontend end to end and worked through the API design with my co-founder as we went, so the screens and the contracts stayed in step instead of being reconciled later.
We took it to GlideSwipe, a global payments platform, and showed them the product running rather than a deck about it. Everything on screen was real.
They hired both of us. I came on as Director of Solutions. Tetrium continues as my co-founder’s consulting practice, and my own consulting runs through this site.
Why it worked
Plenty of people list pre-sales and demo strategy as a skill. This is the version of it I can point at: we built the thing, showed it to the company we wanted to work with, and they hired the people who built it.
It held up because there was nothing to hide behind. The frontend and the API were designed together rather than one being fitted to the other afterwards, so when someone in the room started poking at it, it kept working.
Honest state
Tetrium isn’t a product company anymore, so there’s nothing here you can click through and try. That’s the real limitation of this one as a case study, and it’s why the walkthrough on the UAT-Ops page is the better place to see how I actually work.