Class 9 vs Class 42 for SaaS: Which NICE Class Should You File In?

TLDR: Most SaaS founders file in Class 9 because someone told them "software is Class 9." That's wrong half the time. Class 9 covers downloadable software. Class 42 covers software as a service. If your product is cloud-hosted and customers never download a binary, your strongest claim is in Class 42 — and many founders are filing in the wrong class, getting refusals, and paying for the rework. Below: a decision scorecard, the exact USPTO identification language to use, and the cost of getting it wrong.

Last updated: June 4, 2026.

Why does the Class 9 vs Class 42 question matter for SaaS founders?

Because the USPTO has narrowed how it reads Class 9 over the last decade, and a lot of older filing guidance is now out of date. TMEP §1402.03 requires that the goods or services description in an application be specific enough to match a single class — and for cloud-only software, that usually means Class 42, not Class 9.

The practical consequences of guessing wrong:

A non-final office action from an examining attorney, asking you to amend the class or the identification.
Two to four months of delay while you respond.
Additional USPTO fees if you need to add a class (each additional class is charged separately).
In the worst case, abandonment if you fail to respond within the statutory window.

Filing in the right class first is much cheaper than filing in the wrong one and amending.

What is NICE Class 9, exactly?

Class 9 is the "Scientific & Electric" class under the WIPO NICE Classification (currently the 12th Edition). The class header includes:

"Scientific, research, navigation, surveying, photographic, cinematographic, audiovisual, optical, weighing, measuring, signalling, detecting, testing, inspecting, life-saving and teaching apparatus and instruments; apparatus and instruments for conducting, switching, transforming, accumulating, regulating or controlling the distribution or use of electricity; apparatus and instruments for recording, transmitting, reproducing or processing sound, images or data; recorded and downloadable media, computer software, blank digital or analogue recording and storage media; … "

The key phrase for software founders is "recorded and downloadable media, computer software." Class 9 covers goods — physical or downloadable products. If a customer downloads your software (a desktop app, a mobile app binary, an installable client), it falls in Class 9.

What is NICE Class 42, exactly?

Class 42 is "Computer & Scientific Services." The header includes:

"Scientific and technological services and research and design relating thereto; industrial analysis, industrial research and industrial design services; quality control and authentication services; design and development of computer hardware and software."

And critically, it now expressly covers "providing temporary use of online non-downloadable software" — the entire SaaS business model.

If a customer accesses your product through a browser or API and never downloads a binary, your primary claim is Class 42.

Class 9 vs Class 42 — the decision scorecard

Run your product through these questions. Score each row, then read the result.

1. How does the customer access the product?

Browser-only / web app → Class 42.
Mobile app (iOS / Android) downloaded from an app store → Class 9.
Desktop client (Mac, Windows, Linux installable) → Class 9.
API or SDK that the customer integrates into their own product → typically Class 42; sometimes a Class 9 component if you also ship a binary.

2. Is anything actually downloaded onto the customer's device?

No — everything runs server-side → Class 42.
Yes — installer, .app, .exe, .apk, .ipa → Class 9.
Sort of — a thin client downloads but the substantive software runs in the cloud → Class 42 primary, Class 9 secondary.

3. What does the customer actually pay for?

A subscription that gives them access to your hosted system → Class 42.
A one-time purchase of a downloadable product → Class 9.
A platform fee plus per-use cloud compute → Class 42.

4. Do you also provide services on top of the software?

Pure software access → just the class above.
Software + professional services (implementation, consulting) → consider Class 42 for the services and Class 35 (Advertising & Business) if there's a managed-service component.
Software + a data product → consider Class 42 primary, with a possible Class 35 filing if you're selling business information.

5. What about a downloadable mobile app paired with a SaaS backend?

This is where most modern SaaS products actually live. The mobile app binary (downloadable from the App Store / Play Store) belongs in Class 9. The cloud-hosted service the app talks to belongs in Class 42. You file in both — that's the standard pattern for any product that has both a native client and a hosted backend.

What identification language should I use in the application?

The USPTO's ID Manual is the authoritative starting point. Use language that pulls directly from it where possible — the examining attorney is looking for exact-or-near-exact matches.

Class 9 — typical SaaS-adjacent language:

"Downloadable mobile applications for [specific functionality]."
"Downloadable computer software for [specific functionality]."
"Downloadable software development kits (SDKs) for [specific functionality]."

Class 42 — typical SaaS language:

"Providing online non-downloadable software for [specific functionality]."
"Software as a service (SAAS) services featuring software for [specific functionality]."
"Platform as a service (PAAS) services featuring software platforms for [specific functionality]."
"Application service provider (ASP) services featuring software for [specific functionality]."

