A need written down in public
Most of the demand a sales team hears about arrives once the buyer has decided to look: a form filled in, a request for a quote, a post asking for recommendations. Some of it is visible earlier, in documents the buyer had to file for other reasons. A company that applies for a permit, takes out a licence or registers as a new business has put on record that work is planned, that an activity is starting or that a business now exists, and the record is published whether or not the company has started looking for suppliers.
Sales teams generally know these records exist. Reading them is the obstacle. They are published by several bodies, in formats built for administration, and in a volume where most entries have nothing to do with any one company's offer. Someone takes on the reading in a quiet month, finds a handful of useful names in a long list, and stops once the month gets busy, because there is always something more urgent than a register.
So we treat public records as a source to be watched by a system, with people brought in only where a record has passed the checks. The value lies in the timing, and the timing is lost when the reading depends on someone finding an hour for it.
What a record tells you
A public record is a narrow document, and that is its strength. A permit typically names who applied, the address it concerns, the kind of work approved and the dates it was filed and issued. A licence names the holder, the activity it covers and when it takes effect. A new registration gives the business name, a declared address, the date and, in many registers, a declared activity. Each of these is a fact with a date on it, published by a body with no interest in the sale.
That makes a record a firmer place to start than most of what a prospect list is built from. A purchased list guesses at who might be in the market, while a record says that a particular business did a particular thing on a particular day. When a salesperson later writes to that business, the message can refer to something the business knows it did, which reads very differently from a message that refers to nothing.
The date matters as much as the content. A record read soon after it is published describes a business still at the start of whatever it filed for, and the same record read months later may describe work that is finished or a supplier already chosen. Every public record is open to every competitor, so the advantage a record gives is time, and the automation exists to protect it.
What a record leaves out
A record does not say that anyone wants to buy. A permit shows that work has been approved, and in some cases it is filed by the firm already engaged to carry that work out, so the decision a salesperson hopes to influence has already been made. A new registration shows that a business exists on paper, and some registered businesses never start trading. A licence can be renewed by a company that has used the same supplier for years and has no reason to change.
It rarely says who decides. The name on a record can be an agent, a registered office, an accountant or a holding company, and the person who will choose a supplier is often not named anywhere in it. Declared activities are broad and chosen by the filer, so a category in a register is a weak guide to what a business actually does. And a record seldom includes a contact route the business has offered for sales approaches, which matters for the rules on contact covered below.
None of this makes records less useful, but it settles how they are used. A record is a reason to look at a business more closely, and the lead is qualified afterwards, against criteria the client has agreed, by a step that checks what the record leaves open.
Agreeing what counts before anything is watched
Before any source is connected, we sit with the people who will receive the leads and settle which record types point to a need for what the client sells. The list usually turns out shorter than expected. Of the many kinds of permit or licence a body publishes, a small number describe a situation in which a buyer would need the client's service, and the rest are noise however relevant they look at first.
Then come the checks each record has to pass, written in the salesperson's words: the area the team can serve, the size of business it sells to, what the record says is being undertaken, and anything that rules a record out, such as a filer that is already a customer. A rule that a salesperson would not recognise as their own produces leads they will not call, so the wording of the criteria belongs to sales.
We test the rules against records already published before anything goes live. A salesperson reads a sample by hand and marks the businesses they would have called, and the rules run over the same sample. Where the two disagree, the rule changes, because the salesperson is the one who will work the result, and a rule that sends records they would have skipped teaches them to ignore everything it sends.
From a published record to a lead in the CRM
Once the rules are agreed, the automation reads each source on a schedule and takes in whatever is new. Every record is checked against the agreed criteria, and the ones that fail are set aside with the reason logged, so that anyone can later see why a record was rejected and whether the rule that rejected it was right. A source that returns nothing when it would normally return something raises an alert to a named person, because a register that has changed its format looks exactly like a quiet week.
A record that passes is matched against the CRM before anything is created. If the business is already a customer, has an open deal or appeared in an earlier record, the new record is added to the existing contact instead of starting a second one. Where the record names only a company, a research step looks for the person who decides for it and confirms how they can be reached, and where nobody can be confirmed the lead goes to the team with that gap marked on it.
The lead arrives in the CRM with its source, a link to the original record, the date it was published, the criteria it met and a stage, and it is assigned to one named person. That person can see why the business is on their list without opening anything else, and the reason is written in terms they can repeat to the business itself.
The first message refers to the record
When the team writes, the first message says plainly what the company saw and why it is relevant: the filing, its date and the reason the company thought it could help. It comes from a named person with a working reply address, and it makes one ask. A message that hides where the name came from leaves the reader guessing how the company found them, and stating the source plainly is the more honest position.
Before any outreach starts, the client should check which rules apply to contacting the businesses and people named in public records, for the channel they plan to use and the places their prospects are in, and the sequence is set up to match that answer. Records that name private individuals belong in that check as well. Where the answer is that a record cannot be used for a first approach, the sequence leaves it out.
Any follow-up is short and capped, and the sequence stops on any reply, on a booking and on an unsubscribe. A reply goes to a person and not back into the automation.
