Overview
Financefair is a non-dilutive funding platform operating in a highly regulated fintech environment, where internal teams manage complex customer, facility, and debtor relationships at scale.
As a Product Designer, I worked on improving internal admin tools used by risk, operations, and product teams to ensure faster decision-making, reduced operational risk, and long-term product scalability. My focus was not only on UI, but on clarifying domain logic, aligning stakeholders, and building a design foundation that could support growth.
Problem
As Financefair scaled, internal systems began to show structural issues:
Complex admin workflows
Debtors could have different statuses depending on customer–facility relationships, but the UI did not clearly reflect this. This created ambiguity, error-prone actions, and high cognitive load for admins.
Slow and risky decision-making
Critical financial decisions were made in interfaces that lacked clear hierarchy, contextual validation, and safeguards, increasing the risk of mistakes and slowing down operations.
Fragmented design system
UI patterns and behaviors were inconsistent across the product, making it harder to scale features, onboard new team members, and maintain quality.
Misalignment across teams
Business, risk, engineering, and product teams often had different mental models of the same entities, which led to rework, unclear requirements, and design churn.
Solution
I treated the challenge as a product and operational design problem, focusing on reducing ambiguity, risk, and friction in day-to-day internal workflows:
Made domain logic explicit in the interface
Mapped complex customer–facility–debtor relationships directly into the UI so admins could clearly see what applies where, which actions were allowed, and what the downstream impact would be.
Embedded guardrails into critical workflows
Designed confirmation states, status visibility, and contextual warnings around high-risk actions to prevent errors while keeping experienced users fast and in control.
Shifted the UI from feature-based to decision-based
Reworked information hierarchy and layouts to support how admins actually evaluate data and make funding decisions, reducing cognitive load and back-and-forth.
Turned fragmented patterns into a scalable system
Consolidated UI components and interaction patterns into a coherent design system that improved consistency, sped up delivery, and made future features easier to build and maintain.
Aligned teams through shared artifacts
Used flows, states, and system diagrams as a common language between product, risk, and engineering, helping teams converge on the same understanding before implementation.
The outcome was an internal platform that supported faster, safer decisions, scaled with the business, and positioned design as an enabler of operational efficiency—not just interface polish.