← Back to Product Work

Consumer Credit Platform

KIVRA

KIVRA is a consumer credit platform designed to give people access to flexible spending power based on their financial portfolio.

Project Overview

Product
KIVRA
My role
Product Manager
Product type
Consumer credit platform
Platform
Consumer app + back office
Key responsibilities
Discovery, product strategy, user journeys, requirements, prioritisation, delivery

The Problem

People often need access to money before their income arrives, but credit decisions rarely reflect the full picture of someone's finances. Applications are long, decisions feel opaque, and people are left unsure how much they can responsibly spend or how a decision was reached.

The Product

KIVRA connects a customer's financial account, assesses their financial profile and determines a spending power they can use and repay. Instead of a one-off application, spending power is continuously informed by income, affordability and financial behaviour, and the customer can always see what their limit is based on.

Core Journey

01

Connect financial account

02

Assess financial profile

03

Determine spending power

04

Spend

05

Repay

06

Build future spending power

Product Thinking

Income & affordability

Spending power is grounded in what a customer can realistically repay, not only in what they ask for.

Financial behaviour

Repayment and spending behaviour feed back into future access, so good behaviour is rewarded over time.

Credit access

Reduce the friction of getting a decision while keeping the decision explainable to the customer.

Customer experience

Show the limit, the reason and the repayment obligation in plain language at every step.

Responsible product design

Design defaults that discourage over-borrowing and make repayment the easiest path.

Data-driven decisioning

Connected financial data drives the assessment, with back-office controls for review and oversight.

Product Experience

Click any image to view it larger.

KIVRA — Consumer App
KIVRA — Back Office

My Product Work

Discovery & problem definition

Framed the customer problem around access and clarity rather than credit limits alone.

Product strategy

Positioned spending power as an evolving outcome of a customer's financial portfolio.

User journeys & UX decisions

Mapped onboarding, account connection, spend and repayment journeys and the states between them.

Requirements & prioritisation

Wrote requirements and user stories, and sequenced delivery around the core connect-assess-spend loop.

Stakeholder management & delivery

Worked across engineering, design and operations through agile delivery cycles.

Risk & compliance considerations

Built back-office review, controls and monitoring into the product rather than around it.

Key Product Decisions

Problem

Customers did not understand why they received a particular limit.

Decision

Show spending power alongside the financial factors that determine it.

Reasoning

Explainability builds trust in a credit product and reduces support contact.

Outcome

A clearer relationship between the customer's financial profile and their access to credit.

Problem

Operations needed to review and act on customer cases without engineering support.

Decision

Treat the back office as a first-class product surface with its own workflows.

Reasoning

Operational tooling is where risk controls actually get applied day to day.

Outcome

Operational and risk workflows handled directly in the back office.

Problem

Repayment behaviour had no visible effect on the customer experience.

Decision

Connect repayment behaviour to future spending power in the journey.

Reasoning

It aligns responsible behaviour with the customer's own incentive.

Outcome

Repayment became part of the product loop rather than an afterthought.

What I Learned

  • In credit products, clarity matters as much as approval — people need to understand a decision to trust it.
  • Operational tooling is part of the product; a consumer experience is only as good as the back office supporting it.
  • Responsible design decisions are product decisions, made in journeys and defaults rather than in policy documents.
  • Sequencing delivery around one core loop keeps a complex financial product shippable.

Let's Connect

I'm always interested in conversations about product, fintech, payments and building better financial experiences.

© Temi Abiodun · Product Portfolio