An AI-ready page on their own subdomain, generated from their site or PDF: menu, prices, hours, phone, map, structured data. They did not ask for it and do not need to.
Go-to-market
Every phase has one supply rail that needs nobody's reply, one channel, and one number that says whether it worked. Restaurants never have to do anything for the record to exist; they only have to do something to make it theirs.
| Phase | Supply | Surface | Channel | The number |
|---|---|---|---|---|
| 1 · Chains | The 200 largest chains in India from the corpus; menus from their own sites, PDFs and apps' public endpoints | menufied.com: five question pages per chain | Search for "<chain> menu", "menu prices", "breakfast menu"; AI answers through structured data and llms.txt | Chains in the top three for their own menu query |
| 2 · A city | Every restaurant site in Bengaluru the corpus knows, read by the fleet | Subsites: <restaurant>.menufied.com | Search long tail; WhatsApp to the restaurant: "your menu page is live, claim it" | Subsites indexed; claims per hundred |
| 3 · Claims | Corrections from owners by WhatsApp and the claim form | The mark, the edit pen, Pro analytics | The page itself; brandnames.in for chains that want their own name pages | Claimed share; Pro conversions |
| 4 · Data | The whole record, versioned | API, MCP, feeds, the price index | Direct conversations: answer engines, POS vendors, delivery tooling, analysts; the menuflation index as PR | Keys issued; citations sampled weekly |
| 5 · Next vertical | Bank charges or telecom plans, same method | Menuclature | Same channels | Second vertical live |
An AI-ready page on their own subdomain, generated from their site or PDF: menu, prices, hours, phone, map, structured data. They did not ask for it and do not need to.
One message with the restaurant's phone number claims the page. Corrections are a photo of the new menu; the agents update the record and the change feed the same day.
The biggest button is theirs: site, app, phone, or their delivery listing. We never sit between a customer and the till.
| Tier | Who | What | Price |
|---|---|---|---|
| Record | Every restaurant | The page, the data, the order button, the claim | Free, always |
| Pro | Claimed restaurants and chains | What people ask about your menu, priority recrawl, the mark, photo-to-menu updates | ₹499 a month, ₹4,999 a year |
| Data | Answer engines, POS, delivery tooling, analysts | API, MCP, bulk feeds, the price index, history | From ₹25,000 a month by volume; licences by contract |
| Placement | Brands | Featured in the human view of city and cuisine lists, labelled | By slot; never inside a record |
Distribution and the daily habit of the domain audience; the menuflation index is a natural weekly item.
Chains that want their own "brand + question" pages under their own names buy the naming and acquisition work there.
Menufied enters the directories month as a fighter; the scoreboard says whether the thesis holds in public.
Same rules, same engine rail: read the brand's own published data; never wait for a reply; never touch money.