§ 02
AI Work
Shipped,
not specced.
Most of what’s here runs on production traffic or was built and deployed end-to-end — formal AI training put to work, not left on a certificate. AI fluency is increasingly table stakes for senior product work, and this is what that looks like in practice.
§ 02.1
Production · Exclusive Resorts
AI shipped at scale
in a luxury travel platform.
Some member-facing, some internal tools for advisor teams — production releases and active betas. The member-facing tools draw on CMS and concierge-vetted content first, before broader sources.
What we’ve built
§ 02.2
Personal Project · Built in Bolt
CrewChief — AI-powered
automotive ownership platform.
Full-stack web application I built to solve a real problem: most vehicle owners have no organized system for their car’s knowledge, history, and future work. CrewChief fixes that with a persistent AI advisor that actually knows your car.
When you add a vehicle, the app calls Gemini to generate a comprehensive dossier — known failure points with mileage ranges, full factory maintenance schedule, fluid specs, common modifications, reliability score, and powertrain details. Everything downstream builds from that knowledge base.
Under the hood
§ 02.3
POC · Exclusive Resorts
Lumière Collective — a POC built to test
onboarding drop-off.
We were seeing member drop-off in the community onboarding flow, right at the profile photo step. Working build, demoed internally, not yet rolled out to members.
The bet: if a member doesn’t have a photo they’re confident in, they abandon and don’t come back. This POC gives them an exit — upload or capture a portrait, get four professionally styled variations in under 60 seconds.
Under the hood
§ 02.4
AI Practice
AI as a working environment,
not a feature.
This is harder to show than a shipped product, but it’s probably more relevant to how I’d operate on your team.
Claude Teams — how I actually use it at work
I use Claude Teams across a significant portion of my work, and I’ve built out a structured practice around it — not just prompting, but building shared tooling for my team. The practical effect: tickets, release notes, and interview synthesis start from a structured first pass in minutes instead of a blank page — and the whole team drafts from the same structure.