OpenNous
Get started

one centralized source of truth

OpenNous unifies your team's conversations, meetings and signals, so sales reps spend less time on admin work, revenue leaders trust the pipeline, and deals stop slipping through the cracks.

Marcus Reed
Sales · just now

Built on the tools your team already runs

  • HubSpot
  • Salesforce
  • Attio
  • Gmail
  • Granola
  • Fireflies
  • Fathom
  • Slack
  • Stripe
  • Claude
  • ChatGPT
  • Cal.com

Fragmented revenue data

Revenue data and customer behaviour happen inside Slack, calls, your inbox and PostHog. Your CRM is manually updated and goes stale, which leads to slow follow-ups, forgotten deals and agents hallucinating.

The context graph for people and agents

OpenNous unifies every customer interaction from your revenue tools and turns them into intelligence, so your team and your agents know who to follow up on, which opportunities are rising and what the next step is.

Run revenue from everywhere

Read the same account record wherever the work happens: in Claude Code with the plugin, in your own agents over MCP and the API, or in the OpenNous workspace with your whole team, every answer carrying its source.

Your systemsGmailGranolaFirefliesSlackStripePostHog
Written backHubSpot⇄account · stage · owner
Account briefICP 82
Meridian Health$40k · evaluation
Budget confirmed for Q1call · 12 Sep
Champion replied3d ago
Stage moved to evaluationCRM
Usage down since the demo2w
Next actionSend the security pack
revenue — claude — 118×34
Claude Code v2.1.284
Welcome back Sofia!
▐▛███▜▌
▝▜█████▛▘
▘▘ ▝▝
Opus 5.5 · Claude Max
~/revenue
Tips for getting started
Type / for the opennous skills
Recent activity
2h ago Dealer pipeline review
1d ago Soft pull objections
>
? for shortcuts⏵⏵ accept edits on (shift+tab to cycle)
Get started in seconds
Claude→ChatGPT→Claude Code→
Or build on the headless API →

Run revenue on a reliable infrastructure

The follow-up is drafted for you

Written from the call, each point linked to the moment it was said.

Handoffs write themselves

When a deal closes, CS gets the handoff with every promise and its source.

A pipeline you can trust

New stakeholders, competitors named on calls and threads that went quiet.

Grow the accounts you have

Usage, new teams and renewals turn into an expansion play, ready to send.

Ask in Claude, ChatGPT or your own agent

Your agents read the same account record, with the source behind every answer.

Build on the graph

Read any account over the REST API, MCP or the Claude Code plugin, with the source on every field.

For GTM engineers →API docs →
FIG 2.1
POST/v2/context
curl -X POST https://api.opennous.cloud/v2/context \
  -H "Authorization: Bearer $NOUS_API_KEY" \
  -d '{"focus":"meridian-health.com"}'

{ "icp": { "score": 82 },
  "claims": [{ "property": "deal.budget",
    "confidence": 0.94, "freshness": "fresh" }] }

REST API

The whole account, its people and its timeline in one call.

FIG 2.2
MCP · get_contextaccount · meridian-health.com

MCP server

Give Claude, ChatGPT or your own agent the account.

FIG 2.3
claude code
› /opennous:brief meridian-health.com● get_account · 6 people · 41 claimsPriya Nair is the economic buyer.Budget $40k for Q1 [call 12 Sep]Open: DPA review with IT [email 29 Sep]

Claude Code plugin

Briefs, follow-ups and pipeline reviews from the terminal.

Case studies

View all →
Example

“Every rep walks into a call knowing what was said last time, and the follow-up is written before they close the tab.”

Priya NairVP Revenue · Meridian Health
12 monthsof history on day one
Example

“The CRM stopped being a place we type into. It is current because the calls make it current.”

Tom OkaforRevOps lead · Meridian Health
1 recordper account, across six systems

Every account on one record you can trust

Connect your CRM and your inbox, and the account record builds itself from the last 12 months.

Get a demoStart free