Use cases
Agent Builders Enterprise Search Search Platforms
Product
Context layer Platform Demo Pricing Blog Request demo
The Behavioral Context Layer for Enterprise AI

Your AI doesn't know
who to route to. what to approve or dismiss. who's the right alternative. when to assign or escalate.

Enterprise AI plateaus because it can't access tacit knowledge: who people actually rely on, how decisions route in practice, where work stalls. BehaviorGraph makes it queryable, powered by research-backed behavioral science and organizational network analysis.

Enterprise Search
AI Agents
AI Governance
Workflows

Find the right people, not just the right files.

Live context
Analyzing organizational context...
L7
LEG-07 Primary owner
Senior Counsel · Legal · APAC contracts
Relevance0.92 Load38h/wk CentralityHigh
At capacity
Route to qualified backup
Decision pathLEG-07 → LEG-02 → Dir. Legal
Escalation SLA24h to Director
Peer reliance0.87 — peers consistently route this type of work here
Cross-teamProduct → Legal bridge active
GovernancePolicy-compliant
Audit trail logged · Metadata only · No content accessed

Integrates with your existing stack

Google
Microsoft 365
Slack
Jira
Salesforce
Box
ServiceNow
Workday
SAPSAP

Use cases by your role

Different roles, one behavioral context layer. See what BehaviorGraph looks like for your team.

For AI / Platform Engineering

Wire org context into your AI stack

You build the enterprise search, agents, or RAG pipelines. BehaviorGraph gives your systems the organizational context they're missing: who to route to, who's available, and when to escalate. Plug in via API, MCP, or RAG enrichment.

  • Context API with coded identifiers (LEG-07, ENG-01)
  • MCP tools for agent orchestration platforms
  • RAG pipeline enrichment with people context
  • Sandbox environment for testing before production
  • Works with LangChain, CrewAI, or your own framework
POST /v1/agents/route
// Agent requests routing decision
{
"action": "approve_contract",
"route_to": "LEG-02",
"reason": "primary at capacity",
"backup": "LEG-05",
"escalation": "Dir. Legal (24h)",
"human_action": "required"
}
For Ops, Eng Leads, and Managers

See how your org actually works

The org chart shows reporting lines. BehaviorGraph shows who people actually rely on, where handoffs stall, and which individuals are overloaded. Find bottlenecks before they become incidents. Identify the right alternative when the primary is at capacity.

  • Live org map with relevance, load, and capacity signals
  • Bottleneck and single-point-of-failure detection
  • Bridge connector visibility across teams
  • Slack/Teams bot for quick "who owns this?" queries
  • Team health signals from behavioral metadata
Live Org Map · Your Team
E1
ENG-01 · 89h/wk · Bridge to 3 teams Overloaded
S4
SAL-14 · 92h/wk · 4 teams route here At capacity
O9
OPS-29 · 19h/wk · Peer endorsed Available
P3
PRD-03 · 44h/wk · Cross-team handoffs Normal
"Who can take over APAC procurement if OPS-25 is out?"
OPS-29 (relevance 0.81, available, peer endorsed). Escalate to Dir. Ops if unresolved in 24h.
For Governance, Security, and Compliance

Every AI decision, auditable and explainable

Your agents follow the rules. But rules on paper don't always match how the org operates. BehaviorGraph gives governance teams the behavioral context to evaluate whether AI routing decisions were appropriate in practice, and the audit trail to prove it.

  • Full audit trail on every routing recommendation
  • Explainable math: defined equations, not black box outputs
  • Coded identifiers prevent misuse for employee evaluation
  • Metadata only by architecture (not a config toggle)
  • Model walkthrough available for your security team
  • SOC 2 readiness, GDPR/CCPA alignment
Audit Trail · Routing Decision #4,291
Action Route contract review
Selected LEG-02 (relevance 0.78, available)
Skipped LEG-07 (primary, at capacity 38h/wk)
Escalation Dir. Legal if unresolved in 24h
Signals used Relevance, load, peer endorsement, calendar
Human action Approved by manager
Data accessed Metadata only
For Change & Transformation Leaders

See if your org actually changed — not just the chart

Org charts update in a day. Behavior takes months. BehaviorGraph tracks whether people have actually adopted new workflows, who the informal leaders are that drive real change, and where old routing patterns are still holding your transformation back.

Why BehaviorGraph can see this

BehaviorGraph applies Organizational Network Analysis (ONA) and behavioral science to map how work actually flows — who meets with whom, who routes decisions to whom, and who peers genuinely rely on.

