AI Agent Whitespace: 54 Verticals Scored, 34 Cannot Automate

We scored 54 business verticals for whether they can run on autopilot with AI agents today. 20 can. 16 are one piece short. 18 are wide open. So 34 of 54, roughly two in three, cannot.

The interesting part is not the count. It is that the failures are not scattered. In all 18 of the wide-open verticals, the blocking slot is the same one, with no exceptions: the system of record, the single system a business actually runs and bills from. And every one of those 18 gaps is flagged durable, for a specific recorded reason: no vendor in that slot has shipped an agent surface at all, so no single vendor closes it by adding an endpoint.

That is a different kind of finding from a list of use cases. A gap that one vendor could close next quarter is a feature request. A gap that no vendor in the category has moved on is a market structure, and market structures are what you can build a business inside. This article names the verticals, shows the evidence from three independent datasets, and then goes through what actually survives contact with the constraint.

The answer up front, with the numbers

Two in three business verticals cannot run on autopilot today, and the reason is singular rather than varied. 20 verticals are ready, 16 are one piece short, 18 are wide open, and every one of those 18 is blocked at the system of record. No vertical is blocked at payments, scheduling, accounting, compliance or communications. The constraint is not distributed across the stack, it is concentrated at position zero of it. The supply-side half of the picture, covering every connector that does exist, is in the AI connector census.

If you take one thing from this study, take that. The agent era has a single choke point across most of the economy, it sits at the system a business bills from, and the vendors who own that slot have the strongest commercial reason of anyone not to open it. What follows is the evidence, the verticals by name, and what our kill pass says is actually buildable against it.

The question nobody is answering

Search for AI agents by industry and you will find a dozen pages listing what agents can do in healthcare, finance, retail and manufacturing. Every one of them is a list of capabilities. Not one publishes a measurement, and not one answers the question a builder actually has, which is the negative: where does this not work, and why.

That absence is structural. The parties motivated to write about agent adoption are the ones selling it, and a vendor has no reason to publish a map of where its category fails. So the optimistic half of the picture is thoroughly documented and the useful half is not documented at all. It is the same asymmetry we found looking at plugin ecosystem economics, where every ranking page answered the merchant question and nobody answered the developer one.

The other reason is that the negative is harder. To say a vertical cannot be automated you have to define what its stack is, check every piece of it, and be willing to name the piece that fails. That requires a census, which is why this study sits on top of the connector census rather than standing alone.

The demand for the negative is real and loud. An r/mcp reader hunting for something to build summarised the problem with the optimistic literature: every use case on offer is “either agentic coding, which is already saturated by big players” or a variant of it. A developer in r/SaaS put the same frustration in the first person: “Every time I try to brainstorm an idea I hit the wall. Either someone has already built a tool for it or it does not exist because no one really cares enough to pay for a solution.” and “as a developer living in a tech bubble how do you actually find what normal people or businesses are struggling with?”

A measured gap map is one answer to that question, and it is why we built a complaint corpus rather than another idea generator. Related approaches are in how to find startup ideas and finding problems worth solving.

Method and limitations

Three things we are deliberately not publishing and one we are. We hold back the numeric readiness score, the internal coverage ratio and the per-idea judge scores, all because their scales are not yet trustworthy. We publish the blocking slot concentration, because that one is a count and counts do not need calibration. If you want the working discipline behind that split, it is the same one in how founders research markets. It is why the companion census publishes its empty tables rather than hiding them, and why every corpus study we run, from the Stripe Index to the funded company database, carries a limitation column.

The operating stack

A vertical is scored against its operating stack: the set of systems a business of that type actually runs on. We use 14 slot types, and each vertical carries between 4 and 7 of them depending on how the business works.

A restaurant and a law firm both have a system of record, payments and accounting. Only one of them has inventory. Only one has compliance in the sense that matters. The stack is what makes a per-vertical verdict possible at all, because automating a business is not one problem, it is the intersection of five or six.

