Treasury systems · Technology & AI
The impact of a senior hire. The flexibility of an adviser.
Experienced treasury systems, technology and AI specialists who work alongside your team, advise on decisions and help implement changes.
The difficult part isn't always knowing what to do. It's knowing what to look out for.
Between us we have sat on the vendor's side of a software sale, run the implementations that followed, built the products and then lived with the technical decisions for years afterwards.
That is what you are buying: which questions to ask before a project starts, which promises are worth checking, and which small decision turns expensive two years later.
Two practices. One specialist behind each.
You deal with the specialist, not a sales team and then a handover.
Knowing the software is one thing. Knowing how implementations really work is another.
Belinda has worked on treasury systems since 1997, twenty years of it inside the vendors — ION, FIS, Sungard and Integrity. She now runs selections and implementations from the buyer’s side of the table.
-
Requirements written from your processes and requirements, not a vendor’s feature list. Negotiation tips from working inside ION and FIS
-
New implementations and system migrations. We can recommend what works, and what risks you need to prepare for
-
An honest read on a programme in flight, and what can still be recovered when one has stalled
-
SWIFT, SEPA, XML, DTAZV, EBICS, host-to-host, whether through a bureau or direct. Treasury and commercial
-
IFRS and GAAP. Lead consultant at FIS, specialist at City Financials, chair of the hedge accounting taskforce group at ION
-
A system that went live and never delivered what was promised. Usually process and configuration rather than the system lacking capability. Get to best practice
A technical decision looks different once you have had to live with the consequences.
Simon has built and run software businesses since 2005 and been a fractional CTO for over a decade, across e-commerce, EdTech, SaaS and travel. He works on technology decisions, and on projects that have become expensive or hard to maintain.
Architecture and due diligence
Monolith or microservices, containers and deployment, and whether the codebase can carry what you want to do next. Written from building these systems, not reviewing them from outside
-
Which processes can be checked reliably enough to automate, and which cannot. Language models in production, with the evaluation and fallbacks that keep them usable
-
The comparison done properly, including what the build costs to maintain after year one and who is left supporting it
-
Architecture, infrastructure, security, hiring and delivery decisions, at the point where they are made. Carried rather than advised on, in companies he founded and companies he was brought into
-
Hybrid, fully remote, or half an office and half not. Twelve years running an engineering team across eight countries and five time zones
-
What breaks first as traffic grows, and what it costs to fix then rather than now. Run by small teams at a few hundred thousand users a month
Specialist partners come in where a job needs them — tax, legal, data migration, change management, security.
When clients bring us in
When nobody inside has done this before
Your treasury or technology function has decisions in front of it that nobody has made before, and not enough of that work to justify hiring someone who has. We work with clients over months or years instead, on time that is agreed rather than open-ended.
Before you commit
You are choosing a system, reviewing an architecture, weighing up AI, or about to sign an implementation contract. You want someone who has done it before to look at the options while changing your mind is still cheap.
When something isn’t working
The implementation is late, the software is not doing what you were told it would, or decisions taken two years ago are now costing you. You need someone to find out what is actually wrong and help fix it.
Tell us what you're working on
Planning something, trying to improve a system that is already in, or dealing with a project that has gone wrong — say which, and it reaches the right one of us.