The goldmine is the workflow

Everyone wants to find the next AI goldmine.

So they ask the same questions. What should I build? What pain point is hot right now? What prompt or system is someone else using? What did Lovable, Legora, or Cursor see before everyone else?

I think those are the wrong questions.

The best AI products are usually not born from clever ideas. They are born from workflows that already exist — slow, repetitive, manual systems that thousands of people in the same domain are already running every week.

The product is not the idea.

The product is the compression of the workflow.

What the winners actually saw

Pick any AI-era company you'd want to have built. Lovable. Legora. Cursor. The interesting part isn't the idea itself — it's the workflow each one chose to compress. A workflow that everyone in a domain already did, slowly and manually, every week.

Lovable didn't invent the desire to ship software without coding. That workflow had existed for years across no-code tools, templates, and developer handoffs. Lovable made it feel dramatically more direct.

Legora didn't invent contract review. Law firms were already reviewing, comparing, summarizing, and extracting terms from documents every week. The product wasn't the insight. The shape of the workflow was.

Cursor didn't invent the workflow of getting help rewriting code. Developers were already moving code back and forth between editors and AI chat tools. Cursor compressed that into the editor.

The pattern in every one of them is the same. They found a workflow so universal that everyone in the target domain was doing it the same broken way — and ran it with less friction. The product was the consequence of that mapping, not the start of it.

The mistake is hunting for clever ideas. The win is seeing a universal workflow clearly enough to describe it.

Why most people can't see the workflows they're standing on

Here's the irony. Everyone wants to build the next Lovable. Almost nobody asks the question that made Lovable work: what's the workflow I'm closest to that's broken the same way for everyone who does it?

You see workflows nobody else sees. You know which workaround your team silently tolerates. You feel which 40-minute Tuesday task makes you want to throw your laptop. The advantage isn't your unique situation — it's that you can see clearly something hundreds of other people in your role are doing badly, just out of sight from each other. They're too busy doing it to notice the shape.

The gap between the workflow you can describe and the people stuck doing it is the company.

How to actually find one

If you want to find a workflow worth compressing, look at your own week — not Twitter, not a prompt library, not an /r/Entrepreneur thread.

Five working days. Every time you start a task, jot it down. Title and rough duration. Don't categorize. Don't judge. Don't try to remember at the end of the day — capture in real time or you'll lie to yourself.

By Friday, sort the list. Most things fall into four buckets:

• Keep manual — work where being human is the point.
• Eliminate — work that shouldn't exist at all. The standup that could be a Slack thread. The weekly report nobody opens.
• Hand to a person — work that isn't your highest leverage. Inbox triage, formatting, light research.
• Hand to AI — drafts, summaries, repetitive lookups, light code. Anything where a human's fingerprints don't change the outcome.

Most people are shocked by what shows up where. The "automate this" pile is usually smaller than expected. The "why am I doing this at all" pile is usually larger.

The Hand-to-AI pile is where solo time savings live. The Eliminate pile is where consulting opportunities live. The Hand-to-AI pile across hundreds of people in the same role is where the product is.

The trap

The most common — and most expensive — mistake is compressing a workflow that shouldn't exist.

If a report takes you an hour a week and you build an AI workflow that produces it in two minutes, you feel like a hero. But if nobody reads the report, you've just built a faster way to waste two minutes a week.

The same trap kills SaaS ideas. "Let's build something that automates the weekly competitor report" — except nobody on your team has read one in 18 months. Killing the workflow is always cheaper than compressing it. Killing the product idea is always cheaper than building it.

Before anything moves into the build-it bucket, ask: would the world notice if this stopped happening? If the honest answer is no, eliminate. Don't optimize. Don't ship.

The actual move

Stop looking for the next goldmine.

Look for the workflow that already runs every Monday:

• the spreadsheet someone rebuilds,
• the document someone reviews,
• the research someone repeats,
• the decision someone makes from the same messy inputs again and again.

If it happens often enough, hurts enough, and looks similar across enough people, it isn't just a task.

It's a product waiting to be compressed.