About Vizzly
Building visual development workflow tools for modern teams.
I'm a software engineer who loves building awesome, accessible front-end experiences—web, native apps, or APIs, I've done it all. From 2018 to 2022, I was a critical part of the Percy team (now BrowserStack), handling support, building SDKs, and working on the internal growth team.
Through hundreds of customer conversations at Percy, I learned exactly what teams wanted from visual testing tools and what their biggest pain points were. After leaving and watching the visual testing landscape stagnate for years, I decided to build the collaboration-first platform I wished existed.
I've helped companies like Visa Checkout achieve WCAG 2.0 compliance, ensuring accessibility for millions. I've contributed to the developer community through technical speaking at conferences like JSConf and creating content around testing and accessibility.
When I'm not building Vizzly, you'll find me wrenching on my 1995 NA8 Spec Miata (#20) or racing it in the SCCA Spec Miata Southwest Division. I also love tinkering with IoT gadgets, experimenting with Large Language Models, and building tools like my macOS app, DraftPatch.
in visual testing
customer convos
speaker
Why I'm Building Vizzly
The CI/CD feedback loop is broken
Every visual testing tool forces you to push to CI before seeing results. You should catch visual bugs while coding.
Per-screenshot pricing punishes coverage
Teams avoid adding tests because it costs more money. Vizzly charges by team size, not volume.
Collaboration is an afterthought
Visual reviews involve designers, PMs, and developers. Vizzly is built collaboration-first.
Ready to try Vizzly?
See what visual testing feels like when it's built for collaboration.