祝融说。

In the previous chapter, we established a core premise: independent development is a business. And the starting point of any business is not a "brilliant idea," but an unmet market need.

The question is: we live in an era where it seems every need has already been met. Social — WeChat, Facebook; Office — Microsoft, Google Workspace; Entertainment — TikTok, Netflix... Look around, and everywhere there are tech giants with massive scale and virtually unlimited resources. As independent developers fighting "solo," do we still have a chance?

The answer is: not only do we have a chance, but opportunities are everywhere. They just aren't in the spotlight. They hide in the enormous shadows cast by the giants. These opportunities are what we call "market gaps."

"Gap thinking" is training yourself to abandon the fantasy of a head-on fight with the giants and, instead, to cultivate the ability to discover and extract value at their feet — even in the folds of their bodies. It is a survival wisdom, and the ultimate strategy of the small beating the large.

In this chapter, we will systematically learn how to discover, evaluate, and select these "gaps" in which you can make your living.

2.1 What Is a Market Gap? (Giants Won't Bother, Small Companies Can't Get It Right, Users Complain)

An ideal market gap for independent developers usually satisfies three golden conditions at the same time. It is like a perfect "treasure map marker" — when you find a place with all three characteristics, stop and survey it carefully.

Condition One: The Giant's Blind Spot

Tech giants like Google, Microsoft, and Apple are like aircraft carrier battle groups out at sea. They are immensely powerful, yet they have a fatal weakness: they cannot navigate the narrow inland rivers.

A market with $1 million in annual revenue is a paradise of financial freedom for independent developers like us. But for a company with hundreds of billions in annual revenue, that figure does not even amount to a rounding error on its financial statements. To capture that $1 million, they would need to marshal product managers, designers, engineers, legal, marketing — a whole array of resources — and the internal process alone could take half a year. The return on investment is so low it is almost absurd.

This is "the giant's dilemma": their very size dictates that they can only pursue markets at the "billion-dollar" level. Any demand that is not large enough will be ruthlessly ignored in their strategic planning meetings.

This "won't bother" attitude creates a vast living space for us. It manifests in several ways:

• Features too "niche": Within a massive piece of software, 1% of users urgently need a specific feature. For a product with 100 million users, that 1% is 1 million people — a huge market! But for the product itself, this feature might confuse the other 99% of users and add interface complexity. In the interest of overall simplicity, the giant chooses not to build it. For example, countless designers wish Figma had more powerful batch layer-renaming capabilities, yet Figma has long been reluctant to add it, giving rise to numerous third-party plugins.

• Serving "non-mainstream" workflows: Big-company software pursues the "greatest common denominator," serving the standard workflows of 80% of users. But there is always a 20% (lawyers, scientists, architects, independent podcasters, and so on) with very specific, vertical workflows. For example, a lawyer might want to generate legal citations matching a particular court's format in Word with one click. Microsoft will never build a built-in feature for this niche need, but a dedicated Word plugin could charge lawyers a premium price.

• "Politically incorrect" or compliance-risk tools: Certain tools — scrapers, Twitter auto-management tools — operate in gray zones. Big companies steer clear of them to avoid legal risk and protect their brand image. These tools may have real demand, but individual developers building them shoulder the same legal and platform-ban risks — "giants won't touch it" does not mean "you can safely touch it"; do an independent compliance assessment before entering.

• Strategically abandoned product lines: Remember Google Reader? This RSS reader, beloved by information seekers, was shut down because it did not fit Google's social strategy. Google's abandonment instantly released a huge, hungry market that went on to feed a generation of alternatives like Feedly and Inoreader. Keep an eye on the "graveyard" of big-company products — you might just pick up treasure.

How to discover "the giant's blind spot"? It is simple: become a power user of a giant's product, then ask yourself, "This product is good, but if it just had one more feature to solve my specific scenario, it would be perfect." That "one more feature" is very likely the gold mine the giant overlooked.

Condition Two: The Incumbent's Weakness

So you have found a gap the giant ignores. But when you search, you discover a few "cottage-industry" products already doing it. Should you give up?

