ROI & cost

Cost splits three ways: the build, the running cost, and the internal time to support it. A single well-scoped role is a project-sized investment rather than an enterprise software contract, and running costs are usually small against the staff hours displaced. The number that matters is payback period — most single-role installations should return their build cost inside a year.

We quote against a defined role and a measurable outcome, not a seat count, so the comparison is against the hours it replaces rather than against another licence.

Beware quotes that ignore the third cost. A system nobody inside the business owns will drift, and the cost of that is real.

• Model your own numbers →
• How enterprise ROI is structured →

Take two figures. First, hours displaced multiplied by fully-loaded hourly cost. Second, additional revenue from faster response: extra enquiries converted multiplied by average deal value multiplied by margin. Subtract build and running cost from the sum. Measure both inputs before you start, from your own records, so the after figure has something honest to sit against.

Two disciplines keep the number credible: use fully-loaded cost rather than salary, and attribute revenue conservatively — claim only the lift you can trace to a changed response time.

• The calculator that does this →
• A board-ready return model →

It depends entirely on volume and deal size, which is why any headline percentage should be treated sceptically. In our own installations the recovered figures have ranged from roughly fifteen hours a week in a wellness practice to forty hours a week in a financial services compliance team, alongside faster response and higher intake completion.

Those are our measured client outcomes, not an industry average. The honest way to size your own is to count the hours and the enquiries before anything is built.

• The 2026 benchmark and method →

Mostly by avoiding the next hire rather than removing the current one. When repetitive hours move to a system, existing capacity absorbs growth that would otherwise have required another salary. The saving is the cost of the role you did not need to advertise, plus the recruitment, onboarding and management time attached to it.

This framing also survives scrutiny better internally, because it does not ask anyone to argue for their colleague's redundancy in order to approve a project.

• Staff cost reduction, in detail →
• The Australian picture →

Most pilots fail for the same two reasons: no baseline was measured, so nobody could prove it worked, and no one inside the business owned it after launch. We fix both by construction — the numbers are captured before the build, and the system is handed over with the reporting, the documentation and the accounts in your name.

The third common failure is scope. A pilot spread across five processes proves nothing about any of them. One role, measured properly, is what earns the second.

• Start with the audit, not the build →