QSBS for SaaS Companies: Qualification Guide
SaaS companies can qualify for Qualified Small Business Stock (QSBS), but being a software company is not enough. Consulting, implementation, custom development, and other service activities can complicate the Section 1202 active business test and put the QSBS exclusion at risk.
The stakes are now even higher: eligible stock acquired after July 4, 2025 may qualify for an exclusion of up to $15 million. This guide explains where SaaS companies can run into QSBS problems, how the rules apply, and what founders can do to protect their eligibility.
Key Takeaways
Here’s what SaaS founders should know before assuming their stock qualifies for QSBS:
- SaaS companies can qualify for QSBS, but being a software company does not automatically satisfy Section 1202.
- At least 80% of the company’s assets must generally be used in one or more qualified active businesses during the applicable period.
- Consulting, implementation, custom development, and other service activities can complicate QSBS eligibility, particularly when they fall within an excluded field or become a significant part of the business.
- Stock issued after July 4, 2025 may benefit from the new $75 million gross asset threshold and, for eligible shareholders, a higher $15 million exclusion limit.
- SaaS companies should track stock issuance dates, asset use, business activities, and capitalization as they grow. Contemporaneous documentation can make a future QSBS position significantly easier to support.

Can a SaaS Company Qualify for QSBS?
Yes, nothing in the tax code excludes SaaS companies from QSBS. To qualify, a SaaS company generally needs to:
- Be an eligible domestic C-corporation, not an LLC, S-corp, or partnership
- Stay under applicable gross asset limit, $50 million for stock issued on or before July 4, 2025, or $75 million for stock issued after the date
- Meet the 80% active business test, at least 80% of the company’s assets are used in the active conduct of the software business
- Satisfy the rest of Section 1202’s conditions including how the stock was issued and how long it’s held
The active business test can become more complex when a SaaS company provides consulting, implementation, custom development, or other services alongside its software product.
Why QSBS Can Be More Complex for SaaS Companies
The challenge is how many SaaS companies actually get built. A company may start as a U.S. domestic C corporation with the long-term goal of building a scalable software product, but initially rely on consulting, implementation, custom development, or other services to generate revenue.
SaaS itself is not a problem for QSBS. The complexity arises when software and service activities operate side by side. Section 1202 generally requires at least 80% of the value of the company’s assets to be used in the active conduct of one or more qualified trades or businesses, while certain service fields, including consulting, are specifically excluded.
For a SaaS company, QSBS eligibility may therefore require closer analysis when:
- Service-related activities become a significant part of the business. Assets used to support consulting or other nonqualifying activities may make it harder to satisfy the 80% active business test.
- Real estate or other non-operating assets become significant. Section 1202 contains separate limitations for certain real estate and portfolio assets, making the company’s overall asset mix important.
- The business increasingly depends on individual skill or reputation. Section 1202 excludes businesses where the principal asset is the reputation or skill of one or more employees, which can become relevant when the company operates more like a professional service business than a scalable software product.
The key question is not simply how much revenue comes from software versus services, but what activities the company actually conducts and how its assets are used to support them.
The 80% Active Business Test for SaaS
The 80% test is not a one-time requirement at incorporation. It must be met for substantially all of the period the stock is held, which can be challenging for a growing company.
Qualifying assets generally include those used to operate the software business, such as servers and infrastructure, intellectual property, and product-related receivables. Nonqualifying assets include idle investments and cash held beyond the business’s reasonable operating needs.
This can be especially relevant for SaaS companies after a funding round. A large cash balance does not automatically hurt QSBS eligibility if the funds are reasonably required for working capital, research and development, or near-term business expansion. However, cash that remains idle or is not tied to reasonably expected business needs may become harder to treat as an asset used in the active conduct of the business, so companies should document the intended use of financing proceeds rather than assuming all cash automatically supports the 80% active business test.
SaaS vs. Consulting and Implementation Services
Selling software is different from selling consulting, even when the same company offers both. IRC Section 1202(e)(3) specifically identifies consulting as an excluded field, alongside law, health, accounting, and certain other service businesses. As a result, SaaS companies that also provide consulting or implementation services may need to evaluate whether those activities affect their ability to satisfy the Section 1202 requirements.
The key issue is therefore not just the proportion of service-related assets on the balance sheet. It is also the nature of the activities generating that revenue. Hourly billing for custom implementation work may be treated more like consulting. By contrast, recurring subscriptions that provide customers access to a shared software product are more consistent with a qualifying software business.
Companies that combine services and software should assess which activity represents the core of the business.
What Changed for QSBS in 2025 and Why It Matters for Timing
Timing matters because the rule set depends on when the stock was issued. The OBBBA, signed July 4, 2025, made QSBS meaningfully more valuable, but the improved terms only apply going forward, not retroactively.
| Stock Issued on/before July 4, 2025 | Stock issued after July 4 ,2025 | |
|---|---|---|
| Gain exclusion cap | $10M | $15M , indexed for inflation after 2026 |
| Gross asset limit | $50M | $75M, indexed for inflation after 2026 |
| Holding period for full benefit | 5 years (all-or-nothing) | Tiered: 50% at 3 years, 75% at 4 years, 100% at 5 years |
If your cap table includes shares issued before and after that date, the two tranches are governed by different rules, which is exactly the kind of detail that should be flagged in an attestation, not assumed.
4 Ways SaaS Founders Can Protect Their QSBS Position
None of these are mutually exclusive, and which one fits depends on where your company is in its service-to-SaaS journey. If your company is part service business, part SaaS, these are the practical ways to stay on the right side of the rules.
Here’s what each looks like in practice.
1. Review Real Estate and Non-Operating Assets
Early-stage SaaS companies are usually asset-light, which cuts both ways: a small total-asset base means it’s easy to blow past the 10% real estate limit even with modest holdings. Most startups already avoid buying real estate to conserve cash as a SaaS company pursuing QSBS, and go a step further by avoiding prepaid leases too.
If you do hold prepaid leases while running both a SaaS and a service line, you’ll need to justify how that value is allocated between qualifying (software development) and non-qualifying (service) activity. There’s little established guidance on how to make that allocation defensible, so the simplest fix is avoiding prepaid leases altogether.
2. Make a Clean Transition
A long bootstrapping runway isn’t realistic for most founders, so starting with service work to build reputation and cash before pivoting to SaaS is a common path. The part people get wrong is the pivot itself.
Once you decide to make the shift, actually shift headcount and assets toward the software business instead of letting the service side linger. Companies that make this transition can still qualify for QSBS, but only if the asset-use tests are met during the relevant period, not just on paper.