Quite the opposite — this may be an even stronger positive signal! It proves the demand is real, and someone has already done the work of educating the market. What you need to do is act like a detective: evaluate these existing "small-shop" products and see whether they "can't get it right."

"Can't get it right" usually manifests in the following ways:

• Ugly design, bad experience (Bad UI/UX): This is the most common opportunity and the easiest for us to seize. Many early tools were built by pure engineers who solved the "does it exist or not" functional problem but failed miserably at aesthetics and smooth interaction. An interface that looks like it's from the '90s will scare off new users, let alone persuade them to enter their credit card numbers. All you need is a "visual remake" using modern design language (see Part 4) and a modern tech stack, and you can easily pull their users away.

• Stale features, no updates: You find a WordPress plugin or Chrome extension whose last update was three years ago. Its comment section is full of "Is the author still alive?" and "When will this bug be fixed?" This is practically handing the market to you. Build a functionally comparable version that is actively maintained and iterated, and you become the user's new choice.

• Single-platform only: A great Mac app with no Windows version. A powerful Chrome extension that Firefox users can't use. A Shopify-only store tool, while many merchants run on WooCommerce. These cross-platform "blank zones" are your opportunities.

• Outdated pricing model: A product still charges a one-time $99 purchase, yet the service it provides is ongoing (like data updates). You can adopt a more flexible SaaS subscription — say $9/month — which dramatically lowers the user's decision threshold while giving you recurring revenue.

• Zero marketing and SEO: The product itself may be decent, but its developer has no marketing sense at all. The site can't be found on Google, and it has no voice on social media. Apply a bit of SEO and content-marketing technique (see Part 5), and you can easily surpass it in traffic acquisition.

How to assess "the incumbent's weakness"? Go to their websites. Download and try their products. Ask yourself:

• "Does this website make me feel trust?"
• "Can I understand what it does within 30 seconds?"
• "Are there any moments during use that make me want to swear?"
• "If I were to build this, in what ways could I be clearly more than 10% better?"

If the answers are all yes, congratulations — you have found a competitor that can be "optimized away."

Condition Three: The User's Pain Signal

This is the most core and most real of the three conditions. The first two are based on your analysis; this one is a direct call from the market. Users' complaints are money waving at you.

You must become a "digital anthropologist," lurking where users gather and listening to their "anger levels." These places include but are not limited to:

• Reddit: The world's largest "complaint hub," and an indie developer's gold mine.

  • General complaints: In subreddits like /r/mildlyinfuriating or /r/rant, you see the various annoyances people encounter in everyday life.
  • Specific-software complaints: Go straight to the subreddit of the software you're interested in, like /r/excel, /r/notion, /r/figmaapp. The post titles are usually "How do I...?", "Is there a way to...?", "I wish [Software] had...". These are unpolished, raw demands.
  • "Looking for a tool" complaints: In career-related subreddits like /r/sysadmin, /r/marketing, /r/freelance, people often post, "Anyone know a tool that does X, Y, and Z?" If the replies offer no perfect answer, the post itself is a validated demand.

• Negative reviews on the App Store / Google Play / plugin stores: Find the leading app in your domain. Don't read the five-star reviews — filter for the one- and two-star ones. In these, users will tell you, in the harshest language, their most genuine pain points. A review that says "This app is great, except when I export to PDF the formatting breaks and ruins my afternoon's work!" — that is a demand worth its weight in gold.

• Twitter / X: Use advanced search with keyword combinations like "[Software Name]" sucks, "I hate" [Task], "annoying" "workflow". You'll see a steady stream of real-time, vivid complaints.

• Official product forums/communities: This is where a product's "hardcore fans" and "heavy detractors" gather. A feature request that is repeatedly raised, while the official response is always "we've noted your suggestion," is your opportunity.

The Golden Formula for Gap Thinking

Now we can sum up a golden formula for finding market gaps:

Market Gap = [a big company (e.g., Notion)]'s [a specific user group (e.g., academic researchers)] in [a specific scenario (e.g., managing literature citations)] confronting a problem that [the official product won't solve (won't bother)], [existing plugins handle poorly (can't get it right)], and [is repeatedly complained about on Reddit (users complain)].

