Relentless curiosity.
I dig into problems until I understand them well enough to build something worth using. If I’m not learning, I’m not interested.
Not because someone handed me a spec and a deadline — because something was broken, or missing, or could be better, and the curiosity wouldn’t let me leave it alone.
ShirePath started less than a year ago, but the work started long before that. I’ve been building software professionally for years — C#/.NET, React, TypeScript, Next.js, Python — across workers’ comp brokerage, donor data pipelines, youth sports operations, and whatever problem landed in front of me. At some point I realized the pattern: I keep ending up as the person who looks at a broken system and says “I’ll just build something better.”
So that’s what ShirePath is. A studio where I build software and systems for real problems — usually ones I’m facing myself. I run operations for a youth flag football league in Southern California, so I built the platform to manage it. I wanted Bible reading to feel like an RPG, so I built that. I wanted to send my family a Christmas card that actually meant something, so I built an AI app that writes and narrates personalized stories. Right now I’m wiring a Whoop band to a glucose monitor to figure out what my body actually does with the food I eat.
I’m not trying to build the next unicorn. I’m trying to build a portfolio of things that matter — to me, to the communities I’m part of, and to the people who have the same problems I do. Some of them will become real products. Some of them will teach me something and end up on the Shelf. Both outcomes are fine.
When I’m not building software, I’m restoring a 1985 GMC K2500 square body, leading F3 workouts at 5am, cooking whatever the smoker asks for, or figuring out how to be a good dad to my daughter alongside my wife Erin.
If you’ve got a problem that won’t leave you alone and you want to build something about it, you’ve found the right crew.
None of this means skipping the plan — it means planning by building instead of billing you for slides first. If you want a partner who scopes carefully, ships real software early, and tells you the truth about what’s working, that’s exactly what I do.
I dig into problems until I understand them well enough to build something worth using. If I’m not learning, I’m not interested.
I’ve felt the pain of shipping fast without architecture. Quality matters. Clean code matters. Doing it right the second time matters more than shipping fast the first.
This whole site is transparency. Here’s what I’ve built, here’s what failed, here’s what I’m working on now. No smoke. No decks.
I’d rather build the thing than sell you a plan for it — you’ll see working software early and often, not a stack of slides. Sleeves up. Let’s make it.
The core is four: me and the three below. When the work calls for it, we scale past eight without missing a beat. These are the people I build with: partners, mentors, and a few of my best friends who happen to be dangerously good at what they do.

Takes the first pass and owns the ship date. Full-stack across every build on this site, and the constant the rest of the core plugs into.
One of my best friends, and the person I call when the data layer stops making sense. Co-building on several active projects — he makes the pipes quiet so everything else can be loud.
Partnering up on Jettison Air — role and scope still forming. Another one I’ve known forever, which is the only way I know how to start a company.

Lives on the cutting edge of what’s possible with AI and is generous about dragging the rest of us along. If it involves models, prompts, or agents, I’ve probably run it by Patrick first.
The why behind everything else. Every project has to survive the “is this worth the hours I’d otherwise spend with them” test. Most don’t.
Running league operations for 1,500 families while building software for the operation and whatever else has caught my attention this month.
Shows up in the work — see Biblical Battle Plans — but mostly it just shows up as how I try to live. Quiet, consistent, not performative.
Free men’s fitness in the dark. It’s where half my best ideas land, and where I remember there’s a whole life outside the screen.
Usually a few going at once. A good share of what I end up building started as a line in someone else’s book.
Partnering with the people and businesses around town. The best problems to solve are the ones close enough to drive to.
The short version: I’ve spent the last several years building real software for real operations — not just side projects. ShirePath is where all of that shows up in one place.