How to Turn a Problem You Have Into a Business

Some of the best businesses never started as a business idea at all. They started as someone's own problem, solved for themselves first, out of pure necessity — and only became a company once other people said "wait, can I have that too?"

If you're staring at a blank page trying to invent a market from scratch, you're skipping the easiest source of ideas you have: your own life, right now, today.

Why your own problems are underrated raw material

When you build for a problem you actually have, you already know things a market researcher would spend weeks trying to learn — what the workaround currently feels like, what a real solution would actually need to do, and whether the pain is a mild annoyance or something you'd genuinely pay to make disappear. That's not a shortcut around market research. It's a head start most founders never get.

You also skip the trap that kills a lot of first-time founders: building for an imagined customer you've never actually talked to, because you're already fluent in exactly what this customer needs.

How to find the problem worth building

Start with friction, not inspiration. What do you work around every week instead of solving? What have you paid for that almost worked but didn't quite? What do you explain to other people so often that you've started keeping a template for it? What's the thing you complain about that, if you're honest, you've complained about for over a year without it changing?

Small, specific, recurring friction is far more promising than a big, vague frustration. "I hate how disorganized my finances are" is too broad to build. "I keep losing track of which subscriptions I actually still use" is specific enough to be a real product.

The test that tells you if it's just you

Not every personal annoyance is a market. Before you build anything, ask five people outside your immediate circle whether they deal with the same friction, and listen for how they describe it. If they light up describing their own version of the same problem, unprompted, that's a real signal. If they shrug, that's useful information too — it might still be worth solving for yourself, just not necessarily worth building a company around yet.

Using AI to go from personal fix to real product

This is where the timeline compresses dramatically. What used to take a personal spreadsheet, a workaround, and years of quietly refining it before anyone else saw it can now move from "the thing I built for myself" to "the thing five people are using" in weeks. Claude or Claude Code can turn your personal workaround into a real, shareable version. Perplexity can quickly tell you whether someone's already built this well, and if so, where they're falling short. And once you're past the personal-tool stage, that's exactly the moment to bring the idea to Cameron and start treating it like the business it might actually become — validating it properly, not just assuming your own excitement will carry it.

The advantage that compounds

Founders solving their own problem have a durability advantage over founders chasing an opportunity they read about somewhere. You'll keep noticing what's broken because you're still living inside the problem, long after the initial excitement of "I should build this" fades for everyone else. That's not a small edge. It's often the difference between a founder who quits at month four and one who's still iterating, unbothered, at month fourteen.

---

Already have a version of this you built for yourself? Bring it to Cameron and find out whether it's ready to become something real. Start for free.