The full story

00 — OVERVIEW

The Short Version

I build software and run operations. I started in retail, moved into tech, and now build production applications using AI-first development workflows. My background in operations means I think about systems holistically — not just the code, but the processes, the economics, and the people.

01 — RETAIL

Retail

My first real education in systems came from retail. Ten years managing stores, teams, inventory, and P&L. I learned P&L before I learned programming. I learned about margin before I learned about margin calls. Operations teaches you that everything is a system — and systems can be improved.

Managing a physical store with real constraints — rent, shrink, seasonal swings, vendor relationships, staff scheduling — forces a kind of ruthless prioritization that most software people never encounter. That training never left me.

02 — THE ROCK SHOP

The Rock Shop

I ran a crystal and mineral shop — a six-figure retail operation at its peak, with significant inventory across hundreds of SKUs and a substantial debt load. Full liquidation. It was a masterclass in what not to do, and then how to get out clean.

I learned about inventory velocity, carrying costs, and the brutal difference between revenue and cash flow. That experience is baked directly into Almighty — every feature in the debt payoff engine comes from a real problem I faced. The crystal shop was expensive tuition, but it paid for itself in product intuition.

03 — TECH

Tech

I came to software through necessity. I needed tools I couldn't afford to hire out. I started with no-code, then learned to ship real software using AI-first workflows. I write spec documents before touching code. I treat AI agents as junior engineers.

My development philosophy: spec before code, ship then listen, systems over heroics. I've shipped production apps across mobile (React Native/Expo), web (Next.js), and game development (Godot/C#). I also did B2B software sales — which means I understand what buyers actually care about, not just what engineers think they care about.

04 — URBANPX

UrbanPX

UrbanPX is my AI-first software holding company. Think of it as a small studio run by one person with a systems mindset. The goal: build products that are sustainable, useful, and honest — no growth hacking, no dark patterns, no VC pressure.

Current builds: Almighty (fintech ecosystem — Budget, Split, Platform), SHADOWSTATE (1650s colonial simulation game), and the internal tooling that makes all of it possible.

05 — PHILOSOPHY

The Philosophy

"Every decision should be a favor to your future self."

I believe small teams with strong systems beat large teams with weak ones. I believe in finishing things. I believe honest documentation is a competitive advantage. And I believe the best software comes from people who have actually felt the problem they're solving.

If you're building something and want to think through it — reach out.