Portfolio Analysis in Kraków.

A patent portfolio analysis Krakow R&D leaders can act on starts where this city’s economy does — with software, engineering and the multinational research centres that write it. Kraków is Poland’s largest technology and business-services hub outside Warsaw: Motorola Solutions runs its biggest research and development centre in Europe here, ABB has operated its Corporate Research Center in the city since 1997, Comarch is headquartered in Kraków, and Cisco and IBM run large engineering teams alongside a busy game-development scene led by Bloober Team. For a research centre or a software house the questions asked of a patent estate differ from a manufacturer’s: how patentable are our computer-implemented inventions, who owns what our engineers create, and which families are worth the annuity?

The work is landscape, gap, strength and valuation analysis — not litigation. It is the freedom-to-operate map behind a new software platform, the invention-harvesting review a large R&D centre needs, the utility-model layer that protects incremental hardware, and the pruning decision that stops an estate overspending at the UPRP and the EPO. PerspireIP builds those studies for the software, engineering, deep-tech and game-development portfolio owners across Kraków and the wider Lesser Poland region.

Why patent portfolio analysis Krakow R&D owners frame around software

In Warsaw a portfolio review often begins with a financing round or a pharma estate. In Kraków it begins with software and engineering. This is Poland’s second technology capital and its densest concentration of multinational research centres. Motorola Solutions employs well over 1,600 specialists in what is its largest R&D centre in Europe and one of its largest worldwide, spanning radio, video security, analytics and cybersecurity. ABB’s Corporate Research Center, running since 1997, houses interdisciplinary teams across dozens of labs. Comarch is headquartered here with thousands of engineers, and the city hosts Cisco, IBM and a thriving games cluster around Bloober Team.

That base changes the deliverable. A patent portfolio analysis Krakow owners can use has to read an estate the way a software or engineering organisation does: as freedom to ship the next release, as leverage in a cross-licence, and as a set of inventions that mostly begin life inside an employment relationship. So the study grades how patentable the computer-implemented families really are, maps freedom to operate across enormous rival assignees, checks that ownership actually flows to the company, and separates the crown-jewel families from the long tail that only costs renewal fees.

• Platform and FTO clearance — freedom-to-operate landscaping before a new software or hardware product ships
• Cross-licensing leverage — which of your families carry weight against a rival’s estate in a negotiation
• M&A and diligence — validity, ownership chain and product coverage of a target or an R&D-centre spin-out before a deal
• Board and budget reviews — a periodic strength, gap and renewal-cost picture for the CTO and general counsel

Software and computer-implemented-invention patentability: EPO vs UPRP practice

The single fact that reshapes a Kraków review is that most of the city’s inventive output is software. Neither Europe nor Poland patents software as such. Article 52 of the European Patent Convention excludes programs for computers “as such” from patentability, and the Polish Industrial Property Law contains the parallel exclusion. What both systems will protect is a computer-implemented invention that produces a further technical effect — a technical solution to a technical problem — rather than a pure business method or presentation of information dressed up in code.

That gap between what engineers build and what is actually patentable is where a portfolio quietly wins or loses value. The EPO has a mature, predictable body of practice for assessing the technical character of a claim and for isolating the technical features that can support an inventive step. UPRP examination applies the same statutory exclusion but sees far fewer software cases, so for many Kraków estates the European route is where the CII strategy is really fought and won. A review has to grade each family for genuine technical character, not just for grant.

So a patent portfolio analysis Krakow software owners can rely on reads each family against that test. We flag the claims whose technical effect is solid and the ones that would struggle in an EPO opposition or a Warsaw validity attack, map coverage to the shipping product and the roadmap, and identify the white space — the genuinely technical improvements in the codebase that have not yet been captured. For a research centre generating hundreds of disclosures a year, that triage is the difference between a defensible estate and an expensive pile of paper.

Layering utility models (wzór użytkowy) over incremental engineering

Poland gives an engineering-heavy estate a tool many software-first teams overlook: the utility model, or wzór użytkowy. The UPRP grants a utility model for a new and useful technical solution concerning the shape or construction of an object — a device, not a method or a program — for a maximum of ten years from the filing date. Crucially, the substantive bar is lower than a patent’s: the solution must be novel, but there is no separate inventive-step requirement, so incremental hardware improvements that would fail as inventions can still earn real, enforceable protection.

For Kraków’s hardware, IoT, telecoms-equipment and device teams that opens a deliberate layering strategy. The core architecture goes to patent, at the UPRP or through the EPO; the stream of smaller mechanical and structural refinements that surround it goes to utility models, which are cheaper, examined more quickly, and still give an exclusive right that can be asserted in the same specialised court. A single product can sit behind a patent umbrella and a fence of utility models covering the specific implementations a competitor is most likely to copy.

A portfolio review reads that layer explicitly. We check which device families are carrying utility-model cover and which are exposed, flag inventions filed as patents that might have been faster and cheaper as utility models (and the reverse — utility models that undersell a genuinely inventive advance), and watch the ten-year ceiling, because a utility model cannot be renewed beyond it the way a patent runs to twenty. Getting that mix right is a quiet but real source of value for a Lesser Poland engineering estate.

R&D-centre invention harvesting and employee-invention ownership

Kraków’s estates are built inside employment relationships, so ownership is a first-order question, not a footnote. Under Article 11(3) of the Polish Industrial Property Law, where an invention, utility model or design is made in the course of employment duties, the right to obtain the patent belongs to the employer — not the inventor — unless the parties have agreed otherwise. That default protects a research centre, but it is exactly that: a default that a badly drafted contract, a contractor arrangement or a cross-border secondment can override.