That intersection is why single-point automation keeps disappointing operators. From r/smallbusiness: “A lot of his work involves moving information between different websites that have no integration with each other” and “It also made me realize how many businesses probably have processes that don’t fit neatly into Zapier or Make or API-based automation because the websites involved simply don’t offer integrations.” The stack is the unit of analysis, not the task. The same operator listed the options they had actually tried: employees doing it by hand, spreadsheets as the middleman, browser automation, custom software, or someone maintaining a pile of scripts and extensions. None of those is a product category. All of them are budget.

Which slots appear where

One slot appears in every single vertical and appears first in every one: the system of record. Nothing else is universal. Payments comes close at 50 of 54, accounting at 43. Both of those slots are comparatively well served, which we measured against the companies taking payments live on Stripe. That universality is the first hint at why the failures cluster. It is also why we score the slot rather than the industry, a framing that carries into vertical AI SaaS ideas and B2B business ideas.

The three verdicts

Ready means every slot in the stack has at least one reachable connector from a vendor that serves it. One piece short means most of the stack is reachable but something material is not. Wide open means a core slot has no reachable connector at all.

The bands are deliberately coarse. A three-way verdict is honest about a dataset whose vendor lists are not yet curated, and it is still enough to act on, because the decision a builder faces is also three-way: build here, wait here, or go elsewhere. Sizing that decision properly is covered in calculating market size and researching market size for SaaS.

20 ready, 16 one piece short, 18 wide open

The 20 ready verticals

Accounting firm, architecture firm, catering company, church, consulting firm, ecommerce store, event planning, field service, general contractor, IT managed service provider, manufacturer, marketing agency, nonprofit, online course creator, pet grooming and boarding, real estate brokerage, recruiting agency, SaaS company, salon and spa, wholesale distributor.

What the ready ones have in common

Look at that list and the pattern is immediate. They are digital-native businesses, professional services, or businesses whose system of record is a general-purpose tool rather than a vertical one. A marketing agency runs on a CRM and a project tool. A SaaS company runs on systems built by people who ship APIs by reflex. A consulting firm runs on documents and a calendar.

None of them depends on a single specialised vendor that owns the operational truth. That is the whole difference, and it explains why the ready list reads like a directory of people who already buy software enthusiastically. We mapped the same population from the revenue side in who micro SaaS actually sells to and priced in what micro SaaS actually charges.

Notice what the ready list is not. It is not a list of easy markets. It is a list of markets where the technical blocker has already been removed, which means competition there is ordinary product competition rather than structural advantage. That distinction matters when choosing between a ready vertical and a blocked one, and it runs through the state of micro SaaS competition.

The 16 that are one piece short

Auto repair shop, childcare center, chiropractic clinic, cleaning service, financial advisory, hotel, insurance agency, landscaping, medical clinic, mental health practice, moving company, pest control, private school, property management, trucking company, tutoring business.

What we cannot tell you about this band yet

We can tell you these 16 are short. We cannot yet tell you which piece. Gap rows are computed only for the wide-open band, so the blocking slot for the middle band is genuinely not in this dataset.

We flag that rather than reason from the pattern, because reasoning from the pattern would produce a plausible sentence with no measurement behind it. If the wide-open band is any guide the answer is probably the same slot, and probably is not a finding. The discipline is the same one we hold in idea evaluation: state the confidence you have.

The 18 wide open

Eighteen out of eighteen, one slot

That table is the article. Eighteen different businesses, from a coffee shop to a mortgage brokerage, with nothing in common operationally, and the blocking slot is identical in every single one. There is no second reason. Not payments, not scheduling, not compliance, not communications. One slot, eighteen times.

When a distribution is that degenerate the usual instinct is to suspect the measurement. So it is worth being clear about what would produce this artificially: if the system of record were the only slot ever checked, or if it were weighted so heavily that nothing else could ever be the binding constraint. Neither is the case. All 14 slot types are checked, and all slot weights are 1.0. The concentration is in the world, not in the scoring.

What a system of record actually is

