Selected work

Real work, built around real operations.

A business website, an operations platform, and a custom application. Explore the work behind each.

Primary case studies

Three systems. Real constraints.

Business website

A service-led website connecting drivers to calls, messages, directions, and online booking.

Users: Drivers and shop owners
My role: Structure, UX, visual design, public-site build, growth tools, and QA
Built: Service explorer, online booking, mobile contact paths, and protected owner reporting
Technology: Static and Node build on Vercel; serverless requests, privacy-filtered analytics, and database-backed events

Key decision: group services by driver needs and keep contact options within reach.

DeliveredA clearer route from service discovery to contacting the shop.

Connected operations

Family registration and payments, connected to staff workflows for programs, rosters, capacity, and exceptions.

Key decision: separate family and staff workflows with role-based access.

DeliveredRegistration, payments, and program administration in one place.

Custom application

A custom pool application replacing spreadsheets and messages with shared rules and weekly deadlines.

Users: Players, commissioner, and administrators
My role: UX, application logic, admin flow, build support, and QA
Built: Registration, picks, locks, standings, payouts, and commissioner controls
Technology: Private web application with rules and financial administration

Key decision: lock picks at the first kickoff and reveal them after the deadline.

DeliveredWeekly play and commissioner oversight in one system.

Behind the build

Download example maps, runbooks, and launch checks.

All six examples, one packet.

Discuss your project

Let’s talk through your version.