Vertical Spotlight: Restaurant SaaS

By Ryan Vanshur

Also published on the Guild Letter: Read the original issue.

Subscribe now If you’re building restaurant tech and wondering why that restaurant owner who seemed so excited about your demo never returns your calls, welcome to the vertical where 60% of restaurants fail within 3 years, owners work 80-hour weeks, and convincing someone to adopt new software requires proving it’ll literally save their business. This is the market where Toast built a $4.8B revenue business by making payments mandatory (controversial at launch, genius in hindsight). Where 85% of revenue comes from fintech, not software. Where the real innovation wasn’t building a POS system but figuring out how to embed lending, payroll, and marketing into daily restaurant operations. Market Size : $23B (2023) heading to $51B by 2033. Toast has 21.58% market share. Square, Clover, Lightspeed fighting for scraps. Fragmented enough that there’s room for specialists (quick service, fine dining, bars, cafes each have different needs). Let me explain why restaurants are brutal customers but also why embedded fintech creates 10-15x revenue multipliers that make this market irresistible. The Restaurant Landscape (Why This Is the Hardest SMB Vertical) Restaurants aren’t like other small businesses. They’re uniquely difficult customers. Challenge 1: Catastrophic Failure Rates 60% of restaurants close within 3 years. Your customers are going out of business constantly. Your 12-month churn might be 15-20% even if your software is perfect, simply because restaurants fail. This is why Toast ’s ~5% annual churn is actually impressive. Industry failure rate is 20%+. They’re retaining customers despite apocalyptic closure rates. Challenge 2: Razor-Thin Margins Restaurants operate on 3-6% net profit margins. Every expense gets scrutinized. Your $500/month software better save them $3,000/month or generate $5,000 more revenue, or they won’t buy it. You can’t sell “better insights” or “improved efficiency.” You need to show hard ROI: This software will save you 15 hours/week of labor. That’s $3,000/month saved. Now we can talk. Challenge 3: Owners Are Overworked and Skeptical Restaurant owners work 60-80 hour weeks. They’re slammed during lunch and dinner rush. They’ve been burned by software vendors who promised the world and delivered garbage. They don’t have time for 45-minute demos. They don’t read your follow-up emails. They don’t attend your webinars. You need to prove value in 10 minutes or you’ve lost them. Challenge 4: Staff Turnover Requires Simple Software Restaurant staff turns over 70-100% annually. Your software needs to be so simple that a new server can learn it in 30 minutes or it won’t get adopted. If your POS requires 2 hours of training, restaurants won’t use it. Staff will quit before they’re fully trained. The owner will hate you. Why Toast Won (Mandatory Payments + Fintech Stack) Let’s talk about Toast because they’re the definitive case study in restaurant GTM. Toast’s Controversial Decision: Mandatory Payments 2014: Toast launches with mandatory payment processing. Restaurants complain. “Why can’t I use my own processor?” Toast says: “Because we’re not stupid.” The math… Software-only model: Restaurant pays $500/month software Annual revenue: $6,000 Restaurant can switch to competitor anytime (2-week notice) Churn: 15-20% annually Toast model (software + mandatory payments): Restaurant pays $100/month software + 2.7% of sales Average Restaurant : $1.5M annual revenue Payment Commission : $40,500/year Total Revenue : $42,300/year per restaurant Switching Cost : 6-12 months (migrating payment processing is painful) Churn : 3-5% annually Mandatory payments create 7x more revenue per customer plus 4x better retention. Restaurants complained initially. Then they realized Toast’s all-in pricing was competitive with what they’d pay separately. Complaining stopped. Toast’s Fintech Expansion: Lending, Payroll, Marketing Once you process daily transactions, you can see exactly how much revenue a restaurant generates. This unlocks adjacent financial services banks won’t provide. Toast Capital (Lending): Restaurants need working capital ($10K-$100K for equipment, expansion, seasonal gaps) Banks won’t lend (restaurants are risky) Toast can (they see daily revenue through payment processing) Loan Terms : 10-20% APR, repaid via daily ACH pulls from payment revenue Default Risk : <3% (Toast controls the money flow) Toast Payroll: Restaurants spend 30-35% of revenue on labor Toast tracks employee hours through POS Toast auto-calculates payroll, withholds taxes, deposits wages Revenue : $10-15 per employee per month Lock-in : Extreme (switching payroll providers is a nightmare) Toast Marketing: AI-powered email/SMS campaigns “Your customer Sarah hasn’t visited in 30 days. Send her a 20% off coupon?” Revenue: $100-$200/month Increases customer lifetime value (restaurants make more money, stay longer) The Revenue Stack: Software: $1,200/year Payments: $40,500/year Capital: $3,000/year (interest on loans) Payroll: $2,400/year (20 employees × $10/month) Marketing: $1,500/year Total: $48,600/year per restaurant Compare to software-only ($6,000/year). That’s an 8.1x revenue multiplier. This is why Toast is worth $12B+ despite serving a vertical with catastrophic failure rates. The Three Restaurant Segments (Different Needs) Segment 1: Quick Service / Fast Casual Examples : Chipotle, Panera, Sweetgreen, local sandwich shops Needs : Speed (orders in 2 minutes), kitchen display systems, online ordering integration Archetype : Archetype 2 (SMB) + Archetype 4 (Embedded Fintech) Toast, Square, Clover dominate Segment 2: Full Service (Casual and Fine Dining) Examples : Local bistros, family restaurants, upscale dining Needs : Table management, server tips, split checks, reservations, kitchen routing Archetype : Archetype 2 (SMB) + Archetype 4 (Embedded Fintech) Toast, Lightspeed, TouchBistro compete Segment 3: Bars and Nightclubs Examples : Sports bars, cocktail lounges, nightclubs Needs : Drink-focused menu, tab management, age verification, tip pools Archetype : Archetype 2 (SMB) + Archetype 4 (Embedded Fintech) Toast, Square compete Don’t build generic “restaurant software.” Pick one segment and dominate it. Subscribe now The Restaurant GTM Playbook (How Toast Does It) Step 1: Field Sales at SMB Price Points Toast has hundreds of field sales reps. They visit restaurants in person. This is unusual for SMB software but critical for restaurants. Why Field Sales Works: Restaurant owners are too busy for Zoom calls during business hours Seeing hardware in person matters (tablets, kitchen display systems, card readers) Trust building (restaurants are skeptical, face-to-face helps) The Economics: Field rep closes 10-15 deals/month ACV: $42K average (software + payments + fintech) Rep quota: $500K-$1M annually Cost per rep: $100K-$150K (salary + benefits + travel) Payback: 3-4 months Most SMB SaaS companies can’t make field sales work. Toast does because fintech revenue justifies the CAC. Step 2: Hardware Subsidization Restaurants don’t want to pay $3,000 upfront for POS terminals. Toast figured this out. Toast’s Hardware Strategy: Lease hardware for $150-$200/month (0% interest) Or buy outright ($3,000+) Most restaurants lease Why This Works: Removes upfront cost barrier Increases switching costs (can’t leave until lease is paid off) Toast makes margin on hardware leasing Competitors who require upfront hardware purchases lose deals to Toast. Step 3: Fast Onboarding (Under 1 Week) Restaurant owners don’t have 3 months for implementation. They need to go live this week. Toast’s Onboarding: Day 1: Install hardware, import menu (4 hours) Day 2: Train staff on POS (2 hours) Day 3: Go live with Toast support on-site Week 1: Restaurant is processing orders, tracking sales, managing staff If onboarding takes longer than 1 week, restaurants lose patience and churn during implementation. Step 4: 24/7 Support (Non-Negotiable) Restaurants operate 7 days a week, nights and weekends. If the POS crashes during Saturday dinner rush, they lose thousands in revenue. You need 24/7 phone support with <5 minute response time for critical issues. Chat-only support doesn’t work. Restaurants will call, and if nobody answers, they’ll switch vendors. This is expensive. But critical. Step 5: Embedded Payments From Day One Don’t make payments optional. Make them part of the core offering. Show clear pricing: software + payments = total cost. Make sure it’s competitive. Restaurants that resist usually come around when they realize the all-in cost is the same or less than their current setup, and the integrated experience is seamless. The AI Opportunity in Restaurants Restaurants are ripe for AI because so much work is manual. Opportunity 1: Voice AI for Phone Orders Restaurants lose 30-40% of phone calls because staff is busy. Every missed call = lost revenue. AI voice agent answers phone, takes orders, processes payments. Never misses a call. Never gets orders wrong. Result : 0% missed calls. 20-30% revenue increase from captured orders. Market : 1 million restaurants × $2K-$5K annually = $2-5B market. Opportunity 2: Labor Optimization Restaurants constantly over-staff or under-staff. Too many servers = labor costs too high. Too few = bad service, lost revenue. AI predicts traffic based on historical data, weather, events, holidays. Suggests optimal staffing. Result : 10-15% reduction in labor costs (restaurants’ #1 expense). Opportunity 3: Dynamic Menu Pricing Static pricing (same price all day) leaves money on the table. AI can optimize pricing based on demand. Example : $12 burger at 2pm. $15 burger at 7pm Saturday (peak demand). Result : 10-15% revenue increase without additional costs. Caveat : Customers might hate this. Proceed carefully. Opportunity 4: Ingredient Ordering and Waste Reduction Restaurants waste 4-10% of food. AI predicts demand, auto-orders ingredients, minimizes waste. Result : 5-8% reduction in food costs (major margin improvement). The Metrics That Matter in Restaurant SaaS Payment adoption rate: What percentage of customers use your payment processing? Target: 80%+ if mandatory, 50%+ if optional. Gross Payment Volume (GPV) per customer: Average restaurant should process $100K-$200K monthly. Below $50K and fintech economics don’t work. Take rate: What percentage of GPV do you capture? Target: 2-3%. Toast is at 2.7%. Fintech revenue mix: What percentage of revenue is fintech vs software? Target: 70-85%. Toast is at 85%. Churn (accounting for restaurant failures): What’s your churn excluding restaurant closures? Target: 3-5% annually. Above 10% means your product or service is broken. The Mistakes That Kill Restaurant Startups Software-only model. You charge $500/month software and don’t do payments. Competitors with fintech have 10x better unit economics. You lose. Complex software that requires training. Your POS has 47 features and takes 4 hours to learn. Staff turnover is 100% annually. Nobody uses your software correctly. You get ripped out. Inadequate support. Your support is chat-only, 9-5pm weekdays. POS crashes Saturday night. Restaurant calls, nobody answers. They switch vendors Monday. Slow onboarding. You promise 2-week implementation. Takes 6 weeks. Restaurant is losing patience. They churn during onboarding. Ignoring hardware. You’re software-only, restaurants need to buy their own tablets and card readers. Your competitor provides hardware. You lose the deal. Should You Build Restaurant SaaS? Real talk: Restaurants are brutal but potentially very lucrative if you nail fintech. Build Restaurant SaaS if: You have restaurant experience (worked in restaurants, family in industry) You can build payment processing infrastructure (this is mandatory) You’re okay with field sales (restaurant owners won’t buy on Zoom) You accept high churn (restaurants fail frequently) You have $10-30M in funding (hardware, payments, field sales are capital-intensive) Don’t build Restaurant SaaS if: Pure tech background (restaurant owners won’t trust you) Can’t do embedded payments (software-only doesn’t work) Hate sales (field sales is required) Bootstrapping (too capital-intensive) Need fast payback (CAC payback is 12-18 months) The Upside: Massive TAM (1 million restaurants). High transaction volume (daily payments). Revenue multiplier (10-15x through fintech). The Downside : Customers fail at 20% annually. Thin margins mean price sensitivity. Field sales is expensive. Only build restaurant tech if you’re committed to embedded fintech and field sales. Otherwise you’ll get crushed by Toast. Next Up: Something Different. I’ve spent the last year building an AI-native GTM operating system from scratch. 14 skills. A knowledge architecture that compounds weekly. Operations playbooks. Measurement frameworks. Org design. And an integration layer that connects 6 systems without engineering. All running in production on nine figures of pipeline. I’m releasing the entire blueprint as a 6-part series: The AI-Powered GTM Stack, Built with Claude Code. Part 1 : Skills (the methodology engine) Part 2 : Context OS (the knowledge architecture) Part 3 : Operations (the execution layer) Part 4 : Measurement (proving it works) Part 5 : The AI-Native Org (redesigning the team) Part 6 : MCP Integrations (connecting everything) All six parts drop at once. No drip. No waitlist. The full system from foundation to production, with steal-this artifacts in every part and a free starter kit on GitHub . This is the series I wish existed when I started building. Subscribe so you don’t miss it. Building restaurant tech or tried and failed? Reply with your experience. These stories help others avoid expensive mistakes. Ryan Thanks for reading! Subscribe for free to receive new posts and support my work.