The one system a business runs and bills from. The practice management system in a dental office. The point of sale in a restaurant. The case management system in a law firm. The property management system in a self storage facility. The dealer management system in a car dealership. The student information system in a private school.

It is not the most sophisticated software in the business and it is usually not the most liked. It is the one that holds the operational truth: who the customer is, what was done for them, and what they owe. Everything else in the stack is downstream of it.

Operators do not use the phrase, but they describe it precisely. From r/smallbusiness on the consequence of picking the wrong one: “They lied about the integration with my existing customer database. I couldn’t even access my 7,000 loyal customers after switching.” The system of record is the system that can hold your business hostage, and everyone who has switched one knows it.

Why it stays closed

Because opening it is the one thing that ends the vendor’s business. A system of record vendor in a vertical holds the account through switching cost, and switching cost is made of exactly the data an agent would need to read. Exposing it to a neutral agent converts a sticky product into a replaceable one.

This is not a conspiracy, it is an incentive, and it is stable. A market analyst writing on systems of record in late 2025 titled the piece Long Live Systems of Record, which is roughly where the evidence sits. The connector census agrees from the supply side: only 0.8% of all declared tools are transactional at all, which is what you get when the vendors holding the money-moving systems decline in unison. We covered that constraint in detail in the census.

Why the gap is durable and not just early

Our scoring flags all 18 gaps as durable, and the recorded reason is specific enough to quote: no vendor in this slot has shipped an agent surface, so no single vendor closes it by adding an endpoint.

That sentence is doing real work. There is a big difference between a category where the leader has an API and the followers do not, and a category where nobody has moved. The first closes when one competitor decides to differentiate. The second requires the whole category to change its mind about what it is selling, and categories do that on a decade scale, not a quarter scale.

A useful sanity check on that comes from a vertical SaaS operator arguing on Hacker News that agents are not about to eat his category: “The bottleneck is still knowing what to build, not building” and, on what his customers actually run today, “Their current system is Excel.” A founder in the same thread added “The spreadsheet is my biggest competitor.” Incumbent vendors are not rushing to open anything, because the thing they are winning against is a spreadsheet, not an agent.

A durable gap is the only kind worth building a company inside, which is the distinction we apply throughout the 8-stage validation framework and finding ideas from real pain points.

Two different ways to be blocked

The gap type column splits 14 to 4. 14 verticals are blocked by no connector: a vendor is identifiable in the slot, it simply has no listing on either official directory. 4 are blocked by no vendor: physical therapy, pharmacy, auto dealership and self storage, where we cannot even identify a candidate vendor in the slot that has an agent surface.

The second group is the harder market and the better opportunity, for the same reason. Nobody has built the thing, nobody is about to, and the customers are already paying for something worse. We look for exactly that combination in the best micro SaaS ideas and SaaS product ideas. If nobody in the category has even tried, you are not racing an incumbent’s roadmap. You are in the territory we describe in boring industries begging for micro SaaS.

The census agrees

Independent evidence one. Our connector census, which was built without reference to any vertical, shows healthcare at 2.0% of all connectors and legal at 0.8%. Together they are 200 rows out of 7,000+. Commerce is 1.5%. Nonprofit is 0.1%.

Cross-reference that against the wide-open list and the overlap is near total: dental, optometry, veterinary, physical therapy, pharmacy and home care are all healthcare-adjacent. Law firm and mortgage brokerage are legal and financial. Restaurant, grocery, retail and coffee shop are commerce. The categories with the least connector supply are the verticals with the worst verdict. Two measurements built for different purposes agreeing is why we run cross-corpus checks rather than single queries, a habit documented in cross-source research and competitor analysis for SaaS.

The complaints agree

Independent evidence two, and this one was built years before Agent Index existed. Our complaint corpus scores systemic pain points per software category. Filter it to the wide-open verticals and the highest-gap issues are specifically about the thing a blocked system of record produces.

