← Resources · Field Guide · Startup Ideas Oct 19, 2026
Five Startups That Grow With AI

Build What Agents Need

Five businesses I'd look at building because of where AI agents are going. Each one gets more valuable as the models get smarter, not less. For every idea: who pays, what I'd build first, how I'd get customers, and what could kill it.

The Short Version

Everybody's trying to build the next great AI app. I'd rather build the things all those AI apps are going to need: memory, security, clean data, risk checks and data supply. Start with the test.

Model.Drop.Test✣

A new model drops next month. Does your business get better or worse?

01 · Portable AI memoryBetter
02 · Agent security auditsBetter
03 · Agent-ready dataBetter
04 · AI insurance evaluationsBetter
05 · Industry data marketplaceBetter
A thin wrapper on today's modelWorse
5
Businesses
2
In The Video
1
Question To Ask Of Yours
Picked One Yet?

An Idea Is Step One. Customers Are The Rest.

Five ideas is the easy part. Picking one, testing it before you build, and getting the first person to pay is where most founders stall. That's the part I want to help you with.

The Solo Founder Lab · Opening Soon

I'm building a place where you take an idea like these from a list to a business on your own, with a CTO who's built two seven-figure software companies checking your thinking every week.

Lab.exeWaitlist Open

Test It Before You Build It.

  • Weekly CTO office hours. Live, hot-seat style. Bring the idea and pressure-test it.
  • The Decision Desk. Post the call you're stuck on. I answer the top three on video every week.
  • The First Dollar Wall. Every Founder's first paying customer gets posted, celebrated and pinned.
  • The 30-Day Launch Plan. Validate, plan, build and launch, one week at a time. Members only.

Free to join the waitlist. Opens at $49/mo, and the price goes up as seats fill, so first in pays the least.

The Test

One Question At A Dinner Table

Where This Came From

Greg Isenberg spent 48 hours in San Francisco with AI founders, data labs and execs, and posted what he heard. At one dinner, someone asked the table: "If a new model drops next month, does your company get better or worse?" Half the table went quiet.

Why It's The Right Question

A lot of AI startups are selling a model's current weakness. The product exists because today's model can't quite do the job alone, so the startup fills the gap with prompts, workflow and a nicer screen. Every model release closes part of that gap. Those companies are betting against AI getting better.

The other kind of business has customers whose needs grow as AI gets more capable. More agents doing more real work means more need for memory, security, clean data, risk checks and specialized data. Smarter models make those customers need you more.

To Be Honest About It

None of these five is immune. Memory could become a built-in standard. Security testing could become a platform feature. The claim isn't that they can't be replaced. It's that their customers' need grows as the models improve, and that's where I'd want to be building.

Gets.Worse▼

Sells a gap in today's model.

  • A prompt and a nice UI around something the next model does natively.
  • Value lives in the workaround, not the customer.
  • Easy to clone. People are rebuilding whole apps with agents now.
Gets.Better▲

Sells what agents need to work.

  • Infrastructure, data, security and trust around the model.
  • Treats the model as swappable. Use whichever one is best this month.
  • Owns something a model can't rebuild: data, relationships, a map of messy systems.
Scorecard

All Five At A Glance

Ordered the way I'd talk about them, not by how fast they make money. If you want revenue this quarter, start with 03. If you want the biggest swing, look at 01.

#IdeaWhat You SellWho Pays FirstFirst RevenueBiggest Risk
01Portable AI memoryA memory layer you own, readable by any agent.People and small teams using three or more AI tools.MediumProviders lock memory in, or make it a free standard.
02Agent security auditsFixed-price audits, then a scanner that runs on every change.B2B software companies shipping agents or MCP servers.FastPlatforms bundle guardrails. Services don't scale.
03Agent-ready dataCleanup that makes one department's data usable by agents.Mid-sized companies with an AI mandate and years of mess.FastestConsulting margins. Smarter models tolerate mess.
04AI insurance evaluationsThe tests insurers use to decide which agents they'll cover.A specialist broker that wants to write AI policies.SlowTiming. The market may be years away.
05Industry data marketplaceLicensed, permissioned industry data, sold to AI companies.Vertical AI startups and labs that need domain data.MediumData rights and privacy law. Two cold sides.

