Vol 1: The AI Builder Opportunity

We’re Mike Molinet and Govind Kavaturi.

We’ve spent 15+ years building products and companies. Branch, then Thena, now building full-time again. We’ve shipped software, scaled teams, raised money, sold companies. We know how to build.

But here’s what we’ve learned matters most: knowing what to build.

Most builders never figure this out. They build impressive demos that nobody wants. They chase trends that fade. They solve problems that aren’t expensive enough to matter.

Right now, there’s a mega builder opportunity that most people are missing. It’s not about AI making you code faster. It’s about an entire category of problems that just became economically viable to solve.

This newsletter exists to show you that opportunity.

Every week, we interview one operator. VPs, Directors, team leads running functions at growing companies. We ask them what’s hard. What takes time. What’s broken. Then we publish what they told us and show you what to notice.

Not “here’s a problem, go build it.” But “here’s how to see the pattern of problems worth solving.”

This is Vol 1. Let’s start with what the builder opportunity actually is.

What Most Builders Get Wrong

Walk into any AI builder community right now and you’ll see the same thing:

People building image generators, calculators, guides, and checklist apps. Productivity tools for other builders. Demos that get 1,000 upvotes on Twitter and zero customers.

They’re optimizing for the wrong thing.

They think the opportunity is: “AI makes building faster, so build more things.”

That’s not the opportunity. That’s just noise.

The real opportunity is this:

For decades, there’s been a massive category of expensive, chronic problems inside companies that everyone knew existed but nobody could economically solve.

Not because the problems weren’t painful. But because building and running software businesses around them required too much. Infrastructure. Integrations. Maintenance. Support. Security. Compliance. Teams of 20+ people. Eighteen months to ship. Enough market size to justify venture funding.

The barrier wasn’t “can we build it?” The barrier was “can we run it as a business?”

Most problems weren’t big enough to justify starting a software company.

That constraint just disappeared.

Building in 2020 vs 2026

AI can handle complex, contextual logic. Modern infrastructure makes scaling trivial. Integration platforms connect everything. Small teams can operate software that used to require departments.

What changed isn’t that you can build faster. What changed is what’s now worth building at all.

There’s an entire long tail of expensive problems inside growing companies that just became viable. Problems that affect hundreds or thousands of companies, not millions. Problems that $3M-10M ARR businesses can be built around, not $100M+ venture outcomes.

The new game is different. Find expensive problems in growing companies. Build focused solutions to people. Sell. Scale without needing a massive org.

But you have to know how to see these problems. That’s the skill that matters.

What These Problems Look Like

Sarah Chen is VP of Product at a Series B SaaS company. 40-person org. 8 years in product leadership.

“I spend 8 hours every week translating the same information into different formats. Sales needs slides. Engineering needs Jira tickets. My CEO needs a memo. Same information, three formats, two hours gone. I’m not the VP of Product. I’m the VP of Translation.”

Three examples:

• Last quarter, Sales committed a feature to a $500K deal. Engineering found a dependency. Feature slipped to Q2. Sarah updated everything: Productboard, Slack, email, standups. Three days later, Sales asks: “Feature X is still Q1, right?”
• Three new PMs in six months. 5+ years experience each. Still took three months to be productive. Last month one repeated a mistake from 18 months ago. The learning was documented. Nobody knew it existed. Sarah estimates 40% of their first three months is rediscovering what the org already knows. That’s $150K in wasted salary.
• Someone asks: “What’s the status of Feature X?” Sarah checks six tools. Twenty minutes later she has fragments. Engineering says 60% done. Design says waiting on feedback. Product says open question in Slack. She does this 30 times a week.

The Pattern

Sarah’s three problems are one problem: information architecture collapses at scale.

At 10 people, context is ambient. At 40 people, it’s scattered across tools, docs, conversations, and heads. The org has information but no intelligent way to retrieve or translate it.

Sarah isn’t writing status updates. She’s being human middleware between systems that can’t talk.

Three years ago, fixing this meant 20 engineers and 18 months. Today, 2-3 people can build it in 6 weeks. AI handles contextual complexity. Modern infrastructure makes scaling cheap. Integration platforms connect everything.

The technical constraint is gone.

But most builders would still build the wrong thing. They’d hear “8 hours on status updates” and build a better status update tool.

Wrong. The problem is information architecture failing at scale. Status updates are a symptom.

This is the builder opportunity: Systems breaking under their own weight. Humans becoming glue. Expensive, chronic work that AI can now eliminate.

Sarah isn’t unique. Sales ops, customer success, finance, marketing - same pattern everywhere. Information exists. Systems don’t communicate. Humans translate.

Why Most Builders Miss It

Most builders never see this because they’re not talking to the right people.

They’re in builder communities. They read about other builders. They build for other builders.

The opportunities aren’t in builder land. They’re in operator land.

When you talk to an operator for an hour and actually listen, you hear specific signals:

“I spend X hours a week on...” “The information exists, but...” “Everyone asks me the same question...” “New people take forever to learn...” “It’s in five different places...” “The tools don’t talk to each other...”

These phrases mean someone is being middleware between systems. That someone is expensive. That work doesn’t scale.

That’s your signal.

You’re not looking for “I wish I had a tool for X.”

You’re looking for “I spend my time doing work that shouldn’t require a human.”

That’s the difference between a feature request and a real opportunity.

The builders who win won’t be the ones building faster. They’ll be the ones who know where to look.

What This Newsletter Is

Every week, we interview one operator. We ask them what’s hard about their job. Where time disappears. What creates friction. What they’ve tried to fix and why it didn’t work.

Then we publish what they told us. Not sanitized. Not polished. Just honest conversation about where work breaks down.

This week was Sarah Chen, VP of Product.

Next week will be someone else. Different function. Different company. Same underlying pattern: systems breaking under their own weight, humans becoming the glue.

Over 50 weeks, you’ll develop intuition for what expensive problems look like. Not just “here’s a problem” but “here’s how to recognize this category of problem across different contexts.”

That’s the skill that matters. Learning to see what’s worth building.

We’re also building a community where operators and builders can connect. Where builders learn how to have discovery conversations. Where operators find solutions to problems they’re living with.

The opportunity is massive. Most builders won’t see it because they’re not talking to the right people.

This newsletter is how you learn to see it.

Join Us

If you’re a builder:

Stop building demos. Stop chasing trends. Start talking to operators.

The builders who see this opportunity will own the next five years. The ones who don’t will keep building things nobody wants.

We’re interviewing operators every week. Join our community. Learn how to have these conversations yourself. Get direct access to people who know where systems are breaking.

If you’re an operator:

What takes 3+ hours of your week that feels like it shouldn’t require a human? What have you tried to fix that didn’t work?

Reply with one sentence. We’ll follow up. If we interview you, we’ll feature your insights here. Anonymous if you prefer.

The builder opportunity is real. It’s happening now. Most people are missing it.

Don’t be one of them.

Next week: Vol 2, another operator, another function, another pattern.

Forward this to any builder who’s trying to figure out what to build.

Mike & Govind

The Builder Weekly: Operational intelligence for builders.