Fits the stack you have. Replaces none of it.
The platform reads the book from your core, helps you decide the initiative, and sends the work to the origination, relationship and pricing systems already doing that job. Then it measures what came back.
What it reads and what it writes
EquiTrak is not a system of record. The core stays the source of truth, and nothing is written back without an authorised, logged action.
- Core banking and the ledgerReads
- Account-level balances, rates, maturities, transactions and customer records. A data extract or a read-only feed is enough to start.
- Benchmark and market dataReads
- Competitor rate panels and elasticity reference data. We consume them. A benchmarking provider with pooled account data is a better source than anything we could build.
- Origination and onboardingWrites
- When an initiative reaches account opening, the target list and the reason go to the platform you already bought. The case is tracked through to funding.
- Relationship managementWrites
- Tasks, call lists and drafted outreach land where relationship managers already work.
- Pricing executionWrites
- An approved rate decision goes to your pricing engine, or leaves as a rate card for the core's product configuration.
- Channels and campaignsWrites
- Digital, email, call-centre lists and branch packs, all sequenced from one campaign definition, so contribution can be attributed by channel.
- Identity and risk toolingReads and writes
- Single sign-on in, audit evidence out, in the formats your risk function already uses.
Connectors are built with the first banks that need them, starting from flat-file and warehouse ingestion. Reference connectors for Finacle and Temenos are planned first. We will not show you a wall of logos for integrations that do not exist yet.
What decides the timeline
These four things decide whether integration takes six weeks or six months. It is better to talk about them before contracting.
Data you can retrieve
Account-level balance history is the one hard dependency. Twenty-four months at account level, with rate and maturity, makes a diagnosis possible. Aggregates do not.
Who is who
If the same corporate group appears under four customer numbers, wallet-gap analysis is wrong before it starts. Resolving that is usually the longest task in a deployment.
Approval to write
Reading is a data conversation. Writing a task into a relationship system or a rate into a product engine is a change-control conversation, and it moves at your bank's pace.
Where data and models may sit
In regulated markets this is settled first. Running the models inside your own tenancy is supported and is usually the shorter path to approval.
The lock-in question, answered
If you swap a vendor in eighteen months, what breaks and how much work is it?
- Your data
- It stays yours and can be exported in standard formats at any time, including the full history of cases, decisions and audit records.
- Your connectors
- They are configuration. Replacing an origination or benchmark provider means pointing at the new one.
- Your initiatives
- The library, the thresholds and the control mappings leave with you as structured definitions.
- Your models
- Version-pinned and swappable, including for models you license yourself. Nothing in the loop depends on one provider.
Talk through your stack.
Bring your architects. Forty-five minutes is enough to know whether a read-only proof of value is practical.