Why customers are starting to ask the lineage question
As AI-generated and aggregated metrics become more common in customer-facing products, buyers have become more sceptical of numbers with no visible provenance — understandably, since an aggregated figure can hide a lot of quiet assumptions.
A product that can show, on demand, exactly which sources and transformations produced a given figure answers that scepticism directly, rather than asking for blind trust.
Compliance-grade lineage and customer-facing lineage are different artefacts
Audit-grade lineage needs to be exhaustive and technically precise, often too detailed to be useful to a non-technical customer. A customer-facing version needs to be legible: a simplified, accurate summary of sources and major transformations, not a full column-level graph.
Building the customer-facing view as a deliberate simplification of the compliance-grade lineage — rather than a separate, hand-maintained artefact — keeps both versions honest and in sync.
Making it a genuine differentiator
Competitors rarely invest here because it looks like pure compliance overhead with no visible return. A product that can answer 'show me where this came from' in a sales demo, instantly and accurately, stands out precisely because almost nobody else can do it convincingly on the spot.
This is the kind of capability that takes real engineering investment to build properly, which is exactly why it's defensible once built — it is not easily copied by a competitor over a weekend.
A number nobody can trace is a number customers are learning not to trust. Lineage is how you answer that before they ask.MNB Data Practice
Key actions
- Build a simplified, customer-legible lineage view from the compliance-grade graph
- Demonstrate provenance proactively in sales conversations
- Keep both lineage views derived from one source of truth
- Treat lineage as a product capability, not just an audit artefact