ABOUT.

That's the short version. Here's the longer one.

The hustle years

In June 2019 I left a job and went all-in on freelance — selling marketing services and SEO to local businesses, drop-shipping on Shopify, flipping used books and low-content books on Amazon. Anything that paid. I did that for two years through COVID.

Pricing microwaves on spreadsheets

In August 2021 I got hired as a Marketplace Coordinator at a home appliance distributor and manufacturer — they did $100M+ a year in ecommerce, held the Farberware microwave license, and managed marketplaces for top brands like Shark Ninja and Cuisinart. My job was listing products on Amazon and Walmart, pricing them with a Pricing IQ spreadsheet, manually looking up shipping estimates, and running SEO on the company's Shopify sites. Most of my day was pricing.

I've always been into data. The SEO work taught me to like the technical side of marketing — schema, structured data, crawlers. Once I was deep in pricing, I started looking for ways to do it less manually. I rebuilt our Pricing IQ in Excel with VBA — automated the lookups, the calculations, the comparisons. By January 2022 I didn't want to do the SEO and Shopify work anymore. I wanted to do data.

Why R, and why sports got me there

My dad is a Power BI engineer at a large insurance company. He told me to learn Power BI. I told him I wanted to do predictive analytics, and Power BI wasn't going to get me there.

I picked R. To stay interested while learning, I leaned on what I knew: sports. Lots of data, easy feedback loops, you actually care about the answer. I bought Statistical Sports Models in Excel by Andrew Mack. He builds out a bunch of models in Excel and references R as the next step up. My first real R projects were rebuilding his models, then pushing them further.

For the next few years I built and shared sports models. Bet sports a little. Wrote a book on Bayesian methods for NBA prop bets — that's the one still on this site. I also started trading futures at the end of 2021. The whole time I was trying to bring those skills back to my day job. Pricing was already automated; I wanted to do real analysis of what we were selling on Amazon and Walmart, what was working, where we were losing money. The company wasn't interested.

The quit

By April 2025 I was done. The company wouldn't give me developer tools. Getting clean reports was a fight. I was building things that exposed where the business was failing, and a lot of those failures pointed at specific people. The IT director, especially, was not a fan of being exposed — so he made sure I didn't get what I needed to do my job.

I'd just moved my family into a new house, paid off, and we'd sold the old one. I had two years of savings in the bank. So I quit. The plan was to trade futures full-time. I'd been doing it for three years on the side and making money at it. It felt like the moment.

Two hundred dollars on Lovable

By November 2025, Claude Code was taking over the AI build conversation, and tools like Lovable and Bolt were what people on social were vibe-coding with. I signed up for Lovable. I burned $200 on tokens, hit the ceiling of what it could build, and got fed up. There had to be a better way.

So I subbed to the Claude Max plan and used it to learn how to build better web projects. I'd also been using n8n for a while — self-hosted it earlier in the year when it started showing up everywhere on social — and by the time Claude Code clicked, I was already deep in AI agents, APIs, and automation.

Building models in R taught me how to break problems down. That translated almost directly to agentic coding. I went from maybe 15 GitHub commits a year to 1,200+ in the last six months. CLI tools, web apps, desktop apps, agents, automation — if I could think of it, I built it. Mixing OpenClaw with n8n, learning more about open-source models, just starting Karpathy's neural network course because the next thing I want to understand is how these LLMs actually work under the hood.

Today

I just started a new job as an Executive Operations Coordinator at a company that sells power infrastructure for buildings, data centers, and — increasingly — AI infrastructure. Which is a strange and good place to land if you've spent the last six months obsessed with how AI agents work. The customers are the people building the data centers that run them.

The mandate is to improve internal processes using AI and automation. After five years of building tools nobody asked for, that's exactly the role I wanted. A lot of the work is in the Microsoft ecosystem — Power Automate, Copilot Studio — which is a different shape than what I do in my own projects, but the patterns are the same.

Outside of that, I'm still building, still trading, still open-sourcing most of it. The goal hasn't changed: make small, useful tools that help people, and put them somewhere they can actually find them.

Outside all that

I was on a golf path before any of this. I went to the Golf Academy of America in California to chase the PGA. That didn't work out, but I still play whenever I can.

I live in Little Chute, Wisconsin. Grew up in Green Bay. I'm a Wisconsin sports fan in the textbook way — the Packers, Bucks, Brewers, Badgers — and I hate every team from Minnesota, Michigan, and Illinois with the kind of focused energy that only makes sense if you grew up here. Married, two kids, one of each.

That's most of it. If you want to see the work, the rest of the site has it. If you want to talk, I'm easy to reach.