Core signals from day one
No setup. The moments that matter in every account are found as soon as your tools are connected.
Write your own in plain language
Describe the moment that matters to your business. OpenNous finds it across every account, with the evidence behind each match.
Backfill the last 90 days
A new signal backfills your history right away, so you see how often it happens before you rely on it.
Evidence on every signal
Each signal links to the call, email or product event it came from and says why it matters.
Signals from every conversation
1 "expansion": [{ 2 "signal": "Adding the EU team", 3 "quote": "We're adding the EU team." 4 }], 5 "risks": [{ 6 "risk": "Security review pending", 7 "quote": "Legal needs a week." 8 }]
- Calls, emails, Slack threads and product events.
- Every signal keeps the quote it came from.
- Matched to the right account, deal and person.
Acme · QBRCall ended · 24 SepYour own signals, in plain language
"Customer asks for SSO before they sign" Runs on: every new conversation Backfill: the last 90 days Returns: the account and the quote
- No rules engine and no keywords to maintain.
- Backfilled on 90 days of history before you rely on it.
- The quote behind every match.
Acme“We can’t roll out without SSO.”
Globex“Security needs SAML first.”
Hooli“Is Okta supported?”A next step, where your team works
Expansion → account owner, #deals Churn risk → customer success, #cs Champion left → account owner Competitor → #competitive
- The Inbox, Slack, your CRM or an AI agent.
- Each signal arrives with a drafted next step.
- A person approves before anything is sent.
#dealsnowOpenNous Expansion
Acme is adding the EU team next quarter. Maya, here is the pricing note, ready to send.
“We’re adding the EU team.” · QBR, 24 Sep
Every signal is an event
1 $ curl -X POST https://api.opennous.cloud \ 2 /v2/webhooks -d '{ 3 "url": "https://you.dev/hook", 4 "events": ["conversation.call_ended"] }'
- Signed with HMAC-SHA256.
- A test event and a delivery log for every endpoint.
- The same events the Workspace runs on.
Only the moments worth acting on
Most activity in an account is noise. Four checks run before anything reaches your team, so a signal always means something.
Your own team never fires a signal
Replies from teammates and bulk mail are ignored.
Old facts expire
Fresh, aging, suspect, expired. Stale news never raises a signal.
Every signal says why
Each one explains why it matters for this account.
A person approves the next step
Nothing is sent or written until someone says yes.
Where signals land
SlackIn the channel, with the next stepSee the integration › 
HubSpotTasks and updates on the right dealSee the integration › 
SalesforceOn the opportunity, kept currentSee the integration › 
ClaudeAsk what changed, get the signalsOpenNous for Claude › 
GrokSignals in every Grok chatOpenNous for Grok › WebhooksYour own systems and agentsRead the docs › Frequently asked questions
What does signal engineering do for a revenue team?
It turns customer conversations and product activity into clear signals of buying intent and risk, so your team acts on the right accounts before a deal stalls or a customer churns.
Which signals are included?
A standard set that works from day one: deal stalled, champion left, expansion requested, competitor mentioned, churn risk, budget discussed, buying signal, objection raised, stakeholder identified, next step missed and next step slipped, plus stage changes, wins and losses from your CRM.
Can we add signals specific to our business?
Yes. Describe the moment in plain language. OpenNous applies it to every new conversation and to the last 90 days of history, with the quote behind every match.
How can we trust a signal?
Every signal links to the conversation or product event it came from and explains why it was raised, so your team can verify it in seconds.
How do signals reach the team?
Through the OpenNous Inbox, Slack, your CRM and your AI agents, or into your own systems through webhooks and the events API.
Does OpenNous act on signals automatically?
No. Each signal comes with a recommended next step, and nothing is sent to a customer or written to a system without a person’s approval.
Do we need to set up rules or tag calls?
No. The standard set works as soon as your tools are connected. You only write a rule when you want a signal of your own, in plain language.
Where do signals come from?
From your call recorder or meeting notes (Fireflies, Fathom, Granola), Gmail and Outlook, Slack, your CRM and product usage from PostHog, matched to the right account, deal and person.
How is a signal different from a CRM alert?
A CRM alert fires when a field changes. A signal comes from what customers actually said and did, with the quote or event behind it and why it matters for that account.
Who sees a signal?
The people who can see the account. A signal from a private email or call shares the business fact, not the message itself, so private conversations stay private.
Do signals cost extra?
No. Credits are spent when OpenNous processes a conversation. Signals, insights and account summaries are included.
Can we build our own workflows on signals?
Yes. Every signal reaches your systems as a signed webhook, and your agents can read them over the OpenNous MCP server.
