29 finished apps. Here is what they actually do.

Planning app · 6 modules

The Wedding Planning Suite

Guest list with RSVP states, a drag-and-drop seating chart, a budget with estimates against actuals, a task checklist, a day-of schedule and a vendor tracker — all in one file, all sharing one set of guest records.

The hard part: the seating chart. Tables are dragged around a floor plan, and every move re-runs capacity and "keep apart" checks so a conflict surfaces the instant it is created rather than the night before. The printable floor plan and printable seating list are generated from the same data, so they cannot drift apart from the screen.

Finance dashboard

Budget & Money Tracker

Fast transaction entry, category budgets that fill up as you spend, savings goals, a subscriptions register, and a dashboard that adds it up. Nothing is uploaded anywhere; the whole ledger lives on the device that typed it.

The hard part: the debt payoff planner. It builds a month-by-month schedule for both avalanche and snowball order from the balances, interest rates and minimum payments you enter — including rolling a cleared debt's payment into the next one — and shows you the difference in months and in interest.

Trip planner

Backpacker's Trip Planner

A multi-leg route builder, a hostel and transport bookings log, a per-country daily budget that tracks burn against plan, and a packing list that knows what everything weighs.

The hard part: weight accounting that matches how hikers actually think. Base weight, worn weight and consumables are three different totals, they move between categories when you change one checkbox, and everything has to display in grams or ounces without rounding drift. The route builder also flags any leg with no booking against it, which is the mistake that actually ruins trips.

Health journal · clinic-facing output

Perimenopause Symptom & Treatment Journal

A daily log of symptoms, cycles, treatments and their effects, plus a running list of questions to raise. Private by construction: no account, no sync, nothing transmitted.

The hard part: the output, not the input. Months of daily entries have to collapse onto one printable page a clinician will actually read inside a ten-minute appointment — what happens, how often, what has been tried, what changed. And daily entry had to stay under about twenty seconds, because a journal that takes five minutes is a journal nobody fills in twice.

Also in this line

Play-at-home escape room · 8 puzzles

The Vanishing at Marlowe House

A 1926 country-house escape room for two to six players. Eight interlocking puzzles, a countdown you can set or switch off, a hint ladder that costs you time, a findings tray, a printable pack for people who want paper on the table, and a facilitator screen for whoever is running it.

The hard part: checking answers without shipping the answers. A printed escape room puts its answer key in the same PDF and somebody always reads it. Here every accepted answer is stored as a salted hash, with a second set of hashes for common near misses — so the room can say "right shape, wrong letters" instead of a flat no, and View Source shows nothing but tokens. On top of that, what a player types is normalized before comparison, so capitals, spacing, punctuation, curly quotes, accents and a stray leading "the" never cost anybody the game.

Interactive case file · 1974

The Glass House Case

A cold case worked from twelve primary documents: coroner's report, crime lab, engineer's survey, a Polaroid and its shot log, phone logs, receipts, bank records, a partnership agreement, an interview tape. Read them, flag them, build a timeline, keep a notebook, then make an accusation the game grades.

The hard part: making twelve documents disagree with each other on purpose and still be solvable. The true answer has to be reachable from the evidence alone, every false lead needs an innocent explanation that survives a second reading, and the alibi timings have to hold up when a player lays them on one timeline — which is exactly what the timeline screen invites them to do.

Host-a-murder-mystery kit · 6–10 guests

Murder at the Harvest Ball

A complete dinner-party murder mystery: character packets for each guest, clue cards dealt across the evening, a host's running order, and a print checklist so nothing is missed at eleven at night the day before.

The hard part: the guest count. The same cast has to work with six people and with ten, so changing the number rewrites which characters are in play, which secrets get redistributed, and which clue cards are dealt — without ever orphaning the clue that identifies the killer.

Also in this line

Site engine · 7 published themes

The event-site engine

One codebase behind the wedding, baby shower, bridal shower, birthday, gender reveal, graduation and Halloween sites. Countdown, schedule, venue and directions, RSVP, registry links, FAQ, photo sections, four themes each, and a share screen. All the decorative work is per-theme; the machinery underneath is identical.

The hard part: the setup wizard, which had to be usable by someone who has never opened a text editor. They fill in a form, press download, and the app clones its own document, strips the wizard out of the copy, writes their answers into a config block and hands back a brand-new standalone HTML file. That means every value a guest might type has to be escaped on the way in — including the angle brackets that would otherwise let a name close the script tag it is being written into.

Front end

What the visitor sees

The published side is one page, loads in one request, and works on a five-year-old phone with two bars of signal — which is the actual condition your customers are in when they look you up.

Why it matters commercially: there is no builder subscription behind it and no platform that can change its terms. The owner has the file. They can host it free, move it to another host in ten minutes, hand it to a different developer, or open it in a text editor and change the phone number themselves.

Seven themes, one engine

White-label & re-theming

One build, many listings

Seven event sites from one engine. Three escape rooms whose engines are byte-for-byte identical. Three planners, two reading journals, two gamebooks, two case files. Each re-theme is a genuine product with its own copy, palette, illustration set, example data and setup guide — not a color swap.

The hard part, honestly: resisting the color swap. A re-theme that only changes the palette reads as lazy within about four seconds. The wording, the default examples, the icons and the empty-state text all have to belong to the new audience, or buyers can tell — and say so in reviews.

Three playable examples: one brand, three tools

These three are branded for Marigold & Slate Events, a wedding planning studio that does not exist — an invented example, labeled as invented on every page, built to show what a real studio's own set would look like. They are the tools a planner hands to their own couples, with the planner's name on them rather than anyone else's. Unlike the products above, these are live: open them and use them.

All three carry their brand in a single fifteen-line block at the top of the file, so the name, monogram, colors and contact line on a real build are one edit — which is what makes a set of three affordable rather than a bespoke project three times over.