What I Want To Be

Most career plans are lists of titles. Mine is a list of capabilities. Titles get handed to you; capabilities you take.

I want to be the person teams call when the problem is ambiguous and the deadline is real. Not a specialist in one corner of the stack — a finisher. Someone who can take an idea from napkin to production and make it feel inevitable along the way.

I want to build a company that outlives my attention. BotHive is the first attempt, and it's taught me that the hard part of a company isn't the product — it's designing the machine that makes the product. I want to get genuinely great at that.

I want to be early and right about conversational software. The interface layer is shifting under everyone's feet, and the people building Clara-shaped and Astra-shaped things today are writing the defaults everyone else will inherit. I intend to be one of them.

And underneath all of it: I want a body of work. Not a résumé — a shelf of things that exist because I existed. Products, tools, writing, companies. When someone asks what I do, I want the answer to be visible.

Ambitious? Sure. But every line of this is already in motion.