Personal
One personal subscription for one user
$4.99 / month
PersonalFull app access for the subscriber
Pricing
Choose the package that fits your rollout.
Simple tiers for teams getting started, growing, or planning larger deployments.
Packages
What’s included
Each tier includes the same security model; seat counts and rollout support vary.
Growth
Business-wide access for every active organization member
$19.99 / month
BusinessCovers everyone in the business, even without their own subscription
Lifetime
Lifetime organization access
$299.99 / month
LifetimeOne-time lifetime option replacing All Access
How billing works
Monthly billing
Plans bill monthly; annual terms available on request.
Seat-based
Seats are tied to active users inside your workspace.
Transparent status
Plan changes reflected immediately in the dashboard.
Need help choosing?
Contact us to match a tier to your rollout plan or to discuss enterprise needs.
Pricing questions we hear most
Question
Answer
Can I change plans mid-cycle?
Yes. Upgrades take effect immediately; downgrades at the next billing period.
Do you offer annual terms?
Available on request with consolidated invoicing.
Is support included?
Structured support is included; premium response options are available.
Are integrations extra?
Current connectors are included; custom work is scoped separately.
Operational depth
Interpret pricing as an operating model commitment, not only a monthly cost
Pricing should clarify package boundaries, support implications, and growth constraints so finance and operations can align on sustainable rollout plans.
Primary audience
Finance partners, procurement, and workspace owners
Decision focus
Select a package that matches seat growth, governance needs, and support expectations
Operational risk
Choosing by headline cost alone can force mid-cycle reconfiguration and user disruption
Field scenario
A finance lead models expansion from pilot seats to multi-team deployment while preserving support coverage.
Execution walkthrough
1. Frame the objective
Pricing should clarify package boundaries, support implications, and growth constraints so finance and operations can align on sustainable rollout plans.
2. Align participants
Finance partners, procurement, and workspace owners
3. Validate the decision
Select a package that matches seat growth, governance needs, and support expectations
4. Mitigate known risk
Choosing by headline cost alone can force mid-cycle reconfiguration and user disruption
Interpretation matrix
Signal
Interpretation
Operational scenario
A finance lead models expansion from pilot seats to multi-team deployment while preserving support coverage.
Successful outcome
Successful use of this page leaves teams with clear direction on Select a package that matches seat growth, governance needs, and support expectations.
If skipped
Skipping this step often introduces Choosing by headline cost alone can force mid-cycle reconfiguration and user disruption.
Recommended next step
Coordinate pricing decisions with registration and onboarding paths before activation.