ResOS

ResOS is a restaurant operating system designed for small to medium restaurants that still manage inventory, suppliers, compliance, pricing, and reputation across spreadsheets and disconnected tools.

Comment

Inspiration

The inspiration for ResOS came from watching how difficult it was for my mom to manage her own small business. Like many small business owners, she had to handle everything at once: appointments, customers, inventory, expenses, employee tasks, reviews, and day-to-day operations. Most of this was done manually, through scattered notes, messages, spreadsheets, or just memory. That memory was the motivation behind ResOS: a simple, centralized operating system for small businesses. Our goal was to help restaurant owners spend less time fighting with operations and more time focusing on their customers, their services, and growing their business.

What it does

ResOS focuses on restaurant operations. It lets users manage menu items, track supplier costs, monitor compliance and safety tasks, view business profiles, and organize customer review information in one central place. Each business owner gets their own secure workspace, so their restaurant data stays separate from other users.

How we built it

We started by narrowing down what jobs we wanted to deal with and what approach for it. We definetely struggled with utilizing LLM tools properly, and we also struggled with managing our time. But in the end we were able to divide up the work into two managable groups, frontend and backend, Allison managed the frontend, and Aarav managed the backend.

Challenges we ran into

One of the biggest challenges we ran into was connecting the frontend dashboard to a real backend. At first, the app worked with local data, but we needed to make it persistent so users could log in, save changes, and come back later without losing their information. Another major challenge was handling user access correctly. We had to make sure that each person had their own workspace instead of everyone sharing the same restaurant data. This required setting up Supabase Auth, PostgreSQL tables, Row Level Security, and database functions so that each user could only access the workspace they owned.

Accomplishments that we're proud of

Built a full restaurant operations platform from scratch during the hackathon, combining inventory, supplier tracking, compliance management, reviews, and menu costing into one system. Created a modern dashboard that makes complicated restaurant data easy to understand and act on in real time. Successfully implemented authentication, shared workspaces, and cloud persistence using Supabase and deployed the project online with Vercel .

What we learned

While building ResOS, we learned how much work goes into turning a simple frontend idea into a real full-stack application. At first, it was easy to display business data on a dashboard, but making that data secure, persistent, and user-specific required a lot more planning. We also learned how difficult it is to correctly manage time in a time crunch scenario.

What's next for ResOS

We will implement more APIs to make the website more interconnected, this includes Yelp, Google, and other review aggregation platform APIs so that we can have a better reviews section in our product.

Built With

Share this project:

Updates