Treasury Has Been Waiting Long Enough

For more than a decade in treasury, one theme followed me everywhere:

Waiting.

Waiting for integrations.
Waiting for updates.
Waiting for customizations.
Waiting for IT.
Waiting for budget.
Waiting for “phase 2.”
Waiting for alignment, approval, permission.

Somewhere along the way, waiting quietly became normal.

Treasury teams learned to live with delays.
To adapt processes around systems that couldn’t adapt fast enough.
To build workarounds in Excel while waiting for features that should’ve taken days, not months.
To slow down, even when the business around them was accelerating.

And yet treasury is the function that cannot afford slow.

Treasury needs clarity.
Treasury needs adaptability.
Treasury needs to move at the speed of the company, not at the speed of vendor roadmaps.

Then something happened that forced a question I couldn’t ignore.

AI arrived.

And in the middle of all the waiting, one thought hit me harder than anything else:  “What if treasury teams never had to wait for anyone to get what they need?”

What if the tools could be created instantly?
What if customizations didn’t take six months and a budget cycle?
What if treasurers could build and adapt processes as easily as describing them?
What if the bottleneck disappeared?

That question became the start.

The start became an idea.
The idea became a prototype.
The prototype became a one-year intense build, focused entirely on solving real, everyday treasury problems, not reinventing anything for the sake of buzzwords.

Quiet.
Deliberate.
Obsessively tested.

And now it’s almost time.

No, it’s not another TMS.
And it’s not another tool added on top of a growing stack.
And it’s not a rigid system with a familiar set of limitations.

It’s something else.

A new way of working.
One that lets treasury teams finally move at the speed they always needed.

The beta goes live on 1 December 2025.

More details soon.