The list was accurate. The opportunity had already closed.
Imagine a sales team with a technically valid contact record: the person still works there, the title is correct and the email address works. Meanwhile, the project that made the company a promising prospect has been cancelled or completed. The record can remain accurate while the reason to call has changed.
A purchased list captures what its provider knew at a particular time. Its usefulness depends on how it is refreshed and whether it explains the company’s current circumstances. For a sales team, a relevant name becomes more useful when it is connected to a documented reason to start a conversation now.
Why a valid list is still a historical snapshot
Three clocks run independently inside every prospect record.
The person. Roles change, employers change, responsibilities get reassigned. A contact can remain technically reachable while no longer being the person who owns the problem.
The company. Systems get replaced, acquisitions close, budgets move between years, priorities shift after a bad quarter.
The need. A specific problem opens a window — a system going end-of-life, a warehouse opening, a merger creating duplicate processes — and that window closes whether or not anyone updated a database.
A list reflects what was known at its last refresh. Some providers update frequently; others offer older snapshots. The buyer needs to establish the refresh date, the source and whether current business events are included.
Six things buyers routinely conflate
Lead buying becomes harder to assess when six different deliverables are treated as one product.
| What it is | What it tells you | What it does not tell you |
|---|---|---|
| Contact accuracy | The record reaches a real person | Whether that person still owns the problem |
| Company fit | The organisation matches your profile | Whether anything is changing there now |
| Current business event | Something dated and documented has happened | Whether anyone has budget or intent |
| Inferred need | A plausible consequence of that event | Whether the inference is correct |
| Qualified opportunity | A human has confirmed fit, timing and interest | Whether it will close |
| Won customer | Commercial outcome | Nothing further — this is the end state |
The commercial consequence is straightforward. If you buy at the first row and forecast at the fifth, your pipeline will look healthy and your quarter will not. The useful question to ask any lead source is not 'how many records' but 'which row of this table am I buying, and can I see the evidence for it'.
Why volume is easy to sell and hard to defend
Volume-based pricing makes the file or activity count the obvious deliverable. A buyer still needs to understand whether the contract promises contact records, researched prospects, appointments or something else. A large number of records can create substantial qualification work when the reasons for contacting those companies are missing.
Evidence works differently. A filed document, a published job notice or a stated expansion carries a date and a source. You can open it, read it and disagree with it before spending anything. That is a materially different transaction: instead of buying activity, you are buying something inspectable.
This is where promises of the form 'we keep working until you get accounts' deserve scrutiny. Such an arrangement is not necessarily dishonest, but it defers the definition of success to a future argument. A better structure is to receive something of value first — prospects with visible evidence attached — and decide about further work afterwards.
What has actually been documented
Two public records are worth reading carefully, provided their limits are respected.
A regulatory action. In April 2023, the FTC approved a final consent order against HomeAdvisor, settling allegations about misleading claims concerning lead quality, source and conversion rates. The order required up to $7.2 million for redress and prohibited specified misrepresentations. This was a settlement concerning home-improvement leads, not a finding that every lead provider behaves the same way. It illustrates why buyers should examine precisely what is promised about a lead.
Customer allegations. On a Better Business Bureau profile for a Toronto marketing firm, reviewers describe spending thousands of dollars, disputing guarantees they say were made, and being offered additional calling activity rather than a refund. These are unadjudicated customer allegations on a public review page. They are not verified findings, they are not a representative sample, and they do not establish how often any guarantee is honoured. Read as complaints, they point at a recurring practical failure: the word 'guarantee' was never converted into a defined, testable deliverable.
The transferable lesson from both is unglamorous. Define the unit of delivery in writing — what counts, how it is evidenced, and what happens if it does not arrive.
What a buying signal is, and what it is not
Three categories of signal are commonly used to identify current opportunities.
Official filings. Regulatory disclosures describe material events: acquisitions, new facilities, leadership change, capital commitments, restructuring. The SEC's EDGAR application programming interfaces provide programmatic access to filing data updated as submissions are disseminated, subject to fair-access limits. The publication date and the underlying event date can differ, and reporting schedules vary by filing type. A disclosure does not establish a prospect’s purchasing budget or willingness to buy.
Hiring activity. Job notices advertise where an employer intends to spend management attention. A posting for an integration developer, an ERP analyst or a warehouse systems lead is public evidence of an investment area, often before any press coverage.
Predictive business needs. Signals can be combined to infer a plausible requirement. This category is inference by definition and should always be labelled as such.
Aggregate economic data needs the same care. The Census Bureau's Business Formation Statistics FAQ explains the distinction between business applications and actual formations, among other methodological points. In practical terms, a rise in applications is not the same as a rise in operating firms, and neither is a list of prospects.
A vacancy may be replacement hiring or a sign that the work is moving in-house. A filing is not proof of budget, intent or a purchase commitment. Every signal is a reason to look, not a conclusion.
Illustrative use case: an ERP services firm and a growing distributor
The following is a constructed example for illustration. It is not a customer story, and no company, contact or financial result is real.
Consider a forty-person IT services firm that implements and supports ERP and integration work for mid-market distributors. Its strongest offers are consolidated reporting across business units, employee and sales portals, commission logic, and cloud infrastructure work. Its problem is not capability. It is that its best-fit buyers are unglamorous companies that rarely appear in technology press, so the firm buys lists and calls into nothing in particular.
Signal one — a disclosure. On 14 March, a regional distributor files a document disclosing the acquisition of a competitor with operations in two adjacent states and a note about integrating systems.
Signal two — a hiring notice. On 22 March, an ERP business analyst role appears on the company's careers page, referencing a named distribution ERP and describing the position as supporting 'multiple business units'.
Signal three — a second posting. On 29 March, a reporting analyst role mentions consolidating reporting across recently acquired operations and lists a business-intelligence tool.
The hypothesis, explicitly labelled as such. One hypothesis is that the distributor needs to reconcile information across acquired operations; whether it runs multiple ERP instances must be verified; if the acquired entity used different commission plans, reconciliation and commission logic may also be in scope; if user counts grew, portal access and infrastructure capacity may follow.
What must be checked before anyone calls. Whether the company already has an incumbent implementation partner. Whether its ERP is hosted in a way that constrains third-party access. Whether the two postings describe a new function or backfill for someone who left. Whether an integration programme has already been announced internally.
What would falsify the hypothesis. A published statement that both entities will standardise with an existing partner; a job description explicitly identifying the vacancy as replacement hiring; or evidence that standardisation is already complete.
Prioritisation. Score each opportunity on signal recency, specificity of the evidence, fit with delivered capability, and whether a plausible route to the right buyer exists. This example scores well on recency and specificity and should be worked ahead of a generic list record with no event attached.
Outreach. Relevant, short, and grounded in the public evidence — without implying knowledge the sender does not have.
Subject: Reporting across the two operations
[Name], your posting for a reporting analyst mentions consolidating reporting across recently acquired operations. That is usually where the awkward part sits: two charts of accounts, two item masters, and a month-end that takes longer than anyone planned for.
We work with distributors on exactly that — consolidated reporting, portal access and commission logic when an acquisition leaves two systems running. If it is already handled, ignore this and I will not follow up. If it is still being scoped, I can send a one-page outline of how we sequence it.
The learning loop. Log the reply, the objection and the outcome against the original signal. Over a quarter, patterns emerge: which signal types convert, which are noise, and which roles respond. That record is worth more than any list, because it is yours.
The evidence file: what to record for every opportunity
- The event, stated in one sentence, with its date.
- The source: URL, document name, page or section locator.
- The date you observed it, which is not the same as the publication date.
- What is observed, quoted or closely paraphrased, versus what is inferred.
- Contradictory evidence found, and how it changed the assessment.
- Contact relevance: does this person plausibly own the consequence?
- Existing systems and constraints that affect whether you can help.
- The next action and its date; the outcome, logged.
What DealFORGE actually does
DealFORGE finds current B2B lead opportunities using buying signals from official filings, hiring activity and predictive business needs. The output is positioned as evidence-based opportunities to research and contact — not guaranteed purchases, not closed accounts, and not a substitute for qualification.
The trial offer is deliberately concrete rather than open-ended: participants receive at least 50 leads they can keep and work independently, with no obligation to purchase and without paying an agency up front for an indefinite promise to keep working. The point is to let a sales team judge the evidence quality on its own terms, using its own definition of a good prospect, before committing to anything further.
Questions to ask before paying anyone for leads
- What exactly am I buying — records, events, inferred needs or qualified meetings?
- Can I see the evidence attached to a sample before I pay?
- How is the evidence dated, and how is inference labelled?
- What happens if the evidence turns out to be wrong or out of date?
- Do I keep what I have been given if I decide not to continue?
- Is any guarantee defined in testable terms, in writing?
Honest limits
Evidence-based prospecting is designed to help teams focus their qualification effort. It does not guarantee revenue, and it does not remove the need to qualify. Signals decay: the acquisition that made a company a strong fit in March may be fully integrated by September. Inferences are sometimes simply wrong, which is why contradictory evidence belongs in the record rather than in a salesperson's memory.
What changes is the position you argue from. Instead of defending a spend on a file that produced nothing, you can show what you observed, when, from where, and what you concluded — and let a buyer disagree with the reasoning rather than with the invoice.
Conclusion
A contact database helps a team identify who exists in a market. Current, documented buying signals add another dimension: which companies may be dealing with a relevant change now, and what evidence supports that assessment.
A list is a starting inventory. A dated event with a readable source is a reason to act. The firms that compound advantage in distribution, manufacturing and professional services are not the ones with the largest database. They are the ones that can point at a filing, a job notice or a stated expansion, explain what it probably means, check whether they are wrong, and start a relevant conversation while the window is still open.