Toast: The Restaurant Operating System - [Business Breakdowns, EP.119]

Toast: The Restaurant Operating System — Deep Dive

At a Glance

Guest Will Schreiber (Co-founder & CEO of Bottle) deconstructs Toast from the perspective of a vertical software operator. Core thesis: Toast’s success stems from its extreme focus on the vertical of "restaurants with kitchens," and its true moat is not the POS software itself, but the integrated hardware-software ecosystem built around complex kitchen workflows. However, this advantage faces a structural risk as third-party integrations erode the dominance of POS.

---

1. From "Afraid to Boot Up" to "Operating System": How Toast Solved the Restaurant Industry's Most Painful Pain Point

Will Schreiber believes that the core driver of Toast's early product-market fit was not technological innovation, but the "fear" restaurant managers had of legacy POS systems.

Historical Context and Magnitude of the Pain Point

• In 2011, three MIT engineers (Steve Prudet, Amun Narang, Jonathan Grimm) initially aimed to build a mobile ordering app. Six months later, they discovered that "orders simply couldn't reach the kitchen"—legacy systems (NCR, Aloha) ran on MS-DOS command-line interfaces, and managers feared booting up the POS before dinner rush, because "one wrong command could crash the entire service."
• The founders found that when pitching mobile ordering, client appointment calls took 2-3 weeks; but when discussing POS pain points, managers would "immediately clear their schedules and talk for 1-3 hours." This made them realize that POS was the heart of the restaurant, so they pivoted to building their own POS within six months.

Mechanism Breakdown: Why Are Restaurant POS Systems So Complex?

• Multiple stakeholders: Managers (purchasers but not daily users), servers, kitchen staff, cashiers, and customers—each role has different requirements for the system.
• Extreme variability: Orders must handle combinations like "no cheese," "split checks," "gift cards," and "cash/card/mobile payments"; the kitchen needs order tickets printed in the correct sequence.
• Toast's key technology bet: In 2011-2012, they decided to build custom hardware based on the Android system rather than running an app on iPads. This allowed them to control the entire chain from terminal to kitchen display systems, while competitors were dependent on the Apple ecosystem.

Data Support

• Average monthly transaction volume per Toast merchant is approximately $100,000 (annualized over $1 million)
• Software monthly fee: $0-$170/month (the free version requires a 2-year contract with higher take rates)
• Hardware cost: handheld terminals cost several hundred dollars, complete POS terminals nearly $1,000—Toast loses money on hardware, treating it as a customer acquisition cost

---

2. Revenue Model: 82% from Payments, but Profitability Lies in SaaS

Will points out that Toast’s revenue structure “does not resemble a SaaS company”—82% comes from transaction revenue with a gross margin of only 23%, while the SaaS portion boasts a gross margin of 70%.

Transaction Revenue Breakdown (Using a $100 Transaction as an Example)

Item	Amount	Description
Total Transaction Value	$100	Customer payment
Toast Retained	$2.60-$2.70	2.6%-2.7% take rate
Bank/Card Network Fees	~$2.00-$2.10	~77% of retained amount
Toast Net Revenue	$0.50-$0.60	~50 basis points

• Key Variable: Online transactions (higher share during the pandemic) have a higher take rate, while offline transactions are only ~50 basis points
• Scale Effect: In 2023, Toast is expected to process $110 billion in total payment volume, generating approximately $3.7 billion in revenue

Revenue Structure (2023 Estimated)

Revenue Type	Share	Gross Margin
SaaS Subscriptions	13%	~70%
Transaction Revenue	82%	~23%
Hardware & Services	5%	Loss-making (customer acquisition cost)
Total	100%	~30%

Pricing Strategy: Actively Limiting the Addressable Market

• Toast’s Target Merchants: Monthly transaction volume >$43,000 (annualized >$500,000)—because the $160/month SaaS fee needs to be covered by a 30-basis-point rate advantage
• Comparison with Square: 60%+ of merchants have annual transaction volume <$125,000; Toast’s average merchant annual transaction volume >$1 million
• Will’s Assessment: Toast “actively screens” for genuine restaurants through pricing, avoiding the high support costs of serving micro-merchants

---

3. Growth Ceiling: How Many Independent Restaurants Are Left in the U.S.?

Will believes Toast's biggest risk is not competition, but "running out of firewood"—the number of serviceable independent restaurants in the U.S. may be far smaller than the market assumes.

Market Capacity Estimate

