Portfolio

Systems that are still running.

Not mockups or demos — real systems in production, built to run without babysitting. Some are independent work for local organizations; some come from my engineering career. Each one says which.

The weekly grind that ran itself out of a job

Volunteer project · 200+ member church (Kansas City)

A recurring twice-weekly production routine — recordings into formatted outlines, two websites updated, videos organized, announcements assembled and sent — rebuilt to run entirely on its own. Zero manual hours per week, in production since early 2026.

0 hrs Manual work per week
40+ Subscribers in week 1
~1 hr Monthly maintenance
Read the case study →

The group text that became a scheduling system

Volunteer project · church ministry teams (Kansas City)

A church's volunteer rotations lived in group texts and one person's memory. I built a scheduling system that generates fair rotations, lets people swap and find cover on their own, and puts the schedule on everyone's calendar — no coordinator chasing replies.

2 Teams, one system
Self-serve Swaps, cover & time away
0 Passwords for volunteers
Read the case study →

A contractor website that catches every lead

Website · Ferry Construction & Excavation (St. Joseph, MO)

A local excavation and roofing contractor was running on word of mouth and a Facebook page. I built a fast, multi-page site around his real work and job photos — and wired it so every form, call tap, and text tap is logged to a spreadsheet and emailed to him.

Every lead Logged to a sheet + emailed
10 Service-area towns covered
Read the case study →

The onboarding bottleneck that automated itself away

Engineering career · technical lead at a fintech company

Bringing on each new customer meant engineers hand-mapping that customer's data files into the internal system — slow, manual work every time, and a ceiling on growth. I led the build of an integration platform that drafts the mapping automatically — projected by the company to save millions a year in onboarding time.

Millions/yr Projected onboarding savings
Manual → reviewable draft Per-customer file mapping
Read the case study →

Days of setup, done in an afternoon

Engineering career · internal tooling

Turning written specifications into working system configuration was a manual, error-prone slog — days of careful hand-work each time. I built an internal AI tool that generates the configuration straight from the spec, collapsing days into a single afternoon.

Days → an afternoon Setup time per configuration
Spec-driven Config generates itself
Read the case study →