Skip to content

Leadership and readiness

Data licensing governance metrics that leave out unqualified leads

By SourceX Editorial · Updated

10 sections

Short answer

Meaningful progress in a data partnership pipeline is measured by evidence gates, not conversations: an opportunity counts only once it is qualified against written criteria, then scope accepted in writing, rights cleared, agreement signed, delivery accepted and payment received, each with a dated record and an owner. Inquiries and intro calls are logged as activity and kept out of pipeline totals.

Provenance trail

Data licensing governance

This page covers data licensing governance metrics that leave out unqualified leads.Illustrative

Key takeaways

  • Inbound interest is activity; it never counts as pipeline until written qualification criteria are met.
  • Each stage has entry evidence, an owner and a list of what does not count.
  • Validation checks block stage changes that lack evidence instead of flagging them later.
  • Signed, delivered, paid and recognized are separate measures with separate owners.
  • Report counts, dates and evidence references; leave amounts and revenue to finance.

Which metrics show meaningful progress in a data partnership pipeline?

Count an opportunity only when it passes an evidence gate: qualified against written criteria, scope accepted in writing, rights cleared for that scope, agreement signed, delivery accepted and payment received. Each stage needs a dated record and a named owner. Inquiries, intro calls and inbound emails from AI developers are activity, not progress, and belong in a separate count that never feeds the pipeline total.

Data licensing governance metrics have a narrower job than sales metrics. They tell leadership whether the company is moving toward a licensing decision it can defend: which records, under which terms, approved by whom. A dashboard that shows forty partnership conversations and no scoped dataset is measuring attention, not progress.

The asset below is a metric dictionary for qualification, scope acceptance and payment, plus the record schema and validation checks behind it. It is written for a single company or a business unit tracking its own outbound licensing effort, not for a portfolio-level scorecard.

Why do inquiry counts mislead leadership?

Because a CRM stage records what a salesperson believes, while a licensing decision depends on what legal, privacy and data owners have confirmed. The two drift apart quickly when the stage can be set by hand.

Standard CRM definitions show the gap. HubSpot's lifecycle stages define a lead as a contact or company that converted beyond a subscription, an opportunity as one associated with a deal, and a customer as one with at least one closed deal. None of those definitions asks whether the records in question can be licensed. Salesforce maps opportunity stages to forecast categories and lets users override the forecast category on opportunities they own, which is useful for sales forecasting and risky for a governance report.

A data partnership pipeline needs its own stages, defined by evidence rather than by conversation. The CRM can still hold the records; the dictionary simply decides what is allowed to count.

There is a second, quieter cost. When unqualified leads inflate the pipeline, the people who must review rights and privacy get pulled into conversations that were never going to reach a signed scope. Their time is limited, and a metric that wastes it slows the opportunities that are real.

The qualification, scope acceptance and payment metric dictionary

Each metric counts an opportunity once, at the moment its entry evidence exists. The "does not count" column is as important as the definition, because that is where unqualified leads usually slip in.

Qualification is the gate that matters most, so write its criteria down before the first opportunity is scored. The list below is illustrative; adapt it to your records and your appetite for risk, and keep the version number in each qualification memo so later changes do not rewrite history.

Whatever criteria you choose, the reviewer should not be the person who brought in the opportunity. A second reviewer at qualification costs little and screens out conversations that look like progress on a dashboard but never reach a signed scope.

  • The counterparty is an identifiable legal entity with a stated use for the data.
  • The records it wants exist in one of your systems with a known owner and a known date range.
  • No known contract, notice or law bars the use it describes, pending full rights review.
  • An executive sponsor has agreed to spend review time on this opportunity.
  • There is a dated next step that both sides have agreed.
The qualification, scope acceptance and payment metric dictionary
MetricCounts whenDoes not countOwner
Inquiries logged (activity only)An inbound or outbound conversation about licensing is recordedNever feeds the pipeline total or conversion figuresDeal owner
Qualified opportunitiesWritten qualification criteria are met and recorded with a date and reviewerInterest, an NDA or an intro call without the criteriaDeal owner
Scope acceptedBoth sides confirm in writing the record types, date range, volume estimate and formatA buyer asking for everything, or a scope only one side has seenData owner
Rights-cleared scopeLegal and privacy sign off on the accepted scope, with exclusions listedA general belief that the company owns its dataCounsel and privacy lead
Agreements signedA countersigned agreement exists for the cleared scopeTerm sheets, letters of intent or verbal agreementExecutive sponsor
Deliveries acceptedThe recipient confirms receipt and acceptance against the agreed specificationFiles sent but not yet acknowledgedData owner
Payments receivedCash for an accepted delivery is received and matched to the agreementInvoices issued or amounts expectedFinance lead
Days in stageMeasured from each stage's entry date to the next stage or closureAverages that mix closed and open opportunitiesGovernance lead
Stalled opportunitiesNo dated next step within the stage's review intervalOpportunities paused by a recorded decisionGovernance lead

