Owner notes / Preparation

Prepare for a data licensing review, without sharing your records

Make a short outline of the business, the systems you already use and the work they document. A useful first description does not need a single customer record.

If an operational data-licensing opportunity sounds relevant, the next question is often practical: what should you get together? Start smaller than a data export. Your goal is to help someone understand what the company does and whether its retained history merits a follow-up conversation.

This guide helps you produce one non-confidential company outline. It is not an acceptance test, a valuation method or an instruction to collect new data. Keep your underlying records in their existing systems while you prepare it.

The deliverable: a plain-language outline covering your business, office team, systems, approximate history, workflow examples and unresolved permission questions. No attachments containing records. No screenshots with names or account details. No credentials.

1. Describe the operation in ordinary language

Begin with what your business does and who does the work. A general description such as “commercial maintenance company with an office team managing requests, scheduling and project follow-through” is more informative than “we have lots of data.”

Distinguish the office operation from total company headcount. An owner may have a substantial field team, but the relevant operating history might sit with dispatch, administration, customer service or project management. Describe those functions without naming individual employees.

You can note the approximate size of the office team, how long the company has operated and the language primarily used in its workflows. Be accurate rather than trying to sound like an ideal candidate. The separate starting-profile page explains SID’s current published indicators; do not mistake this outline for a decision on eligibility.

2. List systems, not login details

Make a small inventory of the systems that already hold meaningful operating history. Include the category, what it is used for and roughly when the history begins. You do not need to export the contents or grant access to discover these basics.

System categorySafe description to prepareLeave out
CRMTracks company requests and sales follow-up; used across several operating years.Contact lists, customer names and individual deal records.
Project or task toolDocuments handoffs from office intake to scheduling and completion.Project exports, attached documents and access links.
Internal knowledge baseContains procedures and revised instructions for recurring work.Private policies, confidential text and staff details.
Support systemRecords how the team receives, assigns and resolves requests.Message transcripts, addresses and account information.

Keep system names at a level that your company is comfortable disclosing. If identifying a particular vendor or tool is itself confidential, describe the category instead. Never put passwords, API keys, recovery codes or private sharing links into the outline.

3. Separate company age from retained history

A company may have operated for a long time but retain only a shorter period in its current tools. State the difference. If the CRM was replaced, the older system was archived, or records were deleted under normal policies, make that clear at a high level.

You do not need a precise record count to begin. A practical outline might say “current project system used since 2022; older history exists in a separate archive and has not been reviewed.” That is an illustrative way to describe uncertainty, not a recommendation about how much history qualifies.

Do not restore backups, extend retention periods or collect additional personal information merely to improve this description. Any later request for records should have a legitimate purpose, a defined scope and the appropriate review.

4. Explain a workflow from start to finish

Choose two or three representative categories of work. Describe how a request arrives, which roles handle it, how exceptions are resolved and how the outcome is recorded. Use roles and stages, not real examples containing identifiable people.

For instance, an office workflow could move from a service request to internal triage, scheduling, a completion check and follow-up. Another could involve an estimate, internal approval, a project handoff and a close-out. The point is to show the connected process, not to disclose the underlying communications.

Where tools overlap, explain the connection in plain terms. “The office assigns the request in the task system and records the outcome in the CRM” gives context without giving anyone access. If the tools are not reliably linked, say that too.

5. Make a separate list of open questions

Before presenting the history as available to license, identify what you do not yet know about permissions. That could include customer confidentiality terms, vendor restrictions, contractor-created material or the presence of personal information.

You are identifying issues for the next conversation, not making legal conclusions. Do not paste confidential contract clauses into a general introduction to explain a concern. A short note such as “some customer confidentiality restrictions need review” is enough to flag it.

Our data-rights checklist goes deeper on these questions. Possession of records does not, by itself, establish permission to share them for a new purpose.

A worked non-confidential outline

The following is a fictional preparation example, not a client result, an accepted application or a statement that this business would qualify. Use the structure, not the details.

Business: An established service company with an office operation handling customer requests, scheduling and project follow-through.

Team: Office roles include customer service, administration and project coordination. Field staff are described separately.

Systems and history: A CRM, a project tool and an internal procedure library retain several years of history. Older archived material has not yet been assessed.

Workflow categories: Request intake to resolution; estimate approval to project handoff; procedure updates after recurring exceptions.

Open questions: Customer confidentiality terms and third-party content need review before any material is shared. Company authorization would be needed for a later agreement.

Notice what is absent: no names, contact details, messages, file attachments, account identifiers or promises about legal rights. The outline explains an operating profile while leaving the actual records where they belong.

6. Review the outline before using it

Read it as if a person outside the company were seeing it for the first time. Can they understand the office operation, the kinds of retained history and the questions still unresolved? Remove details that are unnecessary to that task.

  1. Check that the description reflects existing records, not planned systems or activity.
  2. Separate office functions from total workforce size.
  3. Label estimates, gaps and archives honestly.
  4. Remove personal details, confidential excerpts and access information.
  5. Confirm that the person making the inquiry is authorized to speak for the business.

You do not need to make the outline public. Keep it privately within your company until you decide to make an inquiry through the merchant’s intended channel. Business Data Match does not collect or evaluate it.

What happens after preparation?

If you proceed, the referral link takes you to SID’s owner page. Its initial inquiry asks about the business rather than requesting confidential-record uploads. SID then determines what follow-up, if any, is appropriate. Buyer interest, rights, data quality and written terms remain separate questions.

If a later conversation leads to requests for specific records, pause and understand the purpose, scope, authorized channel and agreements first. This guide does not authorize that transfer or guarantee that your outline will lead to an offer.

Merchant-process context: SID’s published business-owner overview, checked November 20, 2026. The outline and fictional example above are preparation guidance from Business Data Match, not an official SID application or legal checklist.