Common Questions

RTP-X digitises the spreadsheet and document-driven work that sits outside your core systems. Account plans, call reports, pricing and portfolio information become a single controlled application with a live, shared, real-time view across the team rather than static files on a drive. It runs as SaaS on its own secure cloud data layer, so no core, CRM or general ledger integration is required.

Your teams work directly in the applications. Information entered once in one module is available to the others through the shared data layer, so there is no rekeying across the suite. What each person sees is governed by their role and your configuration, so aggregated team and portfolio views are available to those authorised to have them and restricted where they are not.

Your organisation owns its data. Each client is provisioned in a dedicated tenancy on AWS, isolated from every other client, in a selected region. Where a market imposes in-country data sovereignty requirements, data for that market can be held accordingly.

Access runs through Command, the central identity, permission and data control layer, with multi-factor authentication and role-based permissions managed centrally rather than module by module. The platform operates in dedicated client environments with encryption, independent security testing and continuous vulnerability scanning. Detailed security documentation is provided to client security teams on request, and a formal information security review is committed to under our agreements.

Authorised users can access and report on their data through the applications at any time, and a full extract of your data can be provided in an agreed format on request under the terms of our agreements. As a newer provider we expect the second half of that question, and we answer it contractually rather than with reassurance: our Master Services Agreement contains continuity provisions triggered if RTP-X becomes unable to continue operating the service.

Pricing has two components: a module licence fee and an implementation fee, each set for a defined number of users. Licence discounts increase with the number of modules licensed. Specialised client customisation is priced on a sliding scale according to the level required. Modules are contracted under a single master services agreement with a schedule for each module, so you can start with one and add others without running a new procurement.

Months, not years. The RTP-X 100 Goal is to have you live on a module for up to 100 users within 100 days. With no core system integration and no systems integrator programme, the timeline is driven by configuration and user readiness rather than technical build, at substantially lower cost and elapsed time than a typical enterprise banking software implementation. We need a nominated business owner, your requirements, and access to the people who will use it.

You get an ongoing SaaS solution, not a handover. That covers user support during Australian and Pacific business hours. Our commitments and processes for future upgrades, customisation delivery, incident response, downtime recovery and data accessibility are set out in more detail in our Master Services and module solution agreements.

The Command Suite is a comprehensive set of corporate banking modules drawn from more than 30 years of experience with the applications these teams actually use, so most requirements are met by the standard product. Our AI-supported development capability means configuration and client-specific customisation can be turned around rapidly, with the approach and pricing set out in our SaaS agreements, available on request.

Our roadmap through 2026 and 2027 focuses on delivering the modules currently in the Command Suite. Beyond that, we are interested in the operational processes, tools, documents and workflows in corporate banking that are still manual document, spreadsheet or email reliant. If you have a data management or analysis need we do not yet cover, let’s discuss a possible RTPX solution.