Owner / BuilderFort Lauderdale

Work

I run businesses and build small systems around the problems worth solving.

Why I do this

The systems run while I’m somewhere else.

Not an agency. No team, no discovery workshop, no slide deck. Just me, the same tools I use in my own businesses, and a strong preference for things that recover quietly at 2am.

I run salon suites in South Florida and help keep properties running in Florida, Ontario, and Idaho—remotely, most of the year. Every system below began with something costing me time, money, or sleep. I built them to solve my own problems, learned a great deal in the process, and only later started helping other operators with theirs.

Three systems / Real annoyances

The evidence

01

The router that crashed every Tuesday

The annoyance: The router at one of my salon locations locked up about once a week. Every time, tenants lost Wi-Fi, door access got flaky, and somebody had to drive over and pull the plug. A service call each week, forever.

The system: A smart power strip that watches the internet connection. Connection dies, power cycles, router comes back — before anyone texts me. About $200 of hardware and knowing where to put it.

The result: The expensive fix was replacing the router. Making the failure irrelevant worked better. Learning that distinction changed how I approach this work.

Read the full note
02

The house that lied about its size

The annoyance: This one started years earlier, when every change to the house meant a service call to a Control4 dealer who got harder and harder to reach. So I replaced the whole thing with a system I run myself. Then that system “wasn't working” — lights ignoring people, automations firing for a family that wasn't home.

The system: Before touching anything, I audited it. The house I thought had 800 connected devices had 1,751. Of 42 automation scripts, 29 had never run once. And the root cause wasn't logic at all — the house didn't reliably know who was home. Fix the presence data and most of the “broken” automations started working untouched.

The result: In this house, the broken automation was really broken input data. It reminded me to audit what a system knows before proposing a rebuild.

Read the full note
03

Southbound

The annoyance: Moving your tax life to Florida means proving 183 days a year here, and the tracking options were spreadsheets and hope.

The system: An iOS app that counts the days for you. I built and shipped it because the spreadsheet was not good enough for my own family.

The result: Sometimes the smallest useful fix is a real piece of software. Carrying this one all the way to the App Store taught me plenty.

View evidence ↗
time zones
3
connected devices audited
1,751
shipped iOS app
1

A direct arrangement

How can I help

  1. Audit the annoyance. Find the actual failure before anyone buys a rebuild.
  2. Build the smallest fix. One fixed price, agreed in full before work starts.
  3. Keep it boring. Monthly care only if the system genuinely needs a keeper.

It starts with one conversation about what's eating your time. If the answer is something small, I'll say so, and you can buy me lunch instead. If it's a real build, you'll know the whole price before we start—and if I'm not the right person for it, I'll tell you that too.

No meter running while I think.

Who this is for

Operators like me: a handful of locations, a franchise or two, salon suites, a few properties. People whose problems are real but too small for enterprise IT and too weird for an off-the-shelf app.

The fine print about priorities

The rest of this site is sunsets, kids, and golf. That's not a hobby section—that's why I care about the work. Good systems buy back time, and the systems keep teaching me how to build better ones.

Email me I read and answer it myself.