Every row carries a dated fact — a filing gone past its date, a first set of accounts falling due — and the written argument for why it means somebody needs something now. Then the contact is checked before it may be sold.
Already late and accruing penalties. Whoever was doing it is not doing it.
An example row. Trigger, wording exactly as delivered; the business is not named and the contact is masked.
This counts the actual database as you narrow it, from the same export the delivery engine runs on. No business record leaves this page — only counts.
Pick a trigger to see the argument that goes with it. Every trigger sold as a reason to call carries one, in writing.
| A data broker | Scraping it yourself | Tipwire | |
|---|---|---|---|
| What you get | Names and emails by industry code | Whatever the site published | A dated event, and the contact |
| Do you know why they'd buy | No. You guess from the sector | No | Yes, in writing, per trigger |
| How fresh | Quarterly at best | As fresh as your last run | Dated to the day it happened |
| Can you say where it came from | Rarely. "Public sources" is the usual answer | Only if you logged it | A source URL on every row |
| Who screens against TPS | Sometimes, and it expires in 28 days | You | You — on every row. Under PECR reg. 21 the duty is the caller's and does not transfer |
| When it's wrong | A support ticket | Your problem | One click, and it is replaced |
| Commitment | Annual contract, typically | Your time, indefinitely | None. Cancel whenever |