Internal Operations Tool

As Moneda scaled, the team managing day-to-day operations — transaction monitoring, user support, compliance flagging — was cobbling together context from multiple tools, exported CSVs, and manual Slack threads. There was no single place to see what was happening across the platform.

This wasn't a minor inconvenience. Delayed visibility meant delayed responses to fraud signals, compliance gaps, and customer issues that were already resolved elsewhere in the product but not reflected in the ops workflow.

Design Challenge

Build an internal tool that consolidates transaction data, user account health, and compliance flags into a single interface — without overwhelming the operations team with raw data they don't need.

The design process started with a week of observation — sitting with the ops team to understand exactly what they were doing, what they looked for first when they opened their laptop, and what caused the most friction during a typical shift. The insights shaped everything: which data surfaces first, what triggers an alert, and how much detail is needed at a glance vs. on demand.

The internal tool organized information around the ops team's actual workflow: a summary view highlighting anything requiring action, a transaction log with inline filtering, and user profiles that aggregated account history, support tickets, and compliance status in one place.

Alerts were designed to be actionable rather than informational — every flag surfaced a recommended action alongside the data that triggered it.

With the internal tool in place, the ops team was able to identify and act on transaction flags significantly faster than before. Manual handoffs via Slack dropped. The compliance team had an auditable record for every review action taken, which became critical as regulatory requirements increased.