Pricing
Priced around the problem, not the seat count.
PACX is quoted per business. It starts with a 45-minute demo where we scope your inventory problem — what you sell, where it sits, and which decisions keep going wrong. The resulting scope records the work, dependencies and commercial assumptions used to prepare a quote.
What PACX does
Planning software organised around the decision and the action that follows.
PACX connects forecasting and retail planning workflows so a team can inspect the assumptions, recommendation and approval path together. The starting point is a defined business decision, not an open-ended technology deployment.
Define the decision
Name the planning question, its product-location grain, owner, review cadence and the action that follows.
Validate the workflow
Review historical performance, assumptions, exceptions and whether the proposed output is usable by the planning team.
Set decision rights
Agree which recommendations remain advisory, which require approval and which may advance inside explicit limits.
How we price
Four things decide your quote.
These are the main scoping variables. Discovery records any additional dependency before a proposal is prepared.
Decision scope
A focused forecast review and a connected forecast-to-allocation workflow carry different implementation and operating scope.
Data exchange
Source systems, required fields, history, refresh frequency and the destination for approved outputs are confirmed during discovery.
Your scale
SKU-store combinations, channels, locations and planning frequency determine the volume and granularity the workflow must support.
Governance and support
Approval roles, operating controls, onboarding needs and the support model are scoped with the technical work.
Illustrative scopes
Three ways to frame the work.
These are discussion patterns, not packages, prices or promised outcomes. The applicable scope is documented from your own operating context.
Focused decision
One planning question with a defined owner and review cadence
- Define the decision grain and horizon
- Agree the minimum data contract
- Review recommendations before operational use
Discussion focus: establish whether one bounded workflow is ready for validation.
Connected chain
Two or more planning decisions that need shared assumptions and hand-offs
- Map inputs and outputs between decisions
- Reconcile shared measures and calendars
- Define exception ownership and review points
Discussion focus: prevent context from being re-keyed or lost between planning steps.
Governed automation
A validated workflow being considered for broader permissions
- Document merchant-set limits and approvals
- Define pause, override and escalation paths
- Agree monitoring and audit responsibilities
Discussion focus: widen decision rights only after the workflow and controls are reviewed.
Proposal detail
Know what is being scoped.
- The decision, scope and planning grain
- Required data fields and exchange method
- Validation and acceptance criteria
- Approval roles and operating limits
- Implementation milestones and dependencies
- Support responsibilities and commercial assumptions
Prepare for discovery
Bring the operating context.
Bring the planning question, the teams who own it, the product and location grain, the calendar used to review it and the systems that currently supply or receive the relevant information.
PACX will map the minimum fields, historical coverage, refresh cadence and output destination required for that workflow. Named connector availability is confirmed against the current engineering record during technical discovery.
Security controls, access mode, retention and deletion requirements are treated as review items and recorded in the applicable technical and contractual documents rather than assumed on this pricing page.
How to get your price
Bring one business question. Leave with a plan and a price.
Forty-five minutes. We map the question, the decision grain, the data it needs and the review path. A quote can then be prepared from the documented scope and dependencies rather than a generic tier.
If you prefer an asynchronous first step, write to us and request the scoping questions by email.