Engineering review
We sit down with the developers and pull out the technical features: data, computation, signals, nodes, interfaces.
DeliverableA map of protectable parts of the product
Filing
We are building a product
The commonest mistake is waiting for a “finished product”. By launch the solution is already public and part of the protection is gone for good. The review makes sense once a prototype works and the architecture is settled.
From architecture to application 3 steps
Novelty check
A search of patent databases and relevant non-patent sources against the extracted features.
DeliverableAn opinion on patentability
Drafting
We formulate the technical effect and prepare claims, description and drawings for examination.
DeliverableA filed application with a priority date
What backs this up
Software engineer by trainingQualified for inventions, software and databases
The architecture is reviewed by an attorney with an engineering degree — there is no intermediate translator between the developer and the claim.
What gets patented is not an idea but a technical solution: a sequence of operations, a configuration of nodes, a method of processing data. So the conversation starts not with paperwork but with how the product works inside and why it performs better than what exists.
This is probably you if
- You need to protect an algorithm, an AI model, a data-processing method, an interface, a device or a hardware-software system.
- You need to separate the technical effect from business logic and describe the solution in the language of patent examination.
- You need an application for Russia, the EAPO, the PCT or foreign national phases.
How it runs
- We review the product architecture with the developers and extract the technical features.
- We formulate the technical effect: accuracy, speed, robustness, security, fewer errors or lower resource use.
- We prepare the claims, description, drawings and the arguments for examination.