SaaS and Software Trademark Preparation

Step 1: Separate the company, product and feature names

List the legal entity, customer-facing product name, app icon and any sub-brand separately. Choose the candidate that genuinely identifies the source of the offering. Record independent use in the website header, app store, login screen and customer materials. Internal project names and descriptive feature labels should not be included merely because they appear in a roadmap.

Step 2: Write a delivery-and-function map

For each offering, write 'customers receive [download or online access] to software that performs [specific function]'. Separate paid hosted access, downloadable mobile or desktop software, and development or consulting supplied to others. Class 9 and class 42 are candidates to investigate, not a finished specification. If an app is simply an access point for a wider service, explain that relationship for professional classification review.

Step 3: Divide current use from genuine plans

Create two lists: available customer offerings and evidenced planned launches. Record the relevant market and how the mark appears for each. US use-based and intent-to-use applications have different requirements; a waiting-list page is not automatically proof of qualifying use. Never fabricate screenshots, sales or dates. Discuss the basis with the approved representative rather than selecting 'use' because the site is online.

Step 4: Build a scoped search and review packet

Include exact spelling, pronunciation, meaningful translations, related goods or services and target markets. Capture official search references and note similar names rather than declaring the name available. Reconcile the applicant with founder and agency ownership questions. Request an explicit mark/market/class scope, and identify any separately priced additional search, filing or later use-evidence step.

Hypothetical example: Browser tool plus desktop download

A fictional invoice-management startup sells hosted access and a separately branded downloadable desktop tool. It records each tool's function, delivery method and current use, then investigates class 42 for the hosted service and class 9 for the download with accepted local wording. It does not automatically add financial-service classes simply because invoices contain money. This illustrates briefing, not a class prescription, clearance opinion or proof of US use.

How Nomadic Go helps

Nomadic Go can review the proposed applicant, mark, market and plain-language goods or services, then coordinate a quote-first preliminary search or a separately reviewed filing route. The standard search covers one mark, one selected market and one class; written findings are preliminary screening, not a legal opinion. Multiple marks, countries or classes require an explicit approved scope rather than an assumed bundle. Professional fees and official charges are separate, and representation must be confirmed for the specific route before payment. Start with non-sensitive scope facts; private identity, contracts and use evidence go only through the secure dashboard after a reviewed request. We do not provide legal or tax advice, guarantee acceptance or promise an authority timeline. Substantive objections, opposition and disputes are not standard preparation work.

Important limitations: Nomadic Go provides assistance and coordination services only. We do not guarantee approval of any bank account, visa, or company registration application. All final decisions rest with the relevant bank, government authority, or regulatory body. We do not provide tax advice, legal opinions, or financial advice.

Does every SaaS business need both classes 9 and 42?

No. Class 9 includes recorded and downloadable software; class 42 includes SaaS and online non-downloadable software. Map what is actually supplied and confirm the relevant office's accepted terms. A class number alone does not protect every software-related activity.

Do I need to disclose my source code?

Not to explain the basic trademark search brief. Describe the customer function, delivery and brand without exposing code, security details or customer data. If specific private evidence is requested after review, use only the secure dashboard.

Can I file before launching the software?

The route depends on the market and facts. The US has an intent-to-use basis for a bona fide plan, with later requirements distinct from an initial filing. A future launch must not be represented as current use; confirm the basis and separate later work with the representative.

Does trademark filing require a US company?

Do not form a US entity just to answer that question. The existing US guide explains foreign applicants, domicile, filing basis and required US-licensed representation. Applicant suitability must be reviewed; an incorporation or registered-agent address does not replace that review.