What I work on
Most of my work is taking a process someone already does in spreadsheets, on paper, or across three browser tabs and turning it into a single screen that gets out of their way.
The projects I’m proudest of share a pattern: a clear operator, a real workflow, and constraints that make the interesting decisions obvious. VerivAfrica, Recurrent, Qatapolt Admin: these all started as the question, how do we stop using spreadsheets for this?
How I work
I lean on React and Next.js because that’s where the ecosystem is, but I’ve shipped production code in Mantine, Tailwind, shadcn, Recharts, Prisma, and whatever fits the brief.
On the design side, I’m a builder, not a stylist. A tight type system, two or three colours, no decoration that hasn’t earned its place. Most project decisions begin and end with that constraint.
How I think about the work
Operator-grade software is durable software. It has to survive a feature freeze, a marketing pivot, three staff turnovers, and the audit that happens two years later. I write for that horizon.
The best engagements look like four to twelve weeks of focused building, often inside an existing team. I work best as a hands-on IC, sometimes as a fractional lead, never as the loudest voice in the room.