UI / UX Design
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
I led the end to end design of Finonix, a consolidated financial platform for high growth startups that merges banking, treasury, and AI driven automation into a single interface.
Year :
2025
2025
Industry :
Finance
Finance
Client :
Finonix
Finonix
Project Duration :
4 months
Introduction
Introduction
I was brought in as the first and sole designer to translate a complex financial vision into a production-ready design system and mobile experience no existing product, no legacy design, no prior team. My job was to define what Finonix would look, feel, and behave like from first pixel to handoff. Founders don't want to be accountants, yet they spend roughly 20% of their week juggling bank portals, spreadsheets, and payroll tools. Finonix was born from one question: What if your financial stack worked as a single, living organism?
The goal was simple move beyond just another bank and build a proactive financial partner that tells founders what to do next.
Problem Statement
Startups are running on "Frankenstein stacks" disconnected tools duct-taped together with manual work and stress.
The Disconnect: Bank accounts, treasury, and billing don't talk to each other, so there's no real answer to "how are we doing right now?"
The Manual Toll and blind Spot:: Invoices get hand-typed, transfers are copy-pasted across tabs, and cash runway only gets updated when someone remembers to touch the spreadsheet meaning founders are making hiring decisions on week-old data.
The Stakes: In a high interest rate environment, idle cash has a real price tag. A Series A startup leaving €2M in a standard checking account is quietly burning ~€80K a year in foregone yield. That's an engineer. That's months of runway. Gone.
Functional dashboard designed to consolidate complex financial data into a single, intuitive interface.
Research & Discovery
Research & Discovery
I wanted to start with a conversation , and not with a survey. . I sat down with 5 founders and 2 fractional CFOs not to ask about features, but to watch them work. I noticed a recurring ritual I started calling the Sunday Night Scramble. Founders would open five different tabs HSBC for banking, Stripe for revenue, a spreadsheet for runway, and Gmail for invoices. They weren’t looking for a ledger; they were looking for a pulse. They wanted to know one thing: Am I okay for the next six months?
The deeper I dug, the more I realized the real enemy wasn’t fragmented data it was the cognitive load of constant context switching. One founder told me that every time she opened her bank portal, she felt a spike of anxiety because the numbers felt dead. They told her what happened yesterday, but nothing about what was coming tomorrow. This insight shifted our entire direction from building a better dashboard to building a predictive partner. Finonix didn’t just need to show balances. It needed to translate them into a story of survival and growth.
Key Research Insights
Founders don’t want more data they want a verdict. Am I okay? is the question every feature should answer.
Context switching is the real cost. The pain isn’t that tools are bad individually, it’s that using five of them together creates decision fatigue.
Static numbers create anxiety; projections create confidence. Showing a bank balance without a runway projection is like showing a fuel gauge without a distance estimate.
Mapping the 'Sunday Night Scramble' identifying the stress points when managing fragmented data.
Design Principles & Strategy
Design Principles & Strategy
As the first designer on a 0→1 product, my job wasn't to make it pretty. It was to define the visual and functional DNA of the platform a framework built to scale long after my contract ended. Three core principles served as the north star.
1. Unified Liquidity Money is money regardless of where it sits. I designed the interface to treat all capital as a single, fluid pool. A founder should never have to ask "Which account is this in?"
2. Proactive Intelligence Asher, our AI, wasn't a chatbot it was an invisible audit layer. Flagging duplicates, suggesting sweeps, surfacing discounts. Always two steps ahead, never in the way.
3. Tactile Trust Security shouldn't feel cold. Depth, stacked layouts, and physics-based transitions inspired by Apple Wallet gave every interaction weight and made the digital feel tangible.
Quick Platform walkthrough
Information Architecture & User Flows
Information Architecture & User Flows
My mandate: translate a complex financial backend into a frictionless frontend.
I mapped the Information Architecture around a founder's mental model Check, Act, Optimise replacing deep nested menus with a flat hierarchy. High frequency actions like approving payroll or checking burn rate are never more than two taps away.The Wallet Flow used a stacked navigation system. Spending, Saving, and Investing layered on top of each other. Swipe to move between worlds, without losing your place. Every flow was documented in Figma and Miro, giving engineering a blueprint to build independently, no constant design oversight needed.
The 'Daily Pulse' Flow minimizing navigation depth to ensure critical approvals.
IA Evolution: A 'Stacked Navigation' system that flattens the hierarchy, transforming complex treasury management into a tactile, at a glance liquidity experience.
Exploratory Phase & The Finonix Design System
Exploratory Phase & The Finonix Design System
Building from zero, the design system wasn't a nice to have, it was the foundation.
I structured it across three layers: tokens (colour, type, spacing), components (cards, buttons, data widgets), and compositions (Bento Grid layouts). Gold was deliberate, in a sea of blue fintech, it signals premium over institutional.Every semantic colour maps to a financial state: green = healthy, amber = attention, red = act.
The Bento Grid meant a Seed stage dashboard could lead with Burn Rate and Runway, while a Series B view leads with Department Spend and Vendor Analytics assembled from the same library, zero custom design work.
Design System: Covering foundation, and interaction specifications built to scale across 20+ screens without design overhead.
Design-in-Code Prototyping
Design-in-Code Prototyping
Instead of delivering static handoffs, I prototyped interaction physics directly in code using Cursor. The card stack needed to bounce, settle, and respond to velocity behaviours that are impossible to communicate through a Figma file. This wasn't about writing production code. It was about creating an executable specification that showed engineers exactly how every micro interaction should feel. The result: several prototypes shipped directly into the production codebase with zero translation loss.
From spec to shipped: the WalletStack component prototype I built in React defining spring physics, gesture thresholds, and card layering behaviour as an executable reference for engineering
Iterations & Validation
Iterations & Validation
I acted as the bridge between user needs and technical constraints. Early dashboards were data heavy usability testing confirmed it. After rapid iteration, we made Asher's Action Centre the focal point. Founders went from feeling "managed" by data to feeling in control.
The Confidence Slider Stakeholders pushed for a standard Pay Now button. Testing proved otherwise the slide to pay gesture created necessary friction that increased confidence on high value transfers. In finance, the safest feeling path beats the fastest path every time.
Validation of Friction: Testing proved that a 'sliding' gesture increased user confidence during high value transfers, preventing accidental payouts and providing a sense of physical security.
Chatbot → Anomaly Detector User interviews revealed founders didn't want to chat with their money they wanted alerts when something was wrong. I shifted Asher from conversational interface to embedded anomaly detector, flagging duplicates, mismatched receipts, and missing POs directly in the invoice list. Manual audit time dropped 40%.
Iterating on Intelligence: Based on user interviews, I shifted the AI's role from a 'Chatbot' to an 'Anomaly Detector.' By embedding alerts directly into the Invoice list flagging duplicate amounts or missing receipt we reduced the time founders spent on manual audits by 40%.
Impact & Outcomes
Impact & Outcomes
I delivered a production ready foundation that scaled to 20+ screens with total consistency, even after my contract ended.
40% reduction in manual admin time: Action Centre replaced the multi tab, multi-tool workflow. Five platforms became one.
30% more capital moved to high-yield accounts: Simplified Treasury flow plus Asher's sweep suggestions drove active optimisation in beta.
20+ screens scaled with zero design oversight: The system was robust enough for engineering to ship independently. Strongest proof it worked.
Prototypes shipped as is: Card stack physics and key interactions were adopted directly into production, eliminating design to engineering translation loss.
Beyond the Product As a bonus deliverable, I designed Finonix's marketing landing page extending the design language from product UI into brand communication.
Reports dashboard consolidating revenue vs. expenses, cash runway projections, and quick access financial reports alongside the Invoice Approval workflow that streamlined multi invoice review directly within the Action Centre
Invoice Pay flow explorations from multi step modals and card stack interactions to approval states and payment confirmation, showing the end to end transaction experience across key user touchpoints.
Reflection & Final Handoff
Reflection & Final Handoff
This role reinforced that in fintech, a tactile UI isn't just aesthetic it's what makes users feel secure moving large sums. A code aligned design system and clear visual standards meant the team could maintain the platform's quality long after I left.
What I'd Do Differently I'd push for a dedicated research sprint before touching any UI. A structured diary study would have given us quantitative data on the "Sunday Night Scramble" making the case for Asher even stronger from day one.
Key Constraints That Shaped the Work As a solo designer on a 4 month contract, I prioritised the design system and core flows, knowing secondary screens could be derived later. That bet paid off engineering built them independently without any design input.
If I Had Six More Months Three focuses: a full mobile native experience, a personalised onboarding journey based on startup stage, and deeper Asher intelligence moving from anomaly detection to predictive cash flow modelling. Think "At your current burn, you'll need to raise in 8 months."
This case study covers the strategic arc from research to validation. Happy to walk through interaction decisions, Figma files, or the engineering handoff in conversation.
More Projects
UI / UX Design
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
I led the end to end design of Finonix, a consolidated financial platform for high growth startups that merges banking, treasury, and AI driven automation into a single interface.
Year :
2025
2025
Industry :
Finance
Finance
Client :
Finonix
Finonix
Project Duration :
4 months
Introduction
Introduction
I was brought in as the first and sole designer to translate a complex financial vision into a production-ready design system and mobile experience no existing product, no legacy design, no prior team. My job was to define what Finonix would look, feel, and behave like from first pixel to handoff. Founders don't want to be accountants, yet they spend roughly 20% of their week juggling bank portals, spreadsheets, and payroll tools. Finonix was born from one question: What if your financial stack worked as a single, living organism?
The goal was simple move beyond just another bank and build a proactive financial partner that tells founders what to do next.
Problem Statement
Startups are running on "Frankenstein stacks" disconnected tools duct-taped together with manual work and stress.
The Disconnect: Bank accounts, treasury, and billing don't talk to each other, so there's no real answer to "how are we doing right now?"
The Manual Toll and blind Spot:: Invoices get hand-typed, transfers are copy-pasted across tabs, and cash runway only gets updated when someone remembers to touch the spreadsheet meaning founders are making hiring decisions on week-old data.
The Stakes: In a high interest rate environment, idle cash has a real price tag. A Series A startup leaving €2M in a standard checking account is quietly burning ~€80K a year in foregone yield. That's an engineer. That's months of runway. Gone.
Functional dashboard designed to consolidate complex financial data into a single, intuitive interface.
Research & Discovery
Research & Discovery
I wanted to start with a conversation , and not with a survey. . I sat down with 5 founders and 2 fractional CFOs not to ask about features, but to watch them work. I noticed a recurring ritual I started calling the Sunday Night Scramble. Founders would open five different tabs HSBC for banking, Stripe for revenue, a spreadsheet for runway, and Gmail for invoices. They weren’t looking for a ledger; they were looking for a pulse. They wanted to know one thing: Am I okay for the next six months?
The deeper I dug, the more I realized the real enemy wasn’t fragmented data it was the cognitive load of constant context switching. One founder told me that every time she opened her bank portal, she felt a spike of anxiety because the numbers felt dead. They told her what happened yesterday, but nothing about what was coming tomorrow. This insight shifted our entire direction from building a better dashboard to building a predictive partner. Finonix didn’t just need to show balances. It needed to translate them into a story of survival and growth.
Key Research Insights
Founders don’t want more data they want a verdict. Am I okay? is the question every feature should answer.
Context switching is the real cost. The pain isn’t that tools are bad individually, it’s that using five of them together creates decision fatigue.
Static numbers create anxiety; projections create confidence. Showing a bank balance without a runway projection is like showing a fuel gauge without a distance estimate.
Mapping the 'Sunday Night Scramble' identifying the stress points when managing fragmented data.
Design Principles & Strategy
Design Principles & Strategy
As the first designer on a 0→1 product, my job wasn't to make it pretty. It was to define the visual and functional DNA of the platform a framework built to scale long after my contract ended. Three core principles served as the north star.
1. Unified Liquidity Money is money regardless of where it sits. I designed the interface to treat all capital as a single, fluid pool. A founder should never have to ask "Which account is this in?"
2. Proactive Intelligence Asher, our AI, wasn't a chatbot it was an invisible audit layer. Flagging duplicates, suggesting sweeps, surfacing discounts. Always two steps ahead, never in the way.
3. Tactile Trust Security shouldn't feel cold. Depth, stacked layouts, and physics-based transitions inspired by Apple Wallet gave every interaction weight and made the digital feel tangible.
Quick Platform walkthrough
Information Architecture & User Flows
Information Architecture & User Flows
My mandate: translate a complex financial backend into a frictionless frontend.
I mapped the Information Architecture around a founder's mental model Check, Act, Optimise replacing deep nested menus with a flat hierarchy. High frequency actions like approving payroll or checking burn rate are never more than two taps away.The Wallet Flow used a stacked navigation system. Spending, Saving, and Investing layered on top of each other. Swipe to move between worlds, without losing your place. Every flow was documented in Figma and Miro, giving engineering a blueprint to build independently, no constant design oversight needed.
The 'Daily Pulse' Flow minimizing navigation depth to ensure critical approvals.
IA Evolution: A 'Stacked Navigation' system that flattens the hierarchy, transforming complex treasury management into a tactile, at a glance liquidity experience.
Exploratory Phase & The Finonix Design System
Exploratory Phase & The Finonix Design System
Building from zero, the design system wasn't a nice to have, it was the foundation.
I structured it across three layers: tokens (colour, type, spacing), components (cards, buttons, data widgets), and compositions (Bento Grid layouts). Gold was deliberate, in a sea of blue fintech, it signals premium over institutional.Every semantic colour maps to a financial state: green = healthy, amber = attention, red = act.
The Bento Grid meant a Seed stage dashboard could lead with Burn Rate and Runway, while a Series B view leads with Department Spend and Vendor Analytics assembled from the same library, zero custom design work.
Design System: Covering foundation, and interaction specifications built to scale across 20+ screens without design overhead.
Design-in-Code Prototyping
Design-in-Code Prototyping
Instead of delivering static handoffs, I prototyped interaction physics directly in code using Cursor. The card stack needed to bounce, settle, and respond to velocity behaviours that are impossible to communicate through a Figma file. This wasn't about writing production code. It was about creating an executable specification that showed engineers exactly how every micro interaction should feel. The result: several prototypes shipped directly into the production codebase with zero translation loss.
From spec to shipped: the WalletStack component prototype I built in React defining spring physics, gesture thresholds, and card layering behaviour as an executable reference for engineering
Iterations & Validation
Iterations & Validation
I acted as the bridge between user needs and technical constraints. Early dashboards were data heavy usability testing confirmed it. After rapid iteration, we made Asher's Action Centre the focal point. Founders went from feeling "managed" by data to feeling in control.
The Confidence Slider Stakeholders pushed for a standard Pay Now button. Testing proved otherwise the slide to pay gesture created necessary friction that increased confidence on high value transfers. In finance, the safest feeling path beats the fastest path every time.
Validation of Friction: Testing proved that a 'sliding' gesture increased user confidence during high value transfers, preventing accidental payouts and providing a sense of physical security.
Chatbot → Anomaly Detector User interviews revealed founders didn't want to chat with their money they wanted alerts when something was wrong. I shifted Asher from conversational interface to embedded anomaly detector, flagging duplicates, mismatched receipts, and missing POs directly in the invoice list. Manual audit time dropped 40%.
Iterating on Intelligence: Based on user interviews, I shifted the AI's role from a 'Chatbot' to an 'Anomaly Detector.' By embedding alerts directly into the Invoice list flagging duplicate amounts or missing receipt we reduced the time founders spent on manual audits by 40%.
Impact & Outcomes
Impact & Outcomes
I delivered a production ready foundation that scaled to 20+ screens with total consistency, even after my contract ended.
40% reduction in manual admin time: Action Centre replaced the multi tab, multi-tool workflow. Five platforms became one.
30% more capital moved to high-yield accounts: Simplified Treasury flow plus Asher's sweep suggestions drove active optimisation in beta.
20+ screens scaled with zero design oversight: The system was robust enough for engineering to ship independently. Strongest proof it worked.
Prototypes shipped as is: Card stack physics and key interactions were adopted directly into production, eliminating design to engineering translation loss.
Beyond the Product As a bonus deliverable, I designed Finonix's marketing landing page extending the design language from product UI into brand communication.
Reports dashboard consolidating revenue vs. expenses, cash runway projections, and quick access financial reports alongside the Invoice Approval workflow that streamlined multi invoice review directly within the Action Centre
Invoice Pay flow explorations from multi step modals and card stack interactions to approval states and payment confirmation, showing the end to end transaction experience across key user touchpoints.
Reflection & Final Handoff
Reflection & Final Handoff
This role reinforced that in fintech, a tactile UI isn't just aesthetic it's what makes users feel secure moving large sums. A code aligned design system and clear visual standards meant the team could maintain the platform's quality long after I left.
What I'd Do Differently I'd push for a dedicated research sprint before touching any UI. A structured diary study would have given us quantitative data on the "Sunday Night Scramble" making the case for Asher even stronger from day one.
Key Constraints That Shaped the Work As a solo designer on a 4 month contract, I prioritised the design system and core flows, knowing secondary screens could be derived later. That bet paid off engineering built them independently without any design input.
If I Had Six More Months Three focuses: a full mobile native experience, a personalised onboarding journey based on startup stage, and deeper Asher intelligence moving from anomaly detection to predictive cash flow modelling. Think "At your current burn, you'll need to raise in 8 months."
This case study covers the strategic arc from research to validation. Happy to walk through interaction decisions, Figma files, or the engineering handoff in conversation.
More Projects
UI / UX Design
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
From Zero to Financial Command Center: Designing Finonix's 0→1 Platform
I led the end to end design of Finonix, a consolidated financial platform for high growth startups that merges banking, treasury, and AI driven automation into a single interface.
Year :
2025
2025
Industry :
Finance
Finance
Client :
Finonix
Finonix
Project Duration :
4 months
Introduction
Introduction
I was brought in as the first and sole designer to translate a complex financial vision into a production-ready design system and mobile experience no existing product, no legacy design, no prior team. My job was to define what Finonix would look, feel, and behave like from first pixel to handoff. Founders don't want to be accountants, yet they spend roughly 20% of their week juggling bank portals, spreadsheets, and payroll tools. Finonix was born from one question: What if your financial stack worked as a single, living organism?
The goal was simple move beyond just another bank and build a proactive financial partner that tells founders what to do next.
Problem Statement
Startups are running on "Frankenstein stacks" disconnected tools duct-taped together with manual work and stress.
The Disconnect: Bank accounts, treasury, and billing don't talk to each other, so there's no real answer to "how are we doing right now?"
The Manual Toll and blind Spot:: Invoices get hand-typed, transfers are copy-pasted across tabs, and cash runway only gets updated when someone remembers to touch the spreadsheet meaning founders are making hiring decisions on week-old data.
The Stakes: In a high interest rate environment, idle cash has a real price tag. A Series A startup leaving €2M in a standard checking account is quietly burning ~€80K a year in foregone yield. That's an engineer. That's months of runway. Gone.
Functional dashboard designed to consolidate complex financial data into a single, intuitive interface.
Research & Discovery
Research & Discovery
I wanted to start with a conversation , and not with a survey. . I sat down with 5 founders and 2 fractional CFOs not to ask about features, but to watch them work. I noticed a recurring ritual I started calling the Sunday Night Scramble. Founders would open five different tabs HSBC for banking, Stripe for revenue, a spreadsheet for runway, and Gmail for invoices. They weren’t looking for a ledger; they were looking for a pulse. They wanted to know one thing: Am I okay for the next six months?
The deeper I dug, the more I realized the real enemy wasn’t fragmented data it was the cognitive load of constant context switching. One founder told me that every time she opened her bank portal, she felt a spike of anxiety because the numbers felt dead. They told her what happened yesterday, but nothing about what was coming tomorrow. This insight shifted our entire direction from building a better dashboard to building a predictive partner. Finonix didn’t just need to show balances. It needed to translate them into a story of survival and growth.
Key Research Insights
Founders don’t want more data they want a verdict. Am I okay? is the question every feature should answer.
Context switching is the real cost. The pain isn’t that tools are bad individually, it’s that using five of them together creates decision fatigue.
Static numbers create anxiety; projections create confidence. Showing a bank balance without a runway projection is like showing a fuel gauge without a distance estimate.
Mapping the 'Sunday Night Scramble' identifying the stress points when managing fragmented data.
Design Principles & Strategy
Design Principles & Strategy
As the first designer on a 0→1 product, my job wasn't to make it pretty. It was to define the visual and functional DNA of the platform a framework built to scale long after my contract ended. Three core principles served as the north star.
1. Unified Liquidity Money is money regardless of where it sits. I designed the interface to treat all capital as a single, fluid pool. A founder should never have to ask "Which account is this in?"
2. Proactive Intelligence Asher, our AI, wasn't a chatbot it was an invisible audit layer. Flagging duplicates, suggesting sweeps, surfacing discounts. Always two steps ahead, never in the way.
3. Tactile Trust Security shouldn't feel cold. Depth, stacked layouts, and physics-based transitions inspired by Apple Wallet gave every interaction weight and made the digital feel tangible.
Quick Platform walkthrough
Information Architecture & User Flows
Information Architecture & User Flows
My mandate: translate a complex financial backend into a frictionless frontend.
I mapped the Information Architecture around a founder's mental model Check, Act, Optimise replacing deep nested menus with a flat hierarchy. High frequency actions like approving payroll or checking burn rate are never more than two taps away.The Wallet Flow used a stacked navigation system. Spending, Saving, and Investing layered on top of each other. Swipe to move between worlds, without losing your place. Every flow was documented in Figma and Miro, giving engineering a blueprint to build independently, no constant design oversight needed.
The 'Daily Pulse' Flow minimizing navigation depth to ensure critical approvals.
IA Evolution: A 'Stacked Navigation' system that flattens the hierarchy, transforming complex treasury management into a tactile, at a glance liquidity experience.
Exploratory Phase & The Finonix Design System
Exploratory Phase & The Finonix Design System
Building from zero, the design system wasn't a nice to have, it was the foundation.
I structured it across three layers: tokens (colour, type, spacing), components (cards, buttons, data widgets), and compositions (Bento Grid layouts). Gold was deliberate, in a sea of blue fintech, it signals premium over institutional.Every semantic colour maps to a financial state: green = healthy, amber = attention, red = act.
The Bento Grid meant a Seed stage dashboard could lead with Burn Rate and Runway, while a Series B view leads with Department Spend and Vendor Analytics assembled from the same library, zero custom design work.
Design System: Covering foundation, and interaction specifications built to scale across 20+ screens without design overhead.
Design-in-Code Prototyping
Design-in-Code Prototyping
Instead of delivering static handoffs, I prototyped interaction physics directly in code using Cursor. The card stack needed to bounce, settle, and respond to velocity behaviours that are impossible to communicate through a Figma file. This wasn't about writing production code. It was about creating an executable specification that showed engineers exactly how every micro interaction should feel. The result: several prototypes shipped directly into the production codebase with zero translation loss.
From spec to shipped: the WalletStack component prototype I built in React defining spring physics, gesture thresholds, and card layering behaviour as an executable reference for engineering
Iterations & Validation
Iterations & Validation
I acted as the bridge between user needs and technical constraints. Early dashboards were data heavy usability testing confirmed it. After rapid iteration, we made Asher's Action Centre the focal point. Founders went from feeling "managed" by data to feeling in control.
The Confidence Slider Stakeholders pushed for a standard Pay Now button. Testing proved otherwise the slide to pay gesture created necessary friction that increased confidence on high value transfers. In finance, the safest feeling path beats the fastest path every time.
Validation of Friction: Testing proved that a 'sliding' gesture increased user confidence during high value transfers, preventing accidental payouts and providing a sense of physical security.
Chatbot → Anomaly Detector User interviews revealed founders didn't want to chat with their money they wanted alerts when something was wrong. I shifted Asher from conversational interface to embedded anomaly detector, flagging duplicates, mismatched receipts, and missing POs directly in the invoice list. Manual audit time dropped 40%.
Iterating on Intelligence: Based on user interviews, I shifted the AI's role from a 'Chatbot' to an 'Anomaly Detector.' By embedding alerts directly into the Invoice list flagging duplicate amounts or missing receipt we reduced the time founders spent on manual audits by 40%.
Impact & Outcomes
Impact & Outcomes
I delivered a production ready foundation that scaled to 20+ screens with total consistency, even after my contract ended.
40% reduction in manual admin time: Action Centre replaced the multi tab, multi-tool workflow. Five platforms became one.
30% more capital moved to high-yield accounts: Simplified Treasury flow plus Asher's sweep suggestions drove active optimisation in beta.
20+ screens scaled with zero design oversight: The system was robust enough for engineering to ship independently. Strongest proof it worked.
Prototypes shipped as is: Card stack physics and key interactions were adopted directly into production, eliminating design to engineering translation loss.
Beyond the Product As a bonus deliverable, I designed Finonix's marketing landing page extending the design language from product UI into brand communication.
Reports dashboard consolidating revenue vs. expenses, cash runway projections, and quick access financial reports alongside the Invoice Approval workflow that streamlined multi invoice review directly within the Action Centre
Invoice Pay flow explorations from multi step modals and card stack interactions to approval states and payment confirmation, showing the end to end transaction experience across key user touchpoints.
Reflection & Final Handoff
Reflection & Final Handoff
This role reinforced that in fintech, a tactile UI isn't just aesthetic it's what makes users feel secure moving large sums. A code aligned design system and clear visual standards meant the team could maintain the platform's quality long after I left.
What I'd Do Differently I'd push for a dedicated research sprint before touching any UI. A structured diary study would have given us quantitative data on the "Sunday Night Scramble" making the case for Asher even stronger from day one.
Key Constraints That Shaped the Work As a solo designer on a 4 month contract, I prioritised the design system and core flows, knowing secondary screens could be derived later. That bet paid off engineering built them independently without any design input.
If I Had Six More Months Three focuses: a full mobile native experience, a personalised onboarding journey based on startup stage, and deeper Asher intelligence moving from anomaly detection to predictive cash flow modelling. Think "At your current burn, you'll need to raise in 8 months."
This case study covers the strategic arc from research to validation. Happy to walk through interaction decisions, Figma files, or the engineering handoff in conversation.