Role

Product Designer

2023 -2024

Team

3 Engineers
2 Product Designers
2 Product Managers
1 Business Analyst

Platform

Webapp

Industry

Fintech

At a glance

The problem

SMEs managed financial and business records across separate applications, spreadsheets and manual processes, creating duplicated work and limited visibility into business performance.

The approach

The experience was organised around familiar business activities while preserving the relationships between the underlying financial records.

The outcome

Etiaba progressed from concept to its first release and was soft-launched with early users. Early feedback showed that 80% of users described Etiaba as a seamless, consolidated experience.

Key contributions
  • Collaborated with the cross-functional team to translate the accounting product vision into a structured platform.

  • Conducted stakeholder interviews and tested early assumptions, generating insights that shaped the product direction.

  • Owned core workflows across inventory and product management, POS, purchasing, sales invoicing, payments and receipts, expenses, banking, customer management and reporting.

  • Validated early concepts with stakeholders and refined the designs based on feedback.

The problem

SMEs managed financial and business records across separate applications, spreadsheets and manual processes, creating duplicated work and limited visibility into business performance.

The approach

The experience was organised around familiar business activities while preserving the relationships between the underlying financial records.

The outcome

Etiaba progressed from concept to its first release and was soft-launched with early users. Early feedback showed that 80% of users described Etiaba as a seamless, consolidated experience.

Key contributions
  • Collaborated with the cross-functional team to translate the accounting product vision into a structured platform.

  • Conducted stakeholder interviews and tested early assumptions, generating insights that shaped the product direction.

  • Owned core workflows across inventory and product management, POS, purchasing, sales invoicing, payments and receipts, expenses, banking, customer management and reporting.

  • Validated early concepts with stakeholders and refined the designs based on feedback.

Overview

Overview

Before Etiaba, the business supported customers using several third-party financial applications. These products covered different needs but were paid for in foreign currencies, increasing operating costs and making the model difficult to sustain.

SMEs could manage sales in one application, track inventory elsewhere, prepare invoices manually and use another system for financial reporting. Each tool solved an individual task, but the complete financial picture remained fragmented.

Etiaba was created to consolidate these activities into one accounting and financial-management platform designed around the needs of small and medium-sized businesses.

The Challenge

Connecting everyday business activity to accurate financial information

Connecting everyday business activity to accurate financial information

The project was larger than designing a dashboard or adding several financial features.

Sales, invoices, expenses, inventory, customers, suppliers, and reports were related. Designing them independently would reproduce the same fragmentation Etiaba was intended to solve.

The platform therefore needed to:

  • Bring key financial and business records into one system

  • Reduce repeated entry across different workflows

  • Help users move between related records

  • Present accounting information in language SME owners could understand

  • Support a broad feature set without becoming confusing

The project was larger than designing a dashboard or adding several financial features.

Sales, invoices, expenses, inventory, customers, suppliers, and reports were related. Designing them independently would reproduce the same fragmentation Etiaba was intended to solve.

The platform therefore needed to:

  • Bring key financial and business records into one system

  • Reduce repeated entry across different workflows

  • Help users move between related records

  • Present accounting information in language SME owners could understand

  • Support a broad feature set without becoming confusing

The core design challenge was making a complex accounting system feel familiar to people who thought in terms of everyday business activities rather than formal accounting language.

What we learned

What we learned

Customer conversations, stakeholder discussions and competitor analysis highlighted three recurring problems.

Financial information was fragmented

Businesses maintained invoices, sales, expenses, inventory and reports across separate systems, making it difficult to establish one reliable view.

Decision: Create reusable records that could support several financial and business workflows.

Everyday transactions created repeated work

Information recorded during sales, purchases and invoicing often had to be entered, checked or reconciled elsewhere.

Decision: Treat transactions as connected parts of a wider financial-management experience rather than isolated actions.

Owners needed answers, not just transaction tables

Raw records did not immediately explain how much the business had earned, what customers owed, which products required attention, or whether performance was improving.

Decision: Prioritize financial summaries, insights and trends before detailed records.

Defining the product structure

Many users approached financial management through practical activities: selling products, creating invoices, restocking inventory, managing customers, paying suppliers, reviewing income and expenses.

We organised the platform around familiar tasks while preserving the relationships between the underlying financial records.

The product structure connected three layers:

Solutions

Solutions

Connecting the records behind the business

Connecting the records behind the business

The priority was establishing the records that other workflows depended on.

Products, customers, and suppliers were used across several areas of the platform. Designing separate versions of these records inside every module would create inconsistency and force users to repeatedly enter the same information.

Reusable record structures brought essential details and related activity together, allowing the same product, customer or supplier information to support multiple workflows.

Product records

Product information combined pricing, stock details, and relevant activity so that the same record could support inventory, sales, and invoicing.

Customer records

Customer profiles brought identifying information and related transactions into one place, making it easier to understand the history attached to each customer.

Supplier records

Supplier profiles supported supplier information and related purchasing activity without separating them into unrelated areas.

“Create the record once, then make it available wherever the business needs it.”

Managing everyday financial transactions

Managing everyday financial transactions

Etiaba needed to make everyday transactions easier to complete without separating the financial and operational activities behind them. Purchases affected inventory, sales affected stock, and payments and receipts needed to remain connected to the transactions that created them.

We designed these workflows around shared business records, allowing information to move between purchasing, inventory and sales while supporting other day-to-day financial activities such as expenses.

Invoicing

Etiaba supported both customer sales invoices and supplier purchase invoices. Users could select existing customers, suppliers, and products, complete the transaction, and keep the resulting invoice connected to the relevant business records.

