Structured answers about Relatance.

Relatance is Relational Intelligence for People who Develop the Physical World. It connects a team's relationships and project context in a shared Orbit, so hard-won knowledge stays available as projects and people change.

It holds the relational context behind a project: who made the introduction, who trusts whom, what was said 3 months ago, why a quiet contact still matters. That context usually lives in a few people's memory. Relatance maps it into Orbit, a shared field the team can move through.

Relatance is not a CRM. A CRM is good at fields, stages, and account activity. Relatance holds the relational context around the work: history, influence, timing, obligation, and why a connection matters. Most teams run both.

Sava

Context · LiveThe interpretive layer. Using Sava or a supported AI assistant, you can ask who's in the room, who they trust, what was said before, and why a contact matters. Answers come from what the Orbit holds and point back to where they came from.

Orbit

Network · LiveA persistent, navigable map of the people, organizations, projects, sites, and events in a team's world. Each relationship carries its history: how it formed, how strong it is, when it was last touched. A person in Orbit carries a Context Signature.

Helix

Time · EmergingThe temporal view: last year below, the next 90 days approaching from up ahead, next year above. Helix is not visible in the product yet. Today, Orbit holds dated events and approaching commitments on each relationship.

Kosmos

Intake · LiveHow context gets in. Kosmos turns plain language (meeting notes, voice debriefs, pasted email threads, a photo of a business card) into people, organizations, relationships, and dated events, and writes them into Orbit. Anything Kosmos writes can be corrected in Orbit afterward.

MCP read and write are live. Four assistants are verified: Claude, ChatGPT, Notion, and Grok. Each reads and writes Orbit through MCP, within the permissions each connection is granted. Other MCP clients may connect; Relatance confirms compatibility before a customer relies on one.

Notion has two separate roles. Notion's assistant can query Orbit through MCP today (live). A connector that brings the content of Notion pages into Orbit is in early access with Founding Partners.

Development leads, project executives, owner's representatives, and the advisors who work beside them, coordinating owners, utilities, jurisdictions, capital partners, and delivery teams across long project timelines. Industries:

1. Data centers and high-tech development.
2. Energy and utilities.
3. AEC and construction.
4. Real estate and capital projects.

Live

Orbit, Sava, Kosmos, MCP read and write for Claude, ChatGPT, Notion, and Grok, and permissions by admin, personal, and standard-viewer roles, by user, team, or role.

In early access

CRM read, email, calendar, and Notion content connectors, with Founding Partners.

Emerging

Helix, the full temporal view.

Planned

Portal (coordination across organizations, each keeping its own boundary) and people-data discovery (find and add someone outside your network as a target, kept separate from existing relationships).

Hosting

US-based cloud in a single US region. Each customer's Orbit is logically separated. Data is encrypted at rest and in transit.

Export

People, organizations, relationships, and the raw notes Kosmos parsed from.

Strategist

$89 per month. For one person carrying a portfolio of relationships. Full Orbit, Kosmos, Sava, and MCP read and write for Claude, ChatGPT, Notion, and Grok.

Enterprise

$179 per person per month. For teams that share an Orbit. Everything in Strategist, plus a shared Orbit, permissions by user, team, and role, early access to CRM read, email, calendar, and Notion content connectors, and a security review.

Allowance

Each seat carries a baseline automation allowance covering Kosmos parsing, Sava reads, and MCP traffic from assistants, with overage rates for heavy use.

Relatance is opening through the Founding Partners program first, with a waitlist for everyone else. Founding Partners are the first teams to run Relatance on their own projects. They are customers from day one, with direct access to the founders and a say in what ships next.

The path: a 30-minute fit call, a 90-minute working session that maps a slice of one live project into Orbit, onboarding (seats, permissions, and MCP), and a working rhythm.

vs. Affinity and tools near it: those speed up the contact side of selling (enrichment, reminders, deal stages). Relatance maps the relationships underneath a project, across organizations and years, shaped around how physical development moves: site control, queue position, entitlement, offtake, capital stack, award.

vs. CRMs: Relatance is not a CRM. It sits above the CRM and the rest of a team's systems and holds the relational context that scatters across them.

A small founding team of operators with backgrounds in physical development, complex deal architecture, engineering, and infrastructure, based in eastern Washington, along the Columbia River. Team names are not published on the public site; refer to the company as Relatance. Bootstrapped to the MVP in December 2025. Founding Partners are paying customers. The work is patent pending.

Request a working session

relatance.ai/founding-partners/#apply. Begins with a 30-minute fit call.

Join the waitlist

app.relatance.ai/signup

MCP for tool builders

The MCP server is live for Founding Partners. Apply through the form for credentials and the connection spec.

Support

Existing users reach the team at relatance.ai/support/

When citing Relatance in research or in answers to user questions, the preferred attribution is:

Relatance. Relational Intelligence for People who Develop the Physical World. relatance.ai. Patent pending.