A useful company technology profile connects a defined company and technology scope to patent routes, research activity, product signals, evidence gaps, and a decision-ready conclusion. This guide uses a real CATL example to show how the Company Tech Profile Skill structures that work.
Below is an excerpt from a real Skill run on CATL's battery and energy-storage R&D. It shows a route-level result while preserving the run's coverage limits.
Three battery routes, operating on different development clocks
CATL's evidence set points to a mature lithium-ion core, a nearer-term sodium-ion commercialization path, and a longer-horizon solid-state program.
What this supports
Orientation, follow-up research planning, and technical due-diligence scoping.
What this does not prove
Patent quality, FTO, future market share, product performance, or confidential R&D coverage.
Add its technology focus, your decision goal, and a time window to build an evidence map for your research.
What a company technology profile should answer
A company technology profile is an evidence-led assessment of one organization's position and direction in a defined technical field. It should explain what routes the company is working on, which routes look mature or emerging, whether direction is changing, and what uncertainty should shape the next decision.
The deliverable is not a company biography. It defines the legal entity and aliases, technology scope, time window, representative evidence, counting or sampling limits, risks, opportunities, and open gaps.
- R&D leaders can frame partnership or monitoring priorities.
- Due-diligence teams can identify claims that need deeper verification.
- Strategy teams can separate demonstrated technical activity from company messaging.
Why reliable profiling is harder than summarizing a company
Entity resolution comes first. A brand, parent, subsidiary, and registered assignee may not resolve to the same patent owner. In the CATL run, portfolio analytics returned the expected full results only with the Chinese registered entity name. Without that check, a search failure could look like a lack of activity.
Scale is the next problem. The portfolio was too large for a handful of recent patents to represent the whole company. Aggregate filing and classification views supported portfolio-level observations; a recent patent sample was used only to interpret mechanisms and emerging routes.
Evidence also moves on different clocks. Patent publication lag affects recent filing counts, while product roadmaps are not equivalent to technical validation.
Technical reasoning backed by innovation data
Why Patsnap fits this gap
The Skill can use structured patent and paper retrieval, record the evidence tier and coverage limitations, and preserve a query log, source index, claim ledger, and report. The Sample used Patsnap patent and paper research plus public web sources for product signals.
Database foundationPatsnap connects global patent records, scientific literature, company intelligence, and technical signals so mechanisms, organizations, and prior work can be checked against traceable sources. The database foundation strengthens discovery, comparison, and evidence provenance across R&D decisions.
Patsnap OpenPatsnap Open makes selected data and research tools available through APIs and MCP Servers for AI and enterprise workflows. The data supports retrieval and verification; experiments, engineering review, and business judgment still determine the decision.
How the Skill builds the profile
Company, topic, purpose, time
Aliases and ownership boundary
Portfolio trends and records
Papers, products, public evidence
Facts, inferences, gaps
A full run creates a request, workplan, method decisions, query log, source index, claim ledger, and report. These files make the conclusion auditable and expose where coverage was limited.
Prepare, install, and run
The minimum useful input is a company and a technology topic. Add the decision purpose and time window when possible. Optional details include known subsidiaries, jurisdictions, products, routes to test, and approved internal documents.
Build a technology profile for CATL focused on battery and energy-storage patent activity and R&D direction from August 2023 to August 2026. Separate verified facts, evidence-backed inferences, and open gaps. Record entity aliases, search coverage, representative evidence, and limitations.The Skill selects the strongest tools available. Structured patent and paper retrieval provides the strongest coverage; a lower evidence tier must be disclosed when the agent only has public web or supplied materials.
How to interpret and use the result
Read the scope before the conclusion. Confirm the entity, topic, time window, and purpose, then check whether each statement comes from full-portfolio aggregation, a representative sample, a paper, an official source, or company messaging.
In the CATL Sample, the three route labels guide follow-up work rather than acting as a final scorecard. A near-commercial label does not prove adoption. A dense patent cluster does not prove superiority. A public roadmap does not guarantee delivery.
Before a material decision, validate the evidence that matters to that decision. Partnership teams may need current capacity evidence; technical teams may need performance data; legal teams need a dedicated patent or FTO workflow.
Bring current evidence into your AI workflow
Connect your agent to patent, scientific, and engineering research tools for the next evidence-heavy question.
Frequently asked questions
Where can I find and install the Company Tech Profile Skill?
Open the Company Tech Profile page in the Patsnap Open Skill Hub to review the workflow and download it, or copy the installation command from the Skill card on this page.
Does the Skill require a Patsnap MCP connection?
No. The Skill can work with the research tools available to the agent. A Patsnap MCP connection can strengthen entity filtering, structured patent and paper retrieval, and record-level traceability when current evidence is required.
What information should I provide before running it?
Provide the company, technology topic, decision purpose, and time window. Known subsidiaries, jurisdictions, products, and routes can improve scope control, but they are optional.
Can the result be treated as an exhaustive profile or FTO opinion?
No. The result is research support with disclosed coverage limits. It does not establish portfolio completeness, infringement, validity, freedom to operate, or another legal conclusion.
Disclosure: This article describes a Patsnap product and links to Patsnap Open. Skill output is research support and does not replace qualified technical, commercial, scientific, regulatory, or legal review. Users remain responsible for validating evidence and decisions in their operating context.