No prices or market sizes here on purpose. These markets are moving monthly. Talk to ten buyers before you trust any number, including one I'd give you.

Idea 01 · In The Video

Notion, But For Agents

Portable AI Memory

A memory layer that you own and every AI can use. Your preferences, projects, people and voice live in one place, and you take them with you when a better model comes out.

The Opportunity

Someone running a big consumer company told Greg the next fight is over memory: the AI that remembers the most about you wins. That's great for the provider. For you it's lock-in. The more your AI knows about you, the more painful it is to switch.

At the same time, the best teams treat models as swappable. They route one job to one model and another job to a cheaper one. Those two trends collide. People want to switch models, and memory is what keeps them from doing it. Someone should own the memory layer that sits outside any one provider.

What I'd Build First
  • An MCP server over a memory store, so Claude, ChatGPT, Cursor and whatever ships next can all read from and write to the same memory.
  • Typed memories, not one big blob. Preferences, people, projects, decisions and writing voice, each with a source and a date.
  • An importer that pulls in what your assistants already know about you, plus your notes and docs.
  • A review screen for humans. See what every agent learned about you, fix it, delete it, and choose which agents see what.
  • Agent-first APIs. Fast search, fetch by type, write with provenance. It shouldn't look or behave like a document editor.
How I'd Get Customers

Developers first. Open-source the MCP server, charge for hosted sync, and share it wherever people trade Claude Code and agent setups. Anyone hand-maintaining CLAUDE.md files and custom instructions across three tools is already doing this job manually.

Spec.Sheet01
Who PaysPower users and small teams who use several AI tools and are tired of re-explaining themselves. Later, companies that want memory to survive a vendor switch.
The WedgeAn MCP server plus a review screen for people who use three or more AI tools.
Price ShapeFree and local. Paid for sync, teams and permissions.
Why.It.Grows▲

Smarter agents do more of your work across more tools, so there's more worth remembering and more agents that need the same context. Better models also get better at deciding what to save and what to recall, which improves your product for free.

What Could Kill It

The providers want memory to be their moat, so they may make it hard to get out. Or the opposite happens: an open memory standard arrives, everyone supports it, and you're a feature. And you'd be holding the most sensitive data a person has. Encrypt it, offer self-hosting, and be boring about security from day one.

Idea 02 · In The Video

Every Agent Is A New Door

Agent Security Audits

Test AI agents, and the software they connect to, for the ways they can be tricked or overreach. Start as a service. Turn what repeats into a scanner.

The Opportunity

We're giving agents our email, our databases, our accounting and our customer records. Every company Greg talked to wants to pipe its internal data into one place and expose it to agents through MCP. As he put it, every agent with access to your systems is a new door into your company, and a lot of those doors were left open.

As screens disappear and agents become the main user of software, the attack surface moves from login forms to prompts, tool permissions and any text an agent reads. OWASP already lists prompt injection and excessive agency in its Top 10 for LLM applications. Most teams shipping agents have nobody who has tested for either.

What I'd Build First
  • A fixed-price audit. Two weeks, a plain-English report, and a retest after fixes.
  • Prompt injection tests through every input the agent reads: emails, web pages, documents, support tickets.
  • A permissions review of every MCP tool and API key. Does the agent have access it never uses?
  • Data leak and dangerous-action tests. Can it be talked into revealing records, sending money, deleting things?
  • Then the product: a scanner that reruns those tests in CI whenever a prompt or tool changes.
How I'd Get Customers

Let enterprise security questionnaires do the selling. B2B companies adding AI features are starting to get asked how they prevent prompt injection, and most don't have an answer. Publish a free checklist, offer the audit at a fixed price, and partner with SOC 2 firms whose clients are asking the same question.

