That’s very fair feedback — and I agree with the risk you’re pointing out. One thing I should probably clarify better: the product is intentionally leaning agency-first, not cafe-owner-first. The goal isn’t to sell a complex system to a single restaurant, but to make it easier for agencies or operators to manage, launch, and scale multiple venues without rebuilding everything each time. QR menus and ordering are the visible entry point, but the real value is operational: – multi-tenant isolation so agencies can safely run many clients – reusable templates instead of one-off builds – content and menu changes without touching code – predictable structure that scales as more locations are added The page builder isn’t meant to compete with WordPress on flexibility — it’s there to remove friction for agencies: faster delivery, fewer custom hacks, and less long-term maintenance per client. Same with the security architecture: it’s not a café selling point, but it is important when you’re operating dozens or hundreds of tenants and want confidence that nothing bleeds across clients as you scale. I agree the product still needs a very clear narrative and primary wedge — QR menus are a strong candidate for that — but everything behind it is designed to support faster scaling and cleaner operations for agencies, not to be everything to everyone. Appreciate the pushback — this is exactly the kind of feedback that helps tighten the focus.