Engagement and pricing

Start with one workflow. Expand from evidence.

PaxRelay engagements move from a bounded workflow review to a measurable pilot and then a production scope shaped by integrations, volume and support needs.

Estimate a pilot

Engagement path

01 · Workflow review
02 · Bounded pilot
03 · Production scope

A useful estimate starts with scope.

An initial conversation establishes the operation, one or two priority workflows and the integration path. That is enough to frame a responsible implementation without turning the first call into a procurement exercise.

No requirement to replace a core system.

Commercial scope is based on the orchestration work being added, not on forcing a reservation, scheduling or operational platform migration.

Operation size: Services, departures, passengers and operating locations in scope.
Integrations: Number, type and complexity of source and destination systems.
Workflow scope: Events, conditions, approvals, exceptions and escalation paths.
Communication volume: Expected passenger messages and operational notifications.
Channels: Email, SMS and other configured delivery paths.
Support requirements: Implementation, monitoring, operating hours and response expectations.

Final commercial terms are documented in a proposal and agreement specific to the customer scope.

Define the first operational scope.

Bring one workflow and its surrounding systems. We will identify the factors that shape a pilot and its commercial scope.

Estimate a pilot Contact us