Markets

A market is a country SignalDock can find signals in and write outreach for. Each market combines three things that ship together:

• a compliance policy (see Compliance) that decides which channels are allowed for which recipients;
• a default locale and the languages outreach is written in;
• the public signal sources that cover the country.

Markets are pure data in @signaldock/domain/market. Adding a country means adding its policy, locale, and source templates there, so the pipeline, API, app, and MCP pick it up at the same time.

RolloutCopy Anchor Link

Countries are added one at a time. A market is live once its sources, entity resolution, and compliance rules have been checked against real publications; beta markets work end to end but have fewer sources.

TED covers tenders above the EU thresholds. TenderNed also publishes Dutch tenders below them, which is why the Netherlands has the widest coverage. DSO zoning plans need an organization credential before they run.

Belgian messages default to Dutch; contacts with a French locale get French. German and Austrian outreach defaults to the formal register, and the compliance policy there requires consent for cold email, so first touches go through LinkedIn, phone, or letter.

Enabling a marketCopy Anchor Link

In the app, open Sources and choose Add sources next to a market. Through the API, call POST /api/markets/{country} (operation enableMarket).

Enabling creates the market's recommended sources in the organization. A provider that already has a source for that country is left alone, so the call is safe to repeat. The response lists which sources were created and which already existed.

Enabling a market does not start outreach by itself: signals still have to qualify, and campaigns follow the organization's review or autopilot settings.

RelatedCopy Anchor Link

• Compliance: per-country rules for each touch
• Data residency: where data is processed
• KvK: Dutch company resolution