Signal types

Signal types are user-configurable per org. Each type has a slug (funding, hiring, m_and_a, ...) and a description that gets injected into the Claude classify prompt.

Adding a new type

1. Click + Add signal type in Settings or the dashboard tab bar.
2. Type a name (lowercased + slugified — M&A becomes m_and_a).
3. Write a description: trigger phrases, examples, edge cases.
4. Save. Triggers an immediate sync so the new type gets backfilled.

What the description does

It tells Claude what to look for. A vague slug like m_and_a with no description is ambiguous; with "Mergers, acquisitions, divestitures. Look for 'acquires', 'closes deal', 'parent company'. Skip rumours." Claude classifies more reliably.

Editing descriptions

Click any chip in Settings or in the type-tabs + Add modal. Changes apply on next sync.

Removing

Click × on a chip. The org needs ≥ 1 type at all times. Existing signals keep their old type slug — they just don't appear in filter UI until you re-add.

Built-in defaults

On a fresh org: funding, hiring, fda_approval, partnership, leadership. All have pre-written descriptions you can override.

hiring is broader than filled roles. The default description catches hiring INTENT in LinkedIn / company posts — phrases like "we are hiring for product design lead", "now hiring", "join our team", "open roles in product / engineering / sales" — alongside the more obvious filled-role announcements ("welcome our new VP of Sales"). Source unchanged — it's still classifying the same scraped LinkedIn posts; the prompt just looks for both signals.