Patsnap Open Skill Guide

A competitor patent landscape helps you compare where different companies are active and which technical approaches their patents may support. The comparison is only fair when every company is searched under the same technology scope, time period, and counting method. This guide shows how an AI Skill builds that common basis and explains the differences without turning patent counts into a leadership ranking.

Patsnap Open TeamInnovation IntelligenceAugust 31, 20266 min read

This partial comparison applies the same sulfide-electrolyte solid-state-battery query to five independently resolved company scopes and checks representative families for distinct technical signals. It is a decision-facing excerpt, not the completed competitive-landscape report.

Sample outputExcerpt from a partial run
Competitive patent landscape excerptDOCDB family counts · Aug 31, 2026

Five company scopes · sulfide solid-state battery evidence

Toyota has the largest subset under this exact query, while verified examples from GM, Samsung SDI, and CATL point to different technical emphases. The result supports deeper comparison, not a declaration of overall technology leadership.

108Toyota query subset
27LG Energy Solution subset
5company scopes compared
CompanyComparable countVerified evidence and next review
Toyota108US11201332B2 supports an architecture and safety signal; deep-read continuity and adjacent families next
LG Energy Solution27Comparable count verified; select representative manufacturing-route families before interpreting emphasis
Hyundai + Kia21Combined scope verified; resolve entity coverage and select material-route evidence
GM10US11217826B2 supports a sulfide-impregnated manufacturing route; compare process claims and continuity
Samsung SDI5US12341154B2 and US11682790B2 support electrolyte-composition signals; compare claims and collaborator roles
Evidence: reproducible Patsnap searches and verified representative patent families · cutoff 2026-08-31
What this supportsA normalized competitor comparison and a representative-family review queue under one defined query.
What this does not proveTotal solid-state-battery portfolio strength, product strategy, market leadership, patent value, or legal blocking position.
Compare the competitors in your field
Normalize company scopes before comparing activity and technical emphasis.
Try this Skill

Why competitor patent comparisons often mislead

A brand may represent several legal applicants, one family may create many publications, and each company may use different language or filing practices. Comparable analysis must resolve those differences before interpreting a chart.

The comparison should answer more than who has the largest subset. Readers need to see which technical routes each company emphasizes, which representative families support that view, where evidence is sparse, and what claim or product evidence would change the interpretation.

Independent company searches make the denominator auditable. A company-by-route matrix becomes decision-ready only after entity aliases and route tags are reviewed under the same rules.

How the Skill creates a comparable competitor view

The Skill uses the same research contract for every company so differences in aliases, filing behavior, or family size do not become false competitive conclusions.

Connected patent intelligence workflow · Step 3 of 5From field activity to company differences

This Skill uses a shared technology scope to compare companies. The resulting entity scopes and verified route signals can become the baseline for ongoing competitor monitoring.

1. Resolve each company scope

It maps brands to relevant legal entities and subsidiaries, records exclusions, and applies one technology and time boundary.

Output: auditable company scopes and alias lists.

2. Retrieve companies independently

It runs each scope under the same technical query and records caps, missing aliases, and result counts separately.

Output: comparable candidate populations with visible retrieval limits.

3. Normalize and verify

It aligns family rules, dates, jurisdictions, and route labels, then reads representative families instead of inferring strategy from titles or volume alone.

Output: a normalized company-by-route evidence matrix.

4. Interpret differences

It explains verified technical emphasis, counterevidence, evidence gaps, and which claim, family, product, or engineering review should follow.

Output: a bounded competitive comparison, not a leadership league table.

Why Patsnap

Patent analysis backed by connected records

Competitive comparison needs normalized assignees connected to families, claims, status, classifications, and technical evidence. Patsnap supplies those patent-intelligence relationships; the Skill ensures every company is compared under the same rules and keeps strategic hypotheses separate from retrieved facts.

Database foundationPatsnap links global patent bibliography, families, applicants, classifications, claims, legal status, citations, scientific literature, and enterprise signals. That connected database foundation makes the evidence easier to retrieve, reconcile, and audit.

Patsnap OpenPatsnap Open provides integration paths through APIs and MCP Servers so selected patent data and research tools can be used inside AI and enterprise workflows. The records support analysis; qualified reviewers still own legal interpretation and current-register checks.

Prepare, install, and run

What you need to provide

  • Technology scope and business question
  • Companies and relevant legal entities
  • Jurisdictions and comparison period

What the Skill keeps consistent

  • The same technical query for every company
  • One family and date rule
  • One route taxonomy and evidence standard

After defining the companies and common comparison basis, use the prompt below. The Skill will retrieve each company independently and show where evidence is comparable or incomplete.

Compare Toyota, LG Energy Solution, Hyundai/Kia, GM, and Samsung SDI in sulfide-electrolyte all-solid-state batteries. Resolve legal entities, use one query and DOCDB family rule, retrieve each company independently, verify representative families, and separate observations from strategic hypotheses.

Before using the result: Verify company aliases and subsidiaries, then review representative families and claims for each technical route before interpreting strategic differences.

How to use the competitor comparison above

The Sample shows which company populations are directly comparable and where representative patent evidence has—or has not—been verified. Use it to select families and technical routes for deeper review.

Do not conclude yet: that the largest subset is the strongest portfolio, that a low count is unimportant, or that patent activity proves product readiness, market leadership, or a legal moat.

Next research step

Deepen the competitor comparison

Move from comparable activity to the families, claims, and technical evidence that explain each company path.

Explore MCP Servers

Frequently asked questions

Does the largest patent subset prove leadership?

No. It is one activity measure under one query; technical depth, claims, status, products, and execution require separate evidence.

Why search each competitor independently?

It preserves entity scope and makes missing aliases, caps, and query differences visible.

Can a low-count company be ignored?

No. A focused family may still carry a distinct technical or legal signal.

Disclosure: This article describes a Patsnap product and links to Patsnap Open. Skill output supports research and does not replace qualified technical, commercial, scientific, regulatory, or legal review.