E2 pricing

Pricing is shaped by operational scope

E2 is subscribed to, not quoted from a tier sheet. The price follows the workflows, teams, products, integrations, governance and continuing support your operation actually needs.

The engagement scope changes. The maturity of the E2 products does not.

Scope a starting point Explore the E2 ecosystem

Three common starting shapes

Every engagement starts somewhere. These are the three shapes most operations recognise. All three run on the same nine mature, connected, subscription-ready products.

Pilot

Let us scope it

Begin with one workflow, team or project.

  • One workflow, team or project
  • Establish the operating record
  • Review & approval people will actually use
  • Prove the implementation fit
  • Close, hands-on onboarding
Scope a starting point
Most common

Operation

Let us scope it

Connect multiple workflows, roles and E2 products.

  • Everything in Pilot
  • Multiple workflows, roles and projects
  • Reporting and management visibility
  • Automate more of the recurring operation
  • Governed AI over your own operational record
Scope a starting point

Enterprise

Let us scope it

Cross-team operation with broader governance.

  • Everything in Operation
  • Broader governance and permission boundaries
  • Integrations with the systems you already run
  • Cross-team operation and advanced automation
  • Continuing support and optimisation
Scope a starting point

Pilot, Operation and Enterprise describe the size of the engagement, not the state of the software. Every shape runs on the same mature, subscription-ready E2 products.

What changes the scope

No guesswork. These are the practical factors that shape an E2 subscription.

Teams & projects

How many people capture, review and approve work, and how many projects run at once.

Workflows & handoffs

How complex the process is: the steps, the review points, and the handoffs that currently break.

Products adopted

Which of the nine connected E2 products the operation runs on today and next.

Integrations

Connections to the systems you already run, so records do not have to be carried by hand.

Governance & AI scope

Roles, permission boundaries and how much governed AI reads and explains the operational record.

Continuing support

How much ongoing implementation, monitoring and improvement the operation wants from us.

How expansion works

Start focused. Add scope when the operation is ready for it, on the same platform and the same operating record.

01

Start with one workflow

Solve one visible, economically meaningful problem and establish the operating record around it.

02

Build the system around it

Connect the records, roles, approvals, reporting and existing tools the workflow depends on.

03

Automate with control

Automate repeatable work while permissions, review points and accountability stay in place.

04

Keep improving the operation

Support, monitor and refine the system as real usage and business needs change.

Each step draws on the same ecosystem. Explore the E2 ecosystem to see which products handle which part of the journey, or see eflow2u in action for a concrete example.

Frequently asked questions

How is E2 priced?

E2 pricing is shaped by operational scope: the products you adopt, the workflows and teams involved, integrations, governance, and the level of continuing support. You get a clear, tailored proposal, never a forced tier.

No. Pilot describes the size of the first engagement, not the state of the software. The engagement scope changes. The maturity of the E2 products does not.

Yes. Most operations begin with a single workflow, team or project, prove the fit, and expand from there. No rip-and-replace.

The E2 products you adopt, the workflows configured around them, the operating record they produce, and the support that keeps them useful. Governed AI and additional products are added by scope.

Yes, on the Operation and Enterprise engagements, connected to the systems you already run.

As more of the operation moves onto E2: more workflows, more roles and reports, more automation, and more of the nine connected products. The subscription grows with the scope, not with a forced upgrade.

Tell us how work moves through your team today. A short conversation gives us enough to scope a starting point and prepare a tailored proposal.

Show us the workflow that should run better.

Start with one recurring process, handoff or reporting problem. We will map where it breaks, which E2 products fit, and what the first engagement should cover.

Scope a starting point Explore the E2 ecosystem