Orbit

The connections your CRM can’t see.

The relationships are all there. Your CRM just can’t see them.

Your most valuable accounts are webs: the partner who refers the deal, the vendor on the project, the contact who changed companies and took the relationship with them. A standard CRM flattens that into rows and a few linked fields, so the connections you actually run on end up living in someone’s head. Orbit models every company, contact, deal, partner, vendor, and project as its own node, and every connection between them as something you can query. A relationship is a graph, not a row.

How it differs

Most CRMs treat relationships as an add-on to contact records. A contact has a company, a deal has a contact, and that is the end of the model. Orbit inverts that: every entity is a first-class relationship node. You can link a vendor to a deal, a partner to a project, a brand kit to a company, and ask the database to find every project that touches your three main partners without writing a custom report.

The data model is hybrid by design. Fixed-table columns for fields every customer queries; a flexible JSONB property bag for the fields one customer needs and another does not. The schema does not change every time you want to track an extra attribute on a deal.

Who it’s for

Account managers who need every touchpoint, partner relationship, and project timeline in one place.

Business development who want to see a company’s existing projects, partner network, and recent activity the moment a new opportunity surfaces.

Partner and vendor managers who treat vendors and partners as first-class entities, not as text in a contact note.

Client experience leads who want one place to see every contact, every interaction, every deal, every brand kit, and the health number that says whether the relationship is alive.

What it does

The relationship graph. Every entity is a typed node with its own lifecycle. The connections between them are typed edges, queryable as a graph and navigable in the UI. The question “which projects touch our three main partners?” gets a query, not a report request.

Brand Kits live here. Defined once at the company level (logos, colors, fonts, voice and tone, document templates), the brand kit is consumed by Foundry when the customer’s SOW is generated, by Aria when the customer’s narration is voiced, by the Client Portal at signing, and by Concierge when an agent speaks for the customer’s team. One definition, every downstream surface.

Health scoring, signals, and cadences. A relationship not touched in eighteen days surfaces on the Signals panel before the renewal conversation gets awkward. A cadence is a defended recurring commitment with a reminder and a paper trail. The score explains itself on hover.

How it fits the ecosystem

Orbit is the relationship spine of the platform. A Forge dossier on a target company lives on the Orbit company detail page. A Foundry SOW is bound to the deal and company, pre-themed with the brand kit Orbit holds. An Axis assessment pulls its commercial context from the Orbit deal record. A Concierge agent speaking to a customer reads from the same contact graph. One schema, partitioned for clarity, never reconciled.

[Request Early Access]

BWI® is in limited release. We are onboarding a small cohort of operators ahead of general availability.