The $30B Market Nobody's Talking About

A founder wanted to build vertical SaaS for pest control. Instead of writing code, he got hired as a technician. What he discovered in 21 days should change how every indie hacker thinks about building for "boring" industries.

This story hit Hacker News yesterday with 248 upvotes and 110 comments. It's the kind of thing that makes you realize: the best product research isn't in Figma. It's in the field.

The Undercover Founder Playbook

The guy's background was white-collar sales consulting. He'd been selling into traditional industries and noticed something: companies stopped taking research calls. Too many requests. Too many founders trying to "disrupt" them without understanding the work.

So he did something radical. He applied to every pest control company in his area and got hired.

"I grew up helping out with our family plumbing business back home, so getting my hands dirty is no second nature."

Within 13 days, he earned his pest control license — a company record. The training manager never asked about the custom GPT he built from study books. Why would he? It could replace 25% of his job.

What He Found in the Field

Here's where it gets interesting. The company he joined was doing billions in revenue through a portfolio of local brands. Their tech stack?

The systems were bloated. The processes were manual. The techs had workarounds for everything. But nobody wanted to rock the boat.

This is the goldmine. Boring industries with broken tooling and zero motivation to fix it internally.

The $30k ARR Proof

After moving into a sales role, he closed $30k in ARR within 21 days. A $24k annual contract with a shopping center, plus smaller upsells. All sourced from a simple outbound campaign he built himself that same evening.

The internal quoting process almost killed the deal. Multiple signatures required. Another account created by corporate. For a $24k deal.

Meanwhile, top sales reps were doing $800k-$1.2M ARR with low churn. Their "training"? A ZoomInfo webinar. Their strategy? Drive around and show up in person.

Lessons for Indie Hackers

Here's why this matters for anyone building products:

1. Go Where the Problems Are

Research calls are drying up because founders are over-indexing on "discovery" without getting their hands dirty. If you want to build for a vertical, work in it first. Even a few weeks changes everything.

2. Boring ≠ Bad

Pest control. Plumbing. HVAC. Landscaping. These are $30B+ markets with fragmented players, legacy software, and zero innovation. The incumbents are slow. The customers are underserved. The margins are good.

3. Internal Resistance is the Real Moat

Employees don't push for better tools because there's no incentive. Their managers know the current systems are broken but won't authorize change. This creates a massive window for outsiders who actually understand the workflow.

4. Ship a GPT Before You Ship SaaS

This guy built a training GPT from scratch before writing a line of SaaS code. It passed the licensing exam in record time. Quick wins with AI tools build domain credibility and validate demand before you commit to a full product.

5. The Real Research is Physical

Ride-alongs are harder to get. In-person visits convert better. Showing up beats sending cold emails. If your research strategy doesn't involve leaving your desk, you're doing it wrong.

The Play That Makes Sense

He's now acquiring a small residential operator to build tooling around and prove the model. This is the right sequence:

1. Work in the industry — Understand the pain firsthand
2. Build quick tools — Validate with simple AI solutions
3. Acquire a small player — Get real customers and real data
4. Build the platform — Only after proving the model works

This is the opposite of how most indie hackers build. Most start with code. He started with a job application.

What You Should Do This Week

If you're looking for your next build, stop scrolling Twitter for ideas. Instead:

• Pick a blue-collar industry that bores you
• Find a local business and ask for a ride-along
• Document every broken process you see
• Build a quick solution with AI and test it
• Talk to 5 workers about what frustrates them

The best opportunities aren't in the spotlight. They're in the truck, with a broken fuel card and 10 apps nobody uses.