The platform
Member Splash is membership management software for swim clubs. 460+ clubs use it to run online registration, collect dues, and manage waitlists. The platform runs on WordPress Multisite. The right tool for the multitenancy model, not the trendy one.
Two product engineers on the platform. We each own features end to end: problem framing, design, implementation, production. Over three years, that's meant working across payment flows, operations tooling, infrastructure, and security.
What I've shipped
A member credential system that rolled out to all 460+ clubs. No opt-in migration. Every existing membership got updated automatically. The systems involved weren't designed to talk to each other, and club data was inconsistent across years of schema drift. The migration had to resolve all of it without touching live membership state.
A check-in flow redesign that brought check-in time from 30+ seconds to under 10. I set the 30-second baseline before building. That number drove every decision. The previous flow had too many steps between "person shows up" and "attendance recorded." Tested with actual club staff before shipping.
A Docker-based development environment that replaced a fragile, documentation-heavy local setup. Before it existed, developers were testing against production. The Docker environment closed that gap. Onboarding time dropped as a side effect.
Security remediation after a third-party audit surfaced vulnerabilities in the codebase. Triaged by exploitability and blast radius. Addressed critical issues first. Documented the vulnerability patterns as a threat-class reference the team now uses in code review. Closing tickets isn't the goal. Not reopening them is.
What I'm after
I own it from design through implementation. Every step.
I work best where the product problem and the technical problem are the same problem.
Architecture and implementation specifics available under NDA on request.