Signals reference
The signals that mark a high-intent user or account, and why each one is on the list.
Scored signals
| # | Signal | Strength | Sales-ready | Why |
|---|---|---|---|---|
| 1 | Several engineers from the same org active in one workspace | High | Yes | This is team adoption, not one person trying it out. It's the point where product-led use turns into an enterprise conversation. |
| 2 | A dashboard shared across two orgs | High | Yes | A new company shows up at zero acquisition cost, and someone they trust already uses the product. |
| 3 | Reading the migration docs | High | Yes | Nobody reads migration guides for fun. There's a project and a budget behind it. |
| 4 | A budget holder shows up | High | Yes | The engineers using the product often aren't the ones who sign. When the person who does appears, you can talk about cost. |
| 5 | Close to the paid-plan ceiling | High | Yes | Usage is forcing the decision. The $49 credit at $0.30/GB runs down in plain sight before the overage lands. |
| 6 | Asks for SSO, RBAC, or longer retention | High | Yes | These are paid-only. They can't keep going on the free tier. |
| 7 | A competitor renewal is coming up | High | Yes | This is the one window where switching is possible. Interest at any other time has nowhere to go. |
| 8 | Connects an integration (AWS, Kubernetes) | Medium | No | It's wired into real infrastructure, but it's still one person and still easy to undo. |
| 9 | Copies a config snippet | Medium | No | Depends which one. Retention or RBAC config means they're going deep. The quickstart means nothing. |
| 10 | A former power user changes jobs | Medium | Nurture | Someone who already trusts the product now sits at a new account. Warm, but the timing is unknown. |
How comparison pages split into tiers, and what to do with each tier, is in Sequence spec.
Regulatory and mandate triggers
A compliance deadline. An end-of-support date. An audit finding. These work like signal 7: they're public, they have a date, and they force a migration whether anyone is interested or not. They're not in the top ten because they're rare. When one fires, it's the surest signal on this page.
Where each signal comes from
| Source | Signals | Who it covers |
|---|---|---|
| Product telemetry | 1, 2, 5, 6, 8, 9 | Cloud users only |
| Website and docs | 3 | Everyone |
| External: Clay, GitHub, community | 4, 7, 10, regulatory triggers | Everyone, including self-hosted |
Most SigNoz users run it themselves, so there's no product telemetry for them. Those accounts get scored on external signals only: GitHub activity resolved to a person and a company, docs behaviour, community activity, anonymous pings from the open-source build.
One caveat on GitHub. Commits default to a noreply address now, so resolving identity from commit email only works for some users. The fallbacks are org membership, who opens issues, and who stars the repo.
The SigNoz community Slack is a signal source that costs nothing to tap. How customers react to changelog posts and migration guides is readable by the same agent described in Ops board.
Signals I cut
| Signal | Why |
|---|---|
| GitHub stars on their own | That's a bookmark, not an evaluation |
| Saving a LinkedIn post | Private interest with no commitment. Kept as weak context only. |
| General docs traffic | Reading, not building |
| Joining the community | Ambient interest |
| A hiring surge | Tells you about the account, not about any one person's intent. Useful as a pre-signal, not a scored one. |
| Firmographic fit | Says who they are, not what they're doing |
Why the score separates champions from buyers
Every case study on signoz.io names an SRE, a DevOps lead, or a VP of Engineering. None of them name procurement.
SigNoz has already documented the trigger. Leo Blondel, CTO at Alien Intelligence:
"Datadog came back and said, 'The trial's over — it's going to cost you over $2K.' I was like, 'Sorry, what?'"
That's a deadline with a dollar figure on it, not a lead.
Source: signoz_assignment_q3.md, plus the four additions agreed on 6 Sep 2026.