Read the pain point column on its own. Cumbersome data entry across platforms. Inability to generate accurate accounting reports. Poor integration capabilities. Complex billing. Those are not usability complaints, they are the symptoms of an operational system that will not hand its data to anything else. Explore the corpus yourself through the Capterra analysis guide or the pain points database.

Scores are abstract, so here is the same finding in the words of the people paying for the software, one wide-open vertical at a time. Every quote is anonymized to platform and software category.

Every one of those is the same sentence wearing a different uniform: the operational system will not hand its data to anything else, so a person does it. That is not a software quality problem to be fixed by a better vendor, it is the shape of the market. Working that shape is what the pain points database and the pain point MCP tools are for.

Three datasets, one slot

The readiness scoring says the system of record blocks 18 of 18. The connector census, built separately, shows the thinnest supply exactly in those categories. The complaint corpus, built years earlier for an unrelated purpose, records the highest systemic gaps in exactly those categories and describes them as cross-platform data problems.

Three datasets, three methods, three different times, one answer. That is the convergence test we apply to every claim we care about, and it is why we cross-reference rather than lean on a single source, as in the state of SaaS pain points and cross-source research.

Restaurant

Six of seven slots covered, blocked at the point of sale. Everything around the POS is reachable: payments, accounting, communications, scheduling, marketing. The system that knows what was sold, to whom, at what price, and what it cost is not.

A restaurant buyer in the survivor set describes the consequence precisely: the seller’s POS is inaccessible and often stays under the seller’s control, so the evidence needed for diligence sits scattered across reports and statements. That is not a software problem, it is a transaction problem, and it recurs every time a restaurant changes hands. Recurring transaction problems are an underrated product surface, which we cover in finding SaaS acquisition targets and using BigIdeasDB for due diligence.

Dental practice

Five of six slots covered, blocked at the practice management system. The complaint record for dental software is unusually specific about what that costs: “Accounting reports are lengthy and confusing. I often need to run multiple reports to reconcile balances, which delays processing.” and “Patients can’t make partial payments under $1,000, which limits their options and creates an unnecessary burden on staff to manage finances manually.”

Dental is also consolidating, which multiplies the problem: groups acquire practices running different practice management products and then have to operate both. Two of our 25 survivors are dental, and both are about reconciling across incompatible systems rather than replacing either.

Consolidation is a reliable whitespace multiplier generally: every acquisition creates a pair of systems that must be reconciled once and then operated in parallel. We track where that capital is moving in the funded company database and the state of SaaS acquisitions.

Law firm

Five of six slots covered, blocked at practice management. Legal carries the smallest connector category in the entire census at 0.8%, and the highest systemic market gap score we recorded at 9.99. Practitioners are blunt about it: “Not being able to integrate properly with other software our firm uses was a deal breaker” and “The accounting tab does not allow for a credit balance, forcing us to maintain an external spreadsheet for client transactions.”

Add trust accounting, where a firm must reconcile matter ledgers, billing, operating accounts, bank statements and accounting postings, and the shape of the surviving idea becomes obvious. From a practitioner in r/lawfirm: “we have to post all ID check fees and search-pack fees manually, one matter at a time” and “No way to bulk-import or automate cost postings? Anyone have workarounds?”

Asking for a workaround in public is the single clearest buying signal in our whole corpus. It means the problem is acute, the budget exists, and no product has claimed the slot. That is the signal we teach people to hunt for in finding business ideas on Reddit and Reddit idea validation.

Self storage

Four of five slots covered, and one of the four no-vendor cases. Nobody in the gate and facility management slot has an agent surface at all. Two of our 25 survivors are self storage, one on access entitlement auditing and one on acquisition cutover, both of which work entirely on exports. The unmanned-facility model makes access control a financial control, the kind of second-order consequence that only shows up when you study a vertical rather than a use case. More of that thinking is in finding niche business ideas and how to find a profitable niche.

Farm

