Pricing
Infrastructure pricing, scoped in a conversation. Start with one decision, not a contract.
Delivered with the practice. Scoped in a conversation.
Priorities.ai is not sold as a standalone software subscription. It is delivered through a Peak Priorities engagement because the platform and the operating practice have to be established together. Software access, implementation, and the first working cycle are scoped as one program.
We don’t publish a rate card. Scope varies with the size of your organization, the depth of implementation, and what your first year needs to accomplish — and we would rather have one honest conversation than a pricing page that overpromises or underdelivers.
Start with one decision
The entry point is a paid working session on one real, contested decision. You leave with a ratified, forwardable decision record, and we both leave knowing whether a broader engagement is a fit.
What a full deployment includes
A full engagement includes platform access without per-seat arithmetic:
- Unlimited users, sessions, and cycles
- All current API access (items, cycles, sessions, tool sessions, catchball, webhooks, connectors)
- MCP endpoint access for AI agent integrations
- Integration connectors (Jira, Slack, Asana, Notion, Miro, Salesforce, and more)
- Standard SSO (SAML/OIDC via Okta or Entra ID)
- Workspace admin console
- Audit and governance event tables
The term and level of access follow the engagement. Volume and multi-year structures are part of the conversation.
Year 1: we run the first cycle with you
This is not optional. Every organization that deploys Priorities.ai gets a structured implementation as part of Year 1 — not onboarding documentation and a Zoom call. We work with your team to:
- Map your organizational decision structure (tracks, altitudes, authority lanes)
- Configure the identity integration (Okta, Entra, or workspace-managed users)
- Run your first full prioritization cycle end-to-end
- Establish the connector integrations to your execution tools
- Train your Cycle Owners and Facilitators
We include this because the platform is only as useful as the operating practice around it. The first cycle establishes that practice with your team.
Enterprise add-ons
Available to organizations with specific compliance or infrastructure requirements; quoted separately based on scope.
| Add-on | Description | Status |
|---|---|---|
| SCIM Provisioning | Automated user lifecycle management from your IDP | Planned |
| Data Residency | EU / APAC deployment option | Planned |
| SOC 2 Type II Report | Annual audit report | Planned |
| Custom Connector Development | Connector built and maintained by Priorities.ai engineering | Roadmap |
| Dedicated Infrastructure | Single-tenant deployment | Roadmap |
| Custom MSA / DPA | Bespoke master services agreement | Talk to us |
We mark these honestly. If a requirement on this list is a blocker for you, tell us — that’s exactly the conversation we want to have before you commit, not after.
The “is it worth it?” question
The right answer is always a function of what the current state is costing. An organization running planning cycles that reset, priorities that drift, and lists that execution teams don’t trust is paying for that continuously — in quarters, not dollars. Pricing the infrastructure against the cost of the problem is the whole conversation, and we’re glad to have it directly.