Unified admin experience

Overview

As part of improving internal tooling, I worked on designing and building a single point of login and a unified admin account across multiple products. The goal was to streamline the admin experience for internal teams and reduce duplicated work—especially around account creation and settings management.

Tech stack: Next.js, TypeScript, React, TailwindCSS, Zod, React Hook Form

Problem discovery

The company offers several products, and many clients use more than one. But admin setup had to be done separately for each product, including repeated global settings like client name, region, and usage limits. Any update meant changing the same data in multiple places, which slowed down client support, introduced mistakes and inconsistencies, and made the setup process painful and confusing.

To understand the problem better, I audited the existing admin pages and found many were outdated and cluttered. I reviewed the SOPs, which were overly complex and hard to follow. I also interviewed client support teams, who said their biggest frustration was how long and unclear the setup was.

Finally, I spoke with product owners to align on backend constraints and requirements. We found that creating a new account could take up to 20 minutes, and people weren’t even confident they had done it correctly.

Solution discovery

I started by extracting only the settings that people actually needed. Together with backend engineers, we mapped these to existing database models to avoid major backend changes.

We created wireframes, held quick feedback sessions with internal teams, and iterated on the information architecture, grouping related settings and adding smart defaults. I then paired with another front-end developer to implement the experience. The flow was designed to be consistent across all products.

Impact

Although rollout is still in progress, we’ve already reduced account creation time from 20 minutes to just 5. That’s roughly 30 minutes saved per client support person every week.

This project showed that cleaning up the UI, rethinking information structure, and introducing smart defaults can lead to big wins in internal efficiency.