The Supply Chain Nobody Audits
When an agency purchases a list of business contacts, that data has usually changed hands at least twice before arriving. A source compiler builds the original dataset. A national aggregator licenses it, often bundling records from multiple compilers. A reseller — sometimes two — packages it for the end buyer.
Each transaction adds margin. Each handoff introduces delay. And each layer creates distance between the agency and any meaningful accountability for data quality.
The economics are straightforward. If three intermediaries each add 20–30% margin, the agency pays significantly more than the data cost at source. But the financial markup is only part of the problem.
Freshness Decays at Every Step
B2B contact data decays at a rate of 20–30% annually. People change jobs, companies restructure, phone numbers are reassigned. A record that was accurate when compiled may already be degraded by the time it reaches the first reseller — and further degraded by the time it reaches the agency.
This decay rate compounds across a supply chain with multiple handoffs and unknown lag times. An agency buying from a reseller has no visibility into when the underlying data was actually compiled, how many times it has been resold, or how long it sat in various databases before being packaged for sale.
The practical consequence is dead numbers. Calls that connect to disconnected lines, wrong contacts, or businesses that no longer exist. Every dead dial costs agent time, reduces contact rates, and inflates cost per lead.
Operations managers track these metrics daily. What they often miss is the upstream cause.
Compliance Risk Transfers Downstream
The Do Not Call Register creates a specific legal obligation: data must be washed against the DNCR no more than 30 days before use. Agencies understand this requirement and build wash cycles into their processes.
What the 30-day rule does not address is the age of the data before the wash. If a record was compiled eighteen months ago, resold twice, and washed yesterday, it meets the technical requirement. But the underlying contact information may have changed entirely — including whether that number now belongs to someone who has since registered on the DNCR.
This is the compliance gap that caught V Marketing. In March 2025, the Federal Court imposed a $1.5 million penalty on the company for DNCR breaches, with an additional $60,000 personal fine for a director. The case turned on calls made to registered numbers — calls the agency believed were compliant based on their data supplier’s assurances.
The maximum court-imposed penalty for DNCR breaches is $2.22 million per day. Infringement notices can reach $222,000 per day. These figures make the cost of cheap resold data look very different when weighed against enforcement risk.
The Reseller Defence Does Not Hold
Agencies sometimes assume that purchasing from a reputable reseller provides a compliance buffer. If the data was bad, the thinking goes, that liability sits with the supplier.
This assumption does not survive contact with the regulator. The ACMA holds the caller responsible for DNCR compliance, not the data supplier. A reseller’s contractual warranty about data quality may support a civil claim after the fact, but it does not prevent the fine, the investigation, or the reputational damage.
The V Marketing case reinforced this principle. The agency’s data processes were examined in detail, and the court found them inadequate regardless of what suppliers had represented. (DNCR Compliance and Guidance)
For operations and compliance managers, the implication is clear: the only defensible position is knowing exactly where data comes from and how recently it was compiled.
What Source Data Actually Changes
Source-compiled data eliminates the reseller chain entirely. Records come directly from the compiler, with known compilation dates and a single point of accountability for accuracy.
This changes three things simultaneously.
First, cost. Removing two or three margin layers reduces the per-record price, often significantly. Agencies buying at source typically find they have been paying a substantial premium for data that has passed through multiple intermediaries.
Second, freshness. Source data has a known age. Agencies can specify recency requirements and verify compilation dates rather than trusting opaque reseller claims. Fresher data means higher contact rates and fewer wasted dials.
Third, compliance. A single supplier relationship creates clear accountability. Wash cycles can be verified against known compilation dates. If something goes wrong, there is no ambiguity about where the data originated or who is responsible for its accuracy.
None of this eliminates the need for proper DNCR processes. The 30-day wash requirement remains, and agencies must still maintain compliant calling practices. But source data removes the hidden variables that make compliance harder to guarantee.
The Question Worth Asking
Every telemarketing agency has a data line item in their budget. Most have never broken down what that cost actually represents — how much goes to the original compiler, how much to intermediaries, and how much freshness they lose at each step.
The exercise is worth doing. Pull your last three data invoices. Ask your supplier where the records originated and when they were compiled. Ask how many times the data changed hands before reaching you.
If the answers are vague, that tells you something important about the risk sitting in your dialling queue.
If you want to know what source-compiled DNCR-screened data costs for your target audience, we can have a count and indicative pricing back to you within one business day. No obligation — just the number.
