Financial Visibility Platform
MONTRA
MONTRA brings a user's financial accounts together to provide a clearer view of spending, credit, savings, investments and financial goals.
Project Overview
- Product
- MONTRA
- My role
- Product Manager
- Product type
- Financial visibility platform
- Platform
- Consumer app + back office
- Key responsibilities
- Discovery, information architecture, user journeys, requirements, prioritisation, delivery
The Problem
People hold money across several accounts, cards and products, so no single place shows where they actually stand. Understanding spending, credit, savings, investments and progress towards goals means checking multiple apps and doing the joining up manually.
The Product
MONTRA connects a user's accounts, brings the financial data together and presents one financial position — spending, credit, savings, investments and goals — so the user can understand it at a glance and act on it.
Core Journey
Connect accounts
Bring financial data together
Understand financial position
Take action
Product Thinking
Financial data
Data from several sources has to be reconciled into categories a person recognises.
Information architecture
Structure the product around the questions users ask, not the accounts they hold.
User experience
Prioritise the few numbers that matter and keep detail one level away.
Simplifying complex information
Reduce dense financial data to a readable position without hiding the underlying detail.
Financial visibility
A single view across spending, credit, savings, investments and goals.
Actionable insights
Insight is only useful when it leads to a next step the user can take.
Product Experience
Click any image to view it larger.
My Product Work
Discovery & problem definition
Defined the problem as fragmented visibility rather than missing features.
Product strategy
Made the aggregated financial position the core of the product.
User journeys & UX decisions
Designed account connection and the path from overview to detail to action.
Requirements & prioritisation
Specified data categories, states and edge cases, and sequenced them for delivery.
Stakeholder management & delivery
Collaborated with engineering and design through iterative delivery.
Risk & compliance considerations
Treated financial-data access and permissions as part of the experience.
Key Product Decisions
Problem
Aggregated data risked producing a dashboard nobody could read.
Decision
Lead with a single financial position and move account detail one level down.
Reasoning
Users want to know where they stand before they want to know why.
Outcome
A simpler entry point into a data-heavy product.
Problem
Insights were interesting but not actionable.
Decision
Pair each insight with a clear next action.
Reasoning
Visibility only changes behaviour when the next step is obvious.
Outcome
Insights became part of the journey rather than a static view.
Problem
Account connection was the biggest drop-off risk.
Decision
Explain the value and the data being accessed before asking for a connection.
Reasoning
Trust is the deciding factor when asking for financial data access.
Outcome
A connection flow framed around user benefit and consent.
What I Learned
- Aggregating data is the easy part; deciding what to show first is the product work.
- Information architecture is the main UX lever in a data-heavy financial product.
- Insights need an action attached, or they are just numbers.
- Explaining data access clearly is a conversion decision as much as a compliance one.
Let's Connect
I'm always interested in conversations about product, fintech, payments and building better financial experiences.
© Temi Abiodun · Product Portfolio