When you can describe a problem clearly with this formula, you have found that X on the treasure map. Your task is no longer "what product should I build," but "what elegant solution can I provide for this clearly defined problem."

This is the decisive step from "self-indulgence" to "business." Next, we will explore how granular this "solution" should be.

2.2 Nano-Vertical: Why Build "a Plugin for Excel" Instead of "the Next Excel"?

In the previous section, we learned how to identify market gaps. Many developers who are starting their first venture, upon finding a gap, tend to get ambitious. They see users complaining about Excel's ugly charts, and their thought becomes: "I'll build a brand-new online spreadsheet tool that's more beautiful than Excel!"

This is a heroic dream, but also a suicidal mission that is almost certainly doomed.

Behind it lies a common thinking error: equating dissatisfaction with "a certain feature" with a rejection of the "entire product." Users complain that Excel's charts are ugly, but they cannot live without Excel's powerful calculation engine, its VBA ecosystem, and the collaboration habits already woven into their companies. What they want is not a "brand-new Excel," but a plugin that can "beautify Excel charts."

This is the core idea of the "nano-vertical" strategy: don't try to replace the platform; enhance it. Don't build your own ecosystem; parasitize the existing one.

Let's run a thorough strategic simulation of these two options: "build the next Excel" versus "build a plugin for Excel."

Option A: Build the "Next Excel"

1. Development cost and timeline: You would need a huge team and years of effort to barely replicate 70% of Excel's core features — spreadsheet calculations, function library, charts, pivot tables, VBA compatibility... This demands tens of millions of dollars in investment. And you are just one person.

2. User migration cost: How do you persuade a finance director who has worked in Excel for ten years to migrate a workflow built on countless accumulated templates and ingrained keyboard shortcuts over to your brand-new, untested platform? User inertia is the most powerful force of gravity in the world.

3. Brand and trust: Behind Excel stands Microsoft. When a user is handling a company's core financial data, would they put their faith in a century-old software giant, or in your unknown little product? Trust is the foundation of B2B payment, and it takes a long time to build.

4. Distribution and marketing: How do you let the world know your product exists? You would need to spend heavily on Google ads, run content marketing, attend industry trade shows... The cost of acquiring each user is staggering.

Conclusion: Choosing this path means facing a losing war. You are throwing your entire stake at the enemy's strongest fortress.

Option B: Build "a Plugin That Beautifies Excel Charts with One Click"

1. Development cost and timeline: You don't need to care about the underlying computation engine. You focus on one thing only: read Excel's chart data, re-render it with a modern charting library (like D3.js or ECharts), and offer rich customization options. This workload might take a skilled developer a few weeks to a month to ship an MVP.

2. User migration cost: Zero. Users don't need to leave the Excel environment they know well. Your plugin is just a new weapon in their toolbox. They can integrate your feature into their existing workflow seamlessly, at near-zero learning cost.

3. Brand and trust: You don't need users to hand over their core data. Your plugin runs locally, or only calls a cloud rendering service when needed. The user's trust threshold drops dramatically. You're not replacing the Excel they trust; you're helping them use it better.

4. Distribution and marketing:

   • Built-in traffic: You can list your plugin on Microsoft's Office Add-ins store. The enormous Office user base means substantial potential exposure, making the store itself a free traffic entry point — but note that category search competition and ranking mechanics exist inside the store too; being listed is not the same as getting traffic.
   • Precise targeting: Your target user profile is crystal clear — people who need beautiful charts in their reports and presentations (consultants, market analysts, students, and so on). You can reach them precisely through SEO or ads when they search "how to make beautiful charts in excel."
   • High willingness to pay: A consultant bidding for major contracts needs their client-facing PPT to look more professional. Would they pay $20 a month for a plugin that markedly improves their charts? For a fair share of consultants, yes — but this is an assumption about your target population to be validated with Chapter 4's methods, not something "beyond doubt."

Conclusion: Choosing this path means fighting a clever "guerrilla war." You avoid the giant's spearhead, parasitize its ecosystem, and draw nourishment from the tiny pain points it fails to serve.

