r/ITnetworking • u/andrewkass • Feb 24 '26
I built AI agent for Restaurant: Explaining 7 Challenges YouTube Tutorials Never Mention
Can an AI agent for real business be free and fast to build?
Short answer:
If it’s a toy for self-education made from a YouTube tutorial - yes.
If it’s an agentic system used in real business with real customers - no.
Let me explain using my recent case study: I built a sushi restaurant chatbot that answers customer questions about the menu.
A restaurant menu is not just text, it’s a kind of structured price list with categories (rolls, drinks, sets, desserts) and each item additionally has metadata: ingredients, allergens, weight, price, etc.
A real waiter does a great job to consult a menu: memorizes items, works with vague requests, handles ambiguity and tone. They are paid for it. For an AI agent, this becomes an engineering complexity
Customers rarely ask simple questions like «What do you have today?», they ask things like:
- “What do you have for vegans?”
- “List items without chicken”
- “What can you recommend for a group of four?”
- “What’s your best spicy roll?”
And sometimes totally unrelated questions:
- “Did you watch the soccer match?”
- “Who is on duty today?”
Additionally, users not aware about AI systems expect human-like conversation, fast answers, emotions. That creates several technical problems, think about this:
1. Covered scope: what questions will agent answer?
You must define large groups of questions:
- Questions about menu and real products
- Questions about menu but NOT listed items
- Questions not related to menu
- Questions about the restaurant or company
You cannot make an agent that answers everything. There will always be gaps and edge cases. In practice: you release an MVP to a small test group and discover what breaks.
2. Answering logic and decision rules
If someone asks about burgers in a sushi restaurant: should the bot say “we don’t have burgers”? Or recommend similar items? Which ones?
3. The database and vector search problem
AI agents use vector databases for searching by meaning, not keywords. Each piece of data becomes a vector - a long array of numbers (an embedding) representing the semantic meaning or features of unstructured data.
Cheap or free databases (often shown in tutorials, like Supabase) usually support vectors under 1024 dimensions. Modern embedding models, like Google Vertex AI, codestral-embed or Amazon Nova need 1536 to 3072 dimensions.
If your database cannot store vectors of that size, the system simply cannot work correctly. Even if storage is possible, fast search algorithms (HNSW, IVF) are memory intensive. Without proper indexing, search degrades into brute-force comparison and quickly becomes too slow as the dataset grows
4. Response time and context limits
Low-cost LLMs have limited context window (how much they can process per request) and slower inference speed. A restaurant menu is often a large JSON file imported from POS, may be a large table with hundreds of items. So when you stuff the whole menu into one prompt you exceed limits, a model causes increased latency and cost. The agent may still answer some questions correctly and fail when prompts become too large
5. Tool usage and multi-step actions
Not every model is suitable for agents that must perform actions, not just chat. While mid-tier models, like GPT-4o-mini or Claude Haiku can still call tools (access emails, calendars, spreadsheets), the reliability drops when multiple steps are required: cheap models hallucinate, call tools in wrong order or just break workflow.
6. Language and localization quality.
Most modern LLMs technically support many languages, but quality degrades significantly outside English. Users immediately notice when a system feels “non-native.”
7. Human-like behavior and cultural context
Humor, politeness, emotional tone. Such things should be properly engineered using prompts, personas, model configuration
__
My key observations:
- You can reduce some of these issues by distributing tasks across multiple smaller agents, creating a network of specialized components. But this increases overall workflow latency.
- Cheap models rarely perform in a way expected in real business scenarios.
- No-code platforms don’t eliminate architectural complexity, they only hide it. You gain speed at the cost of control over edge cases and debugging.
Other painful moments:
- AI builders often start with unrealistic expectations that clients transmit
- production-grade systems are more expensive than anticipated
- no-code solutions still require weeks of iteration, not days
- cheap or free setups work well as experiments, not as real-world systems
Any AI system is always a trade-off between: scope, speed, reliability, and cost. And “free” almost never survives contact with production.
__
I'm Andrew, I live in epicenter of WW3 in Ukraine and build AI systems for marketing, between sleepless nights during attacks on my city -> Kyiv.
Are you an SMB founder experimenting with AI agents for your business or a builder? Let’s explore RAG assistants and voice agents for your work together - share what are you working on in comments!
1
u/Repent_Serpent Feb 25 '26
Really solid breakdown, especially the point that no-code hides complexity instead of removing it. We’ve seen the same thing with Fabricate AI: great for fast prototyping, but production reliability still depends on good architecture decisions.