The problem
What was broken before AI
A lot of personal friction is too specific for off-the-shelf software. Andrew was dealing with hundreds of emails a day, school messages that mattered only occasionally, meetings with subtle interpersonal dynamics, uncertainty about what to wear, and relationship patterns that were hard to see clearly in the moment. None of those problems justified a big software project, but each one created small drag in daily life.
What changed
What the use case made possible
Claude Code made it possible for Andrew to build small tools around those exact problems. His email system filters and triages messages, then offers structured reply options. His parenting workflow pulls important school details out of email and turns them into reminders. His meeting agent looks for red flags in transcripts. His wardrobe system uses a spreadsheet of photographed clothes, the weather, image generation, and text messaging to suggest outfits. The result is a set of highly personal apps that would probably never exist as normal SaaS products.
Why this matters
Why this use case is worth studying
Andrew’s use case shows what happens when software becomes cheap enough to make for an audience of one. Instead of waiting for a company to build the perfect tool, he can turn a recurring annoyance into a small working app. Some of these tools are practical, some are strange, and some are deeply personal. Together they point to a world where more software is custom-built around the way one person actually lives.
Use this when
When this pattern applies
Use this pattern when a recurring annoyance in your life is too specific for normal software, but clear enough that a small custom tool could help. It works especially well when the input is already available somewhere — email, calendar, transcripts, photos, weather, spreadsheets, or messages — and the output is something simple you would actually use.
