How we begin

A first process.
A clear scope.

Together, we define what to address, the information it needs and how it connects with your institution’s operations. Deliverables and validation criteria form part of the agreed scope.

Explore the shared platform

A shared process

Each stage produces
something to review.

This process guides project definition. Final deliverables, responsibilities and conditions are recorded in the scope of your implementation.

01

Prioritize the process.

Choose where to begin: onboarding, connected information or a process for the agents.

What is agreed
The objective, initial journey, responsible teams and project boundaries.
What your institution contributes
The current process, team needs and policies that must be followed.
How it is validated
Both teams review the problem, dependencies and initial scope.
02

Define the connections.

Agree which sources, systems and channels the process needs.

What is agreed
A map of sources and integrations, required data and technical responsibilities.
What your institution contributes
System contacts, available documentation and criteria for authorizing data access.
How it is validated
Connection availability, permissions and dependencies with the providers involved.
03

Configure and validate.

Prepare the OneID, OneGraph or OneTeam journey included in the scope.

What is agreed
Branding, workflows, roles, limits and review points, together with validation cases and expected evidence.
What your institution contributes
Its catalog, policies, evaluation owners and authorized test data.
How it is validated
The team reviews cases, permissions, exceptions and agreed acceptance criteria.
04

Enable and support.

Turn the validated scope into an operational process with defined responsibilities.

What is agreed
A launch plan, responsibilities, follow-up and support conditions.
What your institution contributes
Approvals, operational owners and team availability for the agreed support activities.
How it is validated
Process evidence is reviewed to decide which capabilities to expand next.

For the first conversation

Bring your institution’s
context.

We can start with a general description of the process and systems involved. Personal information and technical access are coordinated later through agreed channels and permissions.

The process and its rules.

  • What your institution needs to improve and which team is involved.
  • Which products, policies and approvals shape the journey.
  • Which sources, providers and channels are involved today.

Conditions for operation.

  • Access, data handling and hosting requirements.
  • Integration, evaluation and operational owners.
  • The evidence needed to accept the first scope.

Metrics to agree

Measure the process.
Learn from its use.

Before evaluating an improvement, we agree a baseline, calculation method and data source. These are examples of measures that can form part of a project.

OneID
Journey progress and completion, outstanding items by stage and onboarding time for the defined process.
OneGraph
Coverage of authorized sources, available information and traceability of signal origins.
OneTeam
Completed tasks, escalated exceptions, human reviews and case continuity.

These are proposed measures for evaluating an implementation. Targets and results are documented using each project’s data.

Agreed support

Support is also
part of the scope.

The proposal defines support channels, responsible teams, assistance and support conditions. Response times, availability and responsibilities across providers are agreed for each implementation.

banku’s core connects the platform layers and integrates with your institution’s banking core and systems according to the agreed scope.

Review controls and responsibilities

Define your
starting point.

Tell us about the process, the systems involved and your institution’s objective.

OneTeam / Leo

Let’s talk about your institution.

Shape the scope. Review it. Take the next step.

Preparing the conversation