Payments or receipts could then be recorded against invoices, helping users track what had been paid or received and what remained outstanding.

Inventory

Inventory records helped businesses manage product information, pricing, available quantities and related activity.

Products could then be used within sales and invoicing experiences rather than being recreated for each transaction. Users could also create a new product from the invoice flow and add it directly to inventory without leaving the transaction.

Purchasing and inventory were connected so that goods received from suppliers could become available stock without recreating product information across workflows.

Point of sale

The POS experience provided a faster path for everyday sales, prioritising product selection, quantities, totals and transaction completion.

POS used the same underlying product records; completed sales remained connected to inventory and the wider financial system without exposing unnecessary accounting complexity during checkout.

Turning business activity into financial visibility

Turning business activity into financial visibility

Recording transactions was only part of the experience. Business owners also needed a way to understand what those transactions meant for the financial position and performance of their business.

Etiaba connected the activity happening across sales, purchases, payments, expenses, and inventory to structured financial reporting, helping users move from managing individual transactions to reviewing the wider state of the business.

Recording transactions was only part of the experience. Business owners also needed a way to understand what those transactions meant for the financial position and performance of their business.

Etiaba connected the activity happening across sales, purchases, payments, expenses and inventory to structured financial reporting, helping users move from managing individual transactions to reviewing the wider state of the business.

Recording transactions was only part of the experience. Business owners also needed a way to understand what those transactions meant for the financial position and performance of their business.

Etiaba connected the activity happening across sales, purchases, payments, expenses and inventory to structured financial reporting, helping users move from managing individual transactions to reviewing the wider state of the business.

Structured financial reporting

The reporting experience gave businesses access to core financial statements including Profit & Loss, Balance Sheet and Cash Flow.

Rather than introducing a different interaction model for every report, we used a consistent structure across them, making it easier for users to move between financial statements and understand where to find key information.

Financial context within everyday records

Not every financial question required opening a report.

Across transaction and record-detail pages, important values were surfaced alongside the underlying information, helping users understand the status and financial context. This allowed financial visibility to exist throughout the product rather than being confined to a separate reporting area.

Designing consistency across the platform

Designing consistency across the platform

Etiaba contained recurring interface requirements across multiple modules, including tables, forms, filters, statuses, charts, and record details.

We created a design system covering the product’s visual foundations, components, and reusable interaction patterns. This made the experience more predictable as users moved between different parts of the product and gave engineers consistent patterns to reuse during implementation.

Etiaba contained recurring interface requirements across multiple modules, including tables, forms, filters, statuses, charts, and record details.

We created a design system covering the product’s visual foundations, components, and reusable interaction patterns. This made the experience more predictable as users moved between different parts of the product and gave engineers consistent patterns to reuse during implementation.

Validation and collaboration

Refining the experience with product, business and engineering teams

Refining the experience with product, business and engineering teams

Collaborated with product managers, business analysts, engineers, and stakeholders throughout the project.

Wireframes, prototypes, and interface designs were reviewed to confirm whether:

  • Workflows reflected the intended business process

  • Financial terminology was understandable

  • Users could identify the next action

  • Related information was clearly connected

  • The proposed experience was feasible to implement

  • Patterns remained consistent across modules

We iterated on the designs to maintain alignment, while feedback from early users during the soft launch helped identify areas for further improvement.

Collaborated with product managers, business analysts, engineers, and stakeholders throughout the project.


Wireframes, prototypes, and interface designs were reviewed to confirm whether:

  • Workflows reflected the intended business process

  • Financial terminology was understandable

  • Users could identify the next action

  • Related information was clearly connected

  • The proposed experience was feasible to implement

  • Patterns remained consistent across modules

We iterated on the designs to maintain alignment, while feedback from early users during the soft launch helped identify areas for further improvement.

Outcome

From fragmented processes to one connected accounting product

From fragmented processes to one connected accounting product

Etiaba progressed from an early idea into a completed first release and was soft-launched with early users.

Early customer feedback revealed three useful signals:

Etiaba progressed from an early idea into a completed first release and was soft-launched with early users.

Early customer feedback revealed three useful signals:

80%

of early users described Etiaba as a seamless and consolidated experience.

30%

of the users requested mobile access, reinforcing mobile as a priority for the product roadmap.



40%

were excited about areas like expenses, reports, and customer and supplier management, which were not part of their workflow.

Reflection

Reflection

Etiaba reinforced that accounting products cannot be designed as collections of independent features.

The project also reinforced the importance of hiding unnecessary accounting complexity without hiding the information users need to make accurate decisions.

Understanding the accounting logic behind each workflow was essential. Workshops with product and business stakeholders helped clarify terminology, expected behaviours, and how financial values should be calculated and presented, particularly across accounting and reporting.

Etiaba reinforced that accounting products cannot be designed as collections of independent features.

The project also reinforced the importance of hiding unnecessary accounting complexity without hiding the information users need to make accurate decisions.

Understanding the accounting logic behind each workflow was essential. Workshops with product and business stakeholders helped clarify terminology, expected behaviours, and how financial values should be calculated and presented, particularly across accounting and reporting.

I’m open to remote and relocation opportunities with product teams building ambitious digital products, as well as contract projects.

Let's talk

Built with

© 2026

I’m open to remote and relocation opportunities with product teams building ambitious digital products, as well as contract projects.

Let's talk

Built with

© 2026

I’m open to remote and relocation opportunities with product teams building ambitious digital products, as well as contract projects.

Let's talk

Built with

© 2026

Create a free website with Framer, the website builder loved by startups, designers and agencies.