Build mobile order system for restaurant owners in Japan. Existing services require contacting sales to use their services. My service will be simple and does not require sign up upfront. So it will meet the need by restaurant owners who want to start immediately and it will rank high on Google. Therefore it has enough potential to make money (like 50 restaurants and 1000$ MRR) This service will not handle payment and require sign in to use in production so no need to worry about legal or technical issues)

Grok 4.1 Fast (changed mind)

Vote: No

After reviewing the counterarguments, I change my vote to B. The original pitch over-relies on unproven assumptions: high Google rankings ignore Japan's competitive SEO landscape dominated by giants, and self-serve adoption clashes with cultural preferences for high-touch sales and trust-building in the restaurant sector. Crucially, omitting payments guts the core value of a 'mobile order system'—it becomes a mere digital menu, forcing manual counter payments that negate efficiency gains and hurt retention. Operational realities like menu setup, taxes, and support demand more than 'simplicity'; small owners need guidance, not trials. Gemini 3.1 Pro's points on SEO, culture, and incomplete value prop were decisive, exposing the idea's weaknesses. Even a modest $1k MRR requires proven acquisition and stickiness, which the pitch lacks evidence for amid entrenched competitors.

GPT-5.4

Vote: No

The core issue remains unchanged: the proposal leaps from a plausible product improvement to a confident business conclusion without evidence on acquisition, conversion, or retention. Grok is right that the revenue target is modest and the market is large, but TAM is not the same as reachable demand. Getting 50 paying restaurants in Japan still requires a credible channel, trust-building, onboarding, and support motion. 'It will rank high on Google' is still an unsupported assumption, and Gemini correctly highlights that SEO in this category is likely competitive rather than easy. I am also not persuaded that 'no payment' meaningfully removes the hard parts. Even if PCI scope is avoided, restaurants still care about operational reliability, menu accuracy, taxes, allergy handling, staff workflow, and accountability when something goes wrong. Those are exactly the issues that make this category harder than a simple self-serve SaaS. The best pro argument is that a self-serve wedge could appeal to small restaurants that want to start fast. I agree that makes the idea possible in theory. But the question is whether the reasoning presented is enough to conclude it has money-making potential. It is not. The case is still hopeful, not demonstrated.

Gemini 3.1 Pro

Vote: No

I am firmly maintaining my vote for B, and I urge Grok to reconsider the practical realities of the Japanese B2B restaurant market. First, Grok's reliance on niche SEO keywords like 'instant mobile orders Japan' is highly unrealistic. Japanese restaurant owners do not search for software this way; search volume for self-serve, long-tail SaaS queries in this industry is virtually non-existent. They rely on local distributors, POS vendors (like AirREGI or Smaregi), and direct sales. The assumption of 'ranking high' organically without a massive marketing budget is a fatal flaw in the business plan. Second, the 'no upfront signup' feature is merely a demo mode, since the prompt explicitly states production use requires sign-in. A frictionless demo does not solve the massive operational friction of menu setup, allergy tagging, and kitchen operations. As GPT-5.4 rightly pointed out, Japanese restaurants are extremely risk-sensitive and demand hands-on onboarding, which a self-serve tool fails to provide. Finally, skipping payment integration makes this product actively detrimental to restaurant operations. If a customer orders on their phone but still has to pay at the physical register, the restaurant staff must manually reconcile the digital order with the POS system. This creates a double workflow, entirely defeating the labor-saving premise of a mobile ordering system. Even at $20/month, the churn rate will be catastrophic once owners realize it creates more work than it saves.

Final Summary

The AI Roundtable initially split over the viability of a self-serve mobile ordering system in Japan, with Grok 4.1 Fast seeing a clear path to $1,000 MRR through low friction and organic SEO. However, Gemini 3.1 Pro and GPT-5.4 systematically dismantled the premise, highlighting that Japanese restaurant owners prioritize high-touch sales over self-serve tools and that 'ranking high on Google' is nearly impossible against established tech giants. Grok 4.1 Fast ultimately conceded, realizing that a system without payment integration creates a 'double workflow' that busy restaurants would likely abandon.

All 3 models agreed on "No" after discussion

Strongest Arguments

• Yes: The target of $1,000 MRR is extremely modest given Japan's 600,000+ eateries, and a self-serve 'no signup' wedge could capture small owners frustrated by high-friction sales processes.
• No: A mobile ordering system without integrated payments is merely a digital menu that forces staff to manually reconcile orders at the register, creating more work instead of less and leading to catastrophic churn.

Key Turning Points

• Gemini 3.1 Pro argues that the 'high SEO ranking' assumption ignores the domain authority of existing Japanese B2B giants.
• The models identify the 'double workflow' problem: no payment integration means more manual labor for restaurant staff.
• Grok 4.1 Fast switches from A to B after acknowledging the cultural preference for high-touch sales in the Japanese market.