Built here · 2 projects

Work nobody
hired me to do.

Products built and shipped in-house, start to finish. No brief, no client, nobody to blame. They exist because the stack has to get proven somewhere, and it is cheaper to find the traps on my own deadline than on yours.

See the client work

In-house projects

Will You Bury Me

Live · Product · Branding · Design · Systems · Web

Plain-language end-of-life logistics. Answer about forty questions, name one person, hand them a document they have agreed to hold.

A product built end to end in-house: brand, interface, questionnaire, encrypted storage, payments and the printed document. The legal research changed what it does rather than just what it says, and the result is a product that deliberately never holds a password.

Identity & Brand System · Systems & Automation

The Will You Bury Me homepage: the headline Will you bury me, with bury set in amber, above the line about the forty decisions and a Get the document button, beside a photograph of a younger and an older woman at a table with the document open between them.

Fourword Thinking

Live · Product · Design · Systems · Web

A daily game. Describe the prompt in exactly four words, then vote on the best ones.

A daily word game built end to end in-house: database, anonymous identity, bot protection, server-side moderation and a full test suite, running on a free tier for nothing a month.

Systems & Automation

The live Fourword Thinking game. A masthead reading FOURWORD slash THINKING with a countdown to the next prompt, then prompt number three, Saturday 26 September, marked open now with four answered. The headline asks the player to describe Being the last one awake, with the word last in blue. Below it the four empty answer slots, numbered 01 to 04, the first outlined in coral with the cursor waiting in it, a Lock it in button, and the line zero of four words. A stat row along the bottom reads three prompts posted, four words always, sixteen winning words, zero accepted excuses.

Why these are on a client-facing site

Because one person carrying a thing all the way to production is the whole proposition.

Every case study on this site says the work did not pass through a handoff. These are the version of that claim with nobody else in the room at all: the identity, the interface, the database, the tests and the deploy, decided and built by the same person. If that holds up without a client, it holds up with one.

Ready when you are

Make the outside
match the inside.

Send the site, the deck, or whatever is bothering you. You get back a one-page read on what your surfaces are signaling and the three things worth fixing first. No charge, no call.

Start a Snapshot

Work nobodyhired me to do.