The Infinite Extension of "Plugin Thinking"

"Build a plugin for Excel" is a way of thinking, not a specific technical form. Here, "Excel" can be any "platform-level product" with a massive user base and an open ecosystem. Your "plugin" could be:

• For Notion: a Chrome plugin that clips web content in one click and auto-tags it.
• For Shopify: an app that automatically sends a customized thank-you email after a purchase.
• For Figma: a plugin that batch-replaces all the colors in a design file.
• For Salesforce: a tool that automatically syncs a salesperson's LinkedIn profile to the customer information page.
• For Webflow: a paid component library containing 100 beautifully designed interactive components.
• For VSCode: an extension that helps developers auto-generate unit test code.

The common traits of these "nano" products:

1. Extremely focused problem: do only one thing, and do it exceptionally well.
2. Clear value proposition: within 30 seconds, the user understands exactly how much time you save them, or how much value you deliver.
3. Symbiosis with the host platform: the platform's success is your success. The more users the platform has, the more potential customers you have.

So set aside your grand "disrupt the world" narrative. In the early days of indie development, your goal is not to become the next Bill Gates, but to become the arms dealer who thrives by selling "shovels" to the gold rushers.

Find your "Excel," then forge for it the sharpest "Swiss Army knife."

But simply finding a gap and choosing a vertical is still not enough to build long-term competitiveness. In the AI era, we have gained a brand-new weapon that can change the rules of the game. This weapon lets you launch a "dimensionality reduction strike" within these gaps.

2.3 Dimensionality Reduction Strike: Use AI to Redo Old Software — 10x Efficiency Is the Strike

The term "dimensionality reduction strike" comes from the sci-fi novel The Three-Body Problem. It describes how an advanced civilization attacks a lower one: instead of competing with you on the same dimension, it directly reduces your dimension, making your laws of survival instantly invalid. For example, forcing a three-dimensional being into a two-dimensional flat picture.

In the business world, the concept applies just the same. When your solution is ten times better than existing ones on some key metric, you have achieved a "dimensionality reduction strike" on the market. That metric can be price, speed, convenience, or anything else users deeply care about.

In the AI era, the most powerful "dual-vector foil" in the hands of us indie developers is using large language models and generative AI to reshape the workflows of traditional software, achieving exponential gains in efficiency.

Many old, non-AI software products essentially provide a "toolkit": they let users complete a task through a series of complex, manual operations. AI-driven new software, by contrast, understands the user's "intent" and then "generates a result" in one click.

This is a fundamental paradigm shift. Let's feel the power of this strike through a few concrete "Before/After" cases.

Case One: From "Manual Editing" to "AI Transcription"

• Old Dimension: Adobe Audition / Audacity

  • Task: Edit a podcast recording, removing filler words (like "um," "uh"), long pauses, and misstated sentences.
  • Process: 1. Put on headphones and listen to the entire 60-minute recording from start to finish. 2. Every time you hear an "um," stop, precisely select that segment of the waveform with your mouse, and press delete. 3. Repeat this process hundreds of times. 4. For misstated sentences, perform more complex cuts and splices to make sure it sounds natural. 5. The whole process takes about 2–3 hours, tedious and highly error-prone.

• New Dimension: Descript

  • Task: Edit the same 60-minute podcast.
  • Process: 1. Drag the audio file into Descript. 2. Within minutes, AI automatically transcribes the audio into text and identifies all the filler words like "um" and "uh." 3. You edit the transcript like a Word document, deleting the filler words directly. Deleted text means the corresponding audio waveform is seamlessly cut out in an instant. 4. Want to delete an entire misstated sentence? Just select that text and delete it. 5. The whole process takes about 15 minutes — intuitive and precise.

Dimensionality reduction analysis: Descript didn't invent new audio-processing technology. It simply used AI's "speech-to-text" capability to reduce a complex operation grounded in "hearing and waveforms" to a simple operation grounded in "vision and text." For tasks like filler-word removal, the time cost of editing dropped by an order of magnitude (the 2-3 hours / 15 minutes above are illustrative numbers demonstrating that magnitude; specifics vary with recording length and content density), and tools of this kind reshaped the workflow of podcasters and video creators. That is a dimensionality reduction strike.

