Product Design
Financial Calendar
The Financial Calendar is a cashflow management tool designed for TBC Business clients to visualize and predict their financial future. Born from the failure of an existing analytics feature, this project transformed user frustration into a forward-looking planning tool that helps business owners make smarter financial decisions. The calendar consolidates future financial activities-utilities, loans, transfers, guarantees, deposits, standing orders, and invoice flows - into a single, clear interface.
Year :
2025
Industry :
Banking
Client :
TBC Bank
Project Duration :
6 monthes
The Problem & Discovery :
TBC's analytics tool wasn't working. User feedback was consistent: business owners couldn't see what was coming, couldn't predict cashflow gaps, and had no way to plan ahead. The tool showed historical data but offered nothing forward-looking. Clients were managing their cashflow in spreadsheets outside the platform, defeating the purpose of having a business banking tool in the first place.
The real issue wasn't the data - it was the structure. Business owners don't think in retrospective charts. They think in upcoming obligations, expected income, and whether they'll have enough money next month to make payroll. The old tool didn't speak their language.
Understanding Our Users
We started by talking to the people who actually use the platform. Through interviews with business clients and workshops with financial consultants who work with them daily, patterns emerged quickly. Business owners live in the future. They need to know what's coming so they can make decisions today. Cashflow prediction isn't a nice-to-have - it's critical for everything from hiring decisions to purchasing inventory. But they don't have time to dig through complex interfaces. If it takes more than a few seconds to understand their financial position, they won't use it.
Our primary users are business owners and financial managers running small to large companies. They're responsible for day-to-day operations and strategic planning. They need to predict cashflow to avoid shortfalls, plan for expenses, track expected income, and make informed decisions fast. Their constraints are real: limited time, variable financial expertise, high stakes. A mistake here isn't just frustrating - it has consequences.
We also learned that visual calendars work. People already use them to plan their schedules, so applying the same logic to finances felt natural. The challenge was translating that familiarity into something that handled the complexity of business banking without becoming overwhelming.
The Solution :
We ran weekly workshops with financial consultants and stakeholders, exploring everything from timelines to tables to hybrid views. The calendar concept kept winning because it matched how people already think about planning. We committed to an agile approach: ship something functional that solves the core problem, then evolve it. Our design principles became clear early: clarity over complexity, actionable information over passive display, and visual hierarchy to guide attention without explanation.
The Financial Calendar is built around three interconnected parts that work together to give users complete visibility and control:
Financial Overview
At the top, three cards answer the question users ask first: "Am I in good shape?" Total balance shows where they stand today. Estimated three-month income and expenses show what's coming. It's quick reassurance or early warning before they dig into the details.
Calendar View
The calendar sits at the center - the primary way users navigate their financial future. Each day shows color-coded dots representing different activity categories: utilities, loans, transfers, guarantees, deposits, standing orders, invoice expenses, and receivables. Multiple activities on one day show as multiple dots. It's simple, scannable, and familiar.
We chose the calendar format because users already understand it. They don't need to learn a new mental model. The color coding adds pattern recognition - users can spot recurring expenses or income clusters at a glance without reading every line.
Transaction Details
Clicking any date populates the right panel with everything scheduled for that day. Transactions are organized by category with amounts clearly displayed. Users can filter by category, see daily totals, and drill into specifics. The panel bridges overview and action - users can quickly understand what's happening and decide what to do about it.
Taking Action
At the top of the transaction panel, an "Add transaction" button opens a modal where users can initiate new activities: request payment, add a bill, request a loan, create a future transfer, or apply for a tender guarantee. These aren't scattered across the interface - they're accessible from the same context where users are viewing their cashflow. This matters because viewing information is only half the job. Users need to respond to what they see.
Design Process & Key Decisions :
We started with wireframes exploring different structural approaches. The calendar emerged as the winner in early user testing - familiar, intuitive, and scalable. The visual design followed TBC's existing system while optimizing for hierarchy and legibility. Color coding needed to be distinct but accessible. Information density needed to feel manageable, not overwhelming. Every design decision was validated through iteration and feedback.
Critical Design Decisions
The three-part layout separates information into digestible zones - overview, calendar, details - so users can navigate at different levels without cognitive overload. Making the date the primary selector aligns with how people naturally plan. Color-coded categories enable instant pattern recognition. Embedded actions eliminate context switching. The entire structure was designed to scale. More activity types, advanced filtering, custom views - the foundation supports future growth without requiring redesign.
During development, I stayed involved to review builds, answer questions, and adjust designs when technical constraints surfaced. The goal was smooth delivery and a product that shipped as designed.
Impact & Reflections :
The Financial Calendar shifted TBC Business from reactive reporting to proactive planning. Clients now have the visibility and control they need to manage finances confidently.
What Worked
Simplicity resonated with users. Collaborative workshops grounded decisions in real needs. Agile methodology let us ship quickly and iterate based on actual usage.
What I'd Improve
More edge case testing with multi-account businesses, earlier mobile optimization, stronger post-launch feedback loops for continuous improvement.
Key Takeaway
This project reinforced something fundamental: great enterprise design isn't about visual complexity. It's about making complexity manageable, empowering users to act, and building systems that serve both the people using them and the teams maintaining them.
More Projects
Product Design
Financial Calendar
The Financial Calendar is a cashflow management tool designed for TBC Business clients to visualize and predict their financial future. Born from the failure of an existing analytics feature, this project transformed user frustration into a forward-looking planning tool that helps business owners make smarter financial decisions. The calendar consolidates future financial activities-utilities, loans, transfers, guarantees, deposits, standing orders, and invoice flows - into a single, clear interface.
Year :
2025
Industry :
Banking
Client :
TBC Bank
Project Duration :
6 monthes
The Problem & Discovery :
TBC's analytics tool wasn't working. User feedback was consistent: business owners couldn't see what was coming, couldn't predict cashflow gaps, and had no way to plan ahead. The tool showed historical data but offered nothing forward-looking. Clients were managing their cashflow in spreadsheets outside the platform, defeating the purpose of having a business banking tool in the first place.
The real issue wasn't the data - it was the structure. Business owners don't think in retrospective charts. They think in upcoming obligations, expected income, and whether they'll have enough money next month to make payroll. The old tool didn't speak their language.
Understanding Our Users
We started by talking to the people who actually use the platform. Through interviews with business clients and workshops with financial consultants who work with them daily, patterns emerged quickly. Business owners live in the future. They need to know what's coming so they can make decisions today. Cashflow prediction isn't a nice-to-have - it's critical for everything from hiring decisions to purchasing inventory. But they don't have time to dig through complex interfaces. If it takes more than a few seconds to understand their financial position, they won't use it.
Our primary users are business owners and financial managers running small to large companies. They're responsible for day-to-day operations and strategic planning. They need to predict cashflow to avoid shortfalls, plan for expenses, track expected income, and make informed decisions fast. Their constraints are real: limited time, variable financial expertise, high stakes. A mistake here isn't just frustrating - it has consequences.
We also learned that visual calendars work. People already use them to plan their schedules, so applying the same logic to finances felt natural. The challenge was translating that familiarity into something that handled the complexity of business banking without becoming overwhelming.
The Solution :
We ran weekly workshops with financial consultants and stakeholders, exploring everything from timelines to tables to hybrid views. The calendar concept kept winning because it matched how people already think about planning. We committed to an agile approach: ship something functional that solves the core problem, then evolve it. Our design principles became clear early: clarity over complexity, actionable information over passive display, and visual hierarchy to guide attention without explanation.
The Financial Calendar is built around three interconnected parts that work together to give users complete visibility and control:
Financial Overview
At the top, three cards answer the question users ask first: "Am I in good shape?" Total balance shows where they stand today. Estimated three-month income and expenses show what's coming. It's quick reassurance or early warning before they dig into the details.
Calendar View
The calendar sits at the center - the primary way users navigate their financial future. Each day shows color-coded dots representing different activity categories: utilities, loans, transfers, guarantees, deposits, standing orders, invoice expenses, and receivables. Multiple activities on one day show as multiple dots. It's simple, scannable, and familiar.
We chose the calendar format because users already understand it. They don't need to learn a new mental model. The color coding adds pattern recognition - users can spot recurring expenses or income clusters at a glance without reading every line.
Transaction Details
Clicking any date populates the right panel with everything scheduled for that day. Transactions are organized by category with amounts clearly displayed. Users can filter by category, see daily totals, and drill into specifics. The panel bridges overview and action - users can quickly understand what's happening and decide what to do about it.
Taking Action
At the top of the transaction panel, an "Add transaction" button opens a modal where users can initiate new activities: request payment, add a bill, request a loan, create a future transfer, or apply for a tender guarantee. These aren't scattered across the interface - they're accessible from the same context where users are viewing their cashflow. This matters because viewing information is only half the job. Users need to respond to what they see.
Design Process & Key Decisions :
We started with wireframes exploring different structural approaches. The calendar emerged as the winner in early user testing - familiar, intuitive, and scalable. The visual design followed TBC's existing system while optimizing for hierarchy and legibility. Color coding needed to be distinct but accessible. Information density needed to feel manageable, not overwhelming. Every design decision was validated through iteration and feedback.
Critical Design Decisions
The three-part layout separates information into digestible zones - overview, calendar, details - so users can navigate at different levels without cognitive overload. Making the date the primary selector aligns with how people naturally plan. Color-coded categories enable instant pattern recognition. Embedded actions eliminate context switching. The entire structure was designed to scale. More activity types, advanced filtering, custom views - the foundation supports future growth without requiring redesign.
During development, I stayed involved to review builds, answer questions, and adjust designs when technical constraints surfaced. The goal was smooth delivery and a product that shipped as designed.
Impact & Reflections :
The Financial Calendar shifted TBC Business from reactive reporting to proactive planning. Clients now have the visibility and control they need to manage finances confidently.
What Worked
Simplicity resonated with users. Collaborative workshops grounded decisions in real needs. Agile methodology let us ship quickly and iterate based on actual usage.
What I'd Improve
More edge case testing with multi-account businesses, earlier mobile optimization, stronger post-launch feedback loops for continuous improvement.
Key Takeaway
This project reinforced something fundamental: great enterprise design isn't about visual complexity. It's about making complexity manageable, empowering users to act, and building systems that serve both the people using them and the teams maintaining them.
More Projects
Product Design
Financial Calendar
The Financial Calendar is a cashflow management tool designed for TBC Business clients to visualize and predict their financial future. Born from the failure of an existing analytics feature, this project transformed user frustration into a forward-looking planning tool that helps business owners make smarter financial decisions. The calendar consolidates future financial activities-utilities, loans, transfers, guarantees, deposits, standing orders, and invoice flows - into a single, clear interface.
Year :
2025
Industry :
Banking
Client :
TBC Bank
Project Duration :
6 monthes
The Problem & Discovery :
TBC's analytics tool wasn't working. User feedback was consistent: business owners couldn't see what was coming, couldn't predict cashflow gaps, and had no way to plan ahead. The tool showed historical data but offered nothing forward-looking. Clients were managing their cashflow in spreadsheets outside the platform, defeating the purpose of having a business banking tool in the first place.
The real issue wasn't the data - it was the structure. Business owners don't think in retrospective charts. They think in upcoming obligations, expected income, and whether they'll have enough money next month to make payroll. The old tool didn't speak their language.
Understanding Our Users
We started by talking to the people who actually use the platform. Through interviews with business clients and workshops with financial consultants who work with them daily, patterns emerged quickly. Business owners live in the future. They need to know what's coming so they can make decisions today. Cashflow prediction isn't a nice-to-have - it's critical for everything from hiring decisions to purchasing inventory. But they don't have time to dig through complex interfaces. If it takes more than a few seconds to understand their financial position, they won't use it.
Our primary users are business owners and financial managers running small to large companies. They're responsible for day-to-day operations and strategic planning. They need to predict cashflow to avoid shortfalls, plan for expenses, track expected income, and make informed decisions fast. Their constraints are real: limited time, variable financial expertise, high stakes. A mistake here isn't just frustrating - it has consequences.
We also learned that visual calendars work. People already use them to plan their schedules, so applying the same logic to finances felt natural. The challenge was translating that familiarity into something that handled the complexity of business banking without becoming overwhelming.
The Solution :
We ran weekly workshops with financial consultants and stakeholders, exploring everything from timelines to tables to hybrid views. The calendar concept kept winning because it matched how people already think about planning. We committed to an agile approach: ship something functional that solves the core problem, then evolve it. Our design principles became clear early: clarity over complexity, actionable information over passive display, and visual hierarchy to guide attention without explanation.
The Financial Calendar is built around three interconnected parts that work together to give users complete visibility and control:
Financial Overview
At the top, three cards answer the question users ask first: "Am I in good shape?" Total balance shows where they stand today. Estimated three-month income and expenses show what's coming. It's quick reassurance or early warning before they dig into the details.
Calendar View
The calendar sits at the center - the primary way users navigate their financial future. Each day shows color-coded dots representing different activity categories: utilities, loans, transfers, guarantees, deposits, standing orders, invoice expenses, and receivables. Multiple activities on one day show as multiple dots. It's simple, scannable, and familiar.
We chose the calendar format because users already understand it. They don't need to learn a new mental model. The color coding adds pattern recognition - users can spot recurring expenses or income clusters at a glance without reading every line.
Transaction Details
Clicking any date populates the right panel with everything scheduled for that day. Transactions are organized by category with amounts clearly displayed. Users can filter by category, see daily totals, and drill into specifics. The panel bridges overview and action - users can quickly understand what's happening and decide what to do about it.
Taking Action
At the top of the transaction panel, an "Add transaction" button opens a modal where users can initiate new activities: request payment, add a bill, request a loan, create a future transfer, or apply for a tender guarantee. These aren't scattered across the interface - they're accessible from the same context where users are viewing their cashflow. This matters because viewing information is only half the job. Users need to respond to what they see.
Design Process & Key Decisions :
We started with wireframes exploring different structural approaches. The calendar emerged as the winner in early user testing - familiar, intuitive, and scalable. The visual design followed TBC's existing system while optimizing for hierarchy and legibility. Color coding needed to be distinct but accessible. Information density needed to feel manageable, not overwhelming. Every design decision was validated through iteration and feedback.
Critical Design Decisions
The three-part layout separates information into digestible zones - overview, calendar, details - so users can navigate at different levels without cognitive overload. Making the date the primary selector aligns with how people naturally plan. Color-coded categories enable instant pattern recognition. Embedded actions eliminate context switching. The entire structure was designed to scale. More activity types, advanced filtering, custom views - the foundation supports future growth without requiring redesign.
During development, I stayed involved to review builds, answer questions, and adjust designs when technical constraints surfaced. The goal was smooth delivery and a product that shipped as designed.
Impact & Reflections :
The Financial Calendar shifted TBC Business from reactive reporting to proactive planning. Clients now have the visibility and control they need to manage finances confidently.
What Worked
Simplicity resonated with users. Collaborative workshops grounded decisions in real needs. Agile methodology let us ship quickly and iterate based on actual usage.
What I'd Improve
More edge case testing with multi-account businesses, earlier mobile optimization, stronger post-launch feedback loops for continuous improvement.
Key Takeaway
This project reinforced something fundamental: great enterprise design isn't about visual complexity. It's about making complexity manageable, empowering users to act, and building systems that serve both the people using them and the teams maintaining them.