REVsign.
Radar Online

The market is noise. Isolating the signal is music to your ears.

The engine is running. We scan companies and publish signals with the source in plain view. You can research and enrich data from this screen, or connect your AI assistant. What you are about to see is the system at work: each narrative, a short track. Want to monitor your own book? Request access

Recent narratives

One narrative per company and event type, with the source in plain view. Filter by event type or by sector. What stays out →

Loading signals…
Sponsored

The outputs and the layer, one engine

The radar above is the first output. The other two run on the same Unified Signal Layer, along with the whole catalogue, grouped by what each one produces.

Market Radar

Market context, audited every day

Every source enters with a unique fingerprint that stops the same piece of news from being loaded twice. On top of that sit our own company census by vertical, with tax IDs verified against the real fiscal registry, and the map of holdings and controlling entities. It is not a purchased database of unknown origin.

See the cases
Autonomous GTM

Real function, not the literal job title

The system decides whether a role really holds the function you need, even when its job title inside the company is unusual. Only then is the credit that reveals an email or phone spent. Before any of that, dead or parked domains are quarantined, so nothing is paid to analyze sites that do not work.

See the cases
Second Brain

Institutional memory that cites or gets discarded

Each account's context lives in two layers: a weekly summary of the market and a daily read of the account itself. When the system drafts, every claim is checked against the original text. If it does not match, the whole read is discarded. Every proposed message is born held and waits for a person's explicit approval.

See the cases
Unified Signal Layer

Infrastructure, not one more dashboard

A single base for companies, people and narratives, with no parallel copies to reconcile. Every piece of outside data comes in through a strict filter that rejects whatever does not match the expected shape. Each client is isolated from the rest from day one, and the cost of every automated step is measured and visible.

See the cases

Each case names the technical piece behind it, not a generic benefit. See the full catalogue →

Sponsored MCP connection

Connect the engine to your AI assistant

What the engine does can be asked for from your assistant: read a company's signals, query the census by vertical, pull an account's full context, verify a domain or a tax ID, run the morning review, log a signal. One address, pasted into the assistant you already use. Today Claude Code and the OpenAI API come in. No per-client integration to write. The assistant is the vehicle. The signal layer, and the rules that govern it, do not change.

The address to paste into your assistant:

https://mcp.revsignlab.com/mcp

  • One connection method, the current one. The older one is out: the standard retired it and several of the assistants no longer accept it.
  • One open query, everything else with a credential. The only thing you can ask for without a credential is a signal already published, the same one anyone can read on the radar. Everything else comes in with its own revocable key, and we check that the account belongs to the company before a single record comes back.
  • A request cap per user. Each credential has its own per-minute limit, so an assistant stuck in a loop cannot drag the engine down or run up the cost.
  • A short list of what can be asked for. Read queries and logging a signal go out through this gateway. Anything that spends an external provider's credit is enabled one at a time, by a written decision.
  • Contact data does not go out through here. Looking up a person and seeing which product an account has not bought yet are out of this gateway by construction, not by configuration: there is no way to switch them on from outside.
  • Writing still goes through a person. A signal logged from a chat is born held, exactly as in the panel. It is a gateway to work with you, not a process that acts on its own.
  • Master switch. The gateway turns off in seconds, with no new release and without touching the engine.

Access is by invitation, not open: apart from that one open query, pasting the address without an enabled user returns nothing. Request access →

These rules are the Founding Mandates applied to this gateway. If it cannot be audited, the data does not exist. The software is the vehicle, the engineering logic is immutable. Rules are not suggested, they are carved in.

Sponsored

Look up your domain

A report of public, verifiable signals for a specific domain: recent press, corporate moves, open job postings. Every claim is cited against its source.

This is asynchronous: there is no progress bar here because the real investigation takes 30 to 120 seconds (several searches plus a synthesis with citations). We will email it to you when it is ready. It does not reveal contacts or which software the company uses. If we do not find verifiable signals, we will tell you that too. What this report covers and what it doesn't →