How to sell business data to AI companies

What does selling business data actually mean?

In a licensing transaction, an agreed copy of specified records is provided for an agreed use. It does not mean selling your company or handing over control of your software accounts. The contract defines what can be used, how it can be used, and what you receive.

1. List the tools your business runs on.

Start with the software names you already know. Think about where your team documents work, resolves issues, tracks orders, and records decisions. You can describe these systems without sending customer files.

• Google Drive or SharePoint: manuals, reports, procedures, and project documents.
• Slack or Microsoft Teams: work discussions and problem solving.
• Salesforce, HubSpot, or Zendesk: account history and support workflows.
• NetSuite, SAP, or other operating systems: inventory, orders, and fulfillment records.

2. Describe the records in plain language.

For each application, explain what your team uses it for and estimate how much data it holds. If you know the time period covered, include that too. “Four years of maintenance reports and repair notes” says more than “a large folder.”

Do not spend days reorganizing files before the first conversation. Red Deer Data’s intake asks about your applications and business so the opportunity can be reviewed before preparation begins.

An illustrative inventory for a business owner.

Imagine a fictional equipment supplier preparing its first inquiry. Its owner starts with a short inventory organized around the work the team does. This is an example of how to describe records, not a claim that these categories will receive an offer.

Add the approximate history available, estimated volume with units, and the person who understands each source. Mark unknowns as unknowns. You can describe these records without copying customer messages or uploading business files.

• Order system: orders and changes that show how requests move through fulfillment. Check whether earlier changes are retained or only the current status.
• Support system: questions, troubleshooting discussions, and resolution status. Note whether complete threads, internal notes, and attachments exist.
• Company drive: installation instructions and operating procedures. Identify which material the business created and which came from another organization.
• Known limitations: missing periods, duplicate exports, records held in another system, or material that needs permission review.

3. Request a bid and review the terms.

Submit your inventory and contact details through the intake. There is no cost to request a bid. If an offer is made, review the proposed amount, included records, permitted use, delivery requirements, and payment timing.

A specific offer is more useful than a generic price per gigabyte. The records and proposed license need to be considered together. Ask questions about anything that is unclear before accepting.

4. Prepare the approved copy.

After both parties accept the bid and terms, the approved licensing copy is prepared. Sensitive information needs review and de-identification, and the business needs authority to license the included material.

Your originals remain with your business. Start with the intake, not an unrestricted export or a shared password.

A worksheet for your Red Deer Data intake.

Copy this list into your own notes and repeat it for each application. The application, storage size and unit, years of data, and short description correspond to the information requested for each application in Red Deer Data’s intake. Use estimates where needed and mark anything you still need to check.

The final three entries are optional preparation notes for your team, not additional required form fields. Describe the records without pasting customer information, uploading source files, or sharing account credentials. When your overview is ready, start the intake.

• Application or system: __________
• Estimated storage size and unit: __________ MB / GB / TB / PB
• Years of data available: __________
• What your team uses the application for: __________. For example: ‘Customer support, equipment troubleshooting, and recorded resolutions.’
• Optional — record types and coverage: __________. Note whether conversations, attachments, historical changes, or only the current records are available.
• Optional — person who can explain this source: __________
• Optional — known gaps or restrictions to review: __________. Note missing periods, third-party material, or records that may need to be excluded.