Y Combinator published 13 ideas it wants funded. We checked every one against documented complaints, funded-company momentum and payment data. Four hold up. One contradicts the data outright.
Y Combinator publishes a Request for Startups each batch cycle: a list of ideas its partners would like to see founders tackle. The Fall 2026 edition runs to 13 requests, and within days of publication it was reprinted across newsletters, LinkedIn posts and aggregator blogs, almost always with the same treatment. Someone summarises what YC said, adds a paragraph of enthusiasm per item, and publishes.
Nobody checks whether the demand is actually there. That is the gap this piece fills. We took all 13 requests and scored each one against four independent evidence sources we maintain: 1M+ documented complaints from Reddit, G2, Capterra and app-store reviews; 17,000+ funded companies with AI-scored category momentum; 30,000+ companies taking real payment through Stripe; and revenue data on 3,700+ startups. Where those sources agree with YC, the request is worth taking seriously. Where they disagree, that is worth knowing before you spend a year of your life on it.
The headline result: four requests are strongly supported by independent demand evidence, four are directionally supported, four sit outside what our data can speak to, and one runs directly against it.
The Fall 2026 RFS frames itself around AI moving into the physical world, with requests contributed by YC partners, founders building on the frontier, and for the first time a sitting U.S. Secretary of the Army. The 13 requests, in the order YC lists them:
| # | Request | What YC is asking for |
|---|---|---|
| 1 | The Primer | An AI tutor that adaptively teaches young children to read, write and do arithmetic at private-tutor quality |
| 2 | The Future of American Defense | Low-cost interceptors, next-gen sensors, drones, resilient logistics and advanced manufacturing for ground combat |
| 3 | A Cloud for Small Software | Deployment and sharing infrastructure for bespoke tools with one or a handful of users |
| 4 | Multiplayer AI | Shared, live agent sessions a whole team can join, redirect and hand off |
| 5 | Compute at Sea | Offshore modular data centres, described as compute flotillas |
| 6 | AI Consumer Products | Consumer AI built for a billion people as token costs fall |
| 7 | The Aging Population | Voice interfaces, monitoring, robotics and caregiver coordination for older adults |
| 8 | OS for the Physical World | Software routing work between AI agents, field robots and humans in construction, maintenance and fleet operations |
| 9 | Crypto Rails | Stablecoins, capital raising, agentic commerce and institutional crypto products |
| 10 | Physical-World Data | Dense sensor and robot-collected data for energy, agriculture, logistics and construction models |
| 11 | The Trust Layer | Verifying a real human is on the other end of a call, message or transaction in a deepfake era |
| 12 | Compliance Infrastructure | AI-native financial compliance replacing spreadsheets, point tools and specialist headcount |
| 13 | API Change Agents | Agents that apply an API provider’s breaking changes directly to customer codebases |
Worth reading closely: YC prefaces the list by saying these “represent just a fraction of what we fund” and that “you don’t need to work on these ideas to apply”. That caveat gets stripped out of almost every summary of the RFS, and it changes how you should read the whole document. This is a statement of partner appetite, not a map of where customers are waiting.
We scored each request on three questions that can be answered with data rather than opinion. Is the problem documented? Is capital already moving? Is the market already served?
Is the problem documented? We search our complaint corpus for the pain the request describes. A request that matches systemic, high-severity complaints across independent platforms scores well. A request that matches nothing is not necessarily wrong, it just has no bottom-up evidence behind it yet. Our complaint analysis platform is where this data lives.
Is capital already moving? We check the request theme against 17,000+ funded companies scored for category momentum and investment attractiveness. A high-momentum category means investors are already active there, which is validation rather than a warning. Competition validates a market is the rule we work to: an existing field means the market is real, and the question becomes whether there is a wedge.
Is the market already served? This is where our Stripe index does work nothing else can. It contains 30,000+ companies taking real payment, classified by category and by whether they are small software. The ratio of small software to total companies in a category is the single most useful number we have found for spotting an opening: a category with many paying operators and almost no small tools is a market with money and no software, which is exactly the shape you want. We wrote about this in our analysis of SaaS market saturation.
Here is every request with its evidence verdict. “Confirmed” means at least two independent sources support it. “Directional” means one source supports it or the evidence is mixed. “No read” means the request sits outside what commercial software data can speak to, which is not a criticism of the request. “Contradicted” means our data points the other way.
| Request | Verdict | Strongest supporting signal |
|---|---|---|
| OS for the Physical World | Confirmed | Home Services and Trades: 960+ paying companies, 0.4% small software density |
| A Cloud for Small Software | Confirmed | 2,000+ micro-SaaS in the Stripe index; devtools momentum 5.4 across 1,300+ funded companies |
| Compliance Infrastructure | Confirmed | Accounting Practice Management integration gap 8.5 across 60 companies; heavy first-hand complaint volume |
| The Trust Layer | Confirmed | Cybersecurity and security are the top two momentum categories we track, both 5.6 |
| API Change Agents | Directional | Devtools momentum 5.4, but no independent complaint volume at scale |
| Multiplayer AI | Directional | ai-infra momentum 5.4 across 1,700+ companies, but builders are already saturating it |
| The Aging Population | Directional | Healthcare momentum 5.0 across 2,000+ funded companies; Medical app complaints heavy |
| The Primer | Directional | Education is our highest-negative G2 category, but the pain is reliability, not missing AI |
| Crypto Rails | Directional | Fintech momentum 5.3 across 2,200+ companies; secondary market for crypto assets is almost nonexistent |
| Defense | No read | Outside commercial software data |
| Compute at Sea | No read | Outside commercial software data |
| Physical-World Data | No read | Industrials momentum 5.2, but sample is small at 38 companies |
| AI Consumer Products | Contradicted | Consumer is last of all categories on momentum (4.3) and attractiveness (5.0) |
YC’s framing here is sharp: agents have made bespoke, single-user tools trivial to build but they are still hard to deploy and share. “Small software should be as easy to share with your colleagues as a Google Doc.”
Our data supports the premise. The Stripe index contains 2,000+ companies we classify as micro-SaaS, meaning software small enough for one person to run. Devtools carries a momentum score of 5.4 across 1,300+ funded companies, joint second-highest of any category, with an investment attractiveness of 6.6. Both numbers say the surrounding market is healthy.
The more interesting signal is where small software is thin. AI Tools and Apps runs a 34.7% small-software density, by far the highest of any category with real volume, which tells you where solo builders are already crowding. Compare that with Nonprofit and Fundraising at 0.2%, Software Development Agencies at 0.2%, and Home Services and Trades at 0.4%. If YC’s thesis is right and deployment friction is what keeps small software out of those categories, those low-density numbers are the size of the prize. Our internal tool ideas research covers the same territory from the builder’s side, and our micro SaaS ideas list catalogues what people are actually shipping at that scale.
One caution. The economics of small software are genuinely difficult. In our revenue data, the micro-SaaS tier under $500 MRR contains 2,500+ startups with a median of $50 MRR. A cloud serving that market is selling infrastructure to customers who mostly earn nothing, which is a real go-to-market problem YC’s write-up does not address.
This is the best-evidenced request on the list, and it is not close.
YC observes that 80% of the global workforce does not sit at a desk, and that software for construction, maintenance and fleet operations has barely changed in 20 years. Our payment data puts a number on the opportunity. Home Services and Trades contains 960+ companies taking real money through Stripe, but only four that we classify as small software. That is a density of 0.4%, among the lowest of any category with meaningful commercial volume.
Read that pairing carefully, because it is the whole argument. Nearly a thousand businesses in the category are paying for software. Essentially nobody is building small, modern tools for them. That is the opposite of the AI Tools category, where 34.7% of companies are small software chasing the same buyers.
The complaint corpus agrees. Construction CRM shows an inadequate reporting gap scored 9.0 across 18 companies, and integration challenges scored 8.5 across 17. Construction Management shows inconsistent support with critical operational impact at 8.5 across 17 companies, at an average severity of 4.5 out of 5. These are systemic issues, meaning they recur across vendors rather than singling one out.
“How do you deal with these fleet management challenges? We ’ve been using a basic GPS system but it’s pretty limited. Thinking of upgrading to a more full-featured platform but I keep hearing mixed things.” – r/Truckers
That is the buyer YC is describing, saying out loud that the incumbent options are not good enough. If you want more of this territory, the most underserved software markets and niche SaaS opportunities by industry both dig into categories with the same money-present, software-absent shape.
YC wants AI-native financial compliance that consolidates fragmented tools and reduces reliance on specialist headcount. This is well-evidenced, and unusually it is evidenced by people describing the cost in their own words rather than by category statistics alone.
“Getting SOC2 certified the first time was almost 2 years of work, requiring a 4-5 person IT team, a 2-person security team... The ‘AI-first’ promise can overstate how hands-off the process really is. While it might feel like a quick win upfront, the real effort shows up later when you’re trying to stitch everything together for the audit.” – r/sysadmin
That second sentence is the important one, and it is a warning to anyone building here. The market has already been sold an AI-first compliance story and found it wanting at the audit-assembly stage. The wedge is not “AI reads the regulations”, it is the unglamorous stitching work that happens afterwards.
The structured data supports the request. Accounting Practice Management shows an inadequate-integration gap scored 8.5 across 60 companies, the widest affected set in our compliance-adjacent categories. Accounting shows inefficient cross-platform support scored 9.0 across 34 companies and cumbersome interfaces at 8.5 across 34. Governance, Risk and Compliance carries 378 tracked G2 insights.
The recurring theme across all of it is not missing intelligence, it is missing connective tissue:
“We have no visibility into what users actually do inside a report, which filters they apply, which records they view... This is becoming a problem because our privacy officers require more detailed auditing.” – r/PowerBI
“I worry that I’m missing renewal dates for my certifications. It would be great to have a reminder system in place.” – r/dentaloffice
Note the gap between those two quotes. YC frames compliance as an enterprise problem for companies hiring chief compliance officers. The complaint data shows the same category of pain landing on a dental practice with no compliance function at all. The small end is underserved and easier to reach, a pattern we see repeatedly in B2B SaaS opportunities.
YC’s pitch opens with a finance worker wiring $25 million after a video call in which every other participant was a deepfake, and asks for infrastructure that verifies a real human is on the other end.
Our category momentum data supports this more cleanly than any other request. Cybersecurity and security are the two highest-momentum categories we track, both at 5.6, with investment attractiveness of 6.9 and 7.1 respectively. That is capital moving into the space ahead of the products.
The complaint corpus adds a constraint worth building around. Users are not asking for verification, they are asking for verification that does not cost them their privacy:
“If all the UK Gov is concerned about is making sure only adults are looking at mature content, can’t they implement Zero Knowledge Proofs for this? Privacy win, since once this system is in place it will prevent any more invasive age verification methods from being implemented.” – r/privacy
YC gestures at this (“ideally it’s one that doesn’t make everyone give up their privacy”) but treats it as a nice-to- have. The demand signal suggests it is the actual requirement, and that a verification product which harvests identity data will meet resistance from exactly the users it needs.
YC’s first request asks for an AI tutor of private-tutor quality for young children, invoking Neal Stephenson’s Diamond Age. It is the most evocative item on the list. Our data says the demand is real but the diagnosis is off.
Education is the category with the highest proportion of negative sentiment in our G2 insight set: 145 tracked insights of which 21 are negative, a far worse ratio than Marketing Software (2 negative of 1,378) or Collaboration and Productivity (3 of 1,318). So education software is genuinely disliked. The question is why.
Reading the actual complaints, essentially none of them are about insufficient personalisation or a lack of adaptive intelligence. They are about software that does not work. Across the lowest-rated reviews in our education set, the recurring themes are crashes during live sessions, audio falling out of sync in recordings, gradebooks losing saved grades, sync failures between mobile apps and web platforms, and routine tasks requiring over a dozen clicks. One platform’s reviewers describe it timing out constantly and losing all saved grades. Another’s describe needing “a degree in coding” to navigate it.
So the honest read on The Primer: the market is real and badly served, but the unmet need documented in our data is reliability, not intelligence. A beautifully adaptive tutor that drops sessions will collect the same reviews the incumbents do. Funded-company data adds a second caution: edtech momentum is 4.8, below our tracked average, and only 12 funded companies in our tutoring-adjacent keyword slice, the thinnest field of any RFS theme except consumer. That can be read as uncrowded opportunity or as an absence of validation, and honestly it is too early to say which.
YC argues AI has not had its multiplayer moment: agents run long tasks but people still use them alone, in a private chat box. The analogy to Figma beating Photoshop and Docs beating Word is a good one.
The underlying category is healthy. ai-infra carries momentum of 5.4 across 1,700+ funded companies, joint second-highest we track, with attractiveness of 6.6.
But this request has a crowding problem YC does not mention. We pulled the top 20 Product Hunt launches from the last 90 days. Roughly eight of them are explicitly agent infrastructure: an inbox designed for humans and agents, browser automation for AI agents, rails that agents use to find and pay you, a publishing API for agents to post across social platforms, an open-source workspace for AI agents and workflows, a live data marketplace for agents, a tool to ship AI agents like web apps, and a trading desk for LLM calls. That is 40% of the most-upvoted launches on the largest launch platform, all in one theme, in one quarter.
Builders do not need to be asked to work on agent infrastructure. They are already there in force. The revenue data suggests how that usually ends: our AI-Native Tools cluster contains 2,000+ tracked startups with a median MRR of $0. Being early to a crowded category with no revenue is not obviously better than being late to an empty one. We covered this dynamic in the AI SaaS revenue reality check and our research on SaaS ideas for AI agents.
One genuinely open frontier sits inside this theme. Of the 30,000+ companies in our Stripe index, fewer than a dozen support machine-payable transactions, and none expose an MCP server. Agentic commerce is not a trend yet, it is an empty room. That is either the best signal on this page or a sign the demand is not there, and we would not pretend to know which.
YC’s consumer request is the most confident item on the list. “Every platform shift mints consumer giants... CONSUMER is going to be so back.” The argument is that intelligence just got good enough and is about to get cheap enough, so whoever builds now owns the moment.
Our data says the opposite, and says it clearly. Across 17,000+ funded companies, consumer is the lowest-scoring category we track on both measures that matter: momentum 4.3 and investment attractiveness 5.0. Every other category scores higher on both. For comparison, cybersecurity sits at 5.6 momentum, devtools and ai-infra at 5.4, fintech at 5.3. And this is not a small-sample artefact: the consumer set contains 2,800+ funded companies, the third-largest category we track. A lot of consumer companies have been funded, and they are collectively showing the weakest momentum of any group.
The narrower slice tells the same story. When we filter funded companies to those matching RFS themes by description, b2b-saas returns 230 companies, ai-infra 201, fintech 115, healthcare 96 and devtools 86. Consumer returns 29.
The app-store data adds texture rather than contradiction. Consumer categories dominate our negative-review counts, with Health and Fitness combined with Lifestyle at 2,300+ negative reviews, the largest single block. So consumers are unhappy with the apps they have. What the funding data says is that solving that unhappiness has not been producing companies with momentum.
None of this proves YC wrong. They are making a forward-looking bet on a cost curve, and our data is backward-looking by construction: it measures companies that already exist. A thesis about a moment that has not arrived cannot be falsified by data from before it arrived. But if you are choosing what to build this quarter, you should know that the most confident claim on YC’s list is the one with the least supporting evidence in ours.
YC is candid that this is a contrarian pick: “prices are down, hot narratives have fallen flat, and many builders are leaving”, and argues bear markets are when real projects get built.
Fintech overall carries momentum of 5.3 across 2,200+ funded companies with attractiveness of 6.4, which is solid. The crypto-specific signal is thinner than the fintech wrapper suggests. In our acquisitions data, covering 630+ live listings, exactly one is categorised as a crypto startup, against 290+ SaaS listings. A secondary market that thin means very few crypto businesses reach the point of being sellable assets with revenue, which is a meaningful data point about the category whichever way you read it. Our guide to using acquisition listings as market validation explains why we treat that market as a signal.
YC’s strongest sub-claim is the one about agents using crypto networks as financial rails, which connects to the empty machine-payable frontier noted above. That is the part of this request we would take most seriously.
The final request comes from a founder who worked with 50+ API vendors and found API communication broken: breaking changes ship with little warning, changelogs go unread. The proposal is Dependabot for APIs, where providers apply their own changes to customer codebases.
Devtools momentum of 5.4 with attractiveness 6.6 supports the surrounding category, and the top-20 Product Hunt list shows adjacent products getting traction, including an API to scrape and enrich data and a publishing API for agents. But we cannot find independent complaint volume at scale for this specific pain. That does not mean it is not real: this is a problem experienced by developers inside companies, which is exactly the population least likely to write a public review about it. It means the evidence here is one practitioner’s well-argued observation rather than a documented pattern, and you should treat it accordingly.
If you are drawn to this one, the adjacent territory in legacy system API wrapper business ideas has better-documented demand for a similar skill set.
Three requests sit outside what our data can honestly assess: defense, compute at sea, and physical-world data collection. Our corpus covers commercial software: complaints about products people buy, companies taking payment, SaaS revenue. It has nothing useful to say about low-cost interceptors or offshore data centres, and we would rather say so than manufacture a verdict.
The one partial read we have is on physical-world data. Industrials carries a momentum score of 5.2 with attractiveness 6.2, which is respectable, but our sample is only 38 companies and we would not build an argument on it. Agtech at 27 companies scores 4.9 momentum. Both numbers are directionally positive and statistically weak.
Worth naming the structural point: these three requests are the least contestable by a solo founder or small team, and they are also the ones where an RFS matters most. If you need capital and a proving ground before you can build anything at all, an explicit invitation from YC and the Army is worth considerably more than it is in software, where you could just ship.
An RFS is as informative for what it omits. Running our own opportunity data against the 13 requests, several well-evidenced categories appear nowhere on YC’s list.
Nonprofit and Fundraising has 640+ companies taking payment in our Stripe index and a small-software density of 0.2%, one of the lowest we measure. Software Development Agencies, 590+ companies, also 0.2%. Scheduling and Booking carries 2,000+ companies at a crowdedness score of 6.1, high but nowhere near the 10.0 of Ecommerce Platforms, and it has 100+ small-software companies proving the category monetises at small scale. Invoicing and Billing runs a 13.5% small-software density across 490+ companies, and Accounting and Bookkeeping 12.1% across 280+, both categories where small tools demonstrably work.
There is a reason for the omission, and it is not that YC missed them. These are good businesses, not venture-scale ones. A tool serving 640+ nonprofits will not return a fund. That is precisely why they are interesting if you are not raising: the absence of venture interest is what keeps them uncrowded. Our low competition SaaS ideas and profitable micro SaaS research are built around exactly this gap between fundable and profitable.
The acquisitions data quantifies the alternative path. Across our live listings, SaaS startups average $517K in asking price on $221K trailing revenue at a 10.6x profit multiple. That is a real outcome available without a batch, an RFS or a term sheet, and our buying versus building analysis walks through the trade.
The failure mode with any Request for Startups is treating it as permission. An RFS tells you what a specific set of investors finds fundable this cycle. It does not tell you a customer is waiting, and it does not transfer conviction to you.
CB Insights’ long-running post-mortem analysis puts “no market need” as the top reason startups fail, at 42%. That failure mode is not solved by picking your idea from a list of ideas investors like. If anything an RFS increases the risk, because it supplies enough external validation to skip the step where you go and check.
A more useful sequence, and the one our 8-stage validation framework is built around:
If you want to run that sequence against a specific idea, the idea validation tool and the pain point database are the two places to start, and how to find startup ideas that get funded covers the fundability question specifically.
Every quote below is from a public forum, anonymised to the subreddit. They are the raw material behind the verdicts above.
“Getting SOC2 certified the first time was almost 2 years of work, requiring a 4-5 person IT team, a 2-person security team...” – r/sysadmin
“Sometimes I can’t find the referral paperwork, and it slows everything down. We need a better way to track all these records.” – r/dentaloffice
“The official Harmonized Tariff Schedule site is... not exactly beginner friendly. Endless PDFs, tiny text, and no quick way to tell if an extra Section 301 duty applies.” – r/SupplyChainLogistics
“My freelance income and investments make taxes a nightmare every year. Need software that could handle all my income types and tell me what I owe without surprises.” – r/consumerfinance
“I’m curious how other Canadian small business owners or consultants handle the technical documentation side of SR&ED claims. Do you usually use spreadsheets, templates, or something more automated?” – r/canadasmallbusiness
“It concerns me that so many of the drivers coming through don’t seem to be able to parse what a BoL or SDS is telling them.” – r/Truckers
Notice how many of these sit inside the compliance and physical-work requests, and how few map to consumer AI. That distribution is the finding.
Score your own idea against the same data. Every number on this page came from the same corpus you can query directly: 1M+ complaints, 17,000+ funded companies, 30,000+ companies taking real payment, and revenue on 3,700+ startups. Instead of guessing whether an RFS theme has demand behind it, check.
Validate an idea against the data →Every figure on this page was queried on August 30, 2026. Counts are rounded down. We list the limitation of each source alongside it, because a source without a stated weakness should not be trusted.
| Source | What it measures | Used for | Limitation |
|---|---|---|---|
| YC RFS (primary) | YC’s published Fall 2026 requests | The 13 requests and YC’s stated reasoning | Refreshed each batch cycle, so it dates quickly. Captured Aug 30, 2026 |
| Funded DB | 17,000+ funded companies with AI-scored momentum and attractiveness | Category momentum, competitive field per theme | Round sizes and dates are unpopulated, so no dollar figures. Scores are model-generated |
| Stripe index | 30,000+ companies taking real payment, AI-classified | Category density, saturation, agentic frontier | Stripe-only, so it misses businesses on other processors. Price tiers are mostly unknown |
| Complaint corpus | 1M+ complaints across Reddit, G2, Capterra and app stores | Whether the pain is documented, and quotes | Complaints skew to categories with vocal online users. Silence is not absence of pain |
| Capterra pain points | Systemic issues with market-gap and severity scores | Compliance, construction and education verdicts | Skews to established B2B categories with review volume |
| TrustMRR | Revenue and growth on 3,700+ startups | Growth-versus-revenue reality check | Self-reported revenue, skewed to indie founders who publish numbers |
| Product Hunt | Launch volume and votes | Builder crowding in the agent themes | Votes measure launch-day attention, not product success |
| Acquisition listings | 630+ live listings with revenue and multiples | Crypto secondary-market thinness, SaaS exit benchmarks | Asking prices are seller-set and usually above clearing price |
Three things this analysis cannot do, stated plainly.
It is backward-looking. Every source measures companies, complaints and payments that already exist. YC is making forward bets, most explicitly on consumer AI, where the argument rests on a token-cost curve that has not finished falling. Backward-looking data is the wrong instrument for judging a claim about a moment that has not arrived. We flag the contradiction because it is real and useful, not because it settles the question.
It cannot see enterprise or hard tech. Our corpus is commercial software with public reviews and public payment footprints. Defense procurement, offshore data centres and industrial sensing are invisible to it. Three requests got “no read” for that reason, and that is a limitation of our data, not a judgement on the requests.
Absence of complaints is weak evidence. Some of the most valuable problems are experienced by people who never post about them. The API change request is the clearest case: plausible, well-argued, and nearly invisible in a corpus built from public reviews. We marked it directional rather than unsupported for exactly that reason. Complaint data is a demand signal, not a business plan.
The Fall 2026 Request for Startups is Y Combinator's published list of 13 ideas its partners want founders to build, covering AI tutoring, defense hardware, a cloud for small software, multiplayer AI, offshore compute, consumer AI, aging and caregiving, an operating system for physical work, crypto rails, physical-world data collection, an internet trust layer, financial compliance infrastructure, and automated API change management. YC states plainly that these represent only a fraction of what it funds and that you do not need to work on them to apply.
Only where independent demand evidence agrees. An RFS is a statement of investor appetite, not proof that customers are waiting. In our scoring, four of the 13 requests line up with heavy documented complaint volume and thin existing tooling, four are directionally supported, and the consumer request actively contradicts our data: consumer is the lowest-momentum category across 17,000+ funded companies we track. Treat the RFS as a shortlist to validate, not a shortcut past validation.
The operating system for physical work. In our Stripe index, Home Services and Trades has 960+ companies already taking payment but only four we classify as small software, a density of 0.4%, one of the lowest of any category with real commercial volume. That is a market full of paying operators and nearly empty of modern tools, which is the exact shape you want. A cloud for small software and financial compliance infrastructure score close behind.
No. YC says explicitly that the RFS represents a fraction of what it funds and that founders do not need to work on these ideas to apply. Historically the majority of each batch arrives with ideas outside the published list. The practical value of the RFS is as a signal of which theses partners find fundable this cycle, which matters more for your framing than for your idea selection.
YC refreshes the RFS roughly each batch cycle, so several times a year. The Fall 2026 edition analysed here replaced the Summer 2026 list of 15 requests. Because the list turns over quickly, any analysis of it ages fast, which is why every figure on this page carries the date we queried it.
If the funding angle is what brought you here, what VCs are funding in 2026 and startup funding trends cover where capital is actually moving, and the funded startups database lets you browse the underlying companies. For the build side, SaaS ideas backed by pain points and how to find startup ideas start from documented demand rather than investor appetite.
For specific territory touched on above: vertical AI SaaS ideas covers the industry-specific angle YC’s physical-world request points at, the state of micro SaaS competition quantifies crowding, the state of indie SaaS revenue shows what these businesses actually earn, and building a moat in the AI era addresses the question every agent-infrastructure founder should be asking. Our revenue intelligence tool and market sizing guide are the practical next steps.
BigIdeasDB Research. (2026). YC Request for Startups 2026, Scored Against Real Demand. BigIdeasDB. Retrieved from https://bigideasdb.com/yc-request-for-startups-2026