This article builds on our earlier pieces, SBIR/STTR Reauthorized Through 2031: What Founders Need to Know Now and Strategic Breakthrough Awards: The Biggest New SBIR Opportunity for Founders? Those articles explain the broader reauthorization reset and the new commercialization upside created by the legislation. This article focuses on a quieter but highly important change that could materially affect how repeat applicants plan: beginning in fiscal year 2027, agencies will be required to impose proposal submission limits for SBIR and STTR solicitations.
For founders who have treated SBIR or STTR as a numbers game, this is one of the most important structural changes in the new law.
For years, one common pattern in the ecosystem was volume. Some companies built highly repeatable application machines. Some submitted across multiple topics. Some relied on frequent proposal activity as a core part of their non-dilutive funding strategy. Congress has now made clear that agencies will no longer be able to leave that question entirely open-ended. Starting in fiscal year 2027, the director of each agency’s SBIR or STTR program office must set a limit on the maximum number of Phase I and Phase II proposals a small business concern may submit in a single fiscal year.
That does not mean every founder should panic. It does mean that the era of assuming unlimited proposal volume is ending. The better question now is not simply whether your company can apply. It is whether your company is building the kind of focused, high-conviction submission strategy that this new framework will reward.
What the New Law Actually Requires
The statute adds a new administrative-burden reduction provision to Section 9 of the Small Business Act. Beginning with fiscal year 2027 and each fiscal year thereafter, the director of the SBIR or STTR program office at each federal agency must set, equally for all small business concerns, a limit on the maximum number of proposals that a company may submit in response to Phase I and Phase II solicitations published by that agency, including all components of that agency, during a single fiscal year.
The law gives agencies three ways to structure that limit. They may impose it on a fiscal-year basis, on a solicitation basis, or on a topic basis. In other words, Congress did not impose one universal cap across all agencies. It imposed a universal obligation to create a cap, while leaving agencies flexibility to choose the method.
That distinction matters.
The statutory change is certain. The practical experience for founders may still vary materially depending on how a specific agency chooses to implement the rule. One agency may set a simple annual ceiling. Another may use topic-based limits that change the way founders target technical opportunities. Another may take a solicitation-based approach that affects timing and sequencing more than total annual volume. The law creates the structure. Agency implementation will determine the day-to-day reality.
Why Congress Added Proposal Limits
Congress framed this section as a measure for reducing administrative burden. That is a useful clue about what policymakers were trying to address.
At a basic level, the change reflects concern that very high-volume proposal activity can strain agency review processes and potentially distort competition. When a relatively small set of companies can flood a program with repeated submissions across many topics or solicitations, the result may be a heavier administrative burden for agencies and a less balanced ecosystem for other applicants. The new framework appears designed to force more discipline into the front end of the process.
For founders, that means the strategic environment is changing in two ways at once.
First, agencies will likely have to become more explicit about how they want the application pipeline to function. Second, applicants will be pushed toward higher selectivity. A company that historically relied on broad submission volume may find that it needs a much sharper screening process, a stronger view on fit, and more internal discipline about where management time and proposal effort should go.
That is not necessarily bad for serious founders. In many cases, a more disciplined process may reward companies with better commercialization planning, tighter technical positioning, and a stronger understanding of which agency or topic is actually the right fit.
This Is a Bigger Deal Than It Looks
At first glance, proposal limits may sound like a narrow administrative rule. They are not.
For some companies, proposal volume has been part of the business model. If a team built its non-dilutive strategy around submitting repeatedly across many opportunities, the new framework could materially change the economics of that approach. Even for companies that are not high-volume applicants, the change matters because it will likely influence internal planning, external deadlines, proposal prioritization, and even how founders discuss grant strategy with investors and boards.
The most important shift is psychological. Many founders used to think about SBIR and STTR as systems where optionality could be preserved by applying broadly. Congress is now signaling that agencies should not simply absorb unlimited volume. That pushes founders away from a “submit everywhere and see what lands” mindset and toward a “pick the right opportunities and execute with discipline” mindset.
That shift is consistent with the broader tone of the reauthorization. Congress did not just reopen the programs. It added more structure, more security review, more commercialization focus, and more operational discipline. Proposal limits fit squarely inside that broader policy direction.
Agencies Have Flexibility, but Not Unlimited Discretion
One reason founders need to watch this closely is that the law requires action, but leaves meaningful room for agency design.
An agency may choose a fiscal-year limit, a solicitation-based limit, or a topic-based limit. Each approach could produce very different practical effects. A fiscal-year limit could force companies to ration submissions over time. A solicitation-based limit could make each release cycle more important. A topic-based limit could push applicants to narrow their technical spread and focus only on their best-aligned opportunities.
This means founders should resist a lazy assumption that “the cap is the cap.” The real impact will depend on how the relevant agency defines and operationalizes its limit. A sophisticated applicant will need to read agency guidance carefully, understand how different components are aggregated, and build an internal planning process that matches the agency’s chosen methodology.
The statute also requires the agency director to establish the proposal limit not later than 90 days before the start of fiscal year 2027 and each fiscal year thereafter. That timing provision matters because it should give applicants some advance notice, but it also means founders cannot wait until submission season to start paying attention.
There Is a Waiver Process, but Founders Should Not Build a Strategy Around It
The law includes a waiver mechanism, but founders should be careful not to treat it as an easy workaround.
On a topic-by-topic basis, the director of an agency’s SBIR or STTR program office may grant a waiver of the proposal limit at the time of a solicitation announcement if the topic is time-sensitive and urgent to the agency’s mission. But the waiver process includes multiple constraints. The director must provide a written justification to the Administrator and the relevant undersecretary, the approval authority may not be delegated, the undersecretary and the Administrator must approve or disapprove the request within 15 days, and the waiver cannot cover more than 5 percent of the agency’s SBIR and STTR topics in any fiscal year. Participating agencies must also maintain records on waived topics and the justifications for those waivers.
That is not a casual escape valve. It is a narrow exception for urgent mission needs.
For founders, the takeaway is simple: do not build your application strategy on the assumption that waivers will open up extra room. They may exist in exceptional cases, but they are not designed to preserve business-as-usual for high-volume applicants. They are designed to let agencies respond to genuinely urgent topics without being trapped by the general cap structure.
The Reporting Requirement Is a Signal Founders Should Not Ignore
Another important piece of the statute is the reporting requirement. Within 30 days after setting or changing a proposal limit, the head of the agency must provide Congress with the methodology for setting or changing the limit, the considerations used in doing so, and how many small business concerns are impacted based on historical data. In addition, when a waiver is granted, the agency must notify Congress and include relevant information about that waiver.
This matters because it tells founders two things.
First, agencies are expected to be able to explain and defend how they set these caps. Second, the implementation process is likely to be visible enough that companies paying attention should be able to develop a more informed view of how the environment is evolving.
In practical terms, this means the new limits are not just internal agency housekeeping. They are part of a broader oversight framework. Founders who follow these developments closely may gain an advantage over companies that treat the rule as a surprise only after it hits a solicitation.
Why This Could Actually Benefit Serious Founders
A change like this will understandably worry some applicants. But it may also create advantages for disciplined companies.
If proposal limits reduce pure volume play, the ecosystem may become somewhat more favorable to teams that are selective, commercially grounded, and deeply aligned with the problem they are trying to solve. A founder who has a clear view of customer need, agency fit, technical readiness, and commercialization pathway may benefit from competing in a system where mass submission is harder to use as a strategy.
This is especially true for companies that were never trying to build a grant factory in the first place. If your company sees SBIR or STTR as part of a targeted capital and commercialization strategy, rather than a broad probability game, the new limits may reinforce the importance of the exact approach you should already be taking.
That does not make the rule painless. It does mean the rule may reward quality and intentionality in ways the old environment did not always encourage strongly enough.
The Founder Mistake to Avoid
The biggest mistake founders can make here is to treat proposal limits as a late-stage operational issue.
They are not.
This change affects how you prioritize topics, how you allocate internal resources, how you work with outside proposal support, how you sequence agency engagement, and how you frame the role of non-dilutive funding inside the broader company strategy. A founder who waits until FY2027 solicitations are live to think about this is likely already behind.
The smarter approach is to start now.
If your company expects to be an active SBIR or STTR applicant in the coming years, this is the time to map where you have historically relied on submission volume, where your strongest topic fit really exists, and which agencies matter most. It is also the time to separate true strategic opportunities from “nice to have” applications that only made sense in a world of broader optionality.
What Founders Should Do Now
Start by auditing your current application model. If your plan depends on large numbers of submissions, assume that model may need to change. If your company has been opportunistic rather than disciplined in topic selection, now is the time to tighten the funnel.
Next, identify which agencies and components matter most to your business. Because the statute leaves implementation flexibility to agencies, founders need an agency-specific planning view rather than a generic understanding of “the new rule.” Watch for how your target agencies define caps, how early they publish guidance, and whether they appear to favor fiscal-year, solicitation-based, or topic-based limits.
Then, improve your internal prioritization process. In a capped world, every submission slot matters more. That means a stronger go/no-go framework, tighter alignment between legal and technical readiness, and more rigorous decision-making about where management attention should be spent.
Finally, update how you communicate this strategy externally. If you talk about non-dilutive funding with investors, board members, or strategic partners, your narrative should reflect that SBIR and STTR are becoming more structured and more selective. That does not weaken the opportunity. It means the company must show it is prepared to compete on focus, not just persistence.
The Bigger Takeaway
The new proposal-limit framework is one of the clearest signs that the post-reauthorization SBIR/STTR world will be more disciplined than the old one.
That is the real founder takeaway.
Congress restored the programs through 2031, but it also made clear that the system is supposed to operate with more structure, more scrutiny, and more selectivity. Proposal caps are part of that shift. They may frustrate applicants who built around volume, but they may also sharpen the ecosystem in ways that reward better companies and better planning.
At Veritas Global, we help founders evaluate the legal and strategic issues that shape SBIR/STTR readiness, including eligibility, ownership and governance structure, foreign-ties exposure, data-rights positioning, commercialization planning, and non-dilutive funding strategy. If your company expects to rely on SBIR or STTR in the years ahead, now is the time to make sure your application model is built for the post-reauthorization rules, not the old assumptions.
