Failed 2023

    Vogo

    Vogo's scooter rental business was devastated by COVID. Maintaining 10,000+ scooters across cities required massive capital that dried up when shared mobility demand collapsed.

    TL;DR — Failure Post-Mortem

    Vogo was a Mobility startup founded in 2016 in India. It raised $70M before collapsing in 2023 — 7 years of runway burned. IdeaProof's AI Failure Score: 50/100, driven by covid impact & asset-heavy model. The shutdown affected employees, investors, and the broader Mobility ecosystem. This case study breaks down the timeline, root causes, competitors that won, and replicable lessons for founders validating similar ideas today.

    Why did Vogo fail?

    Vogo failed in 2023 after 7 years of operation, losing $70M in raised capital. The root cause was covid impact & asset-heavy model. Key lesson: Vogo's scooter rental business was devastated by COVID. Maintaining 10,000+ scooters across cities required massive capital that dried up when shared mobility demand collapsed.

    Verifiable facts
    Sourced
    Founded → Closed

    2016 → 2023

    Funding Raised

    $70M

    Industry

    Mobility

    Country

    India

    IdeaProof AI Failure Score

    50/100
    Market Fit Risk
    40
    Burn Rate Risk
    70
    Founder Risk
    30

    What Happened: The Timeline

    🚀

    2016

    Founded as scooter rental service in Bangalore

    📈

    2019

    Ola invests; fleet grows to 10,000+ scooters

    📉

    2020

    COVID devastates shared mobility; operations halted

    💀

    2023

    Scaled back to minimal operations

    Root Causes

    Vogo was a Bangalore-based scooter rental service operating in major Indian cities. Backed by Ola and Matrix Partners, it operated 10,000+ scooters. But the asset-heavy model required constant capital for maintenance, parking, and fleet expansion. When COVID destroyed shared mobility demand, Vogo couldn't maintain its fleet. The company laid off most staff and scaled back to minimal operations.

    Causal Chain

    Derived · heuristic

    This is our reading of the causal chain — separated from the verifiable facts above. Timeline dates, funding numbers and filings are facts (see methodology); root / proximate / terminal attribution is judgement based on public evidence.

    Root cause

    A combination of demand-side, execution, and capital-market pressures that this record documents without isolating a single dominant driver.

    Contributing factors
    • COVID Impact
    • Asset-Heavy Model
    • Capital Intensity
    • Shared Mobility Decline
    • Competitor "Rapido" captured the same market: Asset-light model using driver-owned vehicles
    Terminal event

    2023: Scaled back to minimal operations

    Base rates

    External sources

    A single failure is an anecdote. These base rates give you the denominator — how common this outcome is across all startups matching Vogo's profile. Sources are third-party; we do not restate them as our own claims.

    ~90%
    all

    of startups ultimately fail — including ~10% that fail in the first year and the rest across the following decade.

    Startup Genome / CB Insights aggregate (2024)
    ~35%
    all

    of new US employer businesses survive past their 10th year (Bureau of Labor Statistics BED series).

    US Bureau of Labor Statistics — BED (2024)
    ~35%
    stage

    of Series A rounds ever graduate to Series B; the rest run out of runway or pivot without a follow-on.

    CB Insights Venture Capital Funnel (2023)

    Key Lessons Learned

    1. Asset-heavy models need pandemic reserves

    Maintaining thousands of physical vehicles requires ongoing capital regardless of demand.

    Competitors That Won

    Rapido

    Grew bike taxi and auto services profitably

    Why they won: Asset-light model using driver-owned vehicles

    Frequently Asked Questions

    Could This Failure Have Been Prevented?

    IdeaProof's AI validates market demand, competitive positioning, and business model viability in minutes — catching the exact issues that sank Vogo.

    Spotted a factual error?

    Approved corrections are published in the public changelog with attribution.