The approach aligns with the frameworks practitioners already use: Prosci ADKAR calls for identifying change champions and measuring adoption reinforcement — BehaviorGraph shows you who those champions actually are based on peer behavior, not job title. Kotter's 8-Step Model requires building a guiding coalition — BehaviorGraph finds the informal connectors who can carry the message across team boundaries. And Nudge Theory (Thaler & Sunstein) shows that behavior follows environment and social proof — BehaviorGraph surfaces where those social proof signals are strongest and where they're absent. Methodology backed by academic research from Columbia University and validated against real organizational data. Read the research →

  • Adoption tracking: new workflows vs. old behavioral patterns side by side
  • Identify informal influence leaders — not just managers
  • Spot resistance signals before they become blockers
  • Measure cross-team connection changes after a reorg
  • Track escalation path changes over time
  • Continuous signal, not a one-time survey
Change Tracker · Q2 Reorg · Week 6
NEW APPROVAL WORKFLOW ADOPTION
ENG
91%
PRODUCT
74%
FINANCE
38% !
LEGAL
85%
Resistance signal FIN-04 still routing old path
Informal leader ENG-11 driving peer adoption
Cross-team links +14 new connections since reorg
Recommended action Brief FIN-04's manager · engage ENG-11 as change champion

Enterprise
Context

Every platform reads documents and org charts. BehaviorGraph adds a behavioral layer — relevance, capacity, response patterns, and real routing paths.

Explore the context layer
Context API Search · Agents · Governance Behavior Graph 🏗️Infrastructure 📦Products People ⚙️Processes 📄Content 🤝Customers 🔗Workflows Relevance scores SME domains Load & capacity Current tasks Response habits Work preferences Personal style MR KL TS J A SC JP ML R Enterprise graph Behavioral graph
The missing layer

Enterprise AI is building on two tiers. The third is still missing.

Tier 1
Structural

Org charts, reporting lines, formal titles. Static. Reflects intended structure, not actual behavior.

HRISOrg chartJob titles
HRIS platforms · reporting tools · org chart systems
Tier 2
Informational

Documents, wikis, tickets, and meeting transcripts. Richer context, but still reflects what was written — not how work moves.

DocumentsWikisTicketsTranscripts
Enterprise search · knowledge bases · ticketing systems · workflow platforms
Tier 3
Behavioral BehaviorGraph

The tacit knowledge that lives in people's habits, not in documents. Captured at scale using behavioral science, validated in real organizations.

Tacit knowledgeCollaboration patternsPulse surveysWorkflow dataSilence signals
Research-backed. Privacy by design. Missing from every other AI stack.
The accuracy wall

Your AI reads the docs. It still misroutes the work.

Enterprise search and agents plateau because they lack behavioral context. Documents tell you what's written. BehaviorGraph tells your AI who knows, who decides, and how work actually flows.

📄vendor-contract-template.docx
📄APAC-policy-v2.pdf
📄procurement-guide-2024.pdf
3 documents found. No people context.
What AI sees

Documents, files & workflows

Authors, org charts, and ticket history. Static snapshots that don't reflect how the organization actually operates.

  • 📄 Files, wikis, and authored documents
  • 🗂️ Org charts and formal titles
  • 🎫 Defined tickets, workflows, and processes
PROCESS + INFORMATION LAYER
DL
??
⚠️Routed to: FIN-04 (by title)
⚠️Reality: FIN-04 is on leave
AI routed by org chart. Work stalled.
The mismatch

Authorship ≠ expertise

Org charts, documents, and workflow definitions each diverge from the reality of how decisions are made and work actually moves.

  • ⚠️ Authorship ≠ expertise or current ownership
  • ⚠️ Org chart ≠ who people actually rely on day-to-day
  • ⚠️ Defined workflow ≠ real execution path
RESULT: AI misroutes work and slows adoption
L7
LEG-07
Relevance 0.92 · Legal · APAC
Backup: LEG-02 (available)
Escalation: Dir. Legal in 24h
Right person + fallback + escalation path.
What BehaviorGraph adds

Operational reality

BehaviorGraph is the behavioral layer: who knows what, who people rely on, how work actually flows, and who has real decision authority.

  • Relevance Score · SME Score per domain
  • Behavior Graph · Network Analytics
  • Approval authority · Informal influence
BEHAVIORAL LAYER → BEHAVIORGRAPH
Organizational Context Layer

