All plays › Local trades and home services

Local trades and home servicesClaude Code

Build the industry software you’re overpaying for with Claude Code, even if you don’t code

Picked and checked by Olga Pearson, host of The Practical AI Show · Published

Result

self-reported

A non-coding CEO built his own kitchen design software with Claude Code over 4.5 months. The tool his industry uses costs $6,600 up front plus $1,850 a year per seat. On air he designed a whole kitchen in about five minutes.

Randy Lorensen runs Premium Cabinets (30-plus locations). He’d never opened Claude Code, but he built TurnKey Cabinet Design alone on two Claude Max plans. A five-minute prompt on a Sunday night ran for three days and came back with a working version. He says the edge cases after that were 99% of the work. The software lays out cabinets using real manufacturer SKUs, with pricing and a parts list, and a bug button sends his spoken reports straight to the coding agents. He showed it on The Practical AI Show, Ep 61.

Who did it

Randy LorensenPremium Cabinets (30-plus locations)The Practical AI Show, Ep 61 (with Randy Lorensen) · Oct 16, 2026

Try it now

  1. Add up what your industry software costs you: up-front price, yearly fee per seat, training days and the hardware it needs.
  2. Write a plain-English spec of the result you want, e.g. ‘someone who has never designed a kitchen can do it without mistakes.’ Describe the result, not the code.
  3. Give that spec to Claude Code, let it build a first version, and expect the edge cases to take most of the time.
  4. Add a ‘report a bug’ button so you and your team can send problems straight back to the build, and test it in-house before you sell it.
Copy-paste prompt
I run [business] and we pay [$X up front + $Y/year per seat] for [software] to do [job]. I don’t code. Help me write a one-page spec for a simpler tool that lets [who] do [job] without mistakes. List the screens, the questions the tool asks, the data it needs (e.g. our product catalog with SKUs and prices) and what it outputs (e.g. a layout plus a parts list). Then list the 10 edge cases most likely to break it. Don’t write code yet.

Make it run every week

A play works once. Turn it into a routine in three small steps:

  1. Run it once and check the result yourself.
  2. Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
  3. Keep a log. One line per run: what was checked, anything flagged, what you did.

See how owners turn plays into systems →

What to watch out for

Told on air. It’s a 4.5-month build with Claude agents running around the clock, so it isn’t a weekend project, and TurnKey is still in beta. Disclosure: Practical AI is hosted by Olga Pearson (who runs AI Business Plays) and Chris Pearson (who builds PageMotor). Build it with Page: a product page and waitlist for the tool you build.

Did it work?

PageMotor keeps this site free.