Data licensing program KPIs for a holding company

Which KPIs should a holding company track for data licensing?#

A holding company should track data licensing KPIs that follow each package from screen to cash, measured at the operating-company level and rolled up to the group. A short funnel of stage counts, two financial measures and two quality measures is enough for most programs.

The aim is to answer three board questions: is the program moving, is it producing cash, and is it creating risk? A KPI that does not inform one of those questions belongs in working files, not on the group scorecard.

The KPI checklist with definitions#

The KPI checklist below defines each measure, names the record that proves it and flags the usual trap. Adopt the definitions before the first reporting period so numbers stay comparable over time.

Not every KPI applies from the first period. Incidents and refresh renewals only mean something once packages have been delivered, so show them as not yet applicable rather than zero. A zero suggests a clean record; not yet applicable tells the board the measure has not started.

Leading and lagging indicators#

Leading indicators, such as companies screened and rights-cleared scope, predict what the program will release; lagging indicators, such as cash received and renewals, show what it has produced. A scorecard needs both so the board sees early progress without mistaking it for results.

In early periods, expect leading indicators to move while cash stays flat. Licensing value is known only once a buyer engages, so the group should resist forecasting cash from the funnel until there is a delivery history to base it on.

• 1Leading: companies screened, companies qualified, rights-cleared scope, packages in preparation.
• 2Conversion: approved releases relative to prepared packages, and contracted value per approved release.
• 3Lagging: cash received, refresh renewals, incidents after release.
• 4Efficiency: internal effort per package, tracked by function.

Definitions that keep the scorecard honest#

Scorecard definitions stay honest when they fix the unit of count, the trigger date and the boundary between stages. Most disagreements about program results trace back to a definition nobody wrote down.

Write the definitions into the group's reporting manual next to its other KPIs, and have the finance lead at each operating company confirm them. A definition agreed only in a kickoff meeting tends to drift as soon as the first package is under pressure.

• 1Count packages, not datasets: one package is one licensed scope from one supplier entity to one licensee.
• 2Count each package once at each stage, with the date it passed that stage.
• 3Record contracted value when both parties have signed, not at term sheet.
• 4Record cash when received, and leave recognized revenue on the accounting team's own schedule.
• 5Report figures gross and net of fees in separate columns.
• 6Attribute every package to the legal entity that granted the license.

Vanity metrics to leave off the group scorecard#

Vanity metrics are numbers that rise without the program getting closer to a signed, delivered license. They appear because they are easy to collect, and they mislead boards that see them next to real KPIs.

If an operating company wants to report one of these figures, keep it in the company's own notes rather than the group roll-up. Terabytes and conversation counts are useful context for a program owner planning work, but next to cash and approved releases they invite the board to read progress that has not happened.

Reporting cadence and ownership#

Reporting cadence for a data licensing program should match the group's normal management reporting, usually a quarterly scorecard for the board and a monthly working view for the program owner. A separate cycle adds work without adding insight.

Name one program owner at the group, often in the CFO's office, and one data contact at each participating company. The company contact owns the source records behind each KPI; the group owner owns the definitions and the roll-up.

Keep the board page to a single view: the funnel by stage, cash and contracted value, incidents and a short commentary from the program owner. Detail by company sits in an appendix, so directors can ask about a specific business without the main page growing each period.

Illustrative: a group CFO builds the first scorecard#

Illustrative: the group CFO of a fictional holding company with software and distribution businesses launches a voluntary program. Before any outreach, she circulates the KPI definitions and an incident log template to each company's finance lead.

After the first reporting period, the scorecard shows several companies screened, fewer qualified and one rights-cleared scope at a software unit, with no cash yet. The board sees a funnel moving rather than a forecast. When the first payment arrives, it is reported gross and net of fees, attributed to the licensing entity and reconciled to the bank record.

The program owner also notices that internal effort at one distribution company is far higher than at the software units, because its order exceptions live in email outside the ERP. The KPI does not judge the company; it points to a records gap the operating team decides to fix before preparing another package.

How SourceX maps to program KPIs#

SourceX stages map directly onto these KPIs. The SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, gives each package a dated status, and each completed package produces a SourceX Evidence Packet that serves as the source of truth for approved releases.

Groups that want to compare companies before screening can use the SourceX Enterprise Data Value Framework to rate record families consistently on the same qualitative drivers. SourceX does not publish price lists or forecast program value.