Five of six slots covered, blocked at farm management. The complaint corpus lists Poor Integration Capabilities as a systemic issue at 8.00 gap, alongside Data Input Bottleneck With Multiple Users and Limited Advanced Accounting Features. Practitioners describe the daily version: “In larger organizations, we often waste time due to slow synchronization when syncing from field to system.” and, from the same category, “syncing has to be uninterrupted to be successful which can be time consuming with slower internet.” Farm is the clearest case in the set where connectivity, not policy, is part of the blocker, which is worth weighing before you pick it. Compare against the other options in boring business ideas.

Fitness studio

Five of six slots covered, blocked at the member management system. Fitness has the largest complaint footprint of any wide-open vertical in our corpus, with Frequent Bugs And Technical Issues affecting 70 companies at 4.50 severity and Complex Billing Systems affecting 66. A surviving idea in this vertical is a diligence data room for studio acquisitions, which exists because the core vendor stays closed while every other system can still be exported. Fitness is also the vertical where the complaint volume most clearly outruns the connector supply, a mismatch we look for systematically in SaaS ideas backed by pain points.

432 ideas, 25 survivors

Knowing where the gap is does not tell you what to build in it. So we generated 432 ideas against the gap map and ran every one through an adversarial pass whose only job is to kill things. 25 survived. That is 5.8%, spanning 22 of the 54 verticals.

A 94% kill rate is the point, not a failure. Most ideas generated against a gap are a connector, a wrapper or a prompt, and all three die to the same objection, which an r/SaaS thread put in the voice of an investor: “What happens when OpenAI or Anthropic releases their next minor model update, context window expansion, or native workflow feature?”

The same thread catalogued the pattern behind that objection as the prompt-as-moat assumption, where the whole architecture is a frontend, an API key, a clever system prompt and a pretty output. Every idea we killed had some version of that shape. Screening for it early is the point of AI SaaS ideas and validating before you code.

What survived has exactly one shape

Read all 25 together and the pattern is almost uncomfortable. Returns Close for ecommerce. Production-to-Cash Daily Close for dental. Trust-to-Books Month-End Close Pack for law firms. SIS-to-Ledger Tuition Reconciliation for private schools. OTA Virtual Card Reconciliation for hotels. Event Margin Close for caterers. Repair-order closeout and margin audit for auto shops. Access Entitlement Audit for self storage. Acquisition Cutover Control Room, also self storage. Pharmacy acquisition record reconciliation. Restaurant Acquisition Operating Diligence.

Every one of them is a reconciliation, a close, or a cutover. Not one is a connector. Not one assumes the system of record opens.

That is not an aesthetic preference, it is what a 94% kill rate leaves behind when the only test is whether a platform update can erase you. The full survivor set with theses, wedges and ICPs lives in Agent Index, and the reasoning pattern generalises in the 8-stage validation framework.

Why reconciliation survives the kill pass

Because it is the one product shape that is made better by the constraint rather than blocked by it. If the system of record were open, a reconciliation product would be less necessary. It is necessary precisely because the data has to be extracted, normalized and compared by hand today.

And it runs on the capability that does exist. The census says reads are 53.2% of all tools and transactions are 0.8%. A reconciliation product needs reads and exports. It never needs to transact. It is built on the half of the ecosystem that works.

An agent developer arrived at the same constraint from the engineering side and stopped voluntarily: “The write-path comments were consistent: preview then confirm in the same loop, idempotency and optimistic lock, fail closed near mutations. That’s enough for me to hold human review. I’m not adding mutate tools until the read loop is tighter.” Products designed for that reality ship. Products that assume it away do not. Guidance on operating inside it is in verifying AI agent work and AI agents beyond coding.

The wedge that works

The survivors share a wedge as well as a shape. Every one of them starts from files, not from an integration: a month of exports, a settlement report, a bank statement, a rent roll. From the childcare survivor: the available system-of-record connections are read-only, which is sufficient for evidence collection.

That is the practical unlock. You do not need permission from the closed vendor to build on top of it, because the operator can already get an export. Starting from exports is the same insight behind simple SaaS ideas for solo developers and single-feature micro SaaS.

Where the moat actually is

