Product design and direction
Taking an early-stage product concept, finding the spine, designing the flows and screens, writing the words. Best when the team is small enough that the design and the build can be the same job.
A few outside engagements a year, for founders and small teams. Always hands-on: I draw the screens and write the code. This is the work I’m best at.
Taking an early-stage product concept, finding the spine, designing the flows and screens, writing the words. Best when the team is small enough that the design and the build can be the same job.
Building production software, top to bottom. Typically Next.js, TypeScript, React, Postgres. The usual neighbourhood. The interesting part is rarely the stack; it’s the edge cases that show up once real people and real money run through the product.
Internal tools, admin surfaces, booking and scheduling flows. The kind of software a team uses every day to run their business. It’s where I’ve spent the most hours, and RitualPass is made of it.
Short, focused engagements where I look at an existing product critically and write up what’s working, what isn’t, and what to do about it. Useful for teams between rounds, before a relaunch, or trying to understand why something feels off.
Engagements run in months, not days, so there’s time to understand the thing: the users, the operations underneath, the parts the team has been meaning to get to.
Design, code, and copy, from the same hand.
Often the most valuable thing is an hour with someone who’s spent time on a similar problem. Sometimes that’s all you need.
If you’re building something and want a hand with it, write to me. Tell me what it is and where it’s stuck.