Not a portfolio

A portfolio is a thing you bring to interviews. When someone says they're building their portfolio, they usually mean they're arranging finished work while they wait to be evaluated. That's not what I wanted here.

What I wanted was a working site. Something that does a job. The job is narrow: when someone I've met, or someone who has been referred to me, opens this URL, they should know within thirty seconds what I do, what I've built, and whether it's worth booking a call. The site should end with a calendar link. That's the brief.

I also wanted to own a piece of the internet that actually sounds like me. Not a LinkedIn summary. Not a consulting firm dressed up with my name on it. Something that reflects how I think, because I spent a few weeks building it from scratch and thinking carefully about what it should say and what it should look like.

The word "portfolio" went early because it implies a posture I don't have: backward-looking, waiting to be judged. I'm a founder. I'm building three products right now. The consulting work runs alongside that. A portfolio suggests I'm between things. I'm not.

I also had an aesthetic I wasn't willing to compromise. AI tools have made the default personal site more uniform than it was before. The same font everywhere, the same gradient cards, the same centered hero with a sub-heading and two buttons. It reads as machine-assembled because increasingly it is. I wanted warm beige and a serif with some character. I wanted it to feel like a slow morning with a good magazine, not a SaaS dashboard. I wanted someone who cares about how things are made to see that I do too.

Whether it works as a lead machine, I'll find out. But the intention is clear. This is a working tool, not a filing cabinet.