Not in the extraction. The survivors put it consistently: the durable asset is the normalized event model, the vendor-specific mapping rules, and the accumulated record of how each exception was resolved. From the law firm idea, the data model and exception rules improve across vendor combinations and prior close histories. From the dental one, historical mappings for providers, locations, adjustment codes and settlement behaviour become hard to replace.

That is a moat that compounds with use and cannot be shipped by a platform update, which is the test that killed the other 407. The same logic runs through buying versus building a SaaS and what transfers when you sell a SaaS, where the transferable asset is almost never the code. It is also the reason an MCP layer on its own is not a moat: the interface is the commodity and the accumulated model is not. Build plans that respect that split are in how to build a SaaS and how to build a micro SaaS.

Outside confirmation we did not ask for

The strongest check on this thesis came from someone who had never seen our data. A builder posted in r/smallbusiness after six months building back-office software across insurance, healthcare, bookkeeping, real estate and consulting: “I expected each industry to need something different. They didn’t. Under the costume, every back-office runs the same 6 shapes.”

The six shapes, two of which are our thesis

Two of their six are the exact product shapes our kill pass left standing. On extraction: “Extract, scheduled or on-demand pulls from a system that doesn’t have an API. The shape behind daily payer eligibility checks, weekly P&L pulls, broker site monitoring, and marketplace order syncs. Every log into the portal and download the report workflow.”

On reconciliation: “Reconcile, compare across two or more sources, flag exceptions. The shape behind 3-way match in AP, EOB matching in medical billing, bank reconciliation, and payment processor matching. Every the same data lives in two systems, and someone has to compare them line by line workflow.”

A developer arrived at our conclusion by building across five industries. We arrived at it by scoring 54 verticals against a connector census. Those are genuinely independent paths and they land on the same two shapes. Independent confirmation is worth more than volume of evidence, which is the standard we hold ourselves to across the state of SaaS pain points and the state of indie SaaS revenue.

The cost side is documented too. From an operator in the same subreddit: “What starts as a quick check turns into a 15-hour-a-month slog of copy-pasting numbers, hunting down missing PDFs, and playing detective to spot duplicate payments.” And from a controller in r/Accounting: “Bank integration eats CONTROLLERS for breakfast. Integration promised automation but delivered manual uploads, broken file formats, cryptic bank error messages.” And from a supply chain operator, the task in full: “to update a PO, I’ve to manually copy the tracking, go to the carrier portal, find the status, then type it back into netsuite. all day, every day. it’s just begging for fat-finger errors.”

A consultant who automated exactly this described the payoff and the starting condition together: “reconciling invoices that live in three, four, even five different platforms by hand” and “I tried spreadsheets, Zapier hacks, even a manual checklist, but the errors kept piling up.” Spreadsheets and Zapier are the incumbents in every one of these verticals, which is a much better competitive set than a funded startup. We make that argument in unique business ideas backed by real complaints.

Ready does not mean served

A trap worth naming. Ready means every slot is reachable. It does not mean the work is done. Three of our survivors are in ready verticals: Client Offboarding Packager for accounting firms, Reporting Contract QA for marketing agencies, Returns Close for ecommerce.

In each case the stack is fully reachable and the cross-system job is still manual, because reachability solves the plumbing and not the judgement. An agency can pull data from every ad platform and still ship a client report built on drifted metric definitions. That is a real product in a ready vertical, and one of the clearest demonstrations that reachability is not coverage. It is the argument in B2B SaaS ideas.

Wide open is not the same as empty

The most expensive misreading available here. A wide-open vertical is not a market with no customers. Restaurants, dental practices, law firms and storage facilities are full of businesses paying real money for software every month. The complaint scores prove they are unhappy with it.

An empty market has no demand. A wide-open vertical has demand, has budget, has incumbents, and has a specific technical reason the obvious solution has not arrived. That is a far better starting position, and it is why we treat existing competition as validation rather than disqualification, as in the state of micro SaaS competition and how to find a profitable niche.

