Skip to content
Luke Walsh

Product manager · owner · builder

I build products fast, and they are right when they go live.

I’ve been adapting to new technology since 2003. Along the way I worked at one of the internet’s first ad exchanges, ran a real-estate software company, sold houses, managed a connected access-control product, and spent a couple of years in the trades. Every time the tools changed, I learned them. The tool now is AI, and I use it to build the products myself.

  1. 2003
    Right Media, one of the internet’s first ad exchanges. Auctions at scale.
  2. 2006
    Product marketing at Yahoo. I wrote the requirements engineers built from.
  3. 2008
    Real-estate software at IDX. I ended up running the company.
  4. 2017
    Licensed Realtor. Contracts, clients and deadlines that don’t move.
  5. 2022
    Product manager for gated-community access control.
  6. 2023
    The trades: disaster recovery by day, computer-science study on the side.
  7. 2026
    Product owner by day. Building my own products with AI the rest of the time.

Judge the number. I didn’t write the estimates. I heard them said out loud on job sites and had to decide whether they were right.

Hit the date. Real estate runs on signed paper and dates that don’t move. I managed the contracts and the people on every side.

Stay steady with people. After a loss, every kind of personality shows up. My job was to keep them, the crews and the insurers moving.

670

pull requests merged across my products in 2026.

Read .

Fast. I reviewed 50RH’s live signup funnel on 8 Aug 2026 and shipped six fixes within a day. Lantern was a tested prototype, ready for a guided demo, 17 days after its first commit. Fast here means fast to something that works: 50RH has no customers yet, and no family has used Lantern.

Accurate. Shipped means live and checked, not merged. When an AI checker in clio found none of six errors planted for it, I retired it and put a plain script in its place.

Scales. One pipeline for feature work: a weekly plan, then an audit, a build and a review. The plan runs on its own; I start each step after it. The planner reads the roadmaps of 50RH, Lantern and this site. The same kinds of checks travel from product to product.

Adapts. AI is inside three of my products and behind all of them, which is the experience AI consultant and forward-deployed product roles draw on. AI in the work

Plan → audit → build → review. How I build

  1. · This site

    I started this site: products first, a design system in light and dark, and tests that fail if a number has no source.

  2. · WPHostGuy

    I repriced WPHostGuy’s plans, and both now include a monthly test that each site’s contact form still works.

  3. · 50RH

    I set 50RH’s beta offer, three free months on a monthly plan with one single-use code per firm; outreach has not started yet.

  4. · 50RH

    50RH’s privacy policy now names every service that is actually running and the retention periods the code enforces.

The whole build log

  • Shipped means live and checked.
  • Never show a number that isn’t true.
  • Propose, don’t auto-promote.
  • Fail closed outside what you’ve verified.

Say hello.

I’m glad to compare notes with people who build products. The best way to reach me is a message on LinkedIn.