things i built because they needed to exist.
Full-stack portfolio project built to demonstrate end-to-end product development. Users create client profiles with brand voice and industry context, then generate platform-specific content using Claude. Multi-tenant architecture with row-level security, Stripe billing integration with three subscription tiers, usage tracking with soft caps, and automated website analysis. Covers the full stack: React/Vite frontend, Supabase backend, payment infrastructure, AI integration, and Vercel deployment.
A 12-project internal automation platform I designed and am building for the AutoVitals support team. The centerpiece is a live command center dashboard with real-time triage queues, active incident tracking, and weekly metrics. The incident detector clusters similar Zendesk tickets to catch outages before customers start calling. The ticket triage system uses AI to categorize, route, and suggest responses. Auto-tag-and-bag links child tickets to problem tickets during incidents and sends customer updates automatically. There's also a health monitor for Twilio/Mailgun/POS integrations, auto-generated weekly reporting, and workflow tools for shop reactivations and data recovery. This is what happens when you let the person who answers the tickets architect the system.
A security incident dropped 100+ tickets in our queue simultaneously. Doing it manually would have taken the team a week. I built a Python automation suite on top of the Zendesk and OpenAI APIs that handled bulk ticket processing, GPT-powered categorization, and real-time team metrics. It now runs daily — reporting dashboards, CLI tools for common operations, automated triage. Cut our manual workload by 40%.
I got tired of running the same fifteen commands in the same order every time someone reported a sync issue. So I built a diagnostic toolkit: SQL Server connectivity checks, network path tracing, DNS verification, registry validation, and log aggregation across 200+ client installations. The team went from 62% first-contact resolution to 78%. Not because they got smarter — because the tooling got smarter.
NAPA deprecated their v1 API. Every affected client needed to migrate to v3 without losing a minute of uptime. I built the tracking system, automated the communication workflows, wrote validation scripts for each migration, and developed rollback procedures for anything that went sideways. Every client transitioned with zero downtime. The rollback procedures were never used.
50+ technical articles. Not marketing content — troubleshooting decision trees and step-by-step procedures for SQL Server, API integrations, network connectivity, and distributed systems. Written so the next person who hits the problem doesn't start from zero. Also built the onboarding documentation that cut new engineer ramp-up time by 60%. Knowledge that compounds is the highest-leverage thing you can build.