MVP Accounting Translator — Transforming Work Days into Hours
Simetrik - 2022–2023
I Designed and Led the MVP of a No-Code Accounting Translator That Converted a Manual Process of 3–5 Days Into Management in Less Than 4 Hours. The Tool Prevented Churn of a Strategic Client and Has Processed Over 6.3M Entries From 532.8B Transactions Today.
The Starting Point
In 2022, Simetrik executed massive reconciliations that needed to be converted into accounting entries for some strategic clients. The problem: the accounting was manual, took days, and relied on a low-code solution operated by a services team. This delayed analysts' work and detracted from the product's value.
We needed a no-code, self-manageable experience for analysts that ensured traceable entries and reliable publication in ERP. The opportunity was clear: if we failed to get a strategic client to adopt the solution, we risked losing them.
My Role
I participated as an Interaction Designer, responsible for defining the information architecture, flows, and validations. I worked alongside a Visual Designer focused on UI consistency, and together with PMs, engineering, and accounting stakeholders, we achieved the first deployment.
Research and Validation
Research: Over 10 interviews and usability tests with 5 analysts (90% success in critical tasks).
Key Insights: Users needed to start from the seats (output), have technical visibility alongside accounting, and avoid cognitive overload by using a step-by-step flow.
Design Decisions
This Balance Between Accounting Clarity and Technical Detail Was Key to Achieving Adoption in Mixed IT and Accounting Teams.
Results
Accounting Cycle: 3–5 Days → ≤4h.
Strategic Client: 2.1M Seats Published with the New Tool.
Total: 6.3M Seats Processed by the Accounting Translator.
Validation of the No-Code Approach as a Competitive Advantage.
The First Integrated ERP Was SAP; Today, It Also Works with NetSuite and Others.
Strategic Evolution
The MVP was born by combining technical and accounting configurations into a single flow, as the focus was on ERP integration. Over time, aiming to establish ourselves as an accounting tool, we decided to separate the two experiences: one for technical integrations and another for accounting analysts. This decision marked the transition from 'making it possible' to 'designing with an accounting identity.'