Note the "for [specific functionality]" requirement. "Software for business management" is too broad. "Software for managing customer relationships and sales pipelines" is specific enough for most examining attorneys.

What does this cost if I file in both classes?

USPTO fees are charged per class. The current TEAS Standard application fee is in the low hundreds of dollars per class — see the current schedule for the exact number. A two-class application is roughly twice the cost of a one-class application; a three-class application is roughly triple. Filing in unnecessary classes is wasteful; filing in too few is risky.

For a typical SaaS startup with a web app, a mobile companion, and an API:

Class 9 — for the downloadable mobile app.
Class 42 — for the SaaS service and the API access.
Often a third class for marketing services (Class 35) if you're a marketing-tech product, or a data class if you're selling business information.

What do real SaaS portfolios look like at the USPTO?

Pick any well-known SaaS owner and run the breakdown. A few representative examples on WikiTrademarks:

Salesforce, Inc. — heavy in Class 9 and Class 42, with strong Class 35 (advertising/business services) and Class 41 (education) footprints.
Atlassian Pty Ltd — a textbook Class 9 + Class 42 SaaS profile with selective Class 16 (paper goods) for swag.
HubSpot, Inc. — Class 9 + Class 42 + Class 41 (education / content) — the same shape, with content investments showing in Class 41.

The pattern is consistent: SaaS portfolios cluster in 9 and 42 with strategic extensions into 35 (for marketing/data services) and 41 (for content and community).

What are the most common SaaS filing mistakes?

Filing only in Class 9 for a web-only SaaS product. The examining attorney will issue a refusal: nothing is downloaded, so Class 9 is wrong. Amendment is possible but adds months.
Filing in Class 42 only and then launching a mobile app. The app binary is technically Class 9. You may need a new application to cover it.
Using vague identification language. "Software" alone is not enough. The USPTO requires specific functionality.
Forgetting Class 41 if you ship a community or content product. Many SaaS companies build sizeable content / education arms (HubSpot Academy, Salesforce Trailhead, GitHub Learning Lab). Class 41 protects those.
Filing 1(a) "use in commerce" before you actually launch. If your product isn't yet shipping to customers, file 1(b) intent-to-use. The TMEP is unforgiving on this — see TMEP §900.

When should I consult a trademark attorney?

This guide is written for founders who want to make smart filing decisions and have a real conversation with their counsel. It is not legal advice. Specifically, get an attorney involved when:

You're choosing between filing your company name vs your product name (often you want both, in different classes).
You're filing internationally and need to coordinate U.S., EU, and other-jurisdiction strategies.
You've received an office action that isn't a simple amendment.
You're in a TTAB opposition or cancellation proceeding.
You're considering a coexistence agreement with a similar mark holder.

The Pro Se Filers index on WikiTrademarks shows what solo filings look like in practice — useful research, not a substitute for advice.

FAQ: NICE Class 9 vs Class 42 for SaaS founders

Should a SaaS startup file in Class 9 or Class 42?

For pure cloud-hosted SaaS where nothing is downloaded to the customer, Class 42 is the right primary class — specifically as "providing online non-downloadable software" or "software as a service (SAAS)." If you also ship a downloadable mobile or desktop app, add Class 9. Many SaaS products end up filing in both.

What is the difference between Class 9 and Class 42 for software?

Class 9 covers downloadable software and recorded media — goods that the customer downloads onto their device. Class 42 covers online, non-downloadable software and software-as-a-service — the cloud-hosted services model. The dividing line is whether anything is actually downloaded.

Can I file in both Class 9 and Class 42 in one application?

Yes. A single USPTO application can cover multiple classes. Each class incurs its own fee — see the current trademark fee schedule for exact amounts.

What if I'm not sure whether my product is downloadable?

If a customer installs anything on their device (a mobile app from an app store, a desktop client, a browser extension), there's a downloadable component and Class 9 is in play. If everything runs entirely on your servers and the customer only ever uses a web browser, Class 42 covers it.

What identification language does the USPTO recommend for SaaS?

The standard form is "providing online non-downloadable software for [specific functionality]" or "software as a service (SAAS) services featuring software for [specific functionality]." The functionality has to be specific — "business management" is usually too broad; "managing sales pipelines and customer relationships" is usually specific enough.

How long does a USPTO trademark application take from filing to registration?

Typical timelines run 8 to 14 months for a clean application with no office actions. Office actions add 2 to 6 months each. The USPTO Trademarks Dashboard publishes current average pendency.

How can I see how other SaaS companies have filed?

Use the WikiTrademarks owner profiles for any SaaS brand — start with Salesforce, Atlassian, or HubSpot — and look at the NICE class distribution. The pattern is consistent and informative.