The tweet and its claim about Tim Hortons; our corpus and fleet capabilities; the schema.org types; the offer.in constraints; the two names being free at Verisign on 17 September 2026.
An idea to look at before building · menufied.com + menuclature.com
Tim Hortons cannot rank for its own breakfast menu; a near-exact-match site with no kitchen does, at fifty thousand visits a month. That gap exists for every restaurant and every "brand plus information" question, because brand sites are built for the brand and not for the question. Menufied fills it from the restaurant's own site, dated, sourced, verified, and published as structured data first and a web page second. Then it hands the order back to the official channel, which is the part the copycats get wrong.
See the site Read the thesisBrands lose their own informational queries to third parties. Their menus sit in PDFs, images and ordering apps; nothing on their site answers "breakfast menu". The third parties are stale and cannot take an order.
The supply is public and needs no permission: every restaurant publishes its menu somewhere. Same premise as offer.in. Whoever structures it, dates it and cites the source becomes the record for search and for AI answers.
Three surfaces: menufied.com brand pages for chains, a subsite per restaurant on its own subdomain built from its own site, and Menuclature, the data layer with an API, llms.txt and a change feed.
The crawl corpus, the capture archive, the fleet that renders PDF and JS at scale, the agents that extract and check, and the names. Ask: register both names, approve a 90-day plan, pick the first city.
Brands do not own their own facts; whoever structures them does. Why the vacuum exists and why it is a market.
MemoOne page for a decision: what to build in 90 days, what it costs, what we are not doing.
Pitch deckFourteen slides, printable: problem, product, why us, model, GTM, competition, the ask.
Go-to-marketChains first, then cities through subsites, then claims, then the API. Channels and metrics per phase.
Competition landscapeThirteen regions, seven kinds of player, verified where possible: who holds menus, who lacks the record, where to start.
menufied.com, the siteHome and a brand page: "Tim Hortons breakfast menu" as the menu of record, with the official order button.
A restaurant subsiteanandbhavan.menufied.com built from the restaurant's own PDF menu: hours, prices, source line, claim.
The AI-first surfaceWhat every page ships for machines: JSON-LD, menu.json, menu.md, llms.txt, a change feed, an API.
MenuclatureThe data layer and the second name: dish taxonomy, the entity graph, the price index, licensing.
The tweet and its claim about Tim Hortons; our corpus and fleet capabilities; the schema.org types; the offer.in constraints; the two names being free at Verisign on 17 September 2026.
Every price, item, hour, count and revenue figure. Anand Bhavan is invented. Tim Hortons items are well known but the prices are placeholders. Market sizes on the deck are reasoned estimates marked as such.