How Noah Glass Conceived Olo

A handheld computer, a coffee queue and restaurant experience shaped the idea.

NGNoah Glass게스트 · Olo
채널
20VC with Harry Stebbings
게시일
2022년 11월 13일
영상
2:22
읽기
1분
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

Olo founder Noah Glass recalls combining early mobile technology with restaurant experience, and describes the decision to commit to the business with investor David Frankel’s support.

  1. 1Mobile as commerceA handheld device suggested an opportunity beyond communication.
  2. 2An everyday problemLong coffee queues suggested ordering ahead.
  3. 3A commitmentFrankel’s offer required Glass to commit to the company.

핵심 정리

  1. A Palm Pilot helped Glass imagine mobile commerce.
  2. A busy coffee shop suggested the value of ordering ahead.
  3. Restaurant work highlighted operational problems.
  4. Investor backing came with a commitment to pursue the idea.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

The idea and the commitment

Glass describes the experiences that led him to start Olo.

Noah Glass recalls using a Palm Pilot in 2003 and an app for nearby restaurants. It led him to imagine mobile devices as tools for commerce, not just communication and content.

A crowded coffee shop in his building suggested another problem: ordering and paying ahead could make a drink ready on arrival and help customers skip the line.

His experience as a teenage pizza delivery driver also showed him operational inefficiencies in restaurants. He hoped advance orders could help restaurants handle more demand.

Glass wrote a business plan in 2003. After moving to Johannesburg, he worked for Endeavor and met investor David Frankel and mobile software developers.

Frankel offered backing if Glass would leave his job and give up his planned place at Harvard Business School. Glass says accepting made Olo his sole path forward.

같은 채널의 다른 글

1:00:17EN
20VC with Harry Stebbings· 2026년 10월 29일팟캐스트 · 3명Harry Stebbings, Jason Lemkin and Rory O’Driscoll on AI financing and venture bets게스트 Jason Lemkin, Rory O’Driscoll · 진행자 Harry StebbingsThe investors debate AI lab economics, spending on infrastructure, open-model risks and how to evaluate fast-moving private investments.Venture CapitalAI cost & performance엔터프라이즈 AI+2
23:48EN
20VC with Harry Stebbings· 2026년 10월 26일팟캐스트 · 2명Satya Nadella on Zero Trust for AI and Why Every Company Should Own Its Intelligence게스트 Satya Nadella · 진행자 Harry StebbingsThe Microsoft CEO argues that capable agents need security boundaries even as alignment research remains unsettled, and explains why firms should retain the value created by their own AI use.엔터프라이즈 AIAI security평가(Evals)+2
1:13:26EN
20VC with Harry Stebbings· 2026년 10월 24일팟캐스트 · 2명Naveen Rao on Energy, AI Hardware, Verification and the Future of Robotics게스트 Naveen Rao · 진행자 Harry StebbingsThe Unconventional AI founder argues that energy efficiency will shape AI hardware, while the growing volume of model output makes verification more valuable.EnergySemiconductorsInference+2
59:41EN
20VC with Harry Stebbings· 2026년 10월 22일팟캐스트 · 3명20VC: Venture Fund Size, AI Valuations and the Changing Software Market게스트 Jason Lemkin, Rory O’Driscoll · 진행자 Harry StebbingsHarry Stebbings, Jason Lemkin and Rory O'Driscoll debate venture concentration, infrastructure risk, code review and the assumptions behind fast-growing AI companies.Venture CapitalInvestingAI cost & performance+2
1:19:50EN
20VC with Harry Stebbings· 2026년 10월 19일팟캐스트 · 2명Sameer Dholakia on AI Investing, Bessemer's Growth Strategy and Company Culture게스트 Sameer Dholakia · 진행자 Harry StebbingsThe Bessemer partner explains his approach to pricing fast-growing AI companies, backing founders and building teams, while discussing the risks behind his optimistic forecasts.Venture CapitalAI StrategyLeadership+2
1:03:05EN
20VC with Harry Stebbings· 2026년 10월 17일팟캐스트 · 2명Harrison Chase on Building Reliable Agents, Model Routing and Memory게스트 Harrison Chase · 진행자 Harry StebbingsThe LangChain co-founder explains why agents remain difficult to control, where domain expertise matters, and how his team manages coding-agent costs.AI agentsAgent orchestration평가(Evals)+2