Spec.Sheet02
Who PaysCTOs and security leads at software companies shipping agents or MCP servers, and companies giving internal agents real access.
The WedgeA fixed-price audit for B2B SaaS teams that just got the AI question on a security review.
Price ShapePer audit, then a subscription for continuous scanning.
Why.It.Grows▲

More capable agents get more permissions and more autonomy, which raises the cost of every mistake. Smarter models also make better attackers, and better testers. The thing you protect keeps getting bigger.

What Could Kill It

Security is crowded and runs on trust, and the big platforms will ship guardrails as features. Your edge is being independent and specific. Services don't scale like software, so plan the move from audits to a scanner early. And never sell "safe." Sell "tested," with the evidence.

Idea 03 · Bonus

The Fastest To Get Paid

Agent-Ready Data

Clean up and organize a company's data so its agents can actually reason over it. A company second brain is worthless if it's full of contradictions.

The Opportunity

Here's the pattern Greg kept seeing. A company decides to pipe all its data into one place for agents. Then it looks at the data: five versions of the same customer, old Slack channels, PDFs nobody can search. The agent project stalls on the mess.

Agents are only as good as what they can read. If the data is organized so an AI can reason over it, every AI feature the company builds on top gets better, and keeps getting better with each model. That's compounding value, and most companies have no one to do the work.

What I'd Build First
  • A fixed-scope engagement on one department: sales, support or ops. Not "all your data."
  • Merge the duplicates. One customer, not five. One current price list, not seven.
  • Tag, date and flag. Mark what's stale, what's contradicted, and who owns what.
  • Write down the tribal knowledge that lives in three people's heads.
  • Hand it over as an MCP server plus a map of what exists, where it lives and how fresh it is. Then turn the repeat steps into tooling.
How I'd Get Customers

Sell the outcome, not the cleanup: "your support agent gives the right answer." Run one department as a paid pilot with a before and after accuracy test. Partner with agencies building agents, who keep hitting bad data and don't want to fix it themselves.

Spec.Sheet03
Who PaysMid-sized companies with an AI mandate and ten years of mess. Usually the COO, or whoever runs the AI project.
The WedgeOne department, fixed scope, with an accuracy number before and after.
Price ShapeA fixed-fee project, then a monthly retainer to keep it clean.
Why.It.Grows▲

Every new model reasons better over clean data, so the payoff from your work grows with each release. Smarter models also do more of the cleanup for you, which lowers your cost per job while your price holds.

What Could Kill It

It's consulting, with consulting margins. Smarter models may cope with messy data well enough that "clean" matters less. Data warehouses and enterprise search tools will bundle pieces of this. Your moat is the playbook and tooling you build from doing it fifty times.

Idea 04 · Bonus

Picks And Shovels For Insurers

AI Insurance Evaluations

Don't start an insurance company. Build the tests insurers will use to decide which agents they'll cover, and at what price.

The Opportunity

Greg thinks agent insurance is coming: once an agent makes an expensive mistake, insurers will want audits before they cover anyone. Insurance companies are huge businesses, and nobody's starting one from their office. But insurers will need a way to measure agent risk, and right now there's no standard way to do it.

Whoever writes the evaluation everyone uses gets a seat in every policy. Insurers will build their own processes too. If you can define what "safe enough to cover" means for an agent, with tests that produce evidence, you're the expert they lean on.

What I'd Build First
  • A scoring rubric for an agent deployment: what it can access, what it can do without a human, how it's monitored, how it fails.
  • A test harness that runs scenarios against a live agent and produces a risk score with evidence.
  • A report written for underwriters, not engineers.
  • A failure log. Real examples of agents going wrong inside companies. Greg heard that's the data even the labs struggle to get.
How I'd Get Customers

Find one specialist broker or underwriter who wants to write AI policies and has no way to price them. Run the evaluations for their first clients at cost, in exchange for the data. Better yet, start with idea 02. Security audits are how you earn the expertise and the failure data, and this is where that business grows up.

