Fairo

I worked across the core product areas sequentially, collaborating with a dedicated Product Manager for each domain and a Product Owner responsible for the overall product.

• Redesigned an early fragmented product into a complete mobile experience
• Designed onboarding, invoicing, bookkeeping, and tax reporting flows
• Worked through complex validation, error, loading, and status scenarios
• Conducted competitor research and translated business and regulatory requirements into product flows
• Built the design system alongside the product
• Worked closely with Product Managers, developers, and stakeholders through refinement and delivery

When I joined, Fairo already had an early version of the app, but it contained only a small number of screens and lacked a consistent product structure or design language.

What started as a redesign quickly became closer to a ground-up product build. We had to establish the foundations of the experience while simultaneously designing the core features for the first product release.

Product decisions were informed by competitor research, business and regulatory requirements, and continuous collaboration with Product Managers and stakeholders.

Before moving into the redesign, I reviewed the existing Fairo experience and compared it with competing financial and accounting products.

The audit helped identify inconsistencies in navigation, interaction patterns, visual hierarchy, and reusable UI. Competitor research helped us understand established patterns around invoicing, bookkeeping, and financial administration, and where Fairo needed to stay familiar versus simplify the experience.

Key areas I focused on:

Fairo brought several complex business tasks into one product. Each area had its own flows and requirements, but they needed to feel like parts of the same system.

Onboarding had to collect and verify much more information than a typical consumer app.

The flow covered registration, identity and business verification, AML requirements, electronic signatures, contracts, and multiple verification scenarios. My focus was to break this long process into understandable steps and keep users oriented even when additional checks or system processing were required.

Registration → ID verification → Business data → AML → E-Signature → Contract

Creating an invoice needed to feel lightweight, while real business scenarios introduced much more complexity.

The experience had to support new and existing clients, international recipients, multiple items, currencies and languages, editable payment details, invoice statuses, sharing, and supporting documents such as Acts of Completion.

I designed the common path to stay fast while keeping advanced options available when they were needed.

Bookkeeping needed to work for users with different levels of automation. Some records could come from connected financial sources, while others had to be added or corrected manually.

I worked on transaction lists, manual entries, transaction details, invoice connections, taxable and non-taxable states, and the supporting flows around managing financial records.

The goal was to connect bookkeeping with the activity users were already creating elsewhere in Fairo rather than make it feel like a separate accounting tool.

Tax reporting combined calculations, reporting periods, deadlines, payments, submissions, and statuses that depended on external systems.

The experience guided users from understanding an upcoming obligation through reviewing their data, submitting a report, and tracking what happened afterwards.

I designed tax and ESV reporting flows, including upcoming and past events, summaries, payments, deadlines, and different submission states.

A significant part of the work happened outside the primary flows.

The product had to account for invalid data, failed verification, processing delays, overdue reports, rejected submissions, missing information, empty states, and recovery scenarios.

Designing these states alongside the main journeys helped make complex financial processes more predictable when something went wrong.

The early product did not have a scalable UI foundation, so I worked on the design system alongside feature development.

I established reusable patterns for typography, colors, navigation, buttons, inputs, financial records, and common components. The system also supported localization and recurring interaction patterns across different parts of the product. This helped keep a rapidly growing number of screens and states consistent across the experience.

I completed my work on Fairo around the launch of P1. The product continued evolving after my involvement and later expanded into banking before eventually being discontinued.

For me, Fairo remains one of the strongest examples of designing a complex financial product from early foundations through launch - across multiple interconnected domains, regulatory constraints, and a large number of real product states.