Benelux registry signals for DACH sales teams

Benelux registry signals are publicly documented company events drawn from official sources in the Netherlands and Belgium: applied-for and granted building permits, published and awarded public tenders, new registrations in the Peppol directory. All of them can be used as precisely timed sales triggers. For DACH companies selling into the Benelux, they close a structural gap: local competitors have been reading these registers for years and know which municipality just granted a permit and which contracting authority is currently buying. A sales team in Munich, Zurich or Vienna usually hears about it only after the contract has long been awarded. Teams that pull the same local triggers automatically contact a company at the moment something has actually happened, instead of on a hunch.

The visibility problem in Benelux sales

The Dutch and Belgian markets are attractive to DACH vendors: geographically close, economically intertwined, digitally advanced. What is missing is on-the-ground market visibility. No local press monitoring, no network in the municipalities, no colleagues who happen to hear that a logistics company in Rotterdam is expanding. The relevant data is public (official gazettes, the procurement platform TenderNed, the Peppol directory), but it is scattered across hundreds of sources, unstructured, and in Dutch. No SDR in Frankfurt reads the announcements of 300 municipalities every morning.

That is exactly the gap a signal feed closes: Slicegraph reads the registers daily, cleans and classifies the events, and resolves them to companies. The dataset currently spans 9,817 signals across 523 regions. That is the same sales data for the Dutch and Belgian markets that local teams work with, just as a structured feed instead of a gazette.

Three signal families, and who sells with them

Building permits (family permit). Applied-for (permit_applied) and granted (permit_granted) construction, hospitality and environmental permits from the Dutch official gazettes: currently 4,220 signals from 341 municipalities, led by Amsterdam, The Hague and Rotterdam. A granted building permit means: the project is starting, the budget is approved, procurement begins. For construction suppliers, fit-out firms, machinery and scaffolding providers, or insurers, that is the earliest reliable buying moment. A look at the permits in Amsterdam shows how dense this stream is.

Tenders (family procurement). TenderNed, the central platform for Dutch public procurement, publishes tenders and awards as open data, as mandated by the Aanbestedingswet, the Dutch Public Procurement Act. Slicegraph normalizes two signal types out of it: tender_published (buying intent with a deadline, relevant for bid teams working the Dutch public-sector market) and tender_awarded (who won the contract, the ideal opening for subcontractors and suppliers, because the winner now has to deliver). Currently 565 procurement events across 246 regions.

Peppol registrations (family einvoicing). The Peppol directory lists every organization reachable on the Peppol e-invoicing network. Each new registration (peppol_registered) is a precise trigger: this company is modernizing its finance processes right now. The dataset holds 4,848 registrations, 4,013 in Belgium and 835 in the Netherlands. Belgium's dominance has a concrete cause: since 1 January 2026, structured electronic B2B invoicing has been mandatory there, and that obligation pushes new registrations onto the network week after week. For ERP, billing and accounting-software vendors from the DACH region, the feed of Peppol registrations in Belgium is a continuously replenishing target-account list.

Exact matching instead of name guessing

A signal is only as good as its resolution to a company. Dutch Peppol participants register under scheme 0106, which is the KvK number, the trade-register number of the Dutch Kamer van Koophandel. This lets these signals be resolved exactly, without fuzzy name matching, and reconciled directly against your CRM data. As a matter of principle, Slicegraph processes company-level data only: no private individuals, no purchased contact databases, and every signal links to its official source document. The full source and GDPR documentation is available at Data sources & compliance.

Walkthrough: a Benelux trigger feed for your team

Here is how a DACH sales team sets up the feed in practice. You need an API key (included in every plan) and a destination for the data: your CRM, an automation tool, or a Clay table.

Step 1: fetch signals via the API. Say you sell billing software and want every new Belgian Peppol registration since the start of the month:

curl -s "https://slicegraph.com/api/v1/signals?family=einvoicing&region=be&since=2026-08-01&limit=100" \
  -H "Authorization: Bearer $SLICEGRAPH_API_KEY"

Each item contains id, family, type, title, region, occurred_at, url (source document), company_id, company_name, kvk_number and a payload with source details. Further filters: type (e.g. permit_granted), region as a lowercase slug (amsterdam, nl, be) and kvk for a single company. limit accepts 1–200; pagination works via cursor.

Step 2: create a webhook subscription. Instead of polling, have new signals delivered to you, for example every permit and procurement event in the Netherlands:

curl -s -X POST "https://slicegraph.com/api/v1/subscriptions" \
  -H "Authorization: Bearer $SLICEGRAPH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"target_url":"https://hooks.ihredomain.de/slicegraph","filter":{"families":["permit","procurement"],"regions":["nl"]}}'

Every delivery is HMAC-SHA256-signed (header X-Slicegraph-Signature), so your endpoint can verify authenticity; failed deliveries are retried automatically. The complete parameter reference lives in the API docs.

Step 3: route into your workflow. If you work with Clay, you are done fastest: the API is Clay-compatible. An HTTP API column with a Bearer key is all it takes, and the signals land directly in your Clay table, where you enrich them and hand them to your sequences. Alternatively, your automation tool (Make, n8n, Zapier) processes the webhook and creates a lead or task in the CRM for each signal. To see what the signals look like live, check the public feed.

Getting started and pricing

The Feed plan (€99/month) covers one signal family of your choice with freely configurable region filters, including API, webhooks and a weekly CSV. Growth (€149/month) includes all families across NL + BE with full history, plus two LinkedIn senders for outreach. If you want to test the Benelux market first, start with Concierge (from €750/month): we define the triggers together and deliver cleaned, outreach-ready lists straight into your CRM. All the details are on the pricing page.

Free sample feed

Every plan starts with a free sample feed for your ICP. Email hello@slicegraph.com with who you sell to in the Netherlands or Belgium: industry, regions, signal family. Within two business days you will receive a first slice with real signals from your target region. Not a demo environment, but the data your team would be calling on next week.