You Don’t Need a Great Idea. You Need a Great Problem.

Most people think entrepreneurship starts with an idea.

It does not.

Every venture that has ever mattered started with something much simpler: someone paying close attention to the world around them, noticing where things were broken, slow, or annoying, and deciding to care.

The idea came later. The problem came first.

✦ ✦ ✦

The Story Nobody Tells You About Great Companies

Let me share three stories. None of them involve garage mythology or billion-dollar exits. They are small, relatable, and more instructive because of it.

Basecamp In 2003, a small web design shop in Chicago called 37signals needed a better way to manage client projects. Emails were piling up. Files were scattered. Deadlines were getting missed. They looked around, could not find a tool that did what they needed without doing fifty things they did not, and built their own. They called it Basecamp. Over the next decade, it grew into one of the most successful software products in history without taking a single dollar of outside funding. Jason Fried has said plainly: we built it because we needed it. Full stop.

Calendly A few years later, a sales software rep named Tope Awotona kept running into the same problem at work. Scheduling a meeting with a client meant a painful back-and-forth of emails. Three suggestions, two counter-proposals, a rescheduled confirmation, and somewhere in there, a connection that should have taken two minutes had eaten up twenty. He built a simple tool to let people pick an open slot on his calendar without the email chain. He called it Calendly. Today it is used by millions.

GatherContent Around the same time, a digital agency in London kept hitting a specific wall on every project they took on: getting content from clients. It always arrived late, in the wrong format, or not at all. Word documents. Spreadsheet attachments. Email threads buried six levels deep. There was no good system, so the founders built one, calling it GatherContent. It was not a flash of brilliance. It was a frustration with an obvious pattern they kept seeing in their own work.

Not one of these ideas was born in a brainstorming session. Each one was born the moment someone stopped and said: why is this so hard?

✦ ✦ ✦

The Shift That Changes Everything

Here is the thing that makes this so exciting right now, in 2026, and the reason I believe we are at an extraordinary moment for founders.

For most of history, noticing a problem was not enough. You also needed capital to build the solution. You needed technical co-founders if you were not technical. You needed a network to reach your first customers. The gap between identifying a problem and actually solving it was enormous, and most people fell into it.

That gap is closing fast.

AI has not changed what it means to find a great problem. It has changed what happens next. If you can see the friction, you can now move from observation to working prototype in days rather than years. You can test a solution with real people before spending more than a few weeks on it. You can iterate based on feedback and build something that genuinely helps people, at a scale that was not available to most founders a decade ago.

The constraint has shifted. It used to be: can you build it? That question is nearly solved. The question that matters now is the same one it has always been: can you see it?

✦ ✦ ✦

What a Problem Detective Actually Does

Most people move through their day trying to fix friction as quickly as possible and move on. A problem detective does the opposite.

They slow down at the friction.

They notice when something takes longer than it should. They catch themselves saying “this is ridiculous” and pause to understand why. They ask whether other people hit the same wall. They treat annoyance as a signal rather than a nuisance.

You do not need a special background to do this. You do not need to work in tech or have built a company before. You just need to start paying attention in a different way.

🔎

The Friction Questions Where do you lose time in your week? Where do the workarounds live? What process at your job do you secretly know is broken? What did you search for online, not find, and give up on? What did you help a friend figure out that you both agreed should be easier? Every one of those moments is a candidate.

✦ ✦ ✦

The Best Ideas Were Never About Ideas

I have been involved in building and launching ventures for a long time. The pattern that has held up across every one of them, and across every founder story I find credible, is this: the best ideas were not the result of clever ideation. They were the result of sustained attention to a specific problem.

When the founder was deeply familiar with the problem, the solution almost built itself. When the founder was working backward from what they thought would be impressive or lucrative, the product usually drifted.

Serving people well starts with understanding what is actually getting in their way. That is not a product insight. It is a human one.

✦ ✦ ✦

A Practical Starting Point

We are building a tool at Plujo that takes this process seriously. It will walk you through a structured conversation: where you spend your time, where you see friction, what you know well, what other people keep asking you about. It is designed to help you surface the problems you are closest to, because proximity is an edge, not a liability.

But you do not need to wait for the tool. You can start today.

The exercise is simple. For the next week, keep a running note on your phone. Every time you feel friction, write it down. Not the solution. Just the friction. What was slow. What was clunky. What required more effort than the result was worth.

By the end of the week, you will have a list worth looking at.

In Part 2, we will talk about why once you have found a great problem, the idea you reach for first is almost certainly the wrong one, and what to do instead.