#What I've Built

Leading the consolidation of three acquired businesses and six apps into a single mortgage platform. Most days are spent killing legacy, rethinking architecture, and figuring out how to make six things behave like one. The hardest part isn't the code. It's aligning teams that built things independently for years toward a shared system.

Took over after the MVP was built and grew it into a successful product. Mortgage marketing platform with smart campaigns that don't feel automated: SMS, email, voicemail drops, sending millions of messages daily in large bursts. Built and optimized the entire messaging pipeline to keep it scaling with growing demand. Acquired by MMI in 2024.

Built a knowledge management system for a large manufacturer's production plants. Complex domains, lots of stakeholders, long feedback loops. Before that, worked on crypto exchange platforms and price aggregators. On the freelance side, built things like a plastic garbage recycling platform. Early career: fast iteration, lots of variety, learning how different kinds of organizations think about software.

Building a fleet management platform with real-time GPS tracking, CAN bus integration, and remote vehicle control. Built a "car-in-a-box" simulation with Arduino so the GPS tracker can be tested against vehicle events like harsh braking without needing an actual car. Set up automatic device provisioning through AWS IoT, and wired up a breadboard with diodes to prove the remote control concept. The plan is remote engine kill and horn trigger. Wanted to get my hands on hardware after years of software-only work. Connecting bits to atoms is a different kind of satisfying. Debugging a GPS module that won't lock or a CAN bus message that doesn't parse is nothing like debugging a failing test.

Building with my gym coach to help him manage training plans for his clients. Using it as a real validation ground. If it works for him, the plan is to turn it into a SaaS product. Solving a real problem for a real user before writing a single line of marketing.

A YouTube channel where I talk about building SaaS products with Laravel — architecture decisions, tooling, and things I've learned from shipping real side projects. Started alongside saaslaravel.com and want to get back to publishing regularly.

Started because I kept seeing the same patterns: people shipping Laravel projects that worked but were impossible to maintain. The original idea was a paid course, but along the way I ended up building tooling that I think is more valuable as open source. The past couple of years haven't been kind on time so it's been sitting untouched, but I want to come back to it properly: release the package, use the domain for its docs, and get back to making YouTube content around it.

Tried to start a consulting agency. Lasted a few months. Learned that selling services is a completely different skill from doing the work, and I didn't have enough appetite for it at the time.

The mature version of something I'd been rebuilding since I was 15. Patient scheduling, visit history, automated notifications. Local-only, no cloud. I rebuilt this thing from scratch probably 10 times over the years, never referencing old code. Writing my own calendar components because I didn't know libraries existed. This project taught me more than anything else. Every edge case was mine to figure out, and the understanding stuck because it was built from trial and error.

Tried to build a tool that would optimize agent swarms by feeding them more domain-context from the codebase. Didn't work out as well as I thought it would, but great learning experience for understanding the limits of agent orchestration.

Upload a .psd as a template, POST to the API with placeholder replacements, get back a rendered image. No UI, just an endpoint. Built it to automate mockup generation for Projekt Plakat product shots.

Started writing a toy programming language in Rust. Never finished, just a weekend rendezvous with a language I was curious about.

Service for replicating a voice and generating text-to-speech output. Experimented with making custom voice clones available as an API.

WordPress plugin that generated voice transcripts of blog posts and attached them as an audio player. Let readers listen to posts instead of reading them.

Built a habit tracking app focused on streaks and consistency. Track habits, see hotstreaks, stay accountable. Never launched publicly.

Built an API that scraped against do-not-call lists and validated line types for phone numbers. Useful for anyone doing outbound at scale and needing to stay compliant.

Imported bank CSV exports, categorized transactions, and generated spending breakdowns. Built it because I wanted to see where my money was going without trusting a third party with my bank data.