Portfolio-wide prioritization

Patent portfolio analysis

Prioritize a defined patent portfolio for a specific business decision, using criteria your team can inspect and challenge.

For IP leaders allocating research effort across a portfolio.

A focused assignment first. Deliverables, responsibilities, timing and fee agreed before research begins.

The decision behind the research

Which patent families deserve attention for product alignment, maintenance, licensing, diligence or deeper technical review?

Ready to connect shortlisted families to products? Explore mapping.

Common reasons to commission this work

  • Annual portfolio review
  • Maintenance-fee decisions
  • Licensing and divestiture preparation
  • M&A diligence
  • R&D and product alignment

Choose the research around the decision and what you already know. A full programme is not required to begin a conversation.

What you receive

A defined work product for your team’s next review.

A normalized family-level workbook, documented criteria, reasoned priority tiers and a shortlist of recommended review tracks.

  • Normalized family-level dataset
  • Technical taxonomy
  • Transparent prioritization framework
  • Ranked family cohorts
  • Product and market alignment notes
  • Executive findings and next actions

What the evidence is based on

Family records, ownership and status information, technical categories and agreed product or market inputs. The relevance and completeness of each input affect the analysis.

How your team reviews the result

Test the rubric on a representative cohort. Agree the factors, weights, treatment of unknowns and extent of manual claim review before applying it more widely.

How sources and uncertainty are recorded

See the work

Which patent families should receive the next round of manual research?

A patent portfolio review organizes patent analysis around a defined prioritization decision, with visible ranking criteria and manual review where agreed.

Each factor is equally weighted here and uses 0 = no signal, 1 = partial signal, 2 = documented signal. Different decisions require different factors.

Review the fictional demonstration to see the fields, reasoning and limitations. The output for your project is agreed during scoping.

Fictional demonstration. All source excerpts, products, patents and dataset values are illustrative, not client work.

Portfolio prioritization demonstration
FamilyScreening factors (0–2 each)Total / tierReason / action
DEMO-01Product alignment 2; evidence availability 2; current business relevance 26 / priority reviewStrong documented alignment; undertake full selected-claim mapping.
DEMO-02Product alignment 1; evidence availability 1; current business relevance 24 / investigatePotential commercial relevance; confirm product features and missing sources.
DEMO-03Product alignment 0; evidence availability 1; current business relevance 01 / deferLimited signal for this business question; retain for separate counsel-led maintenance review.

What you can hand over first

Start with the decision your portfolio review must support.

Use a representative subset that your team understands to test the criteria, treatment of unknowns and extent of manual review. Agree the size around the decision and available information.

Product relevance

Screen families against agreed product lines, features or business priorities.

Typical output within the agreed scope: Priority cohorts for mapping, with relevance rationale and missing inputs.

Discuss this scope

Licensing investigation

Identify families that may justify candidate-product or market-use research.

Typical output within the agreed scope: A shortlist with technical relevance, observability and recommended investigation tracks.

Discuss this scope

Acquisition or divestiture review

Organize a defined asset set around the transaction team’s research questions.

Typical output within the agreed scope: A normalized dataset, technical cohorts, evidence gaps and issues requiring further review.

Discuss this scope

Deeper technical research

Allocate limited claim-review effort to the families most relevant to the agreed question.

Typical output within the agreed scope: Reasoned priority tiers with visible criteria and proposed next actions.

Discuss this scope

We confirm feasibility, milestones and a delivery schedule after reviewing the scope and available inputs. Your proposal identifies the project contact, research responsibilities and review steps.

Discuss your project

How the work is performed

Test the review criteria before applying them across the portfolio.

01

Clean

We normalize families, ownership, status and bibliographic records before scoring.

02

Classify

Families are grouped using a decision-specific technical taxonomy rather than generic labels alone.

03

Signal

We combine explainable legal-status, citation, market, product and evidence indicators.

04

Prioritize

Shortlists include the reason for rank, known gaps and a recommended next action.

For the first discussion

You do not need a finished research brief.

A non-confidential description of the question, what you know and any deadline is enough to start. The following inputs help establish scope; do not upload sensitive materials with your initial inquiry.

  • Portfolio list or assignee scope
  • Business objective
  • Product and market priorities
  • Available internal classifications and prior work
Agree handling arrangements before sharing confidential information

Scope boundaries

  • A universal or definitive patent value score
  • Formal valuation or legal opinion
  • Automated scoring without reviewable factors
  • Patent drafting or prosecution

Technical findings are structured for review. Legal conclusions and final business decisions remain with the appropriate decision-makers.

Discuss delivery and review responsibilities

Before you reach out

Patent portfolio analysis questions

How do you rank patents?

Ranking factors are chosen for the specific decision and shown in the deliverable. We avoid presenting a composite number as objective truth when the underlying signals require context.

Is patent portfolio analysis the same as valuation?

No. Analysis can identify commercially relevant evidence and prioritize assets. A formal valuation additionally requires a defined valuation purpose, financial assumptions and an appropriate valuation professional.

Can internal product data be included?

Yes, under an agreed security workflow. Internal product mappings often improve decision relevance, while public and internal evidence remain clearly distinguished.

Does a ranking determine which patents should be abandoned?

No. A screen helps prioritize further review for a specified question. Renewal, validity, enforceability and financial decisions require additional information and appropriate decision-makers.

How is this different from a landscape?

Portfolio analysis starts from a defined set of assets. A landscape searches a technology field to build and interpret a broader dataset. They can complement one another but answer different questions.

How do we get a quote?

Describe the question and what you already know. We discuss fit and a practical scope, then agree deliverables, responsibilities, timing and a fixed fee before work begins.

Useful research guidance

Start with a conversation

Tell us what you’re trying to understand.

We’ll discuss whether we can help, what information is available and how the work could be scoped.

Discuss your project