Lessons from a 2-Time Unicorn Founder with 2 Billion Users
Waze co-founder Uri Levine discusses how a personal frustration with traffic became a globally adopted product, and uses Waze’s development to explain problem validation, product-market fit, simplicity, experimentation and difficult leadership decisions. The discussion is particularly relevant to operators deciding whether to keep building, start scaling, or reconsider what customers actually value. Speaker: Uri Levine | Podcast: Mahmoud Khodor | Views as of post date: > 105,000
PRODUCTSNEW
About this video
Uri Levine is an Israeli serial entrepreneur and author best known as co-founder of Waze, the crowd-sourced navigation app acquired by Google for over $1 billion, and as a two-time “unicorn” builder who also backed Moovit, sold to Intel for around $1 billion.
Don’t scale a product because customers say they like it; scale when their behaviour shows they keep coming back. Before that point, keep the organisation small, validate the problem directly, remove friction, and treat product development as a sequence of cheap experiments rather than a roadmap you feel obligated to complete.
The harder lesson is organisational: founders often recognise product and people problems early but delay acting because they are emotionally invested in previous decisions. That delay can cost more than making an imperfect decision quickly.
Full Video at the end of page
Core Insight (Plain English)
Start with a painful problem, not an impressive solution.
Find people who genuinely experience that problem. Deliver value manually before investing heavily in technology. Then watch whether customers return.
Once they return consistently, you have something worth scaling. Until then, more marketing, features and headcount can simply make an unresolved product problem bigger.
7 Practical Lessons
Validate before you build. Speak to people you do not already know, and look for specific stories of frustration rather than polite agreement. For a marketplace, validate both supply and demand separately.
Deliver the service manually first. Before writing software, test whether you can actually create the promised value using simple tools such as WhatsApp. This is especially practical for Southeast Asian SMEs, where messaging-based customer interactions are already familiar. If the manual process fails, automation will not fix the underlying proposition.
Measure repeat behaviour, not compliments. Customers saying a product is “great” is weak evidence. Track cohorts and ask whether customers continue using it over a period appropriate to your business. Waze specifically examined usage three months after first use and found repeated early usage strongly correlated with longer-term retention.
Watch new customers struggle. Analytics tells you where people stop; observation and conversation can tell you why. Break the customer journey into stages and talk particularly to people who abandon each stage rather than only interviewing successful customers.
Make customers experience value before asking for unnecessary commitments. Waze discovered that requiring registration early reduced adoption, so registration was moved until users needed functionality that required it. Apply the same test to account creation, forms, app downloads and other friction: does this step help customers reach value, or mainly help your business?
Make every feature justify its complexity. The proposed test is unusually strict: add a feature only if it improves adoption, expands the addressable market or helps generate revenue. Otherwise, consider leaving it out—or removing it.
Make people decisions earlier. Thirty days after hiring, ask: “Knowing what I know today, would I hire this person?” Persistent hesitation is itself information. Delaying a necessary decision can damage the wider team and may push strong performers away.
Summary & Reflections
The problem-first principle is highly useful, but several claims should be treated as operating heuristics rather than universal rules.
Retention is an excellent signal for recurring-use products such as apps, subscriptions and marketplaces, but it cannot literally be the only meaningful measure of product-market fit across every SME. A project-based engineering firm, wedding photographer or specialist machinery supplier may have naturally infrequent repeat purchases. Operators need to define the behavioural evidence of continuing value appropriate to their own buying cycle.
Likewise, “fire after 30 days if you would not hire the person again” is deliberately forceful advice. SMEs should distinguish genuine mismatch from weak onboarding, unclear responsibilities, insufficient training or unrealistic expectations. Employment regulation and contractual obligations also matter.
The strongest underlying principle is therefore not simply move fast. It is shorten the distance between evidence and decision. Product failure, customer churn and employee mismatch become more expensive when management recognises the signal but postpones responding to it.
Regional Consideration — Southeast Asia
Manual validation can be particularly useful across fragmented Southeast Asian markets. A proposition that works in Singapore, Indonesia or Vietnam should not automatically be treated as regionally validated; customer behaviour, purchasing power, language and distribution conditions can differ substantially. This regional interpretation goes beyond the transcript, which illustrates the broader point through Waze's difficulty replicating its initial Israeli success internationally.
Who should watch the full video
Founders, SME owners, product managers and operators building new products or services will get the most value—particularly anyone currently deciding whether they have enough customer evidence to scale.
It is also useful for leaders wrestling with feature creep, weak retention or difficult hiring decisions, because the full discussion provides concrete Waze examples behind those principles.
Decision Rating
Decision Usefulness — ★★★★★
The discussion repeatedly converts broad startup advice into concrete decision tests: validate manually, observe failed users, examine retention cohorts, question feature additions and reassess hires after 30 days. These are decisions an operator can actually make.
Practical Applicability — ★★★★★
Much of the advice can be tested without substantial budgets or sophisticated infrastructure. Customer interviews, manual fulfilment, cohort analysis and watching first-time users are accessible even to relatively small businesses.
Operational Relevance — ★★★★☆
The product-development and people-management principles translate well to SMEs, particularly around focus and resource allocation. The limitation is that much of the evidence comes from technology startups and recurring-use digital products, so operators with low-frequency or project-based businesses need to adapt the specific metrics rather than copy them literally.
Until next time,
The SME Signal editorial Team
Contact
Questions? Reach out anytime.
hello@smesignal.com
© 2026. All rights reserved.