Your org, as it actually operates.

AI works in pilots and verticals. But your org runs horizontally across teams, handoffs, and approval chains. When you optimize one team, others still drag execution down because the handoffs were never designed for AI. BehaviorGraph catches that org design debt so you don't need a reorg. And when AI can't answer, it escalates to the right person with the right context and permission boundaries.

Example: An agent detects an invoice stuck past SLA. The org chart says route to the Finance lead. BehaviorGraph knows she's at 120h/wk and only checking her priority list, identifies a qualified backup who handles the same contract type, and escalates to the Director if unresolved in 24h.

Signals in
Collaboration patternsCalendars, presence, meetings
Relevance & expertiseWho peers rely on, by domain
Pulse surveysTeam health & readiness
Workflow & handoffsApprovals, escalations, routing
Metadata-only · privacy-first
Live Org Map · 7 teams · 42 people / 2,000 total employees
hover a node to inspect
ENG-01 DO NOT ROUTE 89h/wk · Bridge connector across 3 teams
Risk: if this person burns out, knowledge flow between Eng, Product, and Data breaks
SAL-14 OVERLOADED 92h/wk · 4 teams route through here
Action: redistribute to SAL-16 (available, same domain)
OPS-29 SAFE TO ROUTE 19h/wk · Peer-endorsed for cross-team handoffs
Suggested backup for OPS-25 (overloaded)
Large = high centrality
Bridge connector
Overloaded / bottleneck
Peer reliance (thick = strong)
Routing path
Relevance: who peers rely on for this type of work
Plugs into
Enterprise searchAdd people context to every result
Agent orchestrationRoute with real authority & fallback
AI governanceBehavioral context for smarter guardrails
Workflow systemsFix handoff gaps without a reorg
API-first · works with your existing stack
Permission-AwareRespects every access boundary at runtime
Policy-AlignedRoutes within your approval structure, never around it
Human-in-the-LoopKnows when to defer. Escalates to qualified people, not just managers
Full Audit TrailEvery routing decision is traceable and explainable
Metadata-OnlyReads patterns, not message content — privacy by design
The Enterprise AI Stack
Enterprise AI systems require three layers to operate inside real organizations.
Model Layer
Foundational reasoning, language, and code models.
Content & Data Layer
Enterprise documents, knowledge bases, and RAG systems.
Organizational Context Layer — BehaviorGraph
Behavioral mapping of networks, expertise, and workflow.
Designed by behavioral science and enterprise knowledge management researchers.
Built on years of research into how organizations actually coordinate, decide, and transfer knowledge.
Product in action

Routing an AI inquiry through the real org.

An agent detects an invoice approval delay beyond SLA. BehaviorGraph surfaces the primary approver's load, relevance score, and cross-team centrality, then routes to a qualified alternative and flags escalation to the Director.

  • Find the right person, not just the right document. The expert who can actually unblock work
  • Route to actual owners with live relevance paths and fallback ownership instead of static routing
  • Escalate with real org awareness. Know who can approve, who can step in, and when a human decides
BehaviorGraph · Routing Decision Live context
Inquiry
Why has the invoice not been approved? Triggered by agent observing delay beyond SLA.
Decision chain
Primary Candidate
⚠ Load: 40.2 hrs/wk · Overloaded
Alternative Candidate
✓ Available · Relevance: Medium
Escalate per Policy
SLA > 24 hrs → Director
Decision signals
Relevance score (Finance, 99th pct) 0.89
Network centrality High (cross-team)
Current load 40.2 hrs/wk · Overloaded
Dependency impact 4 teams rely on this node
Works with your stack

What BehaviorGraph adds to your existing AI.

BehaviorGraph plugs into your enterprise search, agent platform, or governance layer — adding the behavioral context that makes every AI decision more accurate.

People search

Find the right person, not just the right document

Ask "who handles vendor contracts?" in Slack, Teams, or chat. BehaviorGraph returns the person teams actually rely on, their availability, and a backup if they're at capacity.

Search enrichment

Add people context to your existing search

When your enterprise search returns documents, BehaviorGraph adds who owns each topic, who's available, and the escalation path. Works with Glean, Coveo, Elasticsearch, or your own.

Permission-aware

Different people, different answers

Results respect every access boundary at runtime. Different people get different answers based on their access level, role, and organizational position.

Agent routing

Give agents the org context to act correctly

