Verity for data companies
A data business sells freshness and correctness, and both fail silently. Verity tracks every delivery, source and incident against what the customer was promised.
Verity runs the company. Pipelines, warehouses and processing stay where they are.
Verity / Delivery
LiveCustomer deliveries
184
Deliveries behind commitment
17
Sources under licence
38
Quality incidents open
11
Needs attention
Illustrative figures. Verity shows your own delivery in this shape.
How the business runs
A data company’s product is a delivery that is current and right. Both failure modes are silent: a stale feed still returns data and a wrong field still parses. Seventeen deliveries behind their freshness commitment with customers uninformed is a set of contractual breaches the business has not noticed, and seven of eleven quality incidents being customer-reported means the customer is the monitoring system.
The second characteristic is that the inputs are licensed. Sources come with terms about what may be resold, to whom, in what form and for how long, and six licences renewing in a quarter is six sets of terms that could change what the company is allowed to sell.
The third is lineage. When a customer asks where a number came from, the answer has to trace through sources, transformations and deliveries, and it has to be produceable quickly.
The fourth is usage against entitlement. Three customers using data outside licence terms is contractual exposure in both directions — toward the source that licensed it and toward the customer who exceeded their entitlement.
The fifth is that commitments differ per customer. The same feed carries different freshness and coverage promises to different accounts, which makes breach a per-contract question rather than a system-wide one.
Verity holds delivery commitments, source terms, quality incidents and usage entitlement against every customer.
What Verity calls these things
What gets in the way
Data company difficulties come from selling something whose failure produces no error.
Staleness is discovered by the customer
A feed stops updating and continues returning data.
In Verity Freshness is measured per delivery against each customer’s commitment.
Quality incidents arrive from outside
Customers report problems the business did not detect.
In Verity Incidents carry detection source, so the internal detection rate is measurable.
Source licence terms are not attached to products
What may be resold and to whom lives in contracts nobody consults.
In Verity Licence terms attach to sources and flow through to the products built on them.
Lineage questions take days
A customer asks where a value came from and the answer is reconstructed.
In Verity Sources, transformations and deliveries are linked, making lineage answerable.
Usage exceeds entitlement unnoticed
A customer uses more, or differently, than their contract allows.
In Verity Usage is measured against entitlement with exceptions surfaced.
Commitments differ by customer and are treated as one
A single delivery serves accounts with different promises.
In Verity Commitments are held per customer contract, so breach is assessed correctly.
The complete system
One system across deliveries, sources, customers and incidents.
Work
Each delivery carries its dataset, customer, schedule, last successful run, freshness and coverage against commitment.
Why it matters here The delivery, not the pipeline, is what the customer bought.
In practice Seventeen deliveries behind their freshness commitment.
Control
One permission model and one audit trail, with per-contract freshness, coverage and availability commitments held and measured.
Why it matters here The same feed carries different promises to different customers.
In practice Breach assessed per contract rather than per feed.
Suppliers
Sources carry licence terms, permitted uses, resale rights, cost, renewal dates and reliability.
Why it matters here What the company may sell is determined by what it was licensed to receive.
In practice Six source licences renewing this quarter.
Records
Incidents carry dataset, detection source, impact, affected customers, correction and communication.
Why it matters here Who detected the problem is as important as the problem.
In practice Seven of eleven incidents reported by customers.
Workflows
Sources, transformations and outputs are linked so any delivered value traces backwards.
Why it matters here Lineage questions arrive from customers and regulators and need fast answers.
In practice Lineage from a delivered field back to its sources.
Relationships
Customers carry contracted datasets, entitlements, usage, commitments and incident history.
Why it matters here Entitlement is contractual and usage should be measured against it.
In practice Three customers using data outside licence terms.
People
Staff carry dataset ownership, incident handling, customer responsibility and availability.
Why it matters here A dataset without an owner has nobody watching its freshness.
In practice Datasets with named owners and coverage.
Reports and analytics
Freshness adherence, incident detection rates, source reliability, usage against entitlement and dataset profitability come from the records.
Why it matters here Both the product promise and the licence position are measurable.
In practice Internal detection rate against customer-reported incidents.
Verity AI
Verity AI answers from your own delivery, source, customer and incident records, respects permissions, and can create assigned follow-ups.
Why it matters here The useful questions are about breaches and lineage.
In practice "Which deliveries are behind commitment?" returns them with customers.
Communication
Breach notifications, incident communication and correction notices attach to the delivery and customer.
Why it matters here Telling the customer first changes an incident into a service event.
In practice Breach notification recorded against the delivery.
Orders
Customer contracts carry datasets, commitments, pricing, term and renewal.
Why it matters here Commitments and price sit in the same contract and should sit in the same record.
In practice Contract commitments alongside pricing per customer.
Locations
Delivery destinations and environments are recorded per customer.
Why it matters here A delivery that succeeded to the wrong destination has still failed.
In practice Delivery endpoints confirmed per customer contract.
Work in motion
These already happen. Recorded, silent failures stop being silent.
Comparing per contract rather than per feed is what makes breach assessment correct.
Recording detection source is what improves internal detection over time.
A licence change can invalidate a product the company already sells.
A lineage answer produced in hours is a different service from one produced in days.
Exposure runs both ways, toward the source and toward the customer.
Verity AI
Verity AI reads the same delivery, source, customer and incident records the company creates as it operates. It answers from your own delivery, respects permissions, and can turn an answer into a notification or a licence review.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the company’s own records at the point the condition is met.
When
A delivery misses its freshness commitment
When
A quality incident is opened
When
A source licence approaches renewal
When
Customer usage exceeds entitlement
When
A dataset has no owner
What you can understand
Delivery, quality and licence position from operating records.
Verity records the company’s operations. Pipelines, warehouses and processing continue as they are.
One system, different ways of seeing it
Everyone works from the same records.
Founder
Are we keeping our promises?
Freshness adherence, incident detection rate, licence exposure, dataset profitability.
Data engineering lead
What is broken or stale?
Delivery status, dataset ownership, incident queue, source reliability.
Account manager
What does this customer need to know?
Commitments and breaches, incident history, entitlement and usage, renewal position.
Legal and commercial
What are we licensed to sell?
Source terms and renewals, products dependent on them, customer entitlements, exceptions.
Where it is used
Freshness measured per delivery against each customer’s contracted commitment, so a silent failure surfaces internally rather than through a complaint.
Incidents carrying their detection source, which makes the ratio of internally found to customer-reported problems a measurable target.
Source terms and permitted uses attached to the products built on them, so a licence change is assessed against what the company sells.
Sources, transformations and deliveries linked, so tracing a delivered value backwards is a query rather than an investigation.
Contracted entitlements measured against actual usage, with exceptions raised before they become a dispute in either direction.
Freshness and coverage promises held per contract, so breach is assessed against what that customer was actually promised.
Plain-language questions across deliveries, sources, incidents and customers, with notifications and reviews raised in the same step.
Getting there
Pipelines, warehouses and processing continue and are mapped during implementation. Datasets and deliveries, customer contracts with commitments and entitlements, source licences and terms, and incident history are brought across.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own delivery, source, customer and incident records: which deliveries are behind their freshness commitment, which incidents were customer-reported, which products depend on sources renewing this quarter, where a delivered field came from. Each answer can become a notification or a licence review.
Because the same feed carries different contractual promises to different accounts. A delay that breaches one contract may be inside tolerance for another, so breach has to be assessed against the specific commitment.
Every incident records whether it was found internally or reported by a customer. That ratio is the honest measure of monitoring quality and it becomes a target rather than an impression.
Sources carry their licence terms, permitted uses and resale rights, and the products built on them are linked, so a renewal or term change is assessed against exactly what the company would no longer be permitted to sell.
Sources, transformations and deliveries are linked, so a customer question about where a value came from is traced through the chain rather than reconstructed by an engineer from memory and code.
Usage is measured against contracted entitlement with exceptions surfaced, which matters in both directions: toward the customer who exceeded their contract and toward the source whose licence governs resale.
No. Pipelines, warehouses and processing continue as they are. Verity holds the business around them — deliveries, commitments, sources, licences, incidents and customers.
About four weeks: discovery and mapping of datasets, delivery commitments, source terms and incident processes, configuration, migration of contracts and sources, then an ongoing operations partnership.
The customer usually knows before you do. Tell us how freshness is monitored today.