# Intent signals

Intent signals are changes detected in an organization's hiring activity that indicate a potential selling opportunity. Sumble generates these automatically by analyzing job posts, people profiles, and technology usage across hundreds of thousands of organizations every day.

Signals surface on the [Signals page](https://sumble.com/signals) and can be delivered via [Slack](/enterprise-services/integrations/slack-alerts.md), email, or directly in the Sumble web application.

## Signal types

### Technology adoption

Sumble tracks when organizations start mentioning technologies in their job posts. These signals come in three forms:

**First mention by company**: a technology appears in an organization's job posts for the first time ever. This is a strong indicator that the company is evaluating or adopting a new tool.

**First mention by team**: a technology appears in a specific team's job posts for the first time, even if other teams at the company already use it. This catches expansion within organizations.

**Any mention**: any new job post at a configured organization mentions a technology you're tracking. Useful for monitoring ongoing activity at key accounts.

### Key technology projects

Signals fire when organizations post jobs related to major technology initiatives:

* Cloud migration
* Cloud cost optimization
* Data infrastructure migration
* Design system migration
* Digital transformation
* Frontend migration
* Generative AI projects
* Microservices migration
* Security infrastructure modernization

These indicate budget allocation and active evaluation of new solutions.

### Acceleration in job postings

Detects statistically significant changes in hiring volume for specific technologies or job functions over a 12-month window. A surge in Kubernetes job posts, for example, signals a company scaling its infrastructure investment.

Both increases and decreases are tracked — a drop in mentions of a competitor's technology can be as useful as a spike in your own.

### New hires

Fires when a person with specific technology skills or in a target job function starts a new role at a tracked organization. Signals distinguish between leadership hires (Manager and above) and individual contributor hires.

New leaders often bring in tools they've used before, making this a strong signal for outreach.

### Growth in headcount

Tracks when organizations are growing or shrinking specific job functions over time. Requires a meaningful change (both percentage and absolute) to avoid false positives.

### Competitor churn signals

Combines decreasing mentions of a competitor's technology with related migration projects. When a company is moving away from a competitor, these signals help you time your outreach.

### Own product churn signals

The inverse of competitor churn — flags when a customer may be reducing usage of your product, giving you the chance to re-engage proactively.

### Champion alerts

Tracks key contacts (champions) and alerts you when they change companies. A person who already knows your product at a new organization is a natural warm lead.

Champion tracking requires enterprise configuration. See [Sumble Signals](/enterprise-services/sumble-signals.md) for setup details.

### Keyword tracking

Monitors job posts for specific terms that standard filters don't cover: niche certifications (SOC 2, HIPAA), internal pain points (technical debt, scalability), or methodology mentions. This catches opportunities that standard technology or job function filters would miss.

## Signal tiers

| Plan       | Signal volume    | Configuration                                                                                                         |
| ---------- | ---------------- | --------------------------------------------------------------------------------------------------------------------- |
| Free       | Up to 8 per week | Auto-detected from your browsing activity                                                                             |
| Pro        | Up to 20 per day | Auto-detected from your browsing activity                                                                             |
| Enterprise | Unlimited        | Fully configurable signal types, technologies, job functions, and routing – with native database and CRM integrations |

On Free and Pro, Sumble learns what matters to you from your activity on the platform — the organizations you view, the technologies you filter by, and the searches you run. Enterprise customers configure signals explicitly through [Sumble Signals](/enterprise-services/sumble-signals.md).

## How signals are generated

1. Sumble processes new job posts and people data multiple times per day
2. Each new data point is checked against signal rules (automatic or configured)
3. Matching signals are created with a priority level (high, medium, or low)
4. Signals are routed to the relevant user based on account ownership
5. Delivery happens through the configured channels (web app, Slack, email)

## Working with signals

On the [Signals page](https://sumble.com/signals), you can:

* **Mark signals as relevant or not relevant** — this improves future signal quality
* **Favorite signals** to revisit later
* **Filter by signal type, priority, or organization**
* **Click through** to the underlying organization, job post, or person profile

For enterprise signal configuration, routing, and integration details, see [Sumble Signals](/enterprise-services/sumble-signals.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sumble.com/web-application/intent-signals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