Before your agent takes a consequential action, BehaviorGraph tells it who should handle it, who has authority, and where to escalate. Via API or MCP.

Cross-functional routing

Shortest path across departments

Find the fastest route across legal, finance, ops, sales, and product. Automatic fallback when the primary person is overloaded.

Escalation

Escalate to the right person with full context

When AI can't answer, escalate to the right person with the reasoning, context, and permission boundaries already attached. Not just a ticket.

Governance

Every decision explainable and auditable

Every routing decision is traceable: who was chosen, why, what the alternatives were, and whether it followed your approval structure.

Business impact

What BehaviorGraph saves your organization.

Estimated annual value per 2,000 knowledge workers.

Expertise & authority routing
$3.2M–$6.9M

Find the right person faster. 50% of routing waste recovered.

Fewer "who handles this?" hours $2.5M–$5.0M
AI agent misrouting reduced 70% $0.4M–$1.0M
Wrong escalation delays eliminated $0.3M–$0.9M
Bottleneck prevention & onboarding
$2.0M–$4.4M

Unblock overloaded people. Get new hires productive 30% faster.

Bottleneck productivity recovered $1.2M–$2.7M
Onboarding acceleration $0.8M–$1.7M
Attrition prevention & governance
$2.4M–$5.1M

Detect burnout before departures. Make AI governance behavioral.

Burnout departures prevented $1.5M–$3.5M
AI governance accuracy $0.5M–$1.0M
Compliance cost reduction $0.4M–$0.6M

Estimates per 2,000 knowledge workers at $105/hr fully-loaded rate. Scales linearly with org size. Try the calculator with your numbers →

Open platform

Access organizational context from anywhere.

APIs, MCP, RAG enrichment, or direct chat. Plug behavioral context into your existing stack however it fits.

Context AI for Search
GET /v1/search/enrich
// Enrich search with org context
{
"query": "APAC vendor",
"owner": "LEG-07",
"relevance": 0.92,
"backup": "LEG-02"
}

Context AI for search

Plug into your enterprise search to enrich every result with people context, relevance, and routing.

Agents API
POST /v1/agents/route
// Agent requests routing decision
{
"action": "approve_contract",
"route_to": "LEG-02",
"reason": "primary at capacity",
"escalation": "24h → Director"
}

Agents API + MCP

Expose routing and escalation context to agent platforms via REST API or Model Context Protocol (MCP).

Chat API
POST /v1/chat/ask
// "Why is onboarding slow in Eng?"
{
"bottleneck": "ENG-03",
"load": "42h/wk, 6 teams depend",
"silence": true,
"suggestion": "Redistribute
to ENG-07 (available, peer-endorsed)"
}

Chat API

Embed conversational org intelligence into your apps. Ask questions, get answers grounded in behavioral context.

RAG Enrichment
// Inject into your RAG pipeline
POST /v1/rag/enrich
{
"chunks": ["...doc results"],
"add_people": true,
"add_routing": true,
"owner": "LEG-07",
"escalation": "Dir. Legal"
}

RAG enrichment

Inject people context into your retrieval pipeline. Re-rank by expertise, add owners, and surface who to escalate to.

Live Chat
Who should review the APAC vendor contract if Legal is at capacity?
BehaviorGraph Sarah Chen is primary but at high load. Route to James Park — relevance 0.78, available. Escalate to Dir. Legal if unresolved in 24h.

Governance-compliant · audit trail logged

Live chat

Ask your org questions directly. Real-time answers about who to route to, who's available, and how work actually flows.

API, MCP, and RAG endpoints use coded identifiers (e.g. LEG-07) to prevent misuse for individual evaluation. Live chat uses names for natural conversation and is available for operational queries only, not for HR assessment or personnel decisions. Identity resolution is handled by your internal systems with appropriate access controls.

Beyond documents

Find the right people, not just the right files.

Enterprise search finds what's written. BehaviorGraph finds who can actually help — and connects them.

SR
Sales rep needs feature approval
Standard process: 6 months
1
The situation

A sales rep needs a feature to close a deal. The formal process takes six months. The customer can't wait. The feature was built in a hackathon but never documented.

Standard process won't work. The knowledge exists, but not in any system.
📄product-roadmap.pdf — 6 months out
📄design-spec-v1.docx — outdated
Nothing actionable found
2
What search finds

Product docs, no match. Roadmaps, not for 6 months. Design specs, out of date. The work was never written down, so enterprise search can't find it.

