Define the collection before investing in preparation
The first conversation helps define the collection, the open questions and who could clarify them. You might begin with a period in a service system whose cases and outcomes are still connected. That is a more manageable subject than every record the company stores. With the scope identified, you can decide whether to seek further clarification, involve a colleague or pause the option.
AI training or evaluation may be a proposed use. That does not establish demand for your archive. Contents, context, necessary permissions, expected effort and an actual partner route must be considered together. The appropriate decision may be to investigate a particular part, clarify an outstanding issue or leave the option aside.
Begin with the records your organisation already understands
Support histories may connect a request, actions and a resolution. Correspondence may show the development of a project. ERP, accounting and CRM systems can contain linked business events, while process documents record how work was carried out.
These are categories for describing an archive, not a list of confirmed buying programmes. The data-types guide helps you identify useful distinctions. For your first enquiry, describe the relationships in general terms rather than supplying real examples.
Own software is a separate category. A deliberate code enquiry needs its own questions about original development, earlier public availability, history and rights. General archive information does not establish code eligibility.
Identify engineering records separately
CAD models, assemblies, drawing sets and design revisions can form a distinct technical archive. Record whether those relationships are recognisable and whether the material comes from your own work, customers or suppliers. The specialist CAD offering on Industrial Data Licensing covers that context in greater detail. This voluntary link opens a different website without transferring your enquiry answers. For a mixed archive, you can continue here and describe the technical and general records together in one enquiry.
Define the proposed use before discussing terms
Selling a business, transferring particular rights and licensing a defined use of records are different decisions. A possible licence would need to specify the parties, records, permitted purpose and conditions. The wording “sell company data” does not establish that every record can be transferred or that ownership of the company changes.
We apply M&A thinking to that preparation: establish the subject, decision-makers and release boundaries. About BRIDGERS explains our operator and intermediary role. We do not promise that a buyer will accept the archive or that a transaction will result.
Keep permissions and protection visible
An archive may combine employee work, customer contributions, third-party material and personal information. Access to a system does not establish permission for every further use. Different companies within a group may also require different decisions.
You can record the position as unclear. The personal and confidential records guide helps organise questions for the responsible people. Any actual review must address the proposed purpose and relevant countries; the word European does not settle the law, storage location or cross-border access arrangements.
Start with an overview you can already give
Describe the categories, approximate period, known or estimated quantity, context and your role. Unknown amounts remain unknown. Use the inventory worksheet if records are spread across several systems. For an insolvency situation, the separate guidance addresses scope and procedural decision-making.
Keep files, message contents, code, repository links, client or project identifiers, contracts and credentials out of the first contact. A concrete partner introduction requires separate documented authorisation. Later examination, transfer, preparation and use of source records need their own agreed basis. The process guide explains those decision points.