An operator in a wide-open vertical describing their current system makes the demand concrete: “I missed a callback yesterday that probably cost me a $2k job. My current system, a mix of sticky notes and a spreadsheet, is officially failing.” That is not an absent market. That is a market whose software is losing it money right now, which is the population we study in business ideas that solve real problems.

The commodity trap

The obvious idea when you see a closed system of record is to build the missing connector. Our kill pass rejects that every time, for a reason worth internalising: if you succeed in making the connector valuable, the vendor ships their own and you are done. You have spent your runway validating their roadmap.

The same objection appears from the buyer side in the r/SaaS threads our ICP writes in: “I’m looking for real problems, not build another AI wrapper suggestions” and “I don’t want to spend another 3-6 months building something that people think is cool but nobody actually pays for.” Filters for this failure mode are in AI product validation for solo founders and idea validation tooling.

How to pick your vertical from this

Four tests, in order. They work whether or not you use our data, and each one is answerable in an afternoon of conversation with two operators.

Test 1: what does this business bill from?

Ask an operator which system they would be unable to run a day without. That is the system of record. If the answer is a general tool like a spreadsheet, a calendar or a generic CRM, the vertical is probably in the ready band. If the answer is a specialised vendor most people have never heard of, you are looking at a blocked vertical. One founder put the research method plainly: “I can build software. What problem would you actually pay to solve?” That is the right question and two conversations answer it. Start from how to find problems worth solving.

Test 2: could one vendor fix this next quarter?

The durability test. If the category leader has an API and the rest do not, the gap closes the moment a competitor decides to differentiate. If no vendor in the slot has an agent surface at all, the gap is a category posture and it will outlast your build. All 18 of our wide-open verticals are in the second group.

This test also rules things in, not just out. An existing competitor is validation that budget exists, so a crowded slot with a durable gap underneath it is a better starting point than an empty one. We argue that position in micro SaaS competition and put it to work in finding problems worth solving.

Test 3: is there an export?

The feasibility test, and the one most people skip. A closed system of record is still almost always exportable, because the operator owns the data and periodically needs it. If an operator can produce a monthly CSV, you have a product surface without needing the vendor’s cooperation. If they genuinely cannot, walk away.

This is also the test that keeps your build honest. A product that needs the vendor to cooperate is a partnership, not a company, and partnerships with the party you are routing around do not close. Every one of our 25 survivors starts from a file the operator can already produce. Sequencing that into a first release is covered in what to build as a solo developer and the first $1k MRR.

Test 4: who signs off on this today?

The willingness-to-pay test. Every surviving idea replaces a named human process: a bookkeeper closing the month, a compliance reviewer assembling a file, a buyer reconstructing twelve months of sales. If nobody currently does the job, nobody will buy the automation of it. Pricing that against the labour it replaces is covered in how to price a micro SaaS and what micro SaaS actually charges.

What would change our mind

Stated in advance so it is falsifiable. If any meaningful number of vertical system-of-record vendors shipped agent surfaces, the durability flag on those verticals would flip and the whitespace would compress fast. If transactional tools moved from 0.8% into double digits, the read-only constraint that shapes the survivor set would break. And if the 16 one-piece-short verticals turned out to be blocked somewhere other than the system of record, the concentration finding would weaken rather than strengthen. We would also want to re-check whether the survivor set still skews to reconciliation, because if it stopped doing so the constraint would have moved. Re-running this kind of check is what the idea evaluator and the Agent Index MCP tools are for.

We will re-run this and say so. In the meantime, the specific verticals, blocking slots and surviving ideas are all in Agent Index, the connector layer underneath is browsable at the connector browser, and the Agent Index MCP guide documents the seven tools that put all of it inside your assistant. If distribution rather than whitespace is your question, the ChatGPT directory market map covers that side. If you want the demand side first, start with the pain points database or Discover.

Frequently asked questions

Which business verticals can run on autopilot with AI agents today?

