How I think through IP strategy

The first question is not always “Should we patent this?”

A common starting point in IP conversations is, “Should we patent this?” That is an important question, but it is often too early and too narrow. Before deciding what to file, protect, disclose, license, or keep confidential, it helps to ask what the technology is trying to become.

A patent strategy only makes sense relative to the path the technology may take. A university invention being prepared for licensing has different needs than a startup product, an internal software tool, a joint development project, or an early research concept.

IP strategy is path-dependent

IP is often discussed as if it is only about protection. Protection matters, but strategy also involves timing, ownership, leverage, risk, disclosure, and commercialization fit.

A patent portfolio should not be designed in a vacuum. The relevant questions change depending on the path.

• If the path is startup formation, the IP may need to support defensibility and fundraising.
• If the path is licensing, the IP needs to be understandable and valuable to a potential licensee.
• If the path is joint development, ownership of improvements may be just as important as the original invention.
• If the path is product launch, freedom to operate and implementation risk may become urgent.
• If the path is continued research, preserving optionality may matter more than overbuilding the IP strategy too early.

A logical framework

This is not a universal formula, but I find it useful to separate the questions into a sequence.

Define the technology

What is the actual technical thing being considered? Is it a device, method, material, software workflow, biological process, data pipeline, model, manufacturing process, formulation, or system?

Identify the actual advantage

What makes it valuable? Is the advantage performance, cost, speed, accuracy, manufacturability, regulatory pathway, workflow fit, data, user experience, integration, or something else?

Separate the invention from the implementation

What is the inventive concept? What is merely one embodiment? What alternatives should be captured? What parts are essential, optional, or replaceable?

Identify the likely path to use

Is the technology most likely to become a startup, license, partnership, product, internal tool, grant-funded project, or continued research effort?

Match the protection to the path

Would patents, trade secrets, copyrights, contracts, data rights, licensing terms, or know-how matter most?

Check risk and dependencies

Are there third-party rights, open-source issues, data rights, collaborator rights, publication risks, or freedom-to-operate concerns?

Decide what matters now versus later

What needs to be protected immediately? What can wait? What should be documented? What should stay confidential? What should be revisited once the path is clearer?

The goal is not to answer every IP question at once, but to ask the right questions at the right stage.

Different paths create different questions

Startup path

For a startup, IP often needs to support both the product and the company story. It may matter for investor confidence, defensibility, partnerships, and future product direction.

• What is the defensible core?
• Does the IP map to the product roadmap?
• Are the claims tied to the value proposition?
• What would a competitor try to design around?
• Are there freedom-to-operate issues before launch?
• What should be patented versus kept as know-how?

Licensing path

For licensing, the question is not only whether the invention is protected. The question is whether the rights are clear and useful to another party.

• Who would want rights to this?
• What field of use makes sense?
• Is exclusivity necessary or harmful?
• Can the licensee actually practice the technology?
• Does the claim scope cover what the licensee values?
• Are there improvements or know-how needed to make the license useful?

Partnership or joint development path

In collaborations, the original IP may not be the only issue. The future IP may matter just as much.

• What is background IP?
• Who owns improvements?
• Who can use jointly developed work?
• What happens after the collaboration ends?
• What disclosures are allowed?
• Are incentives aligned?

Grant-funded development path

For grant-funded or non-dilutive development, IP strategy often needs to preserve future commercialization options while supporting a credible development plan.

• Does the IP support the commercialization narrative?
• Are disclosures being timed carefully?
• Are future licensing or startup options preserved?
• Are ownership and data rights understood?
• What milestones would make the IP position more valuable?

Product launch or internal deployment path

When the technology is close to being built or deployed, the IP conversation becomes more practical. FTO, dependencies, contracts, open-source software, data rights, and implementation risk may matter more than filing another patent.

• Can this be practiced without obvious blocking rights?
• Are third-party tools, datasets, or software licenses involved?
• What parts of the system create durable advantage?
• What should remain confidential?
• Are customer or vendor agreements affecting rights?

Continued research path

Sometimes the honest answer is that the technology is still too early. The best IP strategy may be to document carefully, control disclosure, and preserve optionality without pretending the commercialization path is already clear.

• What is still technically undefined?
• What needs more evidence?
• What disclosures are coming?
• Is a provisional useful to preserve options?
• What should be clarified before investing heavily in IP?

Three questions that often get blurred together

Patentability, freedom to operate, and protection strategy are related but not the same.

Patentability

Can we likely obtain claims on this invention?

Freedom to operate

Can we likely practice this product, process, or implementation without infringing someone else’s rights?

Protection strategy

What mix of patents, trade secrets, contracts, know-how, data rights, licensing terms, and timing best supports the path to use?

Patents are important, but not always sufficient

Patents can be very important, especially when the invention is detectable, claimable, enforceable, and central to the commercial value. But patents are not the only form of protection.

Depending on the technology, value may also come from:

• trade secrets
• manufacturing know-how
• data
• workflow design
• software architecture
• regulatory evidence
• customer relationships
• speed of execution
• contracts
• field-of-use restrictions
• integration expertise

The relevant question is not simply, “Do we have IP?” It is, “What kind of protection actually supports the path we are on?”

Common mistakes

Filing before clarifying the path

A filing may preserve options, but it should not substitute for thinking through use case, customer, licensee, or product path.

Treating patent count as value

A long patent list does not necessarily mean strong protection, strong freedom to operate, or strong commercial relevance.

Confusing patentability with freedom to operate

Getting a patent and being free to practice are different questions.

Ignoring ownership of improvements

In collaborations, future improvements may be more valuable than the starting technology.

Underestimating trade secrets and know-how

Some advantages are difficult to capture in claims but still commercially important.

Public disclosure before strategy is clear

Publications, pitches, demos, grant abstracts, websites, and conference materials can affect options.

Using the same playbook for every technology

Software, biotech, devices, materials, manufacturing processes, and AI systems may require different protection logic.

The mistake is often not too little IP activity, but misalignment between IP activity and the path to use.

A simple decision pattern

• What is the technology?
• What is the actual advantage?
• What path might it take to reach use?
• What protection matters for that path?
• What risks or dependencies need to be checked?
• What should be protected now?
• What should be revisited later?

IP strategy should be revisited as the commercialization path becomes clearer. A research project may become a licensing opportunity. A licensing opportunity may become a startup. A product concept may reveal FTO issues. A collaboration may create new ownership questions.

Strategy before paperwork

The most useful IP strategy is not necessarily the one with the most filings. It is the one most aligned with how the technology is expected to create value.

I find IP strategy most useful when it is tied to the real path of the technology, not just as protection in the abstract, but as part of how an invention becomes a product, a license, a partnership, or a usable system.

These notes reflect my own general observations and do not represent any current or former employer, client, or partner. They do not disclose confidential information and are not legal advice.