Toast: how a restaurant-only operating system beat Square

Executive overview

Most restaurant point-of-sale software ran on-premise, crashed mid-service, and terrified the managers who depended on it. Toast moved the POS to the cloud on Android, enabling a platform of hardware, payments, and add-on services built entirely around the complexity of restaurant operations.

Deep vertical focus — not just on payments, but on every stakeholder from host to kitchen — is what separates Toast from horizontal competitors like Square.

The core insight: owning the heart of the restaurant (the POS) creates a sticky payments business, and payments fund an expanding layer of software that makes switching progressively harder.

Origin and founding bet

• Three MIT engineers from Indeca (sold to Oracle for $1B+) initially built a mobile order-pay app — and found no traction within six months
• Pivoted to building the full POS, finding their first customer through a family connection; 20 restaurants signed in three months
• Early investors rejected the idea: restaurants are low-margin, phone-spam targets, not tech-savvy — founder Steve Papa funded them personally
• Key technical bet: built on Android, not iOS, so they could install custom firmware on proprietary hardware rather than depending on iPads

How Toast makes money

• Software (SaaS): $0–$170/month per location; 13% of total revenue; ~70% gross margins
• Hardware: sold at cost or a loss — a deliberate Keurig-model strategy to remove friction
• Payments: ~2.6–2.7% withheld on each transaction; Toast keeps ~50 basis points after interchange; ~23% gross margins; 82% of total revenue
• Blended gross margin across all three streams: just below 30%
• Target merchant: ~$100K/month in volume ($1.2M/year); intentionally priced above Square's free tier to filter for real businesses

Why restaurants chose Toast over incumbents

• Legacy on-prem systems (Aloha, NCR) ran on MS-DOS terminals, crashed during dinner service, and couldn't connect to online channels
• Restaurant managers would clear their calendar for hours to complain about their POS — a signal of intense pain that drove door-to-door sales
• Toast offered deep onboarding and migration support to lower the risk of switching to a more complex cloud system
• Every additional SaaS add-on (payroll, inventory, online ordering) reduces churn on the payments business — software stickiness protects revenue

The restaurant POS complexity moat

• Multiple stakeholders: managers, hosts, wait staff, kitchen, customers — each with distinct needs in the same transaction flow
• Order variants, split payments, gift cards, delivery integrations, kitchen display timing — the API surface area is enormous
• Competing at this level of complexity with matching hardware is extremely difficult to replicate
• Toast dominates where there is a kitchen; Square dominates where there isn't — the kitchen display system is the defining differentiator

API ecosystem and the Shopify parallel

• Toast exposes core functionality (orders, inventory, gift cards, payments) via API — partners like DoorDash, Bottle, and loyalty apps integrate directly
• Similar to Shopify's app marketplace: Toast can't build every restaurant-specific use case, so it lets partners fill the gaps
• Tension: as Toast builds more first-party features (e.g., pay-at-table), it cannibalises partner apps, discouraging future third-party development
• Distribution strategy: partnering with food distributors (e.g., Gordon Food Service) and loyalty apps to acquire customers without cold calling

Growth risks and strategic limits

• SMB restaurant TAM is smaller than headline numbers suggest: of ~860K US restaurants, only ~160K are true single-location SMBs; Toast had 85K at recording
• International expansion is early and uncertain; European processing rates (sub-1%) compress the economics that underpin Toast's US model
• Moving upmarket to enterprise is unattractive: enterprise customers yield ~10 bps vs. ~50 bps for SMBs, and large chains can build custom stacks (e.g., Crumble cookie)
• DoorDash and Uber Eats are incentivised to commoditise the POS layer — they want orders to flow to any system equally, reducing Toast's switching costs
• As cloud POS becomes table stakes, the original "scary on-prem" value prop fades; omnichannel is the new story, but competitors are closing the gap

Key lessons from the Toast story

• Vertical focus first: the founding question was "who are we building for?" not "what are we building?" — restaurant discipline held even as growth opportunities appeared elsewhere
• Distribution creativity: distribution deals with food suppliers and API partnerships replaced pure cold-calling to crack a notoriously hard SMB market
• Choose the hard path: building a full POS (and then custom Android hardware) instead of an easier app created a durable moat that a simpler product couldn't