Automate Axis

Engagements / Commercial clarity

Clear scope before you commit to automation

Automation pricing depends on the workflow, connected systems, data quality, transaction volume, required controls and support responsibilities. We make those factors visible so you can decide whether the investment makes sense.

Colleagues discussing a whiteboard with planning notes

Representative photography · agreeing priorities and scope before investment.

01

Engagement options

01

Workflow diagnostic from USD 2,000

For organisations that need to understand the process and investment before commissioning a build. The agreed assessment covers a defined workflow, stakeholder input, the current baseline, implementation options, risks and a prioritised recommendation.

The output is useful whether you proceed with us, configure existing software or decide the opportunity is not yet strong enough.

02

Bounded pilot from USD 5,000

For a defined uncertainty that needs evidence, such as extraction quality, routing performance, integration feasibility or review burden. A pilot has an agreed sample, access boundary, acceptance criteria and decision point. Production deployment is separately scoped unless explicitly included.

03

Production implementation by proposal

Your implementation proposal identifies the workflow, systems, deliverables, exclusions, acceptance tests, dependencies and release approach. It includes engineering, the agreed controls, operating documentation and training within the signed scope.

04

Managed automation by support scope

Ongoing fees reflect the workflows, event volume, platforms, monitoring requirements, response coverage and improvement allowance. Your support schedule explains what is included, what requires a change request and how incidents are handled.

Displayed starting fees are in USD and exclude applicable taxes and third-party software or usage charges unless expressly included. Your written proposal confirms the currency and total agreed charges. Availability and suitability are assessed before an engagement is accepted.

02

What changes the price?

  • The number of workflows, applications and supported process variants.

  • The condition, format and permitted use of the data.

  • API availability, authentication requirements and legacy-system constraints.

  • The consequences of errors and the validation or approval required.

  • Expected volume, processing time and recovery requirements.

  • Migration, staff training, documentation and ongoing service coverage.

The cost of AI calls is only one part of the operating cost. Review time, software subscriptions, workflow operations, exception handling and maintenance can materially affect the business case.

03

How the commercial process works

The initial conversation is free. We discuss the workflow, the outcome and the information needed to establish fit. Any diagnostic, pilot or implementation is a paid engagement only after its scope and fee have been agreed.

We confirm payment milestones, client responsibilities, software costs and support arrangements in writing. A diagnostic or pilot does not automatically include an implementation credit; any credit must appear in the proposal.

04

Questions about investment

Can you give a fixed project price?

Yes, where the scope and dependencies can be defined adequately. A diagnostic may be needed first. The proposal sets the fee and the process for handling changes.

Do we have to buy every stage?

No. The stages resolve different buying decisions. A pilot may be unnecessary where sufficient validation already exists, and a diagnostic may recommend a simpler approach.

Are software subscriptions included?

Only where the proposal explicitly includes them. Client-owned subscriptions and usage charges are otherwise separate, and their expected effect should be considered before approval.

Will automation guarantee a return?

Business results depend on volume, process design, adoption and how recovered capacity is used. We agree the assumptions and measurement method, including review and operating cost, before treating a benefit as established.

The next step

Get an estimate built around your process

Tell us what you need completed, which systems are involved and the approximate volume. We will explain the appropriate next step.

Request a scoped estimate