Case Two: From "Manual Screenshots" to "AI-Generated Tutorials"

• Old Dimension: Screenshot tool + Word/PPT

  • Task: Produce an operations guide for new employees on "how to submit an expense report."
  • Process: 1. Open the expense system and perform step one. 2. Capture the screen with a screenshot tool. 3. Open Word and paste the screenshot. 4. Use drawing tools to add arrows and boxes to the screenshot. 5. Write explanatory text below the screenshot. 6. Return to the expense system and perform step two. 7. Repeat the above process 20 times. 8. Finally, adjust the formatting and export to PDF. The whole process takes about 1–2 hours.

• New Dimension: Scribe / Tango

  • Task: Produce the same operations guide.
  • Process: 1. Click the Scribe plugin's "Start Recording" button in the browser. 2. Complete the entire expense process step by step, just as you normally would. 3. Click "Stop Recording." 4. AI automatically generates an illustrated online tutorial with step-by-step instructions. It automatically captures each of your clicks, takes the corresponding screenshots, and highlights the places you clicked. 5. You only need a few minutes to review and fine-tune the AI-generated text. 6. The whole process takes about 5 minutes.

Dimensionality reduction analysis: Tools like Scribe use AI's "process understanding and automated documentation" capability to reduce a tedious flow of "manual operation, screenshotting, annotating, and writing" into a frictionless experience of "you operate, AI records and generates." It doesn't provide a tool; it provides the result.

The AI Dimensionality Reduction Opportunity Discovery Matrix

How do you systematically look for such opportunities? Draw a simple matrix:

• X-axis: List the industries or groups you know well (e.g., marketing, law, real estate, freelancers, students, scientists...)
• Y-axis: List those repetitive, rule-based, yet cognitively demanding "old-world" tasks (e.g., data entry, report writing, content summarization, email sorting, contract review, market research, code debugging...)

Then start filling in the intersections of this matrix and ask yourself: "Can I use a single prompt or an AI workflow to make this X-group's Y-task ten times more efficient?"

• (Marketing, report writing) -> Can I build a tool that, given a few competitor URLs, automatically generates a monthly social media performance comparison report?
• (Legal, contract review) -> Can I build a Word plugin that, given a lease agreement, automatically highlights the "unfair terms" that work against the tenant?
• (Freelancers, data entry) -> Can I build a tool that auto-recognizes photos of invoices in various formats and converts them into a standardized Excel spreadsheet?

You'll find that almost every old, tedious software workflow can be "redone" with the help of AI.

Three principles for executing an AI dimensionality reduction strike:

1. Aim at the "process," not the "result": Don't try to create brand-new demand. Find the domains where users must endure an extremely painful "process" to obtain a certain "result" (such as a report). Your AI product should eliminate that painful process.

2. An order of magnitude is the threshold, not the goal: If your AI solution only improves efficiency by 20%, users may have no incentive to switch. But if it's an order of magnitude ("10x" here is magnitude rhetoric, meaning leaps like "from hours to minutes"), users will seriously consider abandoning the old tool. Only improvements of that order constitute a real "dimensionality reduction."

3. Don't just be an "API porter": A thin wrapper is easy to copy and could just as easily be "killed off" by OpenAI itself (see Chapter 5 on moat design). A true dimensionality reduction strike requires deeply integrating AI capabilities with a specific workflow, proprietary data, or a unique interaction design to create distinctive value.

Summary of Chapter 2:

We began with the macro-level "gap thinking," defining the ideal battlefield (giants won't bother, small companies can't get it right, users complain). Then we zoomed the lens in, clarified the "nano-vertical" tactic, and advocated "parasitism" over "confrontation." Finally, we equipped ourselves with the ultimate weapon — AI — and learned how to use "dimensionality reduction strikes" to gain an overwhelming advantage on the chosen battlefield.

Now you have the map to find gold and the tools to mine it. In the next part, we will go deep into how to move from these theories to practice: how to mine specific needs, how to validate them, and how to lock in your first paying users before you write a single line of code.