Leadership and readiness
How to discuss potential data licensing revenue before a deal closes
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Before a deal closes, talk about a data licensing opportunity as an investigation with a stage, a cost and named evidence gaps, not as revenue. Keep it out of the base forecast and the cash plan until an agreement is signed with defined consideration, and treat cash as cash only when it arrives. Until then, share the stage reached, what would move it, and what it costs to find out.
Value drivers
Data licensing value no
Key takeaways
- Until an agreement is signed, the honest output is a decision to investigate, not a revenue figure.
- Tie every stage to evidence a third person could check, and let the stage decide the wording and the forecast treatment.
- Keep unsigned opportunities out of the base forecast; if you model them at all, do it as a separate, labeled scenario.
- Signed is not recognized, and recognized is not received; keep the three apart in every report.
- Count the management time the investigation will take, because that cost is real before any income is.
How should a company discuss potential data licensing proceeds before a deal closes?
Describe it as a scoped investigation with a stage, a cost and an owner, and keep it out of revenue, the base forecast and the cash plan until a signed agreement defines what will be paid and when. That is the decision rule. Everything else in this article is about applying it under pressure from a board that wants a number or a team that has already heard one.
The rule exists because early data licensing conversations fail for reasons the company does not control: the buyer's scope changes, a customer contract turns out to restrict use, the records are thinner than they looked, or rights review takes longer than expected. A figure spoken in a leadership meeting tends to outlive all of those facts.
What leadership can decide now is whether the investigation is worth its cost. What it cannot decide yet is how much the data is worth to a particular buyer, because that question needs a defined scope, a rights answer and a counterparty.
Why does an unsigned data deal not belong in revenue or cash?
Accounting standards already draw the line this article recommends. IAS 37 says contingent assets are not recognized because doing so could record income that is never realized; a contingent asset is disclosed only where an inflow of benefits is probable, and recognized only once it is virtually certain. An unsigned licensing conversation sits well short of either test.
Even after signing, amounts that depend on things outside the company's influence are constrained. IFRS 15 lets a company include variable consideration in the transaction price only to the extent it is highly probable that a significant reversal of cumulative revenue will not occur, and it lists third-party actions among the factors that raise that risk. Delivery acceptance, usage-based payments and buyer approvals are exactly that kind of dependency. US GAAP has its own comparable rules, which your finance team or auditor should apply to the specific terms.
None of this forbids talking about the opportunity. It means the conversation belongs in the language of investigation and possibility, with the accounting answer left to the people who will sign the financial statements.
The pipeline qualification and forecast treatment worksheet
Use one row per opportunity and move it only when the evidence in the second column exists. The third and fourth columns then tell you what you may say and where, if anywhere, the opportunity appears in planning. Stages are cumulative: an opportunity cannot be at stage six without the evidence for stages one to five.
| Stage | Evidence that proves it | Language allowed in board and lender materials | Base forecast and cash plan treatment |
|---|---|---|---|
| 1. Idea | Someone has suggested the records might be licensable | We are considering whether to look into it | Excluded; no line item |
| 2. Eligibility screened | Company and data meet a published eligibility screen | We appear to meet basic eligibility; nothing is scoped | Excluded; investigation cost budgeted |
| 3. Inventory mapped | Systems, years, record counts and fields listed by the data owner | We hold these record types over these years | Excluded |
| 4. Rights triaged | Customer, vendor and employee terms reviewed for the candidate records | Rights review found no blocker for this scope, or found these limits | Excluded |
| 5. Scope accepted by a counterparty | Written confirmation of the scope a licensee wants to evaluate | A counterparty is evaluating a defined scope | Excluded; optional labeled scenario |
| 6. Terms proposed | Written offer with consideration, term, delivery and acceptance conditions | We have received a written proposal and are reviewing it | Excluded; scenario updated with the stated terms |
| 7. Signed | Executed agreement | We have signed a data license; recognition depends on delivery and acceptance | Included per finance's recognition judgment; cash timing per contract |
| 8. Delivered and accepted | Delivery record and acceptance notice under the contract | Delivery is complete and accepted | Recognized as finance determines |
| 9. Invoiced | Invoice issued under the agreement | Invoiced; collection pending | Receivable; not yet cash |
| 10. Cash received | Bank record of payment | Received | Cash |
What goes into each row of the worksheet?
The worksheet only works if every row carries the same inputs, defined the same way across opportunities. The dictionary below is the minimum; add fields, but do not drop these.
At a glance
What goes into each row of the worksheet
- Opportunity ID and owner: one accountable person, usually the executive sponsor, not the person most excited about it.
- Record scope: the systems, record types, years and approximate record counts under discussion, as stated by the data owner.
- Stage and stage date: the highest stage whose evidence exists, and the date it was reached.
- Evidence link: where the proof for the current stage is stored, so a board member or auditor could check it.
- Open evidence gaps: the specific facts not yet known, such as whether a customer master agreement permits the use.
- Investigation cost: estimated hours by role (finance, legal, data, operations) to reach the next stage.
- Opportunity cost: the planned work that will slip if those hours are spent here.
- Risk notes: customer, employee, privacy or reputational concerns raised so far, each with an owner.
- Decision owner and next decision date: who decides whether to continue, and when.
How should the opportunity sit in your CRM and forecast?
If you track the opportunity in a CRM, make the system's forecast logic agree with the worksheet instead of overriding it by habit. In Salesforce, opportunity stages map to forecast categories (Pipeline, Best Case, Commit, Closed and Omitted), and Omitted is excluded from forecasts. Owners can override the category on their own opportunities, so set an explicit rule: a data licensing opportunity stays Omitted until stage seven.
HubSpot calculates a weighted amount as the deal amount multiplied by the stage's probability, and manual edits to the probability stop it from updating automatically. A weighted amount on an unsigned data deal is a guess multiplied by a guess. Leave the amount blank until stage six, and keep these deals in a separate pipeline so they do not inflate the sales forecast that the operating plan depends on.
If the board wants to see possible upside, show it as a separate scenario with its assumptions written next to it, never folded into the plan the company is managed against.
Keeping signed, recognized and received apart once a deal exists
Once an agreement is signed, the risk shifts from inventing revenue to blurring three different facts. Signed means a contract exists. Recognized means finance has decided, under the applicable standard, that revenue has been earned. Received means the money is in the bank. Each one deserves its own line in the monthly pack, with its own date.
At a glance
Keeping signed, recognized and received apart once a deal exists
Data licenses make the blur easy because delivery and acceptance often sit between signing and recognition, and payment can follow acceptance by weeks. A licensee may also have the right to reject a delivery that misses the agreed specification, which leaves recognized revenue exposed until acceptance is recorded.
Three habits keep the lines honest. Report the contract's stated consideration and conditions exactly as written, without rounding toward the hopeful reading. Record the acceptance date from the counterparty's notice, not from the day the files were sent. And keep data licensing receipts in a separately identifiable account or class, so a later diligence team can trace each one back to its agreement without asking for help.
- Signed: agreement date, counterparty type, stated consideration and conditions.
- Recognized: amount and period as determined by finance, with the judgment noted.
- Received: bank date and amount, linked to the invoice and the agreement.
What can you say to a board, lender or investor right now?
Say the stage, the evidence behind it, the next decision and what it costs to get there, in the wording from the worksheet. Do not give a figure before stage six, and after that give the contract's stated terms with their conditions, not a projection of what they might become.
Public companies face formal rules on forward-looking statements. Regulation S-K Item 10(b) encourages management projections only where they have a reasonable basis and are presented in an appropriate format. Item 303 asks management to discuss known events and uncertainties reasonably likely to make reported results a poor guide to future ones. A private company is not bound by those items, but they describe a sound habit: no projection without a basis you could show.
Lender communications deserve extra care, because credit agreements often define what counts in covenant calculations and lenders may rely on management statements. Agree the wording with your CFO before an opportunity appears in any lender update.
Worked scenario (illustrative): a field service company at stage four
The company below is invented to show how the worksheet reads in practice; the counts and durations are illustrative and imply nothing about any real deal.
A regional field service company with about eight years of work orders in one dispatch system hears from its CEO's peer group that service records are being licensed. The CEO asks whether to put the opportunity in next year's plan. Applying the worksheet: the company meets a published eligibility screen (stage two), its operations lead lists roughly 120,000 work orders with technician notes across eight years (stage three), and counsel reviewing the top 20 customer agreements finds that 3 restrict any use of service data outside the customer relationship (stage four, with a limit).
The board materials therefore say: the company holds eight years of work orders, rights review found limits for some customers, no counterparty has seen a scope, and the next step will take an estimated 30 hours of operations and 10 hours of legal time over six weeks. The plan carries no revenue and no cash for it. The investigation hours are budgeted.
The exception: a board member asks for a probability-weighted figure. The answer is that no amount exists to weight until a counterparty proposes terms, and that the scenario model will be built at stage six from the stated terms.
Which assumption changes the decision, and when to pull in specialists
The assumption that most often flips the decision is rights coverage: what share of the records the company can actually license after customer and vendor terms are read. If rights triage shows the usable share is small, the investigation cost may no longer be worth it, whatever a buyer might pay. Show that share as a range with its basis, and update it as contracts are reviewed.
Bring in finance before any figure enters a document that leaves the leadership team. Bring in counsel before rights triage, and before any statement to a lender or investor. Bring in the data owner before anyone describes record counts. If two of those three are not available in the quarter, the honest stage is two, and the plan should say so.
Getting an outside read before the number exists
An outside read can move an opportunity from stage one to stage two without anyone guessing at value. SourceX runs qualification, rights review, contracting, preparation and delivery for companies turning selected records into licensed datasets, and it opens with a short company assessment that needs no data upload.
For the inventory stage, a useful benchmark is that buyers usually want two or more years of consistent history and tens of thousands of records in one system, although rare work can qualify with less and each case is judged on its own. No records are delivered before the company has approved the scope and terms and signed, which is also the earliest point at which the worksheet allows a number into the plan.
How can an investor walk any stated potential value down to recognized revenue?
By testing the figure in five steps, each tied to a definition and a document: what the number counts, whether a contract exists, how much of each contract the accounting standard lets into the price, how much of that price has been earned, and how the revenue is presented. The page above tells a company what to say before a deal closes; these steps let an investor test any data company's potential, pipeline or transaction value:
- Define the figure. The SEC's 2020 guidance on metrics in public companies' MD&A says a metric should generally come with a clear definition, how it is calculated, any estimates or assumptions needed to keep it from misleading, and an explanation when the method changes. A private company owes none of this; an investor can still ask.
- Strike amounts without a contract. IFRS 15 accounts for a contract only when, among other tests, the parties have approved it and are committed to perform. Evidence: an executed agreement behind each surviving line.
- Keep only the transaction price, the consideration the company expects to be entitled to under the contract. IFRS 15 measures it as if the contract will not be cancelled, renewed or modified, treats an option priced at standalone selling price as nothing until exercised, and leaves out variable amounts that fail the constraint described above. Evidence: option, renewal and bonus clauses.
- Split earned from unearned. Price for deliveries made is recognized; the rest is remaining performance obligations, which IFRS 15 asks companies to disclose with expected timing, excluding constrained amounts. Evidence: delivery and acceptance records and a schedule of what is still owed.
- Check presentation. Whether revenue is the buyer's full price or only the company's margin is a separate principal-or-agent test, covered in this site's insight on gross or net recording; settle it before comparing with reported revenue.
Illustrative: how 100 units of stated potential value became 38 units of revenue
Most of this invented gap opens before any delivery question arises. Of 100 stated units, 58 rest on signed contracts and 38 were earned in the period. The 20 units of remaining obligations are real contract value awaiting delivery; the 42 units struck above them were never contract value at all.
It describes no company and no SourceX deal; amounts are units, not currency, computed line by line by a script held for reviewers. A: an indicative estimate, nothing signed. B: a one-time permanent license, delivered. C: a snapshot and two refreshes, one delivered, its price spread equally for simplicity where an accountant would allocate it. D: signed and undelivered, with a buyer refresh option added in the deck. E: a term license, delivered, counted with an expected renewal. F: delivered, with a bonus payable only if the buyer's model passes a benchmark:
| Bridge line (illustrative) | Units | Opportunities | Evidence for the line |
|---|---|---|---|
| Stated potential value | 100 | A to F, as summed in the deck | The figure's written definition and calculation |
| Less: no executed contract | -14 | A | No signed agreement on file |
| Less: refresh option not exercised | -12 | D | Option clause at standalone price, no exercise notice |
| Less: renewal not yet signed | -10 | E | Term end date, no renewal agreement |
| Less: bonus failing the constraint | -6 | F | Benchmark condition outside the company's control |
| Transaction price of signed contracts | 58 | B to F | Executed agreements and the price allocation |
| Recognized in the period | 38 | B, one of three C deliveries, E, F | Delivery and acceptance records |
| Remaining performance obligations | 20 | Two C deliveries, D | Schedule of undelivered promises with expected timing |
What do the value estimates on SourceX's own pages measure?
What SourceX might pay a company for its data, not anything SourceX earns. Its FAQ says a company sees an estimated licensing payout after the fit check, that an estimate is indicative and that not every qualifying company receives an offer. How-it-works says pricing stays indicative until a Dataset Deal Confirmation is signed, the exact payout is fixed in that Confirmation, and data that does not reach Closing earns no payment. Section 6 of the terms calls estimates, examples and sample figures on the site illustrative. Such an estimate sits on the supply side and fails step two: summed, estimates describe possible purchases, not revenue.
The revenue side is not public. The investors page says SourceX licenses data onward to AI developers in its own name and shares company and commercial metrics with investors directly, and section 5 of the terms says SourceX does not publish its commercial terms, so this page reconciles no SourceX figure. SourceX is raising from accredited investors under Rule 506(c), with materials on request at sourcex.si/investors. Ask any data company, SourceX included, for:
- the written definition of every value figure shown, including whether it counts amounts paid to suppliers or amounts due from buyers;
- the walk-down from that figure to the transaction price of signed contracts, each struck amount labeled by reason;
- remaining performance obligations with expected timing, and the delivery records behind recognized revenue;
- the principal-or-agent conclusion behind the revenue line.
Where can a potential-value walk-down mislead?
Allocation, the constraint and whether a license is a right to use or a right to access are accountants' judgments, and US GAAP reporters apply FASB's Topic 606, worded differently from IFRS 15 in places. Remaining obligations can still shrink through failed acceptance, termination or a buyer that cannot pay; IFRS 15 has a company revisit collectability when a customer's ability to pay weakens significantly. A low earned share is no verdict on a young company; the trend under one stable definition says more. And the walk-down ignores cost, margin and cash timing, which the worksheet above keeps apart.
Methods note: the steps, bridge and request list were drawn up on October 27, 2026 from IFRS 15 and the SEC's 2020 MD&A guidance, both verified through search excerpts on ifrs.org and sec.gov, and from SourceX's FAQ, how-it-works, terms and investors pages read the same day. The six opportunities are invented, a script with no randomness computes every line, and no company's contracts were sampled. This is general information, not accounting advice.
This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.
Sources for this section
- IFRS 15 accounts for a contract only when the parties have approved it and are committed to perform, defines the transaction price as the consideration an entity expects to be entitled to and measures it assuming the contract will not be cancelled, renewed or modified, accounts for an option priced at standalone selling price only when exercised, and requires disclosure of the price allocated to remaining performance obligations with expected timing. Source
- The SEC's 2020 guidance on key performance indicators and metrics in MD&A says a metric should generally be accompanied by a clear definition and how it is calculated, with any estimates or assumptions needed so it is not misleading and disclosure when the calculation changes. Source
- SourceX's FAQ says a company sees an estimated licensing payout after the fit check, that an estimate is indicative, and that not every qualifying company receives an offer. Source
- SourceX's how-it-works page says pricing stays indicative until a Dataset Deal Confirmation is signed, the exact payout is fixed in that Confirmation, and data that does not reach Closing earns no payment. Source
- SourceX's terms say estimates, examples and sample figures on the site are illustrative (section 6) and that SourceX does not publish its commercial terms (section 5). Source
- SourceX's investors page says it licenses business data onward to AI developers in its own name and shares company and commercial metrics with investors directly. Source
Frequently asked questions
Should a possible data licensing deal be in next year's budget?
Not as revenue or cash until an agreement is signed. Budget the investigation cost instead, mainly management and legal hours. If the board wants to see upside, show it as a separate, labeled scenario built from stated terms once a counterparty has proposed them.
What is the difference between pipeline value and contracted revenue?
Pipeline value is an estimate attached to an opportunity that has not been signed; contracted revenue rests on an executed agreement. Even contracted revenue is recognized according to accounting rules on delivery and acceptance, and cash arrives later still. Reports should keep signed, recognized and received as separate lines.
Can we use a probability-weighted amount for an unsigned data deal?
Only once a counterparty has proposed terms, and even then as a scenario rather than plan. Before that there is no amount to weight, and a stage probability borrowed from a sales pipeline does not describe rights review or buyer scope risk. CRM tools such as HubSpot will compute a weighted amount automatically if you enter one, so leave the amount blank.
How do I tell employees about a data licensing investigation without raising expectations?
Describe it as an assessment of whether certain records could be licensed, name who is working on it and say that no decision has been made. Avoid any figure or timeline for income. If the records include employee information, say how it will be handled before anyone asks.
When does a data licensing opportunity become reportable to lenders?
That depends on your credit agreement and on what your CFO and counsel consider material. Many companies wait until a signed agreement exists and then describe its terms and conditions. Agree the wording internally before any lender update mentions it.
Sources
- IAS 37 does not recognize contingent assets, discloses them when an inflow is probable and recognizes them only when realization is virtually certain. Source
- IFRS 15 includes variable consideration only to the extent a significant revenue reversal is highly probable not to occur, and lists third-party actions as a risk factor. Source
- Salesforce maps opportunity stages to forecast categories, excludes Omitted from forecasts and lets owners edit the category. Source
- HubSpot's weighted amount multiplies the deal amount by the stage probability, and manual edits stop automatic probability updates. Source
- Regulation S-K Item 10(b) encourages management projections that have a reasonable basis and are presented in an appropriate format. Source
- Item 303 asks MD&A to address known events and uncertainties reasonably likely to make reported results not indicative of future results. Source
See if your company qualifies
A short company assessment. No data uploads are needed.