01
One questionName the business, teaching or investigation decision the proof must inform.
One artist or a representative roster slice, the current toolset and one decision the team needs to improve.
Proof of Value / enterprise buying
Start with a question worth proving.
A proof of value is not an open-ended trial. It is the smallest credible test of a real responsibility, with the evidence, people, success measures and decision point agreed before work begins.
The common charter
Agree the decision before configuring the proof.
02
Representative inputUse a defined artist, cohort, catalogue slice or data sample that can answer it.
03
Named rolesIdentify the sponsor, working users, reviewer and each party's data responsibilities.
04
Success measuresChoose three to five observable measures and record any material change to scope.
05
Readout and decisionAgree the output, review date and what a pass, pause or stop decision will mean.
Choose the relevant shape
Different responsibilities need different proofs.
Every scope is tailored, but the boundary should remain visible. The commercial proposal confirms included capabilities, support, data handling, price and any route from proof to deployment.
01
Roster intelligence
Start with
Produce
A side-by-side review of relevant signals, priorities and workflow outputs.
Evaluate
Clarity, useful difference from the current view, team adoption and the quality of the resulting decision.
02
Distributor intelligence and artist services
Start with
A defined artist cohort, available inputs and a choice of internal analytics, artist benefits or both.
Produce
A configured organisation view, connected artist experience and agreed reporting output.
Evaluate
Coverage, operational usefulness, artist-service fit and the workload required to scale.
03
Royalty investigation
Start with
A defined catalogue slice, one investigation question and the agreed authoritative or officially obtained source record.
Produce
A reviewable investigation workspace with candidate evidence, provenance, investigator actions and explicit limitations.
Evaluate
Traceability, reviewer reproducibility and whether the output supports a responsible next decision. A proof does not guarantee recovery.
04
Education partnership
Start with
Learning outcomes, one course or cohort, teaching period, project format and access boundaries.
Produce
A configured learning journey from artist intelligence to decision, campaign activity, reporting and reflection.
Evaluate
Adoption, completed work, quality of evidence-led reasoning, teaching workload, accessibility and operational fit.
05
Technology and data
Start with
The product being built, selected capability, intended use, delivery preference and representative scale.
Produce
A capability and delivery review, sample structure where appropriate, and an agreed feasibility boundary.
Evaluate
Technical fit, permitted-use fit, data usefulness, integration effort and a defensible build or stop decision.
Proof is not a promise of outcome.
A proof can demonstrate fit, traceability, usefulness and operational effort. It cannot guarantee revenue, recovery, legal acceptance, student adoption or a production decision. Those boundaries belong in the charter and the final readout.
Review trust and procurement information →