Red Deer Data: how to prepare a business data licensing inquiry

What Red Deer describes publicly

Red Deer lists work conversations, documents, business-system records, and operational histories among its data categories.^[1] Its referral page currently identifies businesses with 20 or more employees, prioritizes U.S. organizations, and asks for primarily English material.^[2] The criteria help identify a potential route; intake submission does not establish acceptance.

For an owner, the useful starting point is a short explanation of the work behind the records. Describe a completed process and the systems that preserve it. If your business has several divisions, pick a coherent collection before proposing the entire archive. This makes it easier to identify who understands the records and who would need to approve further review.

Build a clear system inventory

List each relevant system, its purpose, the types of records it contains, and the approximate period available. Note whether the archive includes conversations, attachments, changes, and final outcomes. Identify the employee or contractor who can explain export limits and the meaning of the fields. You can prepare this inventory without granting anyone access.

Consider a hypothetical distributor with order records in one platform and exception discussions in another. The inventory should explain whether order references connect them, whether historical attachments survive, and which years overlap. That is more informative than saying the business has a CRM and an ERP. Keep customer names and confidential examples outside the initial description.

A useful inquiry can include approximate volume, but give the units. Messages, tickets, projects, files, and completed workflows are different measures. Explain how you obtained the count and whether it includes duplicates or automated records. If the count comes from an old export, note when it was created and whether anyone checked its contents.

Avoid spending heavily on preparation merely to produce a more impressive intake figure. A range supported by a known dashboard or system owner can be enough for an initial discussion. If Red Deer needs a more specific count later, ask what decision that count will support and what level of effort is appropriate at that stage.

Understand what the intake authorizes

Red Deer's website terms describe intake as a request to review a high-level inventory. They prohibit sensitive or raw source material in the form and state that submitting it does not transfer or license data. A separate agreement governs any transaction.^[3] Treat the application as the start of a conversation with its own limited purpose.

Within your organization, confirm who can submit accurate business information and respond to follow-up questions. Identify the separate person or group that can approve a sample, a commercial proposal, or a final delivery. Record uncertainty about rights directly. It is better to identify a question at intake than to make an unsupported statement that later complicates the review.

Use the correct link for an approved introduction

Red Deer's referral instructions require the business to start and submit intake through the referrer's personal link.^[2] If you choose to proceed through North Fox, use the exact link provided for that introduction. Keep the confirmation with your internal notes so that the company and the introducer can coordinate the next step.

North Fox may receive compensation from a qualifying referral. Red Deer currently publishes a 5% referral reward capped at $100,000, with payment after the first delivery.^[2] That is a referrer program condition, not a valuation of your archive or a promised payment to your business. Your own proceeds and obligations belong in the separate commercial proposal.

Ask about the proposed preparation process

Discuss which records would be included, which categories would be excluded, and who would prepare the approved copy. Ask how the proposed review handles narrative text, attachments, identifiers, confidential material, and references between records. The answer should match your actual formats and workflow rather than relying on a generic label.

Request a clear approval sequence. Identify when your organization reviews the scope, the permitted uses, the prepared package, and the commercial terms. Determine who would store review copies and what happens if the opportunity does not proceed. Those questions let the person responsible for your systems assess the work before anyone starts a broad export.

Compare the proposal as a complete package

When a proposal is available, write down the amount, the collection covered, the recipients and uses, the preparation responsibilities, and payment conditions. Add any continuing deliveries or exclusive rights. A larger amount can come with a larger commitment, so compare the work and permissions alongside the price.

Separate contracted proceeds from potential future opportunities. If the discussion includes additional licenses, ask how those would be approved and reported. If payment depends on accepted delivery, clarify acceptance criteria and the procedure for resolving questions. Give your commercial and technical reviewers the same scope description so that both evaluate the arrangement being proposed.

Where nonprofit inquiries fit

The reviewed public pages do not confirm a nonprofit-specific purchase policy.^[1][3] A nonprofit with mature operations may have a collection worth discussing, but that is a case-by-case question. Original educational resources, research, media archives, and operational histories also differ enough that they may require different buyer routes.

Start by describing the material and its ownership, then identify mission requirements and any funding or contributor restrictions. North Fox's nonprofit review is designed to organize those questions before an introduction. For a business or nonprofit, the immediate next step is the same: prepare a broad inventory and ask whether a defined review would be useful.