What fields does each pipeline record need?

Keep one record per opportunity with a small, fixed set of fields. The schema below works in a CRM custom object, a spreadsheet or a database table, as long as stage changes are timestamped and evidence is linked rather than described.

At a glance

What fields does each pipeline record need

Linking matters more than it seems. A field that says "rights approved" is an assertion; a field that points to a dated review signed by counsel is evidence that anyone can open. When an auditor, a board member or a new executive asks why an opportunity was counted, the answer should be one click away.

Keep the stage history, not only the current stage. A timestamp for each transition lets you calculate days in stage, spot records that jumped stages, and reconstruct what the report said on any past date.

What fields does each pipeline record need?
FieldTypeRuleIllustrative value
opportunity_idText, uniqueAssigned when the inquiry is logged; never reusedDLP-014
counterpartyTextLegal entity name, not a contact's email domainAn AI developer or licensing intermediary
stageOne of the dictionary stagesMay move forward only when the next stage's evidence field is filledscope_accepted
qualification_refLink and dateRequired for every stage after inquiryQualification memo dated 2026-09-02
scope_refLink and dateRequired from scope_accepted onward; must list record types, date range and formatScope v2 confirmed by both sides
rights_signoffName, role and dateRequired from rights_cleared onward; names counsel and privacy reviewerCounsel and privacy lead, 2026-09-30
agreement_refLink and dateRequired from signed onward; points to the countersigned versionCountersigned agreement in the contract system
acceptance_refLink and dateRequired from delivery_accepted onwardRecipient acceptance email filed
payment_refFinance reference and dateRequired for payment_received; no amounts in the governance reportRemittance matched by finance
next_step_dateDateRequired while open; empty only when closed2026-10-25

Which validation checks keep the dictionary honest?

Run the checks before every report, either as validation rules in the CRM or as a script over an export. Salesforce publishes sample validation rules for opportunity management, and the same idea applies here: block the stage change, rather than flagging it afterward.

Blocking changes behavior; flagging changes nothing until someone reads the flag. If your system cannot block, run the checks as a script over the export and publish only records that pass, with a short exceptions list showing what failed and why.

  • Stage evidence: every stage after inquiry requires its evidence field and all earlier ones; a record at agreement_signed with an empty rights_signoff fails.
  • Forward only: a stage date can never be earlier than the previous stage's date.
  • No double counting: one opportunity_id per counterparty and scope version; a revised scope is a new version, not a new opportunity.
  • Live next step: open records need a next_step_date in the future; past dates move the record to stalled.
  • Inquiry isolation: records at inquiry are excluded from totals, conversion figures and days in stage.
  • Scope match: the agreement and acceptance references must point to the same scope version that rights sign-off approved.
  • No amounts: the governance export carries payment references and dates only; amounts stay in the finance system.

Worked example: a valid record and a failing record

This example is illustrative and does not describe real companies or deals. Two opportunities at a logistics company reach the leadership report in the same week. One passes every check; the other was moved to "signed" by hand after an encouraging call.

Without the checks, both would appear as signed agreements and leadership would see two deals where there is one. With them, the failing record drops back to inquiry, its owner sees exactly which evidence is missing, and the next report shows an honest count. Nothing about the second opportunity is lost; it simply has to earn each stage the same way the first one did.

  • Result for DLP-014: counted in qualified, scope accepted, rights cleared and signed.
  • Result for DLP-019: rejected at the qualification gate and reported as an inquiry until its evidence exists; the stage change is reversed and the owner gets the list of missing fields.
Worked example: a valid record and a failing record
FieldValid record (DLP-014)Failing record (DLP-019)Check that catches it
stageagreement_signedagreement_signedStage evidence
qualification_refMemo dated 2026-09-02EmptyStage evidence
scope_refScope v2: shipment exceptions, 2021 to 2025, CSVEmail saying the buyer wants all historical dataScope match
rights_signoffCounsel and privacy lead, 2026-09-30EmptyStage evidence
agreement_refCountersigned agreement for scope v2Unsigned term sheetStage evidence
next_step_date2026-10-25, prepare delivery2026-08-15Live next step

How should signed, delivered, paid and recognized be kept apart?

Report them as separate counts with separate owners, because each answers a different question and each can be true without the others. A signed agreement is a commitment, an accepted delivery is performance, a received payment is cash, and recognized revenue is an accounting judgment that finance makes under its own standard.

IFRS 15 shows why the last one must not be inferred from the pipeline. It distinguishes a licence that gives a right to access intellectual property over time from one that gives a right to use it as it exists when granted, and it says revenue for a right-to-use licence cannot be recognized before the customer can use and benefit from it. For sales-based or usage-based royalties it recognizes revenue only when the later sale or usage occurs. A governance report that labels signed agreements as revenue will disagree with finance, and finance will be right.