• Total number of U.S. restaurants: approximately 860,000
• Toast's current customers: 85,000 (approximately 10%)
• However, 50% of these are chains (e.g., McDonald's has tens of thousands of stores under a single brand), and the true number of SMB independent restaurants is only about 160,000
• Once a chain exceeds 15 locations, it tends to use POS systems designed for chains, such as Revel

Growth Paths and Risks

Path	Feasibility	Will's Assessment
Penetration of U.S. independent restaurants	Limited	A 10% market share "underestimates the actual penetration rate"; remaining room may be small
International expansion	Uncertain	Take rates in Europe are capped by the EU at <1%; after Toast adds 50 basis points, costs become too high; the U.S. "table-turning culture" is not universal
Upward penetration into chains	Risky	Take rates for large clients are only 10 basis points (vs. 50 basis points for SMBs), and they tend to build in-house (e.g., Crumble Cookie uses Stripe+Adyen to build its own POS)
Horizontal expansion (coffee shops, etc.)	Cautious	The needs of formats without kitchens differ, potentially losing the core advantage of the "kitchen display system"

Falsification Conditions

• Watch international expansion: Whether a profitable model can be found in European markets with low take rates
• Watch chain client retention: Whether large clients continue to choose Toast over building in-house

---

4. The Double-Edged Sword of the API Ecosystem: Stickiness vs. Erosion

Will presents a counterintuitive judgment: the easier third-party integrations become, the more likely Toast’s POS dominance will be eroded.

Current Ecosystem

• Toast integrates with DoorDash, Uber Eats, loyalty systems, etc., via APIs, allowing orders to flow directly into the kitchen from external sources
• This was once a key customer acquisition tool: customers of third-party apps would "incidentally" become Toast users

Structural Contradiction

• Toast’s objective: Make the POS an irreplaceable hub, increasing stickiness through SaaS add-ons (payroll, inventory, financing)
• DoorDash/Uber Eats’ objective: Make the POS replaceable—if order data can be easily routed into any system, restaurants can freely switch POS providers
• Will’s reasoning: If 60% of orders come from online channels, DoorDash only needs to tell restaurants, "Just send orders to the new POS," and Toast’s switching costs drop significantly

Historical Analogy

• "Microsoft’s Embrace, Extend, Extinguish": Toast currently opens APIs to attract the ecosystem but has already started building its own features (e.g., "table-side payment") that compete with third-party apps
• Will’s observation: "The more popular a third-party app is, the more likely it will be replaced by Toast’s own features"—this discourages developers from continuing to invest in the Toast ecosystem

---

Five Reusable Business Lessons

Will summarizes three principles learned from Toast, each with specific mechanisms:

1. Extreme Vertical Discipline

• Not "what product to build," but "who to build for": From day one, Toast made it clear it would "only serve restaurants with kitchens."
• Every piece of copy on toasttab.com is tailored exclusively for restaurant owners, never diluted to coffee shops, retail, etc.
• Falsification condition: Once it starts customizing features for coffee shops or retail stores, it loses the core differentiation of the "kitchen display system."

2. Counterintuitive Customer Acquisition Strategy

• Use partners for distribution: Early on, it secured a "preferred vendor" agreement with Gordon Food Service (a food distributor).
• Use APIs for acquisition: Customers of third-party loyalty apps became Toast users because those apps only integrated with Toast.
• Core insight: The pain point of restaurant managers being "afraid to turn on the system" is more effective than any sales pitch—they are willing to spend hours discussing POS issues.

3. Choosing the Hardest Path

• Abandoned the simple mobile ordering app to build its own POS ("because that is the core problem").
• Abandoned the iPad solution to build its own Android hardware ("to control both cost and experience").
• Will's reflection: "At Bottle, we also learned that choosing the easy path often only delays the real challenge."

---

Mentioned Positions

Position	Analyst View	Key Data
Toast	Bullish on vertical focus, but flags growth ceiling	2023E processing volume ~$110B, revenue $3.7B, blended gross margin ~30%
Square	Competitive comparison; Toast has already won in the restaurant vertical	60%+ of Square's merchants have annual transaction volume <$125K; Toast's average merchant >$1M/year
DoorDash/Uber Eats	Risk warning: may erode POS stickiness	The higher the share of online orders, the lower the POS switching cost
Revel	Competitive comparison; targets chains with 15+ locations	Chains with over 15 locations tend to choose Revel over Toast
Crumble Cookie	Case study: threat from in-house POS	Built full-stack POS using Stripe+Adyen; hundreds of stores require only a small engineering team

---

Judgments Worth Remembering

1. Will Schreiber believes Toast’s true product-market fit stems from "fear" rather than "convenience": Restaurant managers fear their old POS systems crashing and are willing to spend hours discussing pain points—this is more effective than any sales pitch.

2. "Toast’s 10% market share understates actual penetration": Of the 860,000 restaurants in the U.S., half are chains, leaving only about 160,000 truly serviceable independent restaurants, of which Toast already serves 85,000.

3. "The easier third-party integrations become, the more likely POS systems are to be commoditized": If DoorDash orders can be easily integrated into any system, the cost for restaurants to switch POS providers drops significantly—this is a structural risk for Toast.

4. "Toast’s revenue structure does not resemble that of a SaaS company": 82% comes from transaction revenue (23% gross margin), only 13% is pure SaaS (70% gross margin), with a blended gross margin of about 30%.

5. "Toast actively screens customers through pricing": The $160/month SaaS fee requires merchants to process over $43,000 in monthly transaction volume to offset the cost via rate discounts—this keeps them focused on "real restaurants" with annual revenue >$500,000.

6. "International expansion faces structural barriers": In Europe, interchange fees are capped by the EU at <1%, making Toast’s 50-basis-point markup too costly; additionally, Europe lacks the U.S.-style "table-turn culture."

7. "Moving upmarket to chains could be a mistake": Large clients command rates as low as 10 basis points (vs. 50 basis points for SMBs) and tend to build their own POS systems (e.g., Crumble Cookie uses Stripe+Adyen to build a full-stack solution).

8. "Toast’s API ecosystem faces a ‘Microsoft-style’ dilemma": In-house features (e.g., table-side payments) compete with third-party apps, potentially discouraging developers from further investment—this is a modern version of "embrace, extend, and extinguish."