Experiments

How PurposeKit works.

Twelve services, one codebase, and nobody on staff who writes code. Pick a story to watch what happens when Steve ships an update, or when someone at a charity presses the button on a tool.

Stevethe ideaClaude Codewrites the codeGitHubkeeps every versionVercel buildbuilds the siteVercelserves the siteA visitorsomeone at a charityCloudflarethe address bookSupabaseaccounts and dataAnthropic APIClaude answersResendsends emailPostHogwhat gets usedSentrywhat breaks
  • Building
  • Shipping
  • Running
  • Watching
  • Only sometimes

Start here

Pick a story above

Each one follows a single action through the system, one wire at a time. Or tap any box on the map to see what it is.

How it was built

By conversation. Steve describes what he wants; Claude Code writes it, checks it and ships it. What keeps months of separate sessions pulling in one direction is a set of plain-English rule files in the repo, read at the start of every session: the closest thing it has to a memory.

445commits to main
72AI routes on the server
34database migrations
173,000lines of TypeScript
1repository, database and host
~99tools for charities

Commits to main each month, 2026

November is up to the 11th. The quiet summer is real: the site sat mostly still between the first tools and the games.

  1. 23 AprAn empty Next.js app, then the whole platform shell in a day: database, sign-in, error alarms, analytics, account deletion.
  2. 27 AprThe first real tool: the Journey Map.
  3. 1 MayThe design system: one stylesheet for the whole look.
  4. 10 JulDymaxion Rider, the first game, hidden at an unlisted address.
  5. 4 SepThe Top 1,000 fundraising charities explorer.
  6. 11 SepThe Experiments page opens, with Bunker.
  7. 6 OctSnowline, the mountain-building game.
  8. 30 OctFonts moved onto the site itself after a font download broke a deploy.
  9. 1 NovThe course starts sending its own emails.
  10. 7 NovMurmuration: a thousand starlings.
Why one of everything? One repository, one database, one host. With no developer on staff, every extra moving part is something that can break with nobody to notice. Keeping it to one of each means one place to look when something goes wrong.