The operator who builds his own tools

I run live events for a living — and build the tools that make them, and the businesses behind them, better.

I don’t start with “I want to build an app.” I start by doing something — running a wedding in front of 200 people, cutting a photo gallery at 1am, hitting a lift, hunting a job — and hitting the same friction twice. The second time, I build the tool.

That’s the whole method. It’s why my work looks scattered until you notice the pattern:every project is downstream of something I was already doing.47 of them. I call it the Build Loop.

See what I’ve builtWhy I’m here
01

Live Execution

Performs under pressure, in real time, with people watching.

120+ weddings and events as a DJ/MC — 90%+ NPS, Rookie of the Year, #1 DJ Q3 2025. Built on a decade of operations at scale: Amazon logistics, multi-event coordination. Zero do-overs, every time.

Explore →02

Builder

Builds the tool nobody else was going to build for him.

Self-taught, all of it shipped — a competition simulator on 7,000 records, Vision-AI PWAs that read contracts off a photo, resilient data pipelines with real-browser automation, a real-money trading bot with a risk manager. Grouped by the life that spawned each one.

Explore →03

Business Growth

Turned a favor-based side hustle into a real commercial operation.

LA Media: photo/video moving into B2B commercial, with tiered packages, a cold-outreach engine fed by a 25,000-business dataset, and an 8-tab operating system underneath it.

Explore →04

Where It’s Heading

Same builder instinct, aimed at a technical seat.

Software/technical roles where building is the job, not something squeezed in around one. The proof: I built my own AI-ranked job-hunting dashboard to run this exact search.

Explore →

Anchor case study

Mind Games

An IWF-compliant Olympic weightlifting competition simulator — ~7,000 real USAW records ETL’d into PostgreSQL, fed by Playwright automation through Sport80’s authenticated portal. The clearest proof of the thesis: I build where my lived expertise is deepest.

Read the case study →

The one thing to take away

From one app a quarter to several a month — in about a year.

As I learned to leverage AI tooling, my build velocity compounded. That curve — not any single project — is the point, and it’s provable from commit history.

  1. Mid 2025~1 / quarter

    Single-purpose, slow. The first wedding timeline planner.

    TIMELINE
  2. Late 2025a cluster

    Getting reps — a scraper, a coaching platform, a lighting tracker.

    TheKnot scraperWORKOUTFLOWLIGHTLOG
  3. Early–mid 2026several / month

    Velocity compounds as AI tooling gets leveraged.

    POLYBOTthrift-lensk9-overwatchCIVIC-DUTYVBTMind GamesJob HunterECHO