Principle
Let customers lead product strategy once you have PMF
After PMF, expand the platform along lines your existing customers are already pulling you toward.
Toast went POS to payments to capital to online ordering/gift/loyalty to payroll/scheduling to back-office inventory, much of it customer-driven. Capital was added because customers wouldn't switch off legacy without it.
Customers lead the roadmap once you have fit; expansion pulled by demand beats expansion pushed by vision.
Principle
Use payments and embedded financial products to make the business model VC-fundable
Embed payments to make hardware/service cheap and the SMB business model fundable.
Toast made hardware and service far cheaper than legacy POS (a new restaurant could get running for under $5K vs $50K) by embedding payments, which carried the economics. Capital products followed because legacy providers had them and customers wouldn't switch without one.
Payments-as-wedge: embed the money rail to subsidize cheap software and fund growth.
Principle
A good manager's first job is to be a good coach
The number-one job of a manager is to be a coach who can do the work with the team.
Because Toast hires many people out of the restaurant industry, it must teach them what it means to work in a corporate environment and be an effective manager — and Narang insists the foundation is coaching, not box-checking.
A manager who can't coach has no credibility; coaching is the foundation everything else rests on.
Principle
Complementary, long-trusted co-founders beat any specific founding-team size
What matters in a founding team is complementarity and prior trust, not whether it's two or three people.
Narang's trio (product/GTM, innovation/technical, CTO) had known each other six or seven years; he extends the "founder" label to an early core group including an HBS intern and Steve's brother — the first key engineering hire.
Complementary skills plus prior trust matter more than founding-team size.
Principle
Go vertical and lean into complexity instead of staying horizontal
Depth on one vertical's operational complexity is a more durable moat than horizontal breadth.
Toast chose to nail every restaurant type rather than focus one narrow segment, betting the overlap plus the edge cases (e.g. powering a bar's pool tables) would compound into a defensible platform. They later carried the same "lean into complexity" thesis into retail (grocery, gas stations).
Vertical depth beats horizontal breadth — complexity is the moat, not the obstacle.
Principle
Hire a manager who has scaled before to build the systems you have never built
Bring in someone who has scaled before to install org systems founders have never built.
Toast brought in Chris (who had scaled CS at Endeca) as CEO in 2015; founders became presidents. It was the closest the company came to not working, and the outside operator's "superpower" was bringing the team together and making the mission/values real.
Hire a leader who has scaled before — they install the systems first-time founders have never built.
Principle
Frugality is a strategic capability, not just thrift
Extreme early frugality buys the runway to reach the proof points that unlock the next dollar.
Toast took no salaries, leaned into equity over cash, and stretched a $500K seed (released $100K at a time) because they didn't know if they'd ever raise more. Narang ties it to a frugal upbringing — "doing more with less is part of my DNA."
Frugality is a strategic capability: weight comp to equity, conserve cash, make the seed count.
Principle
The pivot is what survives — the original product is often just the probe
A failed first product is a probe; the durable business is the pain it reveals in customer conversations.
Nine months of no traction on the phone-checkout app led to the realization that restaurants ran on disconnected 1990s systems with no APIs. Pivoting the conversation from checkout to "how do you like your technology broadly" surfaced the platform opportunity.
The probe fails, the conversation it buys you reveals the durable business.
Principle
Prioritize usage and revenue growth over price extraction early
Optimize for usage and traction before price; cheap pricing buys the learning that compounds.
Narang argued pricing was a distraction early — usage was fundamental to learning, and traction was the purest way to recruit talent and raise capital when you have no credibility. Revenue growth is "one of the more purest ways" to punch above your weight.
Don't optimize price before you have usage — traction is the currency that buys talent and capital.
Principle
Treat momentum as oxygen — manufacture it on every axis
Momentum on any axis — revenue, hiring, engineering, funding — is the oxygen that keeps a fragile startup alive.
The host framed it and Narang agreed: companies are so fragile that constant movement is how to be anti-fragile. Momentum is a "deposit" into the people there — proof something works that gets you to the next mile marker of validation.
Momentum is oxygen — manufacture validation milestones on revenue, hiring, engineering, and funding.
Principle
Give teams guardrails and autonomy instead of approval gates
Set guardrails and grant autonomy; approval gates that approve 99.9% of cases only add latency.
Toast built approval rules to get disciplined while scaling, then found 99.9% of approvals went through anyway — front-line managers approved everything. The lesson: autonomy within guardrails preserves the speed that matters most in SMB GTM.
If your approval gate approves 99.9% of the time, it's latency, not control — use guardrails instead.