20 of the 54 we scored return a ready verdict. They are overwhelmingly digital-native or professional services: accounting firms, marketing agencies, SaaS companies, ecommerce stores, recruiting agencies, IT managed service providers, consulting firms and real estate brokerages.

How many verticals cannot be automated with AI agents?

34 of 54, which is 63%. 16 are one piece short and 18 are wide open, meaning a core slot has no reachable connector at all.

What is the single thing blocking AI agent automation in most industries?

The system of record. In all 18 wide-open verticals the blocking slot is the system of record, with no exceptions. It is the only slot present in all 54 stacks and the first in every stack ordering.

What is a system of record in this context?

The one system a business actually runs and bills from: the practice management system in a dental office, the point of sale in a restaurant, the case management system in a law firm. It holds the operational truth, which is exactly why its vendor has the least incentive to open it.

Will the system of record gap close on its own?

Our scoring flags all 18 as durable, with a specific recorded reason: no vendor in that slot has shipped an agent surface, so no single vendor closes the gap by adding an endpoint. That is a category posture, not one slow vendor.

Which specific verticals are wide open?

Restaurant, dental practice, law firm, pharmacy, veterinary clinic, farm, grocery store, retail store, fitness studio, auto dealership, home care agency, optometry practice, physical therapy clinic, mortgage brokerage, self storage facility, vacation rental, photography studio and coffee shop.

If the system of record is closed, what can you actually build?

The layer above it. Of 432 generated ideas put through an adversarial kill pass, 25 survived, and almost every survivor is a reconciliation, month-end close or acquisition-cutover product that sits between systems and runs on exports and read-only access.

Why do reconciliation products survive when connector products do not?

A connector is an interface any vendor can add in a sprint. A reconciliation product accumulates a normalized data model, vendor-specific mapping rules and a history of how each exception was resolved. The first is commoditised by the platform. The second gets harder to replace with every close cycle.

How was autopilot readiness scored?

Each vertical is given an operating stack of weighted slots drawn from 14 slot types. Each slot is checked against the connector census for a reachable connector from a vendor serving that slot. The output is a three-band verdict.

Why do you publish a verdict instead of a score?

Because the per-vertical vendor lists are not yet curated, so the numeric score carries more precision than the inputs justify. The three-band verdict is what the data supports.

Is a wide-open vertical the same as an empty market?

No. These verticals are full of paying businesses running expensive software. What is missing is agent reachability, not demand. An empty market has no customers. A wide-open vertical has customers whose software an agent cannot touch.

Do the complaint data and the readiness verdict agree?

They do, which is the strongest evidence in the study. The wide-open verticals are where our complaint corpus records the highest systemic market-gap scores, and the complaints are specifically about cross-platform data entry, accounting reports and billing reconciliation.

What about the 16 verticals that are one piece short?

We can tell you they are short and we cannot yet tell you which piece. Gap rows are computed only for the wide-open band, so the blocking slot for the middle band is not in this dataset. We would rather say that than guess.

Which ready verticals are worth building for anyway?

Ready means reachable, not served. Accounting firms, marketing agencies and ecommerce stores all score ready and all appear in our surviving idea set, because a reachable stack still leaves the cross-system work undone.

How many ideas survived the adversarial kill pass?

25 out of 432, a 5.8% survival rate across 22 of the 54 verticals. The pass kills anything whose only asset is a prompt, a wrapper or a connector.

How often does this change?

The connector census moves daily because directories move. The verdict distribution has been stable across our syncs and the blocking slot concentration has not moved at all. We publish a snapshot date rather than a live claim, and make no trend claim because we have no time series.

Where can I look up a single vertical?

Agent Index has a page per vertical inside BigIdeasDB, and the get_vertical_readiness MCP tool returns the verdict and blocking slot for any of the 54 to an AI assistant directly. The Agent Index MCP guide has example prompts.

BigIdeasDB Research. (2026). AI Agent Whitespace: 54 Verticals Scored, 34 Cannot Automate. BigIdeasDB. Retrieved from https://bigideasdb.com/ai-agent-whitespace-by-vertical