TL;DR — Quick Answer
I built Menujo after spending two years watching local restaurant owners in Amman, Jordan, struggle with the same set of problems: reprint costs of $1,400-6,000/year for menu cards that went stale within weeks, QR menu platforms charging $50-200/month for features most restaurants don't use, and tablet menu setups that broke, got stolen, and required charging routines staff hated. The existing options were either overpriced or under-built. I'm a software engineer; I built the thing I'd want my favorite restaurant to use. The free plan is genuinely free forever; the $7/month plan has no commission, no per-order fee, no cap on scans. Menujo is my answer to a market that's been overcomplicating digital menus for too long.
How This Started
It's 2023. I'm sitting in a café in Amman called Jonas, run by a friend, watching the manager apologize to a Spanish tourist who can't read the printed Arabic menu. The tourist orders coffee, gives up on food, leaves. The manager sighs and says this happens five times a day.
I ask why he doesn't use a digital menu with auto-translation. He shows me his quote from MenuTiger: $46/month for the tier that includes 50+ languages. Annual cost: $552. For a small café doing maybe 100 covers/day. Plus there's GloriaFood, FineDine, Toast — each more expensive than the last, each shipped with features the café will never use (online ordering, kitchen display, multi-location franchise tooling).
The closest cheap option is Menubly at $9.99/month, but the café tested it and found the menu UI was generic, the dietary tags were limited, and the URL was stuck on menubly.com (no custom domain). The free plan from QR Tiger is QR-only — you still need to host the menu somewhere.
So the manager prints another stack of paper menus. $300 every six weeks. $2,600/year. Plus he's back to the same problem: when he changes the price of a coffee, the printed menu lies until the next reprint.
I went home that night and started building.
The Problems I Wanted to Solve
After conversations with 30+ restaurant owners across Amman, Dubai, and remote operators in the US and Europe, four problems kept coming up:
1. Reprint costs are ruinous for small operators
The math is brutal. A 50-table casual restaurant prints menus quarterly at ~$300-500/run. That's $1,200-2,000/year. Add specials cards, drink lists, kid menus — easily $3,000-6,000/year on paper that's out of date by week 2. Most platforms charge enough to make the savings marginal. The math has to work, otherwise the operator goes back to paper.
2. The menu UX optimized for tablets, not phones
Most platforms were built when iPad menus were the trend (2015-2019). Phone-first design was an afterthought. Menus loaded slowly on 4G, photos blurred when zoomed, dietary filters didn't work on small screens. Customer phones are the access mechanism in 2026 — not venue tablets — but the products didn't catch up.
3. Multilingual was a premium-tier feature
Tourist-zone restaurants (anywhere with international travelers — Dubai, Bali, Barcelona, Cancún) need 4-8 languages just to function. Most platforms gated this behind $40-70/month tiers. The cost of multilingual was effectively a premium for being on a tourist street, which felt backwards.
4. The free tiers were trial-grade, not actually free
"Free plan" with a 7×7 item cap (MenuTiger). Free plan with no analytics. Free plan limited to 100 orders/month. Free plan with watermarks on the menu. The market told operators "here's free!" then handed them a hostage situation. I wanted a free tier that was actually free — usable forever for an independent café or food truck without any caps that force an upgrade.
What I Actually Built
The product is intentionally small in scope. Menujo does one thing: display digital menus. It does not do online ordering, kitchen display, payments, inventory, or POS. Those features would have made the platform more comprehensive, but they'd also have required more development time, more support overhead, more pricing complexity. The opportunity I saw was the menu layer — and that's what I built.
Free plan
One menu, unlimited items, unlimited photos, unlimited scans, unlimited menu updates. Forever. No watermark, no signup-to-publish gate, no "upgrade after 14 days" nag. The free plan is the product I'd want my friend's café to use forever if they only have one menu.
Pro at $7/month
Multiple menus (lunch, dinner, drinks, brunch, weekend specials), 90-day analytics, custom themes. The pricing is intentional: roughly half the cheapest competitor, plus a 14-day free trial. I've heard from beta users that $7 is "the price of one cocktail" — easier to commit than $20+ that requires CFO approval at chains.
Business at $12/month
Custom domain, priority support, multi-location operator tooling. Targeted at small chains (3-15 locations) where the cost of fragmented menus across locations dwarfs the platform fee.
Free tools that aren't gated
QR generator, menu pricing calculator, photo optimizer, paper menu digitizer, UTM builder. All free, all browser-based, all without needing a Menujo account. The tools are how I earn trust before asking anyone to pay for the platform itself.
What I Got Wrong (And What I'm Still Iterating)
Building this in public means admitting the parts I underestimated:
I underestimated the SEO learning curve
I thought building a good product was the hard part. Three months in, I learned that getting Google to find the product is harder. Topic-cluster hubs, schema markup, internal linking, brand-vs-brand comparison pages, AI Overview optimization — all of these are non-obvious if you're a software engineer with no marketing background. I've been learning publicly, with a lot of trial and error.
I underestimated multilingual complexity
Auto-translation works for 70% of menu items. The other 30% — proper nouns, regional dish names, cultural references — needs human review. "Mansaf" should not be translated to "tray of meat"; it should stay "mansaf" with a brief description. Each language pair has its own quirks. We're iterating on this now.
I underestimated how much restaurant operators value photos
I thought a clean menu UI with crisp typography would carry the experience. Operators told me, repeatedly, that photos sell items 30-50% more than text-only. I rebuilt the photo handling pipeline (compression, lazy loading, thumbnails) twice to get it right.
I underestimated the demand for offline / cached menu access
Restaurant Wi-Fi is unreliable. Customer cell signal is spotty in basement venues, food halls, mall food courts. The menu must work even when connectivity is poor. We added aggressive caching + offline rendering — but this took 6 months longer than planned.
Why I Keep Going
Most days, the answer is mundane: build the next feature, fix the next bug, ship the next deployment. But underneath that, two things keep me going:
The conversation with operators
Every week I talk to a restaurant owner who tells me a specific story: a customer who used the multilingual feature to order their first-ever Levantine meal, a café manager who saved $1,200/year and put it toward a new espresso machine, a food truck that doubled their menu rotation speed because they no longer had to reprint cards. These are tiny stories at scale, but they compound. The platform exists in their workflows, and they remember they're using it because it works.
The honesty I can maintain
I write every comparison page on this site myself. When MenuTiger has a stronger feature than us, the comparison page says so. When Toast is the right answer for a multi-location operator, our /compare/toast-alternative says so. This editorial honesty is hard to maintain at venture-funded scale; it's easier as a founder-led product where I'm not optimizing for quarterly growth narratives. I'd rather lose a wrong-fit customer than mislead them and lose them later.
The product gets better
Three years in, the platform is dramatically better than what I shipped on day one. Faster, prettier, more features, more languages, better SEO, more trust. Each year compounds. I'm optimistic about year four.
What's Next
The roadmap as of May 2026:
- Localization: Spanish, Arabic, French, German, Turkish — multi-language menu management UI for operators in non-English markets.
- More free tools: Menu allergen checker, food cost calculator, profitability matrix calculator, QR A/B test analytics. Each tool earns trust without gating value behind a signup.
- Customer story page: Real restaurants on Menujo, with their permission, sharing how they use the product. The case studies aren't marketing fluff — they're operational decisions other restaurants can learn from.
- Statistics + research: Original surveys of restaurant operators, aggregating responses to publish "State of Digital Menus 2026" — the kind of data that earns industry citations and helps operators make better decisions.
If you're running a restaurant and reading this — I'd love to hear from you. [email protected]. The next year of the platform will be built around what operators tell us they need.
Frequently Asked Questions
Why is Menujo's free plan really free? What's the catch?
There's no catch. The free plan supports one menu with unlimited items, unlimited scans, and unlimited menu updates — usable forever. The platform earns revenue from operators who upgrade to Pro ($7/month) for multiple menus and analytics. We don't monetize the free tier through ads, data sales, or watermarks. The free plan is the product I'd want my friend's café to use without paying.
Are you a venture-backed startup or bootstrapped?
Bootstrapped. I run Jorbox LLC and self-fund operations from revenue + my own software consulting income. Bootstrapping lets me prioritize sustainable growth (real-cost-real-margin) over the venture growth narrative that pressures aggressive monetization.
Where is Menujo based?
I'm based in Amman, Jordan. The platform serves restaurants globally — most users are in the US, Turkey, Germany, and the broader Middle East. Cloudflare's edge infrastructure means the menu loads fast regardless of where customers are scanning.
How does Menujo make money if the free plan is fully featured?
Restaurants with multiple menus (lunch, dinner, drinks, weekend brunch, private events) need the Pro plan ($7/month). Restaurants with multi-location operations need Business ($12/month). Enterprise restaurants need custom plans. The free tier exists as a genuine product, not a marketing funnel.
Why don't you have online ordering / payments / POS?
Two reasons. (1) Building a payment-grade product is dramatically more complex than display-only menus — the regulatory, security, and integration overhead would have prevented the platform from being affordable. (2) The market is well-served by ordering platforms (GloriaFood, MenuTiger, Toast). I chose to be excellent at one thing rather than mediocre at five. Operators who need ordering pair Menujo with one of the ordering platforms or use their POS's built-in ordering.
Is the founder really the one writing all this content?
Yes. Every blog post, every comparison page, every founder note on this site is written by me (Ahmad Tayyem) with help from editorial review for grammar and structure. AI tools assist with research and outline drafting, but the voice, opinions, and judgment are human. The editorial policy at /editorial-policy explains the workflow in detail.
How can I support Menujo if I'm not a restaurant?
If you're a developer interested in the codebase, follow my GitHub. If you're a journalist or food blogger, I'm always available to talk about restaurant tech ([email protected]). If you know restaurant owners, sharing their menu URLs (when they choose to make them public) helps the product get discovered. The platform doesn't need fundraising or angel investment; it needs more restaurants finding it.
What if I want to use Menujo but it's missing a feature I need?
Email me directly: [email protected]. I personally read every feature request. We don't build everything — the platform stays focused on display-only menus — but we evaluate every request for fit. If we don't build it, I'll often suggest a competitor that does.
