Protecting software, algorithms and datasets: a practical checklist
Which protection fits code, algorithms, models and datasets, how to build the asset inventory and what to hand your IP counsel before anything is published.
Read guideAI + engineering services
A new product usually raises the same questions at once: what is actually new, which standards your customers will ask for, what is worth protecting and how the product reaches customers. We answer them with your team in short, documented stages. First we look at the product itself and separate the new parts from the standard ones. Then we list the standards and certifications your buyers expect in each market and show where they overlap, so you test once wherever you can. We go through what deserves protection, such as code, models, data, methods and brand, and recommend the right tool for each: copyright, trade secret, trademark or a conversation with a patent attorney. The result is a staged product plan with owners, evidence and dates, and a view of how each part makes money: direct sale, licence or partnership. Where a registration makes sense, we prepare a technical brief your IP lawyer can work from. Each stage ends with a workshop and a written playbook, so your team can run the process without us. If the plan calls for software, the same team builds it: ERP, CRM, AI, mobile apps or IoT monitoring. Work is priced per stage, and anything extra is billed at a fixed hourly rate.
Start with your workflow. We agree the first deliverable, data boundaries, scope and budget before work begins.
What we can deliver
Workflow in focus
For example, a small manufacturer has developed a camera-based method for spotting defects on its production line, plus a dashboard for operators. Walking through the work separates what is new (the detection method and its labelled image set) from what is standard (the dashboard). The plan lists the quality standards its customers expect in each export market, recommends copyright registration for the code and a trade-secret policy for the image set, and flags the detection method for a conversation with a patent attorney before anything is published.
The final design follows your systems, documents and operating requirements.
Map approved data sources, access rules, retention and provider use before connecting AI to company information.
Scope EU servers or self-hosting and disclose the processing location of model APIs, logs and backups.
Agree where AI may suggest, where it may act and where a person must approve the next step.
Yes. Start with one workflow, one team and an agreed outcome. We scope the pilot after learning about your data, systems and constraints.
We can scope EU-hosted or self-hosted options. The proposal identifies where each component processes and stores data, which providers are involved, and any transfer or remote-access implications. EU hosting alone does not establish compliance.
We start with your current workflow and systems. The proposal identifies the integrations, data access and handoffs needed for a useful first deliverable.
From idea to implementation
Which protection fits code, algorithms, models and datasets, how to build the asset inventory and what to hand your IP counsel before anything is published.
Read guideBuild a technology roadmap that separates new from standard parts, uses maturity levels, names the evidence for each stage and turns into tracked work.
Read guide