Every business has a trigger that no standard catalog lists. A company opening a second warehouse. A restaurant chain announcing a new location. A manufacturer earning a specific certification. A school district publishing a new curriculum. A municipality awarding a particular kind of contract.

These are real buying contexts, often the single best one for a given product, and they are too niche for any pre-built signal to cover, because they matter to one kind of seller and nobody else. A custom signal is how you catch them anyway: you describe the event in plain language, and a search-and-crawl process goes looking for the companies it happened to.

The signal is whatever you define it to be, with one honest condition: the event has to leave a public trace that a search can find. Within that condition, the range is enormous, because almost any meaningful business event ends up written down somewhere online.

The use case: I want to contact a company WHEN [your event], because the trigger that actually means "they need me now" is usually too specific for any off-the-shelf list.

Why a custom trigger beats a generic one

The pre-built signals like funding, hiring, and job changes are broad because they apply to almost everyone, and that breadth is also their limit, since a signal that applies to everyone is not specific to your business.

They are excellent general-purpose triggers, but the event that genuinely means a company needs your particular product right now is usually narrower than any of them, specific to your category in a way a general catalog cannot anticipate.

A custom signal trades the convenience of a ready-made trigger for precision. Instead of inferring intent from a generic event and hoping it correlates with a need for your product, you watch for the exact event that maps to your offer, the one where the connection is not an inference but a near-certainty.

The constraint, and the thing to be honest about from the start, is what a search can actually find. A custom signal works when the event you care about gets written down somewhere public, in a press release, a news article, a regulatory filing, or a page on the company's own site.

If the trigger leaves no trace online, no search can surface it, no matter how meaningful it is. So the art is choosing a trigger that is both meaningful to you and visible on the web, which is a real design decision rather than a technicality. That timing-first reading of public context is the same instinct behind the produced intent signals from a provider like Rodz, applied to a trigger you define yourself rather than one chosen for you.

What the signal actually is

You fill in the blank with the trigger that matters to your business, described in plain language, and because the event is read from the open web rather than pulled from a structured database, the mechanism underneath is search and scraping.

A programmatic search looks across news and web pages for content matching the trigger you described. A crawler then navigates to the promising results, reads them, identifies the companies involved, and confirms the event actually happened rather than was merely speculated about or reported as a rumour.

In effect, it does what a diligent researcher would do if you sat them down and explained your trigger: query for the thing you care about, open the results that look right, read them properly, and pull out the companies that genuinely match, except it does this continuously and at a volume no person could sustain.

The output is a list of companies that recently matched your trigger, refreshed as new matches appear. It is worth understanding the mechanism because it explains both the power and the limits of the signal: it can find anything a search can reach, and it can miss anything that is not written down or is written so ambiguously that the crawler cannot confirm it.

How to use it

The whole game is the definition, and most of the value or failure of a custom signal is decided the moment you write the trigger. Describe it precisely, because "opened a new location" is vague enough to surface half the internet, while "announced the opening of a new distribution center in France" is something a search can actually pin down and a crawler can confirm. The more your description resembles the words that would appear in a real announcement of the event, the better the matches.

Anchor the trigger on findable traces. Favor events that show up in news or on company sites, since certifications, openings, launches, awards, regulatory filings, funding-adjacent announcements, and public contracts all leave written traces, while purely internal decisions, private conversations, and unannounced changes do not.

Then filter the surfaced companies by size, industry, and geography, because a broad search will inevitably pull in matches outside your market that share the trigger but not the fit.

Finally, treat the output as an inference signal rather than a stated fact: it tells you a company very likely matched your trigger based on what search and a crawler could read, which is strong evidence but not a guarantee, so verify the high-value matches with a quick look before you commit to heavy outreach.

The verification step is cheap, and it protects you from the occasional false positive that any search-based signal will produce.

Who to target

It depends entirely on the trigger, so there is no single answer the way there is for a job-change signal, and that is part of what makes custom signals flexible. Once a custom signal surfaces a company that matched your event, you resolve the persona you sell to inside it, the same company-level two-step you use elsewhere, because the signal finds companies. You still have to find the right person within them.

Match the role to the event, because the event usually points at who owns it. A new-location trigger points at operations or expansion leads who are standing the location up. A certification trigger points at quality, compliance, or the function the certification governs.

A new-contract trigger points at whoever now has to deliver on it. The trigger you design tells you not just which companies to approach, but which person inside them just acquired a new problem, which makes the persona resolution sharper than a generic company-level signal.

How to write the message

One signal, one message, built around the specific event, and this is where custom signals reward the work you put into the definition. The advantage of a custom trigger is that it is precise, so your message can be precise too, in a way that generic-signal outreach rarely can.

To a manufacturer opening a new production site, a seller of shop-floor safety equipment might note that fitting out a floor from scratch is the one moment to get safety set up right instead of retrofitting it later, which always costs more and disrupts more, then ask for a short call while the plans are still on paper rather than poured in concrete.

The deeper advantage is that, because the trigger is your own and almost nobody else is watching for it, your message is often the only relevant one in the prospect's inbox that week. Where a funded company drowns in forty congratulations emails, the company that just matched your obscure trigger hears from you and no one else, which is an enormous edge.

Don't waste it by sending a generic pitch for a specific event, because the whole reason you can reach them uncontested is that you noticed something specific, and a generic message throws that advantage away and makes you sound like everyone they ignore.

Stacking custom signals with other signals

A custom signal is often the sharpest tool in a stack, precisely because it's tailored to your business rather than shared with every other seller.

A company that matched your niche trigger and that also just raised or hired in the relevant function is about as qualified as an account gets for you specifically, because the custom signal confirms the precise fit. In contrast, the produced signals confirm the budget and the timing.

Use the custom signal as the precision layer that says "this is exactly my kind of company in exactly my kind of moment", and the produced ones from the broader set Rodz defines in its guide to intent signals to confirm that the budget and urgency are there too.

The custom trigger tells you the account is a perfect fit; the produced signals tell you it can act now. Together they let you spend your best outreach on the accounts where both are true, which is the whole point of running signals rather than lists.

Frequently asked questions

What kind of triggers can I define?

Any event that leaves a public trace: openings, launches, certifications, awards, regulatory filings, public contracts, announcements, news of a particular kind. The test is simple, if a person could find it by searching the web and reading a few pages, a custom signal can be built around it, and if they could not, it cannot.

How does it actually find the companies?

By searching and crawling. A programmatic search looks for news and pages matching your trigger, and a crawler navigates to the results to read them, identify the companies involved, and confirm the event genuinely happened. It automates the research a diligent person would do by hand, continuously and at scale.

How reliable is it?

It infers from what search can read, so reliability depends on two things: how clearly your event is reported online and how precisely you described it. A well-defined trigger for a well-reported event is very reliable; a vague trigger for a rarely-written-about event is not. Define it tightly, filter the results, and verify the high-value matches.

What if my trigger has no online footprint?

Then a custom signal cannot find it, because it works only off public traces. Either pick a different trigger that does get written down, or choose a proxy event that is reported and reliably accompanies the unobservable one you actually care about, the way a job posting can be a proxy for a process a company never announces directly.

How is this different from the pre-built signals?

The pre-built signals are general triggers chosen to fit many businesses; a custom signal is a trigger you design to fit only yours. That makes it less broad but far more precise, and it lets you catch the buying moment that matters most to your category even when no standard catalog includes it.

Custom signals cover the contexts no standard catalog includes. The pattern is the same as every other intent signal: catch the company in the moment, reach the right person while the event is recent, and send one message that earns the reply.

With lemlist's Intent Signal Agents, teams can do exactly that at scale: