The trust industry needs to move from time spent to value created.

Time is easy to record and easy to bill.

But time is not always a good proxy for value.

A trustee may make an important judgement quickly because of years of experience.

A payment may consume significant administrative time but be seen by the client as a basic service expectation.

A compliance review may take longer than it should because the supporting data is incomplete.

A relationship manager may spend time chasing internally rather than advising the client.

All of that time is real.

But not all of it creates the same value.

That distinction matters because automation will increasingly expose the difference between high-value professional judgement and low-value administrative friction.

Clients will pay for expertise, responsibility and confidence.

They will be less willing to pay premium rates for avoidable administration.

If automation reduces effort by 20%, where does the value go?

This was one of the most important questions raised in the roundtable discussion.

In a time-spent model, efficiency can reduce billable hours unless pricing changes.

In a fixed-fee model, efficiency can improve margin if service quality is maintained.

In a capacity model, efficiency can help the business grow without adding headcount.

In an outcome-based model, efficiency can support shared value if outcomes are clearly measured.

So automation value cannot be assessed only as a cost-saving exercise.

It has to be connected to pricing, capacity, client experience, service levels and growth.

Without that connection, the value can be eaten up into the operating model.

Most technology in the roundtable poll was still priced mainly on a seat basis.

That is understandable.

Seat-based pricing is familiar, simple and easy to budget.

But it does not always align with automation value.

Automation value is often created through:

These are outcome measures, not seat measures.

If a firm is trying to grow without adding headcount, or process more volume without increasing operational cost, then pricing based only on the number of users may not reflect how value is actually created.

That does not mean every pricing model should become outcome-based overnight.

But it does suggest the future is likely to be more hybrid.

Outcome-based pricing sounds attractive.

But it requires confidence.

The client needs confidence that the outcome is real.

The firm needs confidence that the outcome can be delivered profitably.

The technology provider needs confidence that its contribution can be measured.

Everyone needs confidence in the baseline.

That baseline is often the missing piece.

• What does a payment currently cost?
• How long does onboarding currently take?
• What is the current exception rate?
• How many tasks are handled manually?
• How much relationship manager time is spent on administration?
• How much capacity would be released by automation?
• What service level is realistic?

Without this data, outcome-based pricing becomes difficult to govern.

Payments are a practical example of why commercial models need to evolve.

They are often operationally heavy, approval-led and sensitive from a control perspective. They may involve multiple people, systems and review steps. They may also be viewed by clients as an expected service rather than a high-value advisory activity.

This creates a commercial tension.

If processing a payment can consume hundreds of pounds of billable time, the firm needs to understand whether that effort is properly priced, whether it can be reduced, and whether the value of improvement should be captured through margin, service quality or capacity release.

There is also a cost to not deploying technology.

It shows up when:

This opportunity cost may not appear as a direct line item.

But it is real.

And over time, it becomes a competitive issue.