Get in touch

Enterprise

Keep your systems of record. Keep your execution tools.

Capability-layer architecture for organizations that already have a stack. 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.

Systems of record

  • Workday
  • Salesforce
  • SAP
  • ServiceNow
  • NetSuite

Signal in — objectives, headcount, budget, customer commitments

Priorities.ai · the capability layer

  • The FrameWho decides, what is eligible, which criteria
  • The CascadeLevels contribute, leadership answers
  • Plan of RecordWhat was decided, and why

REST API · MCP endpoint · Webhooks

Commitment out — epics, milestones, project entries with rationale attached

Systems of execution

  • Jira
  • Azure DevOps
  • Asana
  • Linear
  • ServiceNow PM

IdentityOkta · Entra ID · SAML/OIDC

InsightSnowflake · 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 deployment

  1. 01Connect your identity providerOkta, Entra ID, or any SAML/OIDC IDP
  2. 02Provision usersAdmin console or POST /v1/workspace/members
  3. 03Issue API keysOne per consuming system
  4. 04Connect the execution toolJira, Azure DevOps, Asana, Linear
  5. 05Subscribe to publication webhooksFires when a priority list publishes
  6. 06Run the first cycleWe run it with your team

Added when you already have the data infrastructure

  • WorkdayHeadcount and org structure → item pool enrichment
  • SalesforceCustomer commitments → dependencies on the items they touch
  • Snowflake / DatabricksDecision log → your analytical layer, by webhook

Implementation is included in year one of the enterprise license.

Supported integrations

Shipped Planned

Systems of execution

  • Jira
  • Azure DevOps
  • Asana
  • Linear
  • ServiceNow PM

Systems of record

  • Salesforce
  • Workday
  • SAP
  • ServiceNow HRSD/ITSM

Identity

  • Okta SAML/OIDC
  • Entra ID
  • SCIM provisioning
  • Ping Identity

Insight

  • Snowflake
  • Databricks

Other

  • MCP endpoint
  • HubSpot
  • GitHub

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

Data residency controls and dedicated infrastructure options are on the roadmap for enterprise customers with compliance requirements. Contact us →