Team
The functions behind the platform
What matters when you are choosing a vendor is less who appears on a leadership page and more who picks up when a deployment stalls. These are the functions, and where each one meets you.
Individual profiles are not published yet. They will be added here once the company has confirmed who appears and in what form, rather than filled in with placeholder names.
Six functions
Who you actually deal with, by function
Engineering, liquidity, deployment, compliance, support and commercial — each with a distinct role in a deployment, not a flat list of names.
How the company is organised
Six functions, and one of them is yours to know well
Engineering
Builds and maintains the products. Structured around the account model rather than around individual products, which is why a change in one rarely breaks another.
Liquidity and connectivity
Runs the pricing relationships and the aggregation layer, and handles certification when a broker connects their own provider.
Deployment and client operations
The people who configure your stack and stay with it afterwards. This is the function you will deal with most, before and after go-live.
Compliance and risk
Keeps jurisdiction rules, screening integrations and reporting current, and reviews what we can honestly claim on a page like this one.
Support
Incident response and day-to-day questions, working from the same records your desk sees rather than from a separate ticket system.
Commercial
Scoping, quoting and the ongoing relationship. Not incentivised to sell you products you do not need, because a stalled deployment costs more than it earns.
Who you actually deal with
Named people, at every stage
A shared inbox is where deployments go quiet. Each stage has a person attached to it, and the handover between stages is a conversation rather than a ticket transfer.
During scoping
A commercial lead and a deployment engineer, both named, from the first call.
During build
The same deployment engineer, plus whoever owns the integration you are connecting.
After go-live
A named support contact, with escalation to the engineer who built your configuration.
Ask to speak to the engineer, not just the salesperson
It is a reasonable request and we would rather you made it early. Scoping calls include a deployment engineer by default.