Spec.Sheet04
Who PaysFirst, insurers and brokers who need to price AI risk. Then the companies seeking cover, who pay to get evaluated.
The WedgeOne broker partner, one kind of agent. Customer support agents that can issue refunds, say.
Price ShapePer evaluation, plus a yearly re-evaluation.
Why.It.Grows▲

As agents get more autonomy, their mistakes cost more and the demand for cover grows. Every new capability is a new kind of risk that needs a new test. Could models get so good you never worry about safety? I don't think that ever happens.

What Could Kill It

Timing. This market may be years away, and insurers move slowly. Big carriers may build evaluations in-house, or a standards body may publish a free framework. It's the most speculative of the five, which is why I'd get there through security audits, not start here.

Idea 05 · Bonus

Some Companies Are Data Companies

Industry Data Marketplace

A marketplace where companies list licensed, permissioned industry data, and AI labs and vertical AI startups buy it.

The Opportunity

Greg heard story after story of data brokers making around $2M a week selling company data to labs. He couldn't tell if it's the beginning or a bubble. He also heard that a shut-down startup with five years of Slack, email and code can get paid to license all of it, and that some SaaS companies are secretly data companies.

If software can be rebuilt quickly, the value moves to data. Vertical AI is beating generic AI, and vertical AI needs data about one industry that nobody can scrape. Right now those deals happen by hand, through people who know people. That's what marketplaces replace.

What I'd Build First
  • Be a broker in one vertical before you build a platform. Legal, medical billing, logistics, construction.
  • A listing flow that captures what the data is, how much, what dates, and who owns the rights.
  • The trust layer: rights checks, personal data removal, consent records, and contracts that say how the data can be used.
  • Samples and data cards so buyers can judge quality before they pay.
How I'd Get Customers

Supply first. Talk to founders winding down, investors holding dying SaaS companies, and trade associations. Build a catalog in one industry, then take it to the labs and vertical AI startups that need it.

Spec.Sheet05
Who PaysBuyers: labs and vertical AI startups. Sellers: companies with deep archives, including ones shutting down.
The WedgeHand-brokered deals in one industry, then a marketplace once both sides show up.
Price ShapeA cut of every license.
Why.It.Grows▲

Every lab is training on the same public internet. As models get smarter, the edge moves to specialized data they can't scrape. Smarter models also make it cheaper to clean, label and scrub what you sell.

What Could Kill It

Legal risk. Customer data often isn't yours to sell, and contracts, privacy law and terms of service get in the way. Labs could lean on synthetic data or deal directly with big data holders. It might be a bubble. And marketplaces are the hardest thing to start, with two cold sides. Broker before you build.

Your Turn

Run Your Idea Through The Test

Four questions I'd ask about any AI startup, including the one you're already building.

Question 01

If the next model is twice as smart, do my customers need me more or less?

If the honest answer is "less," you have a clock on your business. Know how long it is.

Question 02

Am I selling a gap in today's model?

If your product exists because models can't quite do X yet, every release is a threat. If it exists because agents are doing more, every release is a tailwind.

Question 03

What do I own that a model can't rebuild?

Data, relationships, trust, distribution, a map of messy systems. Code isn't on the list anymore. People are cloning whole apps with agents.

Question 04

Do better models cut my costs or my price?

In a good business, smarter models make your work cheaper to deliver. In a bad one, they make your product cheaper to replace.

One More Thing

Tools Are The Easy Part.

Anybody can build software now. Not everybody can build a business.

The Solo Founder Lab

Reading about tools is a great way to feel busy. The Lab is for Founders who'd rather get customers: weekly office hours with a CTO who's built two seven-figure software companies, and a room of other Founders who care whether anybody buys what you're making.

Lab.exe✣

Less Theater. More Customers.

Want my 30-Day Launch Plan? It's for Lab members only: validate, plan, build and launch, one week at a time.

See The Solo Founder Lab ▶