Getting started
What to expect on a first call about licensing your data
By SourceX Editorial · Updated
Short answer
A first call about licensing your data is a metadata conversation: which systems hold your records, how many years of history you have, your peak full-time headcount and any contract or privacy restrictions. You are never asked for files, exports or credentials. The call ends with one decision: whether a metadata-only fit check is worth doing.
Key takeaways
- A first call covers your company, systems, history and restrictions, not the records themselves.
- A careful first call never asks for files, samples, exports, customer names or system credentials.
- Ten facts prepared in advance, from peak headcount to signing authority, answer most first-call questions.
- Nobody can state a value for your records on a first call, because value is known only once a buyer engages.
- The only outcome of a first call is a decision about the next step, and you can stop at any point.
What happens on a first call about licensing your data?#
A first call about licensing your data is a structured conversation about which records exist and whether they could fit a license, held before anything is shared. Expect questions about your business, your systems and your constraints, followed by an explanation of how the process works.
The call is not a price negotiation and it is not a technical review. Nobody looks at records, connects to systems or asks for samples. If the conversation points to a likely fit, the next step is a metadata-only fit check; if not, the call ends there with no obligation on either side.
A typical first-call agenda#
A typical first-call agenda moves from context to systems to constraints, then closes on next steps. The order matters, because restrictions you raise early decide which systems are worth discussing at all.
Expect the systems part to take the most time. That is where a founder learns that a helpdesk retired years ago may matter more than the current CRM, or that a project tool everyone treats as clutter holds the decision history a buyer would look for.
| Part of the call | What is discussed | What you leave with |
|---|---|---|
| Context | Why you are looking now: a migration, acquisition, succession plan or shutdown | A shared view of timing and urgency |
| Company profile | Years in operation, peak full-time headcount, legal entity and ownership | An early read on basic fit |
| Systems and records | Which tools hold support, CRM, project, job, order or engineering records | A short list of record families worth a closer look |
| Restrictions | Customer contracts, confidentiality terms, client-owned work, sensitive data | Known exclusions noted before any scoping |
| Process | How the transaction runs and who approves each step | A clear picture of what would happen next |
| Next step | Whether to run a fit check, build an inventory or stop | A decision you control |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Ten things to prepare before the call#
Ten things prepared before the call let you answer most questions from memory and keep the conversation on substance. None of them require exporting data; a page of notes or a simple spreadsheet is enough.
If you are unsure of an answer, say so. An honest estimate of accessible history is more useful than a confident figure that later turns out to hide a gap left by a migration.
- The legal entity that holds the records and who has authority to sign licenses for it.
- Peak full-time headcount, with contractors excluded, and how long the company has operated.
- Every system that holds operational records, such as Zendesk, Salesforce, Jira, ServiceTitan, NetSuite or Procore.
- Roughly when each system was adopted and whether it is still in use.
- Past migrations and what history was left behind in old systems or exports.
- Record families that connect a request to a decision and an outcome, such as tickets linked to fixes or quotes linked to orders.
- Customer, client or vendor contracts with confidentiality or data-use clauses you already know about.
- Sensitive content to flag, such as health, financial or other personal information about individuals.
- Anything off-limits: named customers, product lines, competitors or business units.
- Approvals beyond your own, such as a board, parent company, investors or lenders.
What you will never be asked for on a first call#
What you will never be asked for on a first call is any record itself: no files, exports, samples, screenshots or system access. The table shows what is requested instead, so your team knows exactly where the line sits.
Treat any request for credentials or bulk data on an introductory call as a warning sign, whoever makes it. A careful process collects descriptions first and moves records only after rights review, preparation and your written approval.
| Never requested | Requested instead |
|---|---|
| Files, exports or samples | Names of record families and the systems that hold them |
| System credentials or admin access | Who administers each system and whether exports are possible |
| Customer or client names | Whether customer contracts restrict how records can be used |
| Employee personal details | Peak full-time headcount as a single figure |
| Financial statements | A general company profile and ownership structure |
| Signed commitments | Your view on whether to take a next step |
Who from your side should join#
The people who should join from your side are the person who can decide and the person who knows the systems. In most companies that means the founder or CEO plus a COO, CTO or IT lead who can say which tools hold which records and how far back they reach.
Finance and legal usually join later. A CFO adds most once deal structure, payment timing and accounting treatment are on the table, and a general counsel once a rights review begins. If a parent company, lender or private equity sponsor will need to approve, mention it on the call so the process plans for it.
Illustrative: a consulting firm's first call#
Illustrative: the managing partner of a fictional operations consulting firm booked a first call while planning her succession. The firm had peaked above 50 full-time employees and kept proposals in a SharePoint library, pipeline in Salesforce, project reviews and playbooks in Confluence, and staffing decisions in its resource planning tool.
She arrived with the ten-item list and one concern: client deliverables. Her master services agreements gave clients ownership of the reports and models produced for them. The call noted that up front, so the discussion moved to records the firm created for itself: internal proposal reviews, staffing rationale, project retrospectives and methodology playbooks.
No files changed hands. The agreed next step was a metadata inventory of those internal record families, with client deliverables excluded from the start, plus a separate check of whether any client contract limited internal reuse of project notes.
What happens after the call, and how SourceX runs it#
What happens after the call depends on fit, and every later step needs your approval. SourceX runs licensing through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Supply starts with the metadata fit check; rights review and privacy preparation follow only if you choose to continue.
If a license goes ahead, SourceX documents it in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. Records are licensed, not sold outright, your company keeps ownership, and you can stop at any step before delivery.
Frequently asked questions
Will we hear what our data is worth on the first call?
No. There is no price list, and value is known only once a buyer engages with a specific, scoped package. A first call can explain which qualities tend to raise or lower value under the SourceX Enterprise Data Value Framework, such as human-generated signal, recency and privacy burden, without attaching a figure.
Do we need an NDA before the first call?
Usually not, because a first call covers descriptions rather than records. If you plan to discuss sensitive matters such as a pending sale or a shutdown, ask for a mutual NDA beforehand. Either way, keep customer names and confidential contract terms out of the conversation until they are actually needed.
Should our lawyer join the first call?
It is rarely necessary. Legal questions on a first call stay high level: whether contracts restrict use and who can sign. Counsel becomes essential at the rights review stage, when customer agreements, vendor terms and employee notices are checked in detail.
Can a company that has closed or been acquired still take a first call?
Yes. Operating, acquired and wound-down companies can all qualify. For a closed company, the questions shift to who now controls the records, whether the systems or exports are still accessible, and whether a wind-down officer, trustee or acquirer must approve.
What if our company is smaller than the typical fit?
Typical fit is a company with 50 or more full-time employees at peak and several years of history. Smaller specialized companies may still be reviewed when a buyer has a specific request for their kind of records, so it is worth describing what you hold.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.