
Role
Product Designer
2023 -2024
Team
3 Engineers
2 Product Designers
2 Product Managers
1 Business Analyst
Platform
Webapp
Industry
Fintech
At a glance
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
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.
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:

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.”
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.
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.

Validation and collaboration
Outcome
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.















