How to Use Claude Code for Real Problems, Not Just App Ideas

*Claude Code gets framed as an app-building tool. Most project lists that come up when you search prove it: personal website, expense tracker, SaaS with Stripe. Those are real builds. They're not the builds most people actually need. This is a different list with 19 starting points from daily work, personal life, and family time, each mapped to four levels of build. *

I wrote an article earlier this year about building apps with Claude Code. 15 projects, tiered by difficulty, with the exact first prompt for each.

The most common reply wasn't "great, I'll try Project 4."

It was some version of:

• *"I don't actually want to build an app. I just want to fix the stuff that's eating my time."
• "I have Claude Code now, but I don't really know how to or want to do code"*

Tell me if this sounds familiar.

You have Claude Code open. You've run through the basics. Maybe you even shipped something small. And now you're looking at a list of Claude Code project ideas. Nothing on that list matches the friction you actually have right now.

The contract you need to understand before tomorrow's meeting. The survey responses nobody has had time to read. The family plan you need to update but never get around.

None of those are apps.

All of them are builds.

That's what I felt too since building with Claude Code in 2024. (At that time, Claude Code was Anthropic's terminal-based coding tool: plain-English instructions, runs on your machine, no prior coding required.)

My first project was a local photo search: 30 minutes, 12,000 images now searchable by description, nothing uploaded anywhere. I shipped it, then retired it. I built it because I was spending 20 minutes a week digging through folders. That problem is gone.

The Gmail digest I built later: 918 emails processed in 40 seconds, before I open my inbox. Did not make to an app. But stayed as a workflow, which I later turned it into a cluster of workflows with multi-account gmail MCP.

The thing I learned: any friction point is a build.

That build to friction could be:

• A Task you do once.
• A Workflow that runs every time.
• An App you can hand to someone.
• An Agent that runs without you.

You don't have to go all the way. Instead, you pick the level that actually solves the problem.

The previous article was about building apps. This article is about everything between "I opened Claude Code" and "I shipped a product."

We'll map out 19 friction points from real daily work, personal life, and family time. Each one shown across these four possible levels.