IP Readiness

Prepare technical intellectual property for funding or M&A

Make code ownership, proprietary technology, patent coverage, licensing and unprotected inventions understandable before the investor or buyer asks.

Review formats

From an initial screen to transaction-ready technical material

3–5 business days

Readiness screen

Identify the first technology and IP questions an investor is likely to ask.

  • core technologies and owners;
  • employee and contractor assignments;
  • major dependencies and licenses;
  • urgent gap list.
Request a screen →
1–2 weeks

Full technical IP review

Connect the product, code, architecture, existing patents and invention candidates.

  • proprietary-mechanism map;
  • patent coverage and gaps;
  • third-party and open-source dependencies;
  • candidate portfolio and data-room readiness.
Discuss the full review →
2–4 weeks

Gap remediation

Create the missing technical material and processes before the transaction.

  • technical invention disclosures;
  • product-to-patent map;
  • descriptions of core technologies;
  • joint action plan with counsel and patent attorneys.
Prepare the data room →

Minimum paid engagement: 3 business days, from RUB 200,000 or the equivalent in another currency. After a short introductory call, scope, deliverables, validation method and price are fixed.

Review areas

What must be ready before the transaction

01

Code ownership

Employees, contractors, previous companies, joint development and assignment of rights.

02

Third-party dependencies

Open source, commercial libraries, license constraints and supplier criticality.

03

Core-technology map

Which mechanisms create product value and where they are implemented.

04

Patent-to-product mapping

Which existing patents cover the current architecture and roadmap.

05

Protection gaps

Important solutions without disclosures, filings or a clear trade-secret regime.

06

Candidate portfolio

New ideas, priority, owners and readiness for patent-counsel work.

07

Technical data room

Architecture, repositories, code provenance, licenses, patents and process evidence.

08

Risk-remediation plan

What to fix before the round, use as a deal condition or leave for the first 100 days.

Engagement model

KernelSoft is an independent expert practice

Maxim personally owns architecture, critical code, diagnostics and final technical review. Additional engineers or domain specialists are involved only by customer agreement, with roles and accountability defined in advance.

28+years
60+patents
14years at Acronis
2,400+citations

Discuss transaction preparation

Describe the upcoming transaction and current state of technical IP

Include the product, transaction type, code-development history, existing patents, major dependencies and the deadline for investor or acquirer material.

Target response time: one business dayNext: a short discussion → NDA → material checklist and review plan.