The Googleplex is not a single building. It is a network of roughly forty buildings spread across Charleston Road, Crittenden Lane, Amphitheatre Parkway, and the new Bay View campus near the salt ponds. Inside that footprint, Google's food program runs roughly twenty-five cafeterias and microkitchens. Breakfast at 7 AM, lunch at noon, dinner at 6:30. Espresso bars, smoothie stations, vegetarian and vegan rooms, regional rotating menus (Korean barbecue on Tuesdays, Sichuan on Wednesdays, Roman pizza on Thursdays), a fish-and-grain counter, a salad-and-bowl counter. The food program reportedly serves on the order of 100,000 meals per day across all Google offices. The Mountain View campus is the densest single concentration.
For Castro Street, the cafeteria does three things to the operator math at once. First, it sets the lunch price floor at zero dollars for any engineer on campus. Second, it changes the lunch decision from a price comparison (cafeteria versus restaurant) to a context comparison (am I taking my team off-campus today, am I treating a candidate, am I avoiding the cafeteria crowd, do I want pho specifically). Third, it pulls the bulk of the daytime population into the campus footprint between 11:45 AM and 1:15 PM, leaving Castro Street's lunch hour quieter than the surrounding population would suggest.
The operator response is to give up on competing with the cafeteria on a per-ticket basis and to win on the team-outing channel instead. A Castro Street room that runs a streamlined group ordering page (pre-set menu, group order links shareable in Slack, scheduled pickup windows, corporate net-30 invoicing) captures the engineering manager's Tuesday team lunch and the recruiting team's candidate lunch and the off-site interview lunch. These tickets are larger, more predictable, and structurally direct. They do not flow through DoorDash because DoorDash does not invoice on net-30, does not produce departmental budget reports, and charges a 28 percent commission line that procurement cannot explain to the CFO.
The platform feature that matters here is a catering portal with group order links, lead-time rules, and corporate invoicing. Most Castro Street rooms have a version of this, but most have it stapled together from email plus PDF plus a third-party form. The direct ordering platform that wins the channel is the one that runs the group ordering link, the catering portal, the per-item meals tax setting, and the integration with the operator's normal POS, on a single ledger, with one set of payouts. The cafeteria sets the floor; the team-outing channel is the lever.
A second-order effect: the cafeteria is closed on weekends. Saturday lunch and Sunday lunch on the Google campus are quiet hours. Castro Street, El Camino, and the Shoreline area absorb the weekend daytime demand from the same engineers who would have eaten free on a weekday. Saturday at Cocola, Sunday brunch at Cascal, weekend afternoon ramen at Maru Ichi: the same customer who skipped the Castro Street lunch on a Wednesday is back on Saturday at 12:30 PM with two kids and an out-of-town visitor. The week's revenue rhythm follows the cafeteria's hours, inverted.