What is the primary problem Wideo aims to solve?

Wideo identifies a 'FOMO' (fear of missing out) problem based on volume. Slide 2 uses a logarithmic scale to show that while there are over 116,000 Facebook events and 15,000 Eventbrite events daily, an individual can only attend a maximum of three. The implication is that crowdsourced video coverage allows users to 'attend' or view these events virtually.

Who is the intended user for this platform?

According to Slide 3, the company targets US-based smartphone users between the ages of 13 and 34. They break this down into three segments: 13-17 (6.5 million), 18-24 (11.8 million), and 25-34 (18.1 million). Interestingly, they acknowledge that 47% of the market is 35+, but they do not appear to be targeting that demographic initially.

What was the status of the product at the time of this pitch?

The product was in pre-alpha. Slide 4 notes that the 'basic back-end' was almost complete and front-end design was in progress. The roadmap scheduled a private alpha at Stanford University for April 2012, with a full version 1.0 release not expected until late June 2012.

How does Wideo differentiate itself from competitors like Facebook or Eventbrite?

Slide 5 argues that competitors like Eventbrite, Plancast, and Facebook focus primarily on 'upcoming' events and social circles. Wideo positions itself as a way to view coverage of events as they happen or after they occur, rather than just a discovery tool for future planning.

Is there a clear path to revenue in this deck?

No. The provided slides contain no information regarding unit economics, subscription models, advertising, or any other form of monetization. The deck is entirely focused on the product build and the theoretical user base size.

Wideo Pitch Deck Teardown: A Pre-Product Roadmap

Wideo presents a solution for 'crowd-sourced event coverage,' addressing the gap between the massive number of daily events and the limited number an individual can attend. The deck is a classic early-stage artifact from 2012, relying heavily on demographic assumptions and a technical roadmap rather than traction or revenue models. It identifies a problem through a logarithmic scale chart showing 116,666 Facebook events daily versus a maximum of 3 attendable events. While it provides a clear development timeline and basic wireframes, the deck lacks a business model, team slide, or specific fu…

Key takeaways

The core problem is defined as the physical limitation of attending events, citing 116,666 Facebook events daily versus a human max of 3 (Slide 2).
The target audience is narrowly defined as US iOS and Android users aged 13-34, totaling approximately 36.4 million people (Slide 3).
The development roadmap was highly aggressive, spanning from a March 2012 MVP to a mid-August public beta web app release (Slide 4).
At the time of the pitch, the company was in the very early stages, still looking for mentors and advisors (Slide 4).
The competitive landscape analysis dismisses existing players like Clixr for having a 'clunky UI' and others for focusing only on 'upcoming' events (Slide 5).
Product visualization is limited to low-fidelity wireframes showing a feed, discovery tool, and user profile (Slide 6).
There is no mention of a business model, monetization strategy, or revenue projections in the provided slides.
The deck omits a team slide, failing to establish the founders' credibility or technical expertise beyond a single contact email (Slide 1).

Introduction: The Crowdsourced Coverage Concept

Wideo's pitch deck is a lean, 12-slide presentation (of which 6 are analyzed here) that attempts to solve the problem of event saturation. The tagline, "Crowd-sourced event coverage," suggests a platform where user-generated content provides a window into the thousands of events happening simultaneously that a single person cannot attend. The deck is dated February 22, 2012, placing it in the middle of the mobile app gold rush.

Slide 1: Title Slide

The title slide is minimalist, featuring a bright green logo that incorporates a play button icon. It identifies the company's core value proposition: "Crowd-sourced event coverage." The only personal identifier is Tony Jin, with a wideo.me email address. The lack of a larger team presence or a more descriptive subtitle immediately signals that this is a very early-stage, perhaps solo-founder, project.

Slide 2: The Problem of Scale

Slide 2 attempts to quantify the "Problem!!!" using a bar chart on a logarithmic scale. It lists the average number of events per day across various platforms:

Facebook Events: 116,666 · EventBrite Events: 15,273 · LiveNation Concerts: 57 · Stubhub Concerts: 41 · Max You Can Attend: 3

The visual argument is that there is a massive delta between available content and human capacity. However, the slide doesn't explain why a user needs to see coverage of 116,000 Facebook events. It assumes that volume equals demand for coverage, which is a significant logical leap.

Slide 3: Target Demographics

Titled "Who Will Use Wideo?", this slide uses a pie chart to segment US iOS and Android users. The founders focus on the 13-34 age bracket, which they calculate as approximately 36.4 million potential users. The breakdown is:

25-34: 26% (18.1 Million) · 18-24: 17% (11.8 Million) · 13-17: 9% (6.5 Million)

While the data provides a sense of the Total Addressable Market (TAM) for mobile users in these age groups, it fails to explain why these specific users would choose Wideo over existing social media platforms like Instagram or YouTube, which were already established by 2012.

Slide 4: The 2012 Roadmap

This slide provides a granular look at the company's development goals for Q2 and Q3 of 2012. The timeline includes:

