AI SaaS for restaurants
Qrusty
- Role
- Founder & Full-Stack Developer
- Stack
- Next.jsClaudeOpenAIPostgres
- Timeline
- 3 months (ongoing)
- Status
- Live

01
The Problem
Restaurants have menus that change often, need to exist in multiple languages, must comply with allergen regulations, and need to be published fast. Most solutions force the team to enter each dish manually, in each language, with each allergen tag. Unrealistic for a kitchen.
02
The Approach
I built Qrusty from scratch as a multi-tenant SaaS. The core idea: a restaurant uploads a photo or PDF of their menu and AI does the heavy lifting — detects dishes, sections, prices; translates to 9 languages; suggests allergen tags following EU 1169/2011. The restaurant reviews, adjusts, and publishes. From paper to QR menu in minutes.
03
What I Built
- 01Multi-tenant architecture with row-level security
- 02AI pipeline using Claude + OpenAI for menu parsing and structured extraction
- 03Automatic translation engine (9 languages) with context awareness
- 04Allergen tagging compliant with EU 1169/2011
- 05Reusable dish catalog across menus
- 06Role-based permissions (owner / staff)
- 07QR generation for print + digital embedding
- 08Custom dashboard for menu management
04
The Outcome
Qrusty is live, onboarding restaurants in Spain. The key unit economics: what used to take days of manual entry now takes minutes. AI isn't an add-on — it's the core of the product.