The real-time, continuously evolving ontology of your enterprise, as an API or MCP

Bring ERP, CRM, finance, mail, support, HR and more into a connected model of how your business works. Give your team and agents tools to navigate it, understand what changed, and trace the source records.

Explore it for your team See the tools

Our first offering: the ontology for RevOps

FORMALINSIGHT ONTOLOGYIllustrative model

EntitiesWho & what

RelationshipsHow it connects

EventsWhat changed

SourcesWhere it came from

YOUR OPERATIONALOntology oracleA queryable model of the business

CRM / EXAMPLE DOMAINAccounts · opportunities · contacts

AccountholdsSubscription

Connect the commercial view to the customer’s wider operating history.

Access the ontologyAPIMCPDecision Terminal

A company-wide foundation. A focused first offering.

Model the sources you connect. Preserve identities, relationships, events and source records. Put the ontology to work for your revenue team.

WHAT WE BUILD

An operational ontology.
Not another context feed.

FormalInsight constructs a queryable ontology using your operational data: the entities, relationships, events and source records that describe how your business works.

Model the business.

Give accounts, people, orders, invoices and other operational objects explicit identities and relationships.

Entities + relationships

Creates a temporal ontology.

Model how entities and relationships evolve through time, connecting dated events with their source records.

Time + relationships + sources

Equip the agent.

Expose structured operations through API and MCP, so agents can query the model one question at a time.

Tools + reasoning

Built around your operating model.

ERP, CRM, finance, mail, support, product, HR and custom domains can be modeled through reviewed source mappings. Coverage follows the data and definitions you connect.

Inside your ontologyAn illustrative journey

01/05

It starts with how
your company works.

ERP. CRM. Finance. Mail. Support. HR. Bring the operational data you connect into one business model.

Scroll to exploreSkip

THE DIFFERENCE IS THE OPERATING MODEL

From finding information
to understanding operations.

Retrieval-only RAG gives an agent relevant passages to read. FormalInsight gives it tools to query a persistent model of your business: its identities, relationships, events and source records.

EXPLORE A QUESTION

Which Northstar account?

Illustrative example

RETRIEVAL-ONLY RAGSearch → passages

CRM01

Northstar Labs

Account ACC-1042 · Renewal in review

FINANCE02

Northstar Laboratories Ltd.

Customer CUS-782 · Invoice INV-309

SUPPORT03

Northstar / Integration

Organization ORG-91 · Open case

Relevant records, ready to read.

Matching names are useful clues. The identity relationship still needs to be established.

FORMALINSIGHT ONTOLOGYTool → structured result

resolve_identity()MCP

CANONICAL ACCOUNTNorthstar Labs

CRMACC-1042

FINANCECUS-782

SUPPORTORG-91

Source records remain attached.

One reviewed account identity.

Navigate the account and inspect how each source identity maps to it.

Reviewed mappings · Source identifiers retained

WHY IT MATTERS

Build the identity once. Reuse it across workflows.

THE ONTOLOGY IS THE WORKSPACE

Give agents tools
to work with your business.

Discover the model. Resolve an identity. Follow a relationship. Inspect a timeline. Calculate. Verify. Each step is an explicit operation over the ontology.

THE AGENT’S QUESTION

Which account do these records belong to?

FormalInsight Ontology MCPresolve_identity()Illustrative tool workflow

WHAT THE OPERATION MAKES AVAILABLENorthstar Labs

CRM ACC-1042 and billing CUS-782 resolve through reviewed identity mappings.

CRM · ACC-1042Billing · CUS-782

Start with a defined entity instead of asking the model to infer a join from matching names.

These tools navigate and analyze the ontology. Actions in ERP, CRM, mail or other business systems require separately authorized integrations.

CURRENT OFFERING / REVENUE OPERATIONS

The foundation is operational.
The first team is RevOps.

Give revenue teams a connected account model across commercial, financial, product and service data. Understand renewal friction, adoption changes and expansion assumptions with the source records in reach.

FormalInsight/Revenue operationsIllustrative product view

ACCOUNT OVERVIEW

Northstar Labs

Reviewed identity

Northstar LabsOne connected account

CRMRenewal notePositive outlook

BILLINGInvoiceOverdue

SUPPORTIntegrationThree related cases

↳Accounts, relationships and source records. Together.

SOURCE RECORDS

CRM

ACC-1042

A positive renewal note.

The commercial outlook is one part of the account’s story.

✓

Reviewed mappingSource → Northstar Labs

Ontology foundationFictional account. Connections shown after mapping review.

REVENUE LEADERS

See the account behind the forecast.

Bring commercial expectations, payment friction, adoption and service history into the same review.

A better-supported revenue conversation

REVOPS MANAGERS

Move from scattered signals to priorities.

Give the team a connected view of the accounts that need attention, and the questions still open.

Clearer handoffs and review priorities

REVOPS OPERATORS

Stop rebuilding the same joins.

Reuse the account model, inspect its history, and prepare a brief with source records attached.

Less repeated lookup and reconciliation

The opportunity: spend less effort collecting the account story and more time deciding what to prioritize next. Workflow benefits shown here are not measured performance guarantees.

A CONNECTED RENEWAL REVIEW

Less “where is it?”
More “what changed?”

Churn concerns can form across months of ordinary events. Connect the account, inspect the sequence, and ask a better question before the renewal review.

Northstar LabsILLUSTRATIVE ACCOUNT REVIEW

CRM · ACC-1042Positive renewal noteCommercial outlook

Same
account

BILLING · CUS-782Overdue invoicePayment status

CRM + BILLING

One customer. Several versions of the story.

Northstar Labs has a positive renewal note and an overdue invoice. The records use different customer identifiers.

Illustrative account review. Human review remains essential.

FORMALINSIGHT / THREE WAYS IN

One operational ontology.
For your team and your agents.

Ontology API01

Build on the business model.

Query entities, relationships, timelines and source records from your own applications.

Ontology MCP02

Give agents connected tools.

Let your agents discover the vocabulary, resolve identities and query the ontology.

Decision Terminal03

Bring the review together.

Use the RevOps Terminal to inspect account histories, challenge assumptions and prepare a decision brief.

START WITH YOUR REVENUE TEAM

Build your operational ontology.
Start with RevOps.

Bring a revenue question that crosses systems. We’ll map the sources, definitions and workflow needed to turn it into a connected operational view.

Explore FormalInsight