The other half of the rule is remuneration. Unless the parties agree otherwise, the creator is entitled to remuneration for the commercial exploitation of the invention, and where no amount was agreed it is set in due proportion to the profits the business earns from it, taking account of how the invention was made and the creator’s role. For a large Motorola- or ABB-scale centre that turns employee-invention terms into a live financial and compliance issue, and Polish case law on increasing that remuneration has been anything but settled.

A portfolio analysis stress-tests the chain of title before it ever reaches a data room. We trace each family back to its inventors, check that assignments and employment or contractor terms actually vest the rights in the company, flag foreign-secondment and joint-development gaps, and confirm the remuneration position is documented rather than left to litigate later. For an R&D centre planning a filing programme it also underpins invention harvesting — a repeatable capture pipeline that turns engineers’ disclosures into owned, filed and graded assets instead of ideas that walk out the door.

Poland outside the UPC: national validation and enforcement

Poland is a full member of the European Patent Convention, but it has not joined the Unitary Patent or the Unified Patent Court, and there are no current plans to do so. For a Kraków estate that has two concrete consequences. First, there is no unitary patent covering Poland and no UPC opt-out decision to make for Polish effect — a European patent takes effect here only through classic national validation at the UPRP. Second, Poland is not a party to the London Agreement, so validation requires a full translation of the granted specification into Polish, filed within three months of grant.

That translation cost is a real budgeting lever, and a patent portfolio analysis Krakow owners commission has to price it. Full-text Polish translation is materially more expensive than the claims-only validation available in London Agreement states, so the review reads which European families genuinely warrant Polish validation, which markets a filing programme should prioritise, and where a national UPRP filing might serve better than validating an expensive European grant.

Enforcement stays national too. Infringement and validity of a classic European patent validated in Poland run under Polish rules — invalidity before the UPRP and administrative courts, infringement before the Warsaw Regional Court — rather than through a pan-European UPC action. That insulates a Polish estate from a single central revocation attack, but it also means cross-European enforcement has to be assembled country by country. We grade each family for where it can actually be asserted and defended, so the estate is read against the enforcement system that really governs it.

The specialised Warsaw IP court for technical cases

Since 1 July 2020 Poland has channelled intellectual-property disputes into specialised divisions rather than general civil courts. The reform created dedicated IP divisions in five regional (district) courts of first instance — Warszawa, Poznań, Gdańsk, Lublin and Katowice — with appeals to specialised divisions of the courts of appeal in Warsaw and Poznań. The aim was concentration of expertise, and for technical rights it went further than that.

The Warsaw Regional Court holds exclusive nationwide jurisdiction over technical matters. That covers inventions and patents, utility models, computer programs, topographies of integrated circuits, plant varieties and the technical secrets of an enterprise — precisely the categories a Kraków software and engineering estate lives in. Wherever the parties sit, a patent, utility-model or software-secret dispute is heard in Warsaw, which means Polish precedent on validity and claim construction for technical rights is building up in one forum rather than a patchwork.

For a portfolio owner that concentration is useful intelligence before any dispute begins. A single specialist first-instance court and a defined appeal route make outcomes more predictable and let an estate be graded against a coherent body of technical case law. We read each family with that forum in mind — how its claims are likely to be construed, where validity is soft, and which assets are strong enough to carry an assertion — so the analysis reflects how a Polish technical dispute would actually be fought.

How PerspireIP builds a patent portfolio analysis Krakow teams can act on

Every engagement follows the same disciplined path, scaled to whether you are clearing a platform, defending a budget, prepping a data room or planning next year’s filings. We inventory the portfolio, verify legal status and ownership, map each asset to products and competitors, grade strength, CII patentability and enforceability, and price the estate for the decision that prompted the review.

• Full inventory with legal-status, term and renewal timeline for every asset across the UPRP, EPO and national routes
• Product-to-patent coverage mapping and a claim-strength score across the estate
• Software and computer-implemented-invention patentability grading against EPO and UPRP practice
• Utility-model (wzór użytkowy) layering review for hardware and device families
• Chain-of-title and employee-invention ownership checks under Article 11(3) of the Polish IPL
• Renewal-fee pruning recommendations plus a valuation view for financing, M&A or licensing, delivered as data-room-ready exhibits

We work alongside your in-house IP team, R&D leadership or outside counsel as a specialist analysis partner, deliver to your release or budget calendar, and keep every engagement confidential. Whether you need a one-time diligence study before a Kraków acquisition, a CII-patentability and freedom-to-operate read for a new software platform, or an annual portfolio health check for the board, we scale to fit. Send us the assignee name or a patent list and we will scope the work within one business day.

IP Landscape & Resources in Kraków

Key intellectual-property authorities and venues relevant to Kraków:

• Patent Office of the Republic of Poland (UPRP) — grants Polish national patents and utility models, examines applications, and handles validation of European patents and invalidity proceedings
• European Patent Office (EPO) — grants the European patents that must be validated at the UPRP to take effect in Poland, and sets the practice that governs computer-implemented-invention patentability
• Regional Court in Warsaw (Sąd Okręgowy w Warszawie) — the court with exclusive nationwide jurisdiction over technical IP cases in Poland — patents, utility models, computer programs and technical secrets
• AGH University of Science and Technology — Kraków's leading technical university, a major source of the region's engineering and deep-tech inventions and spin-out IP

Request a Patent Portfolio Analysis in Kraków

Explore related PerspireIP services: Patent Portfolio Analysis services · IP services in Poland · patent invalidation · patent infringement analysis · patent monetization · patent market research.

Frequently Asked Questions