Work
Projects
Each one started as a question I couldn't stop thinking about. Here's what happened when I actually tried to answer it.
Project Title One
A short, plain-English description of what this does and who it's for. One or two sentences. If your neighbor wouldn't understand it, rewrite it.
What problem were you solving? What was the approach? What did you learn or ship? Replace this with your actual narrative — the context is the part people remember.
Project Title Two
What does this app do in one clear sentence? Who benefits from it and why does it exist?
What problem were you solving? What was the approach? What did you learn or ship? Replace this with your actual narrative — the context is the part people remember.
Project Title Three
One crisp sentence on what this project is and why it exists. Avoid jargon — if your neighbor wouldn't understand it, rewrite it.
What problem were you solving? What was the approach? What did you learn or ship? Replace this with your actual narrative — the context is the part people remember.
About
The person
behind the projects
I'm Adam — a CX and operations executive who got hooked on building things. After 23+ years scaling service organizations at places like Google, Meta, and Indiegogo, I started spending more time in the maker end of the pool.
My sweet spot has always been the intersection of human empathy and operational efficiency — knowing when to automate and when to keep the human in the loop. These projects are me applying that same lens to problems I actually care about.
When I'm not at this desk, I'm surfing, climbing, or doing my best thinking somewhere without a screen.