It also helps to hold off on fundraising until the pivot is genuinely done, so the company’s assets clearly show a qualifying business by the time new stock gets issued.
3. Maintain Detailed Documentation
If your company has both qualifying and non-qualifying activity going on, start tracking asset allocation now, not after the fact. Note which assets support the software side and which support the service side, and hang onto records of development costs and how headcount is split. If the IRS ever asks you to prove the split, this is what you’ll be handing them.
4. Consider Whether a Separate C Corporation Is Appropriate
Some founders don’t want to manage a gradual pivot at all. Depending on the circumstances, they may consider separating the SaaS business from the existing service entity or forming a new C corporation, which can create a clearer distinction between the service and software activities.
In some structures, the new C corporation may receive assets in exchange for stock rather than cash. However, the tax treatment of the transfer and whether the newly issued stock qualifies for QSBS depend on the specific transaction, including the assets transferred and the requirements of Sections 1202 and 351. It takes careful legal and tax planning to structure properly, but a separate entity may help avoid some of the qualification issues that can arise when service and SaaS activities remain combined.
How to Document QSBS Eligibility for a SaaS Company
QSBS eligibility must be supported with records that remain reliable years after the original transaction. This documentation is especially important during an acquisition, financing, or a shareholder’s claim for the Section 1202 exclusion. Keeping records at the time of each event is far more effective than attempting to recreate them later.
At a minimum, a SaaS company should maintain:
- Stock issuance records: Issue dates, share amounts, and recipient details. QSBS eligibility is determined on a stock-by-stock basis, not at the company level.
- Gross-asset records for each issuance date: The $50 million/$75 million threshold is evaluated at specific points in time, making dated financial snapshots essential.
- Cap table history: A record of ownership and structural changes, particularly around financing rounds or a transition from services to SaaS.
- Documentation of software and service activities: Records showing how company assets and operations are allocated between qualifying software activity and service-based work, which supports the 80% active-business test.
A formal QSBS eligibility attestation consolidates this in one place, turning scattered internal records into a documented Section 1202 position that a shareholder, investor, or acquirer can rely on.
FAQS
Can a SaaS company qualify for QSBS?
Yes. SaaS companies can qualify for QSBS if they satisfy the requirements of Section 1202. They’re usually domestic C-corps from the start and tend to be asset-light, which helps with the 80% test. The complications arise when a SaaS company also runs a meaningful service business alongside the product.
Does a SaaS company have to generate 100% software revenue to qualify for QSBS?
No. QSBS eligibility is not based on the percentage of revenue generated from software. The key question is whether at least 80% of the company’s assets, by value, are used in the active conduct of one or more qualified trades or businesses during the applicable period.
Can consulting or implementation services affect SaaS QSBS eligibility?
Yes, in two ways. Service-related assets count against the 80% test directly. But consulting is one of the fields Section 1202(e)(3) excludes outright, regardless of how the asset percentages shake out. If a meaningful chunk of the business looks like billed consulting work rather than productized software, it’s worth getting a real answer on which side of that line the company actually sits.
How does the 80% active business test apply to SaaS companies?
The test looks at how the company’s assets are actually used and generally must be satisfied throughout substantially all of the shareholder’s holding period. For SaaS companies, assets supporting software development and operations may count toward the 80% requirement. Cash may also qualify when it is reasonably required for working capital, R&D, or near-term business needs, while excess cash held without a documented business purpose may require closer analysis.
Can a SaaS company lose QSBS eligibility as it grows?
Yes. A company that starts out clean can drift out of compliance as it raises capital, builds up cash reserves, or lets a service line grow faster than the product business. That’s the whole reason the active-business test has to hold for substantially all of the holding period, not just on day one.
What records should a SaaS company keep to support QSBS eligibility?
At minimum: stock issuance details, gross asset snapshots at each issuance date, cap table history, and a documented breakdown of how assets are split between software and service activity.
How do I know if my SaaS company currently qualifies?
QSBS eligibility depends on both issuance-date requirements, such as the gross asset test, and requirements that apply during the shareholder’s holding period, including the active business test. A QSBS eligibility review or attestation can help document these requirements using the company’s historical financial, capitalization, and operating records.
Get a Defensible QSBS Attestation
For SaaS founders, QSBS qualification is a real selling point for investors and a tax advantage at exit, but moving from services to SaaS creates real compliance risk if it isn’t handled precisely. Whether stock qualifies often comes down to how assets are valued and documented when shares are issued.
Eqvista’s valuation team provides QSBS attestation for tech companies, delivering clear and defensible reports that let investors confidently claim their exclusions. Contact us to see where your company stands.
