The situation
Zero Cheating was already live on the Chrome Web Store, with real users relying on it. The codebase had stability issues, and there was no way for admins to manage customer access without going into the backend directly. Every time someone needed to be added or removed, a developer had to do it. In practice that made it closer to a prototype with users than a finished product.
What I was brought in to do
I was brought in to stabilise the platform and deliver an admin panel that gave the Zero Cheating team control over their own product.
What I built
I managed the delivery of two parallel workstreams: a code stability pass that addressed the existing issues in the Chrome extension and backend, and an admin dashboard built from scratch.
The admin panel gave the Zero Cheating team the ability to onboard new customers, revoke access, and manage their user base without touching the codebase. Work that previously required a developer now took about thirty seconds in a dashboard.
I coordinated between the technical team and the client throughout, kept scope from drifting, and held the delivery to what was actually agreed rather than to the items that kept getting added to the wishlist.
The result
The work produced a more stable product and an admin infrastructure the team could operate on its own. The dashboard removed the developer bottleneck for routine access management. The platform is active, in market, and continues to be maintained.