Technology / PlatformB2B Platform Company (Anonymous)

Internal operations tool rebuilt around how the team actually works — not how it was originally designed

A platform company's support and operations team worked daily with an internal admin tool that had grown without direction over several years. Each team had added what they needed; nothing was connected. Handling a customer issue meant switching between multiple screens and copying data by hand. We spent two weeks observing how the tool was actually used, then rebuilt the three workflows that consumed most of the team's time. The tool now works the way the job works.

4 screens → 1
for the most common support workflow: all relevant data in one view
audit trail introduced
every billing adjustment now has a timestamped record with the acting user
new agent ramp-up
noticeably faster — contextual interface replaced the need to memorise navigation
0 backend changes
rebuilt entirely on the existing API — no infrastructure risk, no data migration

The Challenge

The admin panel covered customer management, billing adjustments, and user permissions — all in separate, unconnected sections. A support agent handling a billing dispute had to look up the customer record in one place, check their usage in another, find the relevant invoice in a third, then make the adjustment in a fourth. There was no audit trail for billing changes — no record of who had changed what or when. New agents took weeks to become effective because the interface gave no contextual guidance and the knowledge of how to navigate it lived in experienced colleagues' heads, not in the tool itself.

The Solution

We started by mapping actual workflows: what did agents do most often, in what sequence, and where did they lose time. Three workflows accounted for around 80% of daily activity. We rebuilt those three as purpose-built screens: a unified customer view that brought together account, usage, and billing data; a billing adjustment flow with inline validation, confirmation, and an automatic audit entry; and a user management screen with clearly scoped permission controls. The work used the existing backend API — no infrastructure changes, no data migration. We delivered incrementally and adjusted based on feedback from the team using it before the final rollout.

The insight that changed everything was simple: we watched someone actually use the tool for a day. Every design decision after that came from what we saw, not what we assumed.

Customer Success LeadB2B Platform Company
internal toolsoperationsadminworkflowplatform

Want similar results?

Let's discuss your specific context.

Contact us