Keep your systems of record. Keep your execution tools.

Your organization has already invested significantly in the right infrastructure at both ends of its operating model.

At one end: Workday for people data. Salesforce for customer data. SAP for financial truth. ServiceNow for operational workflows. These are not going anywhere, and replacing them is not the point.

At the other end: Jira, Azure DevOps, Asana, or Linear for execution. Your teams are in these systems. The work happens here.

Priorities.ai does not ask you to replace any of them. It connects to the ones you have and fills the structural gap between them.

The capability layer model

Priorities.ai is designed to be deployed as a horizontal capability layer — an API and governance surface that sits between your existing enterprise systems without displacing them.

┌──────────────────────┐    signal     ┌──────────────────────────┐    commit     ┌───────────────────────┐
│  SYSTEMS OF RECORD   │    ──────→    │   PRIORITIES.AI           │    ──────→   │  SYSTEMS OF EXECUTION │
│                      │               │                           │               │                       │
│  Workday             │               │  The Frame                │               │  Jira                 │
│  Salesforce          │               │  The Cascade             │               │  Azure DevOps         │
│  SAP                 │               │  The Plan of Record       │               │  Asana / Linear       │
│  ServiceNow          │               │                           │               │  ServiceNow (PM)      │
│  NetSuite            │               │  ─── REST API ────────    │               └───────────────────────┘
└──────────────────────┘               │  ─── MCP endpoint ────    │
                                       │  ─── Webhooks ──────────   │
                                       └────────────┬──────────────┘
                                                    │
                                   ┌────────────────┴───────────────┐
                                   │                                │
                        ┌──────────┴──────────┐         ┌──────────┴──────────┐
                        │  IDENTITY           │         │  INSIGHT            │
                        │  Okta / Entra / SCIM│         │  Snowflake          │
                        │                     │         │  Databricks         │
                        └─────────────────────┘         └─────────────────────┘

The integration points:

Signal in (from Systems of Record): Strategic objectives, headcount constraints, budget data, customer commitments, and operational signals flow into Priorities.ai to inform the Frame and populate item pools.

Commitment out (to Systems of Execution): Published priority lists trigger structured synchronization to execution tools — creating epics, milestones, or project entries with the item’s priority, rationale, and relationship context attached.

Identity plane integration: Organizational identity (who is in the system, what roles they hold, which authority lanes they belong to) comes from your identity providers — Okta, Entra ID, or any SAML/OIDC-compatible IDP. Provisioning is managed through SCIM (planned) or direct user management.

Decision warehouse export: The decision log — every governance event, every session result, every published priority list — can be piped to your analytical warehouse for cross-system reporting, executive dashboards, and compliance audits.

Organizational identity mapping

Every enterprise deployment requires a mapping between organizational identity and Priorities.ai roles.

Priorities.ai uses an internal identity concept — External Identity — to bridge external system users with the platform’s governance model. External identities carry:

A workspace-scoped identifier
A role assignment (Cycle Owner, Facilitator, Contributor, Observer, Admin)
An external system reference (Jira user ID, Workday employee ID, Okta ID)

This mapping is what allows Catchball proposals to carry the organizational weight of the authority behind them. When a VP submits an acceptance, the platform knows not just that a user clicked a button — but that the user holding the VP-level authority lane for this track accepted the proposal.

Implementation architecture

Minimum viable deployment:

Configure identity provider (Okta, Entra, or SAML IDP)
Provision users via admin console or API (POST /v1/workspace/members)
Create API key for each consuming system
Configure connector for execution tool (Jira, Azure DevOps, etc.)
Set up webhooks for priority list publication events
Run first prioritization cycle

Full-stack deployment (for organizations with existing data infrastructure):

All steps above, plus:
Workday integration: headcount and org-structure signals → item pool enrichment
Salesforce integration: customer commitment data → dependency relationships on relevant items
Snowflake / Databricks: decision warehouse export via webhook → your analytical layer

Implementation is included in Year 1 of the enterprise license. We run the first cycle with your team.

Supported integrations

Category	System	Status
Systems of Execution	Jira	✅ Shipped
	Azure DevOps	✅ Shipped
	Asana	✅ Shipped
	Linear	✅ Shipped
	ServiceNow (PM)	✅ Shipped
Systems of Record	Salesforce	✅ Shipped
	Workday	Planned
	SAP	Planned
	ServiceNow (HRSD/ITSM)	Planned
Identity	Okta SAML/OIDC	✅ Shipped
	Entra ID (Azure AD)	✅ Shipped
	SCIM provisioning	Planned
	Ping Identity	Planned
Insight	Snowflake	Planned
	Databricks	Planned
AI Agent	MCP endpoint	✅ Shipped
CRM	HubSpot	✅ Shipped
Engineering	GitHub	✅ Shipped

Deployment model

Priorities.ai runs as a cloud-hosted service on Supabase infrastructure. Every enterprise deployment is:

Isolated at the workspace level with row-level security on all tables
Accessible via a dedicated Supabase project URL
Administered by your designated workspace owner