Documents exist, but nothing actionable. Search hits a dead end.
👤Engineer found — built similar feature
Peer recognized · relevant activity
Hidden expertise, surfaced
3
What BehaviorGraph discovers

An engineer who built a similar feature in a hackathon. Peer recognized, relevant code activity, proven impact. None of it in any document.

Hidden expertise, surfaced. Invisible to search, visible to BehaviorGraph.
SR
AK
Connected within guardrails
🛡️Approval path respected
4
AI takes action

Connect the sales rep to the engineer who built it. Share the customer need, past hackathon work, and domain fit so both sides have full context before the conversation.

Within guardrails — org policies, access controls, and approvals respected.
FAQ

Common questions

What is BehaviorGraph?

BehaviorGraph is the behavioral context layer for enterprise AI. It turns collaboration patterns, relevance signals, pulse surveys, and workflow data into a queryable layer that enterprise search, AI agents, and governance platforms can use at runtime to find the right person, route decisions correctly, and escalate with full context.

Why do enterprise AI platforms need behavioral context?

Enterprise AI reads documents and org charts, but doesn't know how the organization actually works. Who do people rely on? How do decisions route in practice? Where do bottlenecks form? This missing behavioral layer causes AI to misroute work, miss the right person, and stall on escalation.

What is tacit knowledge and why can't AI access it today?

Tacit knowledge is what people know but don't write down: who actually handles APAC contracts, which team boundary always stalls handoffs, who to go to when the usual person is overloaded. Today's AI reads documents and org charts but is blind to how work actually flows. BehaviorGraph captures tacit knowledge at scale using a research-backed framework grounded in behavioral science and organizational network analysis, tested in real enterprise environments. The result: organizational intelligence your AI can query at runtime, from six data sources you already have, privacy by design.

How does BehaviorGraph work with existing enterprise search?

BehaviorGraph plugs into your existing stack via REST API, MCP (Model Context Protocol), or RAG enrichment. It adds people context to every result: who actually owns a topic, who is available, and who to escalate to. Users find the right person, not just the right file.

Does BehaviorGraph read emails or message content?

No. BehaviorGraph operates on metadata only: collaboration patterns, calendar signals, presence data, and pulse survey responses. It never reads message content, emails, or documents. Privacy by design.

How does it strengthen AI governance?

BehaviorGraph makes governance behavioral, not just rule-based. It knows when to escalate, who can approve, and when a human must decide. It routes within your approval structure, never around it. Every decision is auditable.

What data sources does BehaviorGraph use?

Collaboration patterns (calendars, meetings, presence), relevance and expertise signals (who peers rely on), lightweight pulse surveys (team health, readiness), workflow events (approvals, escalations, handoffs), and cross-team communication patterns. All metadata-only, connected via API.

Do we need an enterprise search product like Glean to use BehaviorGraph?

No. BehaviorGraph works in three ways: (1) As an overlay on top of your existing enterprise search, enriching results with people context. (2) As a standalone context layer that your AI agents query directly via API or MCP. (3) As a full behavioral intelligence platform with its own routing, escalation, and governance capabilities. If you already have enterprise search, BehaviorGraph makes it better. If you don't, BehaviorGraph still provides the organizational context that search alone can't.

How does BehaviorGraph work with AI agents and orchestration platforms?

Your agents call our API or MCP tools before taking action. BehaviorGraph tells them who to route to (based on org chart authority combined with behavioral relevance), who's available as backup (when the primary is overloaded, with qualified alternatives suggested and a human in the loop for confirmation), and when to escalate (with the full decision path and approval chain). You can use this alongside agent platforms like LangChain or CrewAI, or directly through our API without any other platform. We cover the part others don't: the organizational context that makes routing decisions accurate.

Can we start with just one use case and expand later?

Yes. Most companies start with one of three entry points: (1) Search enrichment for teams already using enterprise search. (2) Agent routing for teams deploying AI agents. (3) Bottleneck detection for operations or engineering leads who want to find where work stalls. You can also add our AI agent directly to Slack or other platforms so your team can ask questions like "who owns APAC vendor contracts?" right where they work. Or you can build BehaviorGraph into your own workflows through our API. Each connects to the same behavioral graph, so expanding to other use cases later requires no additional data setup.

Request demo

Your AI already reads the docs. Give it the org.

BehaviorGraph works alongside your existing enterprise search, agent platform, or governance stack. If your AI is accurate on content but still misroutes decisions, stalls on escalation, or misses the right person, we should talk.