I design and build the things other designers use.

Most designers hand you the ideal version. Opeyemi hands you the real one; low resolution screens, spotty networks, and all. We shipped the driver and transporter apps together, and the edge cases were already covered before I wrote a line of code.

I built the admin dashboard and payments product against his designs. Every state was accounted for — pending, failed, partially settled, the ones you usually discover in QA. I have done less guesswork from a design file with Opeyemi than with any other designer.

We worked together on Omega and the Hotel Entertainment Hub. Opeyemi turns a vague brief into something the whole team can build against, and he kept us honest about the question that actually mattered: what does a tired guest want from the screen in front of them?

Opeyemi builds the things the rest of the team ends up standing on. Poseidon started as his argument for one component library instead of five, and he made the case so well that adoption stopped being something we had to enforce.

We asked for a logo and got a system we still design against. Opeyemi was thinking about how the mark would hold up on a receipt and an app icon before we had thought to ask the question.

He is the person you want reviewing your work. Opeyemi will tell you the component you are about to build already exists, show you exactly where, and somehow you leave the conversation more confident than you went in.