Conversor IAE CNAE: Why I Chose This Niche (and How I Validated the Idea in 48 Hours)

The Story: A Problem Nobody Was Solving

It started with a simple question on Twitter: "Does anyone know how to convert an IAE code to CNAE without losing your mind?"

The answer was chaos. People sharing broken links, others saying to go to a tax advisor, some suggesting to call the tax authority. Nobody had a clear tool.

That's when I knew I'd found something.

Quick Validation: The 48-Hour Method

I didn't want to waste time speculating. I applied a simple process:

1. Search Volume Check

First, Google Keyword Planner. I needed to confirm people were actually searching for this. Terms like "conversor IAE CNAE", "código IAE", "código CNAE" showed consistent searches. I didn't need exact numbers to know there was real demand.

2. Competition Analysis (The Key Point)

This was the surprise: searching Google, GitHub, Spanish SEO tools. The result: practically nobody offered a direct, free solution.

Normally this would be a red flag ("why isn't anyone doing this?"). But in this case, the answer was obvious: the niche is too specific to Spain. Tax advisors prefer clients to call. Big platforms don't see ROI in such a small niche.

It was the perfect scenario: high search volume + zero competition = opportunity.

3. Direct Validation

I posted a simple tweet: "I'm building a free IAE to CNAE converter. Interested?"

Immediate responses. People asking when it would be ready. Freelancers requesting specific features.

That was enough. I had validation.

The Build: How I Went From Idea to MVP

My stack was deliberate:

**Next.js 15.5.4** + **React 19.1.0**: Because I needed something fast, scalable, and that worked in the browser.
**TypeScript**: 93% of the codebase. Not a whim, it's a requirement to maintain quality in a project others might use.
**Supabase + PostgreSQL 17.6.1**: Database with 2,247 official codes (1,187 IAE + 1,060 CNAE). I needed something reliable that scales without issues.
**Vercel**: Automatic deployment. Every commit goes to production in seconds.

The Dataset: The Real Work

The tool is useful because it has accurate data. I collected and structured 2,247 official codes. This wasn't trivial, but it wasn't complicated either. It was tedious and necessary.

That's the kind of work that differentiates a real project from a prototype.

Design Decisions That Mattered

Advanced Search

It's not a simple converter. It's a search engine. Users don't always know exactly which code they're looking for. They needed to:

Search by description
Filter by activity type
See the relationship between IAE and CNAE

This required thinking about UX, not just technical functionality.

PDF Export

Many freelancers need to take the code to a tax advisor or the tax authority. I added the ability to export to PDF using `html2canvas-pro` and `jspdf`. Small detail, big difference in usability.

Analytics and Monitoring

I used Microsoft Clarity and Vercel Analytics. Not to obsess over metrics, but to understand how people use the tool. Where do they get lost? What searches are most common?

This guides future iterations.

The Most Important Learning

What I really learned wasn't technical. It was this:

Small niches are powerful because they have unsolved problems.

You don't need millions of users. You need users with a real, specific problem. The millions of freelancers in Spain need to convert IAE codes to CNAE. That's a real market.

Most entrepreneurs look for big niches because they think more market = more opportunity. But more market also means more competition.

I chose the opposite: small market, zero competition, real problem.

Why This Approach Works

1. Low Entry Cost

I didn't need funding. I built this in my spare time with tools I already knew. The server, database, deployment: all affordable and scalable.

2. Fast Validation

48 hours of research. That was enough to confirm it was worth building.

3. Public Iteration

My recent commits (January 2026) show the kind of work I do:

AdSense optimizations
TypeScript fixes
Mobile navigation improvements

It's not sexy, but it's real. It's the work that keeps a project alive.

What Didn't Work (And What Did)

Didn't Work:

Thinking the name "Conversor IAE CNAE" would be enough. I needed SEO.
Assuming users would find the tool on their own. I needed marketing.

Did Work:

Building something specific for a specific problem.
Using modern technology (Next.js, Supabase) that scales without friction.
Iterating in public and collecting feedback.
Keeping code clean (93% TypeScript, no technical debt).

What's Next

Now that the MVP exists and works, the question is: how do I monetize without breaking trust?

The tool is free. But there's room for complementary services:

Advice on code changes
Integration with management software
Exportable data for businesses

But that comes later. First, I need people to use it and love it.

Takeaway: How to Validate Your Next Idea

1. Look for the magic triangle: High search volume + low competition + real problem 2. Validate in 48 hours: You don't need months of research. You need quick confirmation. 3. Build with technology you know: This isn't the time to learn a new framework. 4. Iterate in public: Real feedback beats any analysis. 5. Maintain quality: 93% TypeScript isn't a whim. It's the difference between a project and a toy.

The Conversor IAE CNAE niche will probably never be a unicorn. But it's profitable, it's useful, and it's mine.

That's enough.

---

Do you have an idea you think has potential but don't know how to validate? Use this method. 48 hours. Search + competition + direct feedback. If it passes all three tests, build it.