When a new user signed up in the app, rental agents had to manually check several things: whether a valid payment method was on file, whether a duplicate account existed, and any potential history of non-payment. This was time-consuming, error-prone, and could lead either to approving risky users or to unjustified rejections and delays for legitimate ones. Clients needed a simple, visible, actionable indicator right inside their operational tools.

I started by observing and understanding the agents' day-to-day: what decisions they had to make, when, and with what minimum information to act effectively. The initial request was for two tags for an MVP: payment-method validation and duplicate-name detection. But talking to several clients, I found a shared need that varied according to each one's business rules. Rather than building a client-specific solution, I steered the product toward a flexible, configurable tag system that could grow and adapt to different use cases and entities over the long term.

The system displays tags visible immediately in the operator interfaces, indicating key statuses such as whether a valid payment method is on file or whether a duplicate account has been detected. The architecture was built to be extensible from the start: while the MVP targeted users, the same logic could later apply to other entities (vehicle models, categories, groups, and so on). The solution was developed in close collaboration with the Backend, Frontend, and UX teams, then tested across several client configurations before release.