Signal-led LinkedIn outreach, starting a sequence from a permit, a tender or a Peppol registration

Most LinkedIn outreach starts from a list and searches for a reason to write. Signal-led outreach starts from the reason. A company applied for a building permit yesterday, won a public tender last week, or registered on the Peppol e-invoicing network this morning. Each of those is a dated, public, verifiable event, and each is a better opening line than anything a template can invent.

Slicegraph ingests those events daily from official Dutch and Belgian registers, 10,421 signals so far, 4,220 of them permits. This post explains how one of them becomes a LinkedIn sequence.

The feed as a campaign source

A feed in Slicegraph is a filter over the signal stream: a family (permits, tenders, Peppol registrations, insolvencies), optionally a region and a signal type. The same feed can go to a webhook, to Clay, or to a CSV digest. It can also be attached to an outreach campaign as a source.

When a new signal matches the feed, the worker looks up the company and searches LinkedIn, from your own account, for the people there whose titles match the personas you set on the campaign. It takes at most two people per company. That cap is deliberate: a company event is a reason to write to one or two decision makers, not to blanket a staff list.

Signal family	Typical event	Who it is a reason to write to
Permits	Building or environmental permit applied for or granted	Construction suppliers, fit-out, installation, equipment rental, insurers
Tenders	Public contract published or awarded	Subcontractors, staffing, equipment, compliance services
Peppol registrations	Company joins the e-invoicing network	Accounting software, accountants, ERP and invoicing vendors
Insolvencies	Bankruptcy or suspension of payments declared	Restructuring, asset buyers, replacement suppliers to their customers

The event in the message

Every lead sourced this way carries the signal it came from. Two template variables expose it: signalTitle and signalType. A first message can therefore say what actually happened, in the register's own words, rather than "I noticed your company is growing". The built-in "Signal-led outreach" template opens with exactly that line.

Variables have fallbacks, firstName|there renders "there" when the first name is missing, for example, and a template with a leftover [placeholder] in brackets refuses to activate, so a prospect never receives the brackets.

The sequence around it

A signal-led campaign usually stays short. The event is fresh for a few weeks, so a typical spine is: invite with a one-line note that names the event, wait three days, message those who accepted, end. Nothing about the sequence engine changes; conditions, InMail and withdraw steps are available exactly as on any other campaign. The outreach page lists them.

Why this is the part other tools cannot copy

A sequencer can only be as good as its list. Search-based lists are static and shared: every competitor with the same filters reaches the same people in the same month. A registry event is neither. It happens once, it is dated, and the day it is published is the day the company is deciding who to call. Slicegraph is the only outreach engine that reads those registers itself, which is what the Apollo comparison and the lemlist comparison come down to.

Getting started

Browse a live slice first: permits in Amsterdam or Peppol registrations in Belgium show what the events look like. Then create a feed with the same filter, attach it to a campaign, connect a sender, and activate. Pricing is €29 per sender per month on the Outreach plan; the Growth plan adds the signal feeds and two senders.