Toast: Aman Narang. How a Long Wait for the Dinner Check Launched a $2 Billion Business.
with Aman Narang
Executive Summary
Toast began with a payment app that diners barely used. Listening to restaurant owners revealed a more important problem: disconnected, unreliable operating systems. Building a focused replacement created demand, but growth exposed service and reliability failures. Narang’s account argues that customer understanding must be matched by operating systems, capable leadership and a team that can learn through shocks.
Key Takeaways
A failed product can reveal a better question
The team began with diners waiting for a check, but could not generate sustained app use after a launch party. Owners gave little attention to the payment pitch and much more to their broader technology problems. The useful signal was not simply low adoption; it was the repeated pain uncovered while trying to understand that failure. A pivot should follow evidence about an important problem, not a desire to rescue the original idea.
The system around a feature can determine whether it works
The payment app depended on check data inside many different restaurant systems. Narang says the founders underestimated both integration work and the range of workflows those systems supported. A better interface could not remove those dependencies. Map the data, hardware, offline needs, staff behavior and partner access a feature relies on before assuming it can scale independently.
A narrow industry focus can justify deeper product work
Toast chose restaurants and initially pursued busy locations rather than offering a generic small-business tool. Orders, kitchen timing, bars, employee schedules and payments demanded a purpose-built approach. That focus supported a differentiated product but also created a large delivery burden. Vertical depth is a choice about what to learn and support, not evidence that building every component internally is always wise.
Mission-critical software must earn the right to replace the old system
A customer may dislike incumbent software and still resist changing it. Training, hardware, downtime and a service interruption all carry risk. The first Toast installation failed within minutes, and the founders worked physically in restaurants to learn what production required. A convincing sales pitch needs a credible migration, continuity and support plan, not only a longer feature list.
Demand and a distribution partner do not make operations scalable
A food-distributor relationship helped Toast reach beyond Boston and interest grew, but hardware, outages and support were not ready. Narang says his own focus on growth left insufficient attention for the systems needed to serve it. More leads can worsen the customer experience when fulfillment and service are fragile. Track operating capacity separately from pipeline and revenue.
Leadership changes can add missing capability without erasing the founders
Narang describes Comparato joining in2015as a practical response to what the business needed, not a fight over titles. The team worked on customer experience and a shared understanding of the company. Narang later returned to the CEO role with historical context, commitment and trusted colleagues around him. The useful lesson is to match responsibilities to needs and blind spots, not assume an outsider or founder is automatically best.
Hard work matters, but timing and resilience are not fully controllable
The pandemic sharply reduced restaurant transactions and forced painful decisions. Customers’ off-premise needs shaped the next product response. At the close, Narang credits capital raised just before the crisis, enabling technology shifts, colleagues and leadership timing as well as effort. This does not make success inevitable for a diligent team. Build room for shocks while acknowledging the role of circumstances outside the company’s control.
The Conversation Breakdown
Endeca, mobile experimentation and the founding team
Narang recalls meeting Fredette at Endeca, learning through an internal business-intelligence effort and then benefiting from the move to mobile commerce. Their employer supported exploration, and the acquisition by Oracle created a moment to consider a new company. Grimm joined the founders, who still had to decide what problem to pursue.
The slow check and a payment app that did not catch on
Waiting at Firebrand Saints suggests paying from a phone. The team persuades the owner to try it, builds an app and holds a launch party. Some friends and family use it, but regular adoption fails to follow. The experience is buggy and the restaurant integration is built on systems not designed for this use.
Restaurant conversations reveal the larger platform problem
Owners spend more time discussing their point-of-sale and disconnected software than the checkout app. A restaurateur walks Narang through payments, loans, accounting, inventory, gift cards, payroll and online orders. The team chooses a restaurant-specific cloud platform and Android-based hardware while confronting a much larger problem than it first understood.
Basement work, investor rejection and the first production outage
Early support from Steve Papa funds a small team, while institutional investors question low-margin restaurants and entrenched incumbents. Working from a basement saves money. The first installation at Dwelltime fails shortly after opening, showing that real service cannot pause for startup bugs. The improvised payment anecdote is historical, not a safe procedure to copy.
Selling, serving and expanding beyond Boston
The founders pitch hundreds of owners, work on-site, train staff and improve the software with customer feedback. New restaurants can avoid some switching pain, while a Gordon Food Service partnership opens more markets. The memorable Google Voice support call illustrates direct founder involvement, but also the limits of an informal service model.
Growth outpaces operations, then COVID forces another reset
Outages, hardware returns and unhappy customers expose the gap between demand and delivery. Comparato joins as CEO and emphasizes customer experience. Years later, pandemic shutdowns sharply cut activity and the team, while restaurant needs drive off-premise tools. The account preserves the uncertainty and harm rather than turning crisis into a simple success formula.
Founder leadership, new opportunities and the role of timing
Narang describes becoming CEO in2024with a trusted leadership group. Busy restaurants, data-driven marketing, AI and geographic or retail expansion are presented as later opportunities, not checked present-day outcomes. The ending credits co-founder values, acquired experience, financing and technological timing, then returns to the original restaurant location’s successor.
Core Frameworks & Ideas
Failure-to-problem discovery
Record where the proposed solution fails, speak with the people it was meant to help, and look for recurring problems they care about more. Compare those problems with the team’s capability before choosing a pivot. Low adoption alone does not identify the right new product.
Dependency map before scale
List every system, data source, hardware component, partner, offline path and staff workflow needed for the product to work. Test the riskiest dependencies in real conditions and make their limits visible. A polished feature is not independent of its surrounding system.
Demand versus delivery readiness
Track customer interest separately from uptime, installation capacity, hardware reliability and support quality. Expand distribution only at a pace those capabilities can serve. When demand rises but service deteriorates, solve the operating bottleneck rather than treating more sales as the cure.
Capability-led founder roles
Name the company’s current problems and the founders’ blind spots. Add leaders and responsibilities that fill the gaps, agree how decisions work, and reassess as the company changes. A title is less useful than a team capable of doing the next stage’s work.
Actionable Next Steps
- ✓Ask prospective customers which part of the workflow they would most want to change, rather than only pitching your current feature.
- ✓Map the integrations, hardware, offline conditions and people required for a successful production experience, then test the weak points.
- ✓Design a migration, training and compliant continuity plan before asking a customer to replace a mission-critical system.
- ✓Review support load, installation quality and reliability alongside sales, and set an expansion pace the service team can handle.
- ✓Identify a leadership or operating capability the business lacks, then decide who can own it and how success will be checked.
Notable Quotes
“we grossly underappreciated how much these systems did.”
“we were going to go all in on restaurants.”
“these systems are mission critical”
“customer obsession and not being too competitor obsessed.”
“we had a hypothesis for what we we thought we needed to build”
“We were just concerned about trying to make the company survive.”
“There's so many breaks that went our way.”
The One Thing to Remember
Separate proof that customers want the product from proof that the company can deliver it reliably at the next scale.