Side projects — not the Salesforce work (that lives in the case studies), but how I keep my hands on real product and test ideas before they reach client work.
Personal iOS app for task and expense tracking.
Built to scratch my own itch with mobile-first time tracking. Local-first architecture, clean swipe gestures, and a small backend behind a Google SSO flow. The app is small on purpose. The interesting work is in the data model and the sync story, not in the screen count.
Instagram content series on go-to-market systems.
A vocab series that breaks down one RevOps concept per reel: ICP, pipeline, forecast, and the rest. Each reel runs through a custom Remotion-based pipeline that handles planning, rendering, music, and cover art. The point is to make the foundational vocabulary of GTM easy to share inside a team.
Building and testing AI agents on top of personal infrastructure.
Custom multi-agent setup for research, writing, and operational work, layered over an Obsidian-based second brain. Most of the value is in the connective tissue: how memory persists across sessions, how agents hand work to each other, and how the human stays in the loop without becoming the bottleneck.
Three different reasons. Logger Slogger is a craft project, a way to keep my hands on real product work. @gtmdiscipline is a teaching project that forces me to compress what I do into language a non-RevOps person can use. The agent work is research, mostly to figure out which AI patterns actually hold up inside a working revenue org and which ones are demos.
If you are building something in the same space, I am always interested in trading what works for what does not.