Keep the governance pipeline to counts, dates and references. Let finance publish its own figures, and link to them instead of copying them.

Who resolves a disputed stage, and on what evidence?

Disputes are normal: a deal owner believes scope is accepted, a data owner disagrees. Decide in advance who settles each kind of dispute and what document ends it, so the report does not wait on a meeting.

Scope evidence is easier to agree when it follows a known structure. Datasheets for Datasets proposes documenting a dataset's motivation, composition, collection process and recommended uses, and the Data & Trust Alliance's Data Provenance Standards group metadata into source, provenance and use. Either can serve as the checklist for what a scope reference must state.

Most disputes end quickly once the evidence standard is clear. The deal owner who believes scope is accepted can usually produce the confirmation, or discovers that the other side never replied. Escalation is for the rare case where two owners read the same document differently, and the sponsor's decision should be written into the record so the same question is not argued again next month.

Who resolves a disputed stage, and on what evidence?
Disputed pointDecidesEvidence that settles itEscalation
Is the counterparty qualified?Deal ownerQualification memo against the written criteriaExecutive sponsor
Is the scope really accepted?Data ownerScope document confirmed in writing by both sidesExecutive sponsor
Are rights cleared for this scope?CounselSigned rights and privacy review with exclusionsGeneral counsel
Was the delivery accepted?Data ownerRecipient's written acceptance against the specificationCounsel if the agreement defines acceptance
Has payment been received?Finance leadRemittance matched to the agreementChief financial officer

What belongs in the monthly report, and what should stay out?

A one-page report is enough: counts by stage, entries and exits since last month, days in stage for open opportunities, and the stalled list with owners. Leave out anything that cannot be traced to a record.

The report is also a governance record in its own right. Keep each month's version, because the change from one month to the next is often more informative than the snapshot: an opportunity that has sat at rights review for three months is telling leadership something about scope, records or counsel's capacity.

  • Include: opportunities by stage, with the change since last month.
  • Include: the stalled list, each with an owner and the missing evidence.
  • Include: rights exclusions decided this month, so leadership sees what was ruled out and why.
  • Leave out: inquiry volume as a headline, which rewards noise.
  • Leave out: estimated deal values or weighted pipeline, which invite figures nobody has agreed.
  • Leave out: any revenue figure not published by finance.

Mapping the pipeline gates onto a SourceX deal

Working with SourceX, the qualification stage opens with a short company assessment and no uploaded data, giving the qualification_ref field a dated outcome while no records move. Because SourceX covers sourcing and qualification, rights review, contracting, preparation, delivery and payment, each evidence field maps onto a documented step.

The agreement_signed gate corresponds to the moment the company, having approved the scope and terms, signs before anything is delivered. Counsel should still review the specific agreement and records.

Frequently asked questions

What should a data licensing metric dictionary include?

Each metric's name, the evidence that makes an opportunity count, what explicitly does not count, the owner and the source field. Add the record schema and validation checks so the definitions are enforced, not just written down.

Should inbound interest from AI developers count as pipeline?

No. Log it as activity so you can see volume, but keep it out of pipeline totals and conversion figures until written qualification criteria are met and recorded.

Can we track this in our existing CRM?

Usually yes, with a custom object or custom fields for each evidence reference and validation rules that block stage changes when evidence is missing. The CRM's standard sales stages can stay as they are for other deals.

Why not report weighted pipeline value?

Weighted values depend on probabilities and amounts that nobody has agreed for a licensing deal, and they tempt teams to report figures finance has not published. Counts, dates and evidence references give leadership a truer picture.

What makes a failing record?

Any stage without its evidence, a stage date earlier than the previous one, a scope reference that does not match the signed scope, or an open record with no future next step. The record is reported at the last stage it can prove.

Sources

  • HubSpot defines a lead as a contact or company that converted beyond a subscription, an opportunity as one associated with a deal, and a customer as one with at least one closed deal. Source
  • Salesforce maps opportunity stages to forecast categories, requires Closed/Lost stages to map to Omitted, and lets users override the forecast category on opportunities they own. Source
  • Salesforce publishes sample validation rules for opportunity management that enforce consistency between stage and other fields. Source
  • IFRS 15 distinguishes a right to access from a right to use intellectual property, bars recognizing right-to-use licence revenue before the customer can use and benefit from the licence, and recognizes sales-based or usage-based royalties only when the later sale or usage occurs. Source
  • Datasheets for Datasets proposes that each dataset be accompanied by a datasheet documenting its motivation, composition, collection process and recommended uses. Source
  • The Data & Trust Alliance Data Provenance Standards define metadata fields grouped into three standards: source, provenance and use. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies