SaaS · Internal admin
Managing a restaurant platform isn't just about restaurants, it's about operating the business behind them. Administrators need a single place to monitor tenants, users, subscriptions, revenue, integrations, and platform health without switching between disconnected tools.
This project explores how I designed a scalable internal control plane that helps operators understand the state of the platform at a glance while making complex administrative tasks easier to navigate.
What is AI-ROS admin
AI-ROS admin is a multi-tenant SaaS restaurant operating system. This is the admin side - the internal control plane an operator uses to see how the platform itself is performing across every restaurant group on it.
What was the problem
As the platform grew, so did the amount of operational data.Platform administrators were responsible for managing:
restaurant groups
thousands of users
subscriptions
billing
transactions
integrations
platform health
reports
Although all of this information existed, it wasn't organized around how operators actually worked. Finding answers often meant navigating multiple sections and interpreting dense tables instead of quickly understanding what required attention.
The challenge wasn't adding more functionality it was designing an interface that helped operators make better decisions faster.
Understanding the user
The primary user is a Super Admin responsible for the health of the entire platform.Their day typically involves answering questions like:
Which tenants are active?
Is revenue growing?
Are any integrations failing?
Which customers need attention?
Are subscriptions functioning correctly?
Is the platform healthy today?
Instead of treating these as separate tools, I wanted the experience to answer these questions naturally through the interface.
The approach
I anchored the design around four questions: Who's on the platform? What are they paying? What's breaking? Where's revenue moving? Everything had to earn its place by answering one of them without collapsing into the wall of dense tables admin tools so easily become.
I organized everything into six clear domains so the operator always knows where they are:
Platform Management — tenants, users, locations
Billing — plans, subscriptions, transactions, revenue
Data & Integrations — explorer, sources, storage, export
System Ops — health, audit logs, feature flags, jobs
Reports — platform, tenant usage, revenue, user activity
Dashboard — the at-a-glance home
The Process
The whole thing came together through iterative back-and-forth with Claude Code. Crucially, this wasn't writing code — it was designing out loud: describe the intent, see it rendered, react to what felt wrong, refine.
The loop:
Describe the surface in plain language.
See it live almost immediately.
React with what's the hierarchy doing, is the eye landing in the right place?
Refine and repeat across each screen.
Seeing real layouts instantly instead of static mockups meant design decisions got tested against a working interface in minutes, not days. The bottleneck shifted from production to judgment, which is where a designer should be spending their time.
What was the outcome
The result was a complete internal administration platform capable of supporting platform operations across multiple restaurant organizations.
Most importantly, the platform establishes a scalable foundation that can support future administrative capabilities without increasing complexity.