CTO, systems architect and full-stack engineer. Blockchain specialist, AI-native across the stack, and twelve years turning ambiguous product ideas into systems that ship.
Start a conversationCurrently building Tuo, a DeFi protocol that generates yield, scaling Croisée, my bootstrapped mobile app, and shipping AI automation alongside both.
I have spent twelve years on the same problem from three different angles: as the engineer who writes the code, as the architect who decides what the code should be, and as the CTO who is accountable for whether any of it reaches a user.
That range is the point. I have taken products from an empty repository to production and paying customers several times over, which means I have already made most of the expensive mistakes, usually on my own budget rather than someone else’s.
The last five years have been mostly on-chain: token standards, account abstraction, protocol interfaces that move real money, and the review work that has to happen before any of it is deployed. Smart contracts are unforgiving in a way ordinary product work is not, and that discipline has made everything else I build better.
I have worked on several continents and with teams spread across the world, each with its own language, hours and way of doing things. Adapting fast is the skill I trust most, and a distributed, international team is where I do my best work.
The rest is temperament. I start things, I take the risk, and I stay curious about almost everything: give me a problem I have not seen before and I will be three steps into it before the meeting is over. If you are building something ambitious, I would love to hear about it.
12 YEARS
10+
05
01
Backends built to carry real load rather than to demo. Data models and service boundaries that hold as traffic grows, security and access control designed in from the first commit, and systems that scale out across machines as readily as they scale up on one.
02
Solidity that is written to be reviewed. AMM pool maths that decides whether a protocol survives its first volatile day, token standards and vaults, subgraphs that make on-chain state queryable off it, and the fuzzed Forge suites and audit preparation that turn a working contract into a deployable one.
03
Landing page to dashboard to billing to infrastructure, by one person who holds the whole picture. Most useful in the phase where the product is still changing weekly and handoffs cost more than they save.
04
Pointing models at the work nobody should be doing by hand. Content pipelines that run on a schedule, coding workflows that shorten the loop between intent and merged code, and the back-office processes of enterprises and smaller teams wired together with n8n and custom code.
Companies I founded, products I built and clients I worked with.
Ship before perfect. Learn before know. Build before talk. Every system I have been proud of got there by being put in front of real users earlier than was comfortable, and every one I regret was protected from that for too long.