Early March: Linking front and back end, testing, and debugging. · Late March: Completion of the MVP for iOS. · Early April: Private alpha testing on the Stanford campus. · Early June: Public beta release focused on the Bay Area. · Late June: v1.0 in the App Store. · Mid August: Public beta web app release.

Under "Current Progress," the slide admits the back-end is only "almost complete" and the founder is still "beginning look for mentors & advisors." This confirms the company is in the pre-seed/idea stage, seeking validation rather than scaling an existing product.

Slide 5: Appendix A - Competitors

The competitive analysis is presented as an appendix, which is an unusual choice as competition is usually a core concern for investors. The slide lists five competitors with brief, dismissive notes:

Sharypic: Noted as being European. · Clixr: Criticized for a "clunky UI." · SwitchCam: Noted for a narrow focus on concerts. · Eventbrite/Plancast: Dismissed for focusing only on "upcoming" events. · Facebook: Dismissed for focusing on "upcoming & your friends."

The analysis is superficial. It doesn't address the massive network effects of Facebook or the technical hurdles of competing with established video platforms.

Slide 6: Appendix C - Current Mockups

The final slide in this set shows low-fidelity wireframes of the mobile app. The mockups show three screens:

Feed: A list of events (e.g., Crunchie Awards, LED Party) with indicators for how many people are interested and the time since the last update. · Discover: A toggle between "Events Near You" and "Trending Events," showing locations like Stanford, CA. · Profile: A standard user settings page for "tony," including location services toggles.

The mockups are functional but do not showcase any unique "killer feature" that would distinguish Wideo from a standard social feed.

What Wideo Does Well

The deck is very clear about its timeline. By providing specific months and even parts of months (Early March vs. Late March), the founder sets a clear benchmark for accountability. If an investor were to follow up in May, they would know exactly where the product should be (Private Alpha at Stanford). The use of a specific geographic testing ground (Stanford/Bay Area) is also a smart way to demonstrate a focused go-to-market strategy, rather than trying to launch globally on day one.

What is Missing from the Deck

The omissions in this deck are significant, even for a 2012 pre-seed pitch:

The Team: There is no mention of who is building this. Is Tony Jin a developer, a designer, or a business lead? Does he have a technical co-founder? Investors bet on people at this stage, and the people are invisible here. · Business Model: There is zero mention of how Wideo intends to make money. Will they take a cut of ticket sales? Will there be ads? Will they sell the data? · The "Why Now": In 2012, mobile video was difficult due to bandwidth constraints (3G was still prevalent). The deck doesn't explain how they will handle the technical cost of hosting and streaming crowdsourced video. · The Ask: The deck never specifies how much money is being raised or what that capital will be used for.

Founder Takeaways: What to Copy and What to Avoid

Copy the focused roadmap. Showing a month-by-month plan for the next two quarters gives investors confidence that you have thought through the logistics of product development. It moves the conversation from "what if" to "when."

Avoid the "Logarithmic Problem" trap. Slide 2 is a classic example of a founder finding a large number and assuming it represents a problem. Just because there are 116,000 events doesn't mean there is a market for a 116,001st app to watch them. You must prove that people want to watch these events, not just that the events exist.

Don't hide your competition in the appendix. If you have competitors, address them head-on in the main body of the deck. Dismissing them for having a "clunky UI" is a weak argument; UIs can be redesigned. You need to identify a structural or functional advantage that a competitor cannot easily replicate.

Include your team. Especially in the early stages, your resume is your most valuable asset. Omitting a team slide is perhaps the biggest mistake a founder can make in a pitch deck.

Frequently asked questions

What is the primary problem Wideo aims to solve?: Wideo identifies a 'FOMO' (fear of missing out) problem based on volume. Slide 2 uses a logarithmic scale to show that while there are over 116,000 Facebook events and 15,000 Eventbrite events daily, an individual can only attend a maximum of three. The implication is that crowdsourced video coverage allows users to 'attend' or view these events virtually.
Who is the intended user for this platform?: According to Slide 3, the company targets US-based smartphone users between the ages of 13 and 34. They break this down into three segments: 13-17 (6.5 million), 18-24 (11.8 million), and 25-34 (18.1 million). Interestingly, they acknowledge that 47% of the market is 35+, but they do not appear to be targeting that demographic initially.
What was the status of the product at the time of this pitch?: The product was in pre-alpha. Slide 4 notes that the 'basic back-end' was almost complete and front-end design was in progress. The roadmap scheduled a private alpha at Stanford University for April 2012, with a full version 1.0 release not expected until late June 2012.
How does Wideo differentiate itself from competitors like Facebook or Eventbrite?: Slide 5 argues that competitors like Eventbrite, Plancast, and Facebook focus primarily on 'upcoming' events and social circles. Wideo positions itself as a way to view coverage of events as they happen or after they occur, rather than just a discovery tool for future planning.
Is there a clear path to revenue in this deck?: No. The provided slides contain no information regarding unit economics, subscription models, advertising, or any other form of monetization. The deck is entirely focused on the product build and the theoretical user base size.