BUILD

Websites and apps, built with Claude Code.

Most of my career has been building things people walk into. These days I also build the screens around them: websites for small businesses, and the apps an event runs on. I bring the brief, the taste and the testing on real devices. Claude Code writes the code with me.

Websites.

Four sites, one browser. Click a tab, drag the amber line to see the before, and scroll inside the window. On a phone, press and hold to scroll the site.

Omwell Energy.

My sister's energy healing practice and shop. The ask: a site that feels as calm as a session with her, booking that just works, and one she can keep editing herself.

Client
Omwell Energy
Built on
Shopify, with custom sections
What changed
5 new pages, 5 rebuilt, 11 custom sections, reviews and online booking
Live
11 Nov 2026
omwellenergy.com
omwellenergy.com
Omwell's old homepage Omwell's new homepage

For events.

Apps I've built for RGXM's activations. They run on iPads and phones at the venue, so they have to keep working when the Wi-Fi doesn't.

Dracula audio stations.

The ask. Listening stations for an exhibit: guests put on headphones, tap play and hear the story.

What I built. An iPad app that plays with the Wi-Fi off, a staff menu behind a code, and a dashboard that counts every play. Four iPads, three stations, four headsets each.

How it went. 647 plays over the weekend, and 82% of them were heard to the end.

An iPad mounted on a weathered wooden post beside an old lantern; its screen shows the same wood grain behind a play button
A station at the exhibit. The player's background follows the grain of the post it hangs on.

Diablo Maple Forest booking.

The ask. Timed entry for a brand activation in December: book a slot online, walk up if there's room, check in at the gate.

What I built. Booking with QR check-in on an iPad at the gate, a digital walk-up line, texts and emails to guests, and a report for the client afterwards. It held when 50 people tried to book the same slot at once.

What the client gets. A live report that saves as a PDF or a spreadsheet: sign-ups and who came, the show-up rate and no-shows, walk-ups and how long they waited, the busiest hour, where bookings came from, and how many opted in to hear from the brand.

How it went. The show is 3 and 4 December. Ask me after.

The booking app's first screen: Diablo Maple Forest, the dates and place, and Reserve your tap

Open the link: when, where, and one button to reserve your tap.

On the side.

Things I build for myself, because I want them to exist. Pick one.

fee@home: ~/builds

A fear and greed gauge for the Pokémon card market, read the way traders read the stock market. It rebuilds itself every morning from public price data, for me and a few friends who collect.

Three markets, a reading from 0 to 100 for each, and what history says tends to come next. Leads, not advice.

Three gauges: Japanese market 31, fear; English market 19, extreme fear; Japanese vintage 61, greed
The morning's readings, 11 Nov 2026.

The itch. The voice typing app I used put a weekly cap on its free plan.

What I built. My own. Hold a key, talk, let go, and the words land wherever the cursor is. It runs on my own computer, so nothing I say leaves the room.

Now. One version on my PC, a twin on my MacBook.

Dictate's tray dot in three states, red for listening, amber for writing and grey for ready, under a Ctrl key and the words "Hold Right Ctrl and talk. Let go, and it pastes."
The dot in my taskbar: red while I talk, amber while it writes, grey when it's ready.

The itch. My dad's theory: when the forecast turns bad, golfers cancel and good tee times open up.

What I built. A lookout on the forecast. When the weather turns, it messages us, and it nudges us just before new tee times are released.

The rule. It never books. We do that ourselves.

Now. Resting until the season starts in April.

A Fore Cast chat alert: "Your course, Sat 15 May: forecast just turned worse", where two of three weather models now see rain, asking "Did a slot appear?", with a button to open the tee sheet.
An alert as it lands, with a made-up forecast.

The itch. Each invoice took about twenty minutes by hand.

What I built. I ask for a draft, and my records become an invoice in my accounting app.

The rule. It drafts. I review it and press send.

A sample invoice draft for Sample Client Inc., stamped SAMPLE and marked "Draft, not sent", with three lines totalling $1,600.00 and a tick saying it matches the agreed total.
What a draft looks like, with made-up numbers. It checks the total against what we agreed, then waits for me.

The itch. Notes, to-dos and numbers scattered across three computers.

What I built. One private dashboard for my to-do list, my projects and my money, with a version for my phone.

Where it lives. On a laptop I won in a contest, now my always-on home server. It checks its own health every five minutes and messages me if something is off.

A laptop and a phone showing my private dashboard: the tab names and section labels are readable, and every task, number and note is replaced by a grey bar.
The real thing, on my laptop and my phone. The private parts are greyed out.

I still produce events, and building the tools around them is the same job: listen to the ask, sweat the details, and test it on the real thing before the doors open.

Let's build something together.

Drop me a line or connect on LinkedIn.

Hi Fee, I'm from .
You can reach me at .

Your details are only used to reply.