The Usupport presentation, spanning 72 slides in its full version, functions more as a detailed product requirement document (PRD) than a traditional high-stakes investor pitch. The slides analyze the journey of a specific persona, 'Alexa,' a 22-year-old battling non-Hodgkin's lymphoma, to justify the need for a social networking site dedicated to health topics. While the deck provides granular detail on front-end feature prioritization (MUST, SHOULD, COULD, WONT) and stakeholder involvement across development phases, it lacks critical financial data, competitive analysis, and a clear investm…
Key takeaways
- The deck utilizes a deep-dive persona, 'Alexa,' to illustrate the emotional and informational pain points of young cancer patients (Slide 2).
- Usupport aims to provide a social networking site that allows users to talk about health-related topics and offset healthcare costs through community programs (Slide 3).
- Product mockups show a legacy mobile interface focusing on exercise class selection and location-based alerts (Slide 4, Slide 5).
- Market data claims that 80% of users utilize native apps, but only 19% use health-related apps, suggesting a growth opportunity (Slide 7).
- The presentation uses the MoSCoW method for feature prioritization, listing 'Terms of Agreement' and 'Notification Button' as 'Must' items (Slide 8).
- A stakeholder involvement matrix maps roles like Product Manager, CEO, and UX Designer across five stages from Pre-Launch to Approvals (Slide 9).
- The deck omits standard fundraising metrics such as current traction, burn rate, and a specific capital request.
- The primary value proposition is the integration of social support with accurate medical information to reduce patient anxiety (Slide 2).
Presentation Overview
The Usupport presentation is a lengthy, 72-slide document that leans heavily into product management and user experience design. Rather than a lean startup pitch, it resembles a corporate project proposal or a detailed product roadmap. The sample provided focuses on the empathetic 'why' behind the product and the technical 'how' of its execution.
Slide 1: Title Slide
The cover slide is minimalist, featuring the brand name 'USUPPORT' set against a geometric background of white, lime green, and teal. There is no tagline, date, or presenter information on this slide. It establishes a clean, medical-adjacent color palette that carries through the rest of the presentation.
Slide 2: Meet Alexa (User Persona)
This slide introduces the primary user persona, Alexa, a 22-year-old female in NYC diagnosed with non-Hodgkin's lymphoma. The slide is dense with qualitative data, including her hobbies (boxing, yoga) and her psychological state (anxious, sad, then angry). Crucially, it identifies two specific pain points: the fear of inaccurate online information and the need for emotional support to maintain mental strength. This slide serves as the emotional anchor for the entire pitch, grounding the technology in a human struggle.
Slide 3: More on Core Objectives
Usupport defines its mission through three bullet points. The first is the creation of a social networking site for health topics. The second is resource generation. The third is a more ambitious goal: offering programs to offset the cost of healthcare. This suggests a potential fintech or insurance-adjacent component to the business model that is not fully explored in the subsequent product slides.
Slide 4: Uhealth Settings (Product Mockup)
This slide shows a mobile interface using legacy iOS design patterns (the 'spinner' selection wheel). The screen asks, 'What classes do you really like?' and offers options such as Body Endurance, Strength Training, and Yoga & Pilates. This indicates that Usupport intends to integrate physical wellness and activity tracking into its social health platform.
Slide 5: Notifications and Map Integration
Continuing the product walkthrough, this slide demonstrates a push notification for an exercise class. It features a map of what appears to be Barcelona (based on the 'Passeig de Picasso' label), showing a pin for 'Prana Yoga.' The text explains that notifications will be integrated with calendar and map applications. This highlights a 'Should' feature from the later prioritization slide, focusing on local, real-world engagement rather than just digital chat.
Slide 6: The Market (Transition)
A simple transition slide titled 'THE MARKET.' In a 72-slide deck, these dividers are necessary for organization, though they provide no data on their own.
Slide 7: Usupport Native Application Market
This slide provides the only quantitative market data in the sample. A bar chart shows that 80% of users use native apps and 70% use notification features. The 'opportunity' is highlighted by the fact that only 19% of users currently use health-related apps. The deck implies that by combining high-usage features (native apps/notifications) with an underserved niche (health), Usupport can capture the remaining market share.
Slide 8: Front-End Feature Prioritization
Using the MoSCoW method, the founders list their development priorities. 'Must' features include basic navigation, terms of agreement, and a notification button. 'Should' features include map integration and an ON/OFF toggle for notifications. 'Could' features include a 'Chat Button' and a 'Loving button.' Interestingly, a 'Bookmark folder for loved items' is listed under 'WONT,' showing a clear decision to limit scope for the initial build.
Slide 9: Stakeholder Involvement
The final slide in the sample is a matrix mapping internal roles to project phases. It covers Pre-Launch, Development, Building, Launch, and Approvals. It shows that the Product Manager is the only role involved in every single phase. Investors are notably excluded from the 'Development,' 'Building,' and 'Launch' phases, appearing only at the bookends of the process for Pre-Launch and final Approvals.
What Works
Strong Persona Development: By focusing on a specific diagnosis (non-Hodgkin's lymphoma) and a specific age bracket, the founders make the problem statement feel urgent and real. · Clear Scope Management: The feature prioritization slide (Slide 8) is excellent for showing investors that the team understands the difference between 'need-to-have' and 'nice-to-have' features, which reduces perceived execution risk. · Holistic Approach: The inclusion of exercise classes and cost-offsetting programs suggests the founders are thinking about the 'patient' as a whole person, not just a set of symptoms.
What is Missing
Competitive Landscape: There is no mention of existing health communities like PatientsLikeMe or specialized Facebook groups. · Business Model: While 'offsetting costs' is mentioned, there is no explanation of how the company generates revenue. Is it a B2B play for insurers or a B2C subscription? · The Ask: The sample does not include a slide stating how much money is being raised or what the valuation expectations are. · Traction: There are no user numbers, waitlist counts, or pilot program results. The deck feels like a 'Day 0' plan rather than a 'Day 100' progress report.
Founder Takeaways
Founders should look at Slide 8 as a model for communicating product roadmaps. Many decks fail because they promise everything at once; Usupport’s use of the MoSCoW framework is a professional way to signal discipline. However, founders should avoid the 72-slide format for initial investor outreach. A deck of this length is better suited for a second or third meeting where deep-dive due diligence is required. Finally, ensure that market data (Slide 7) is clearly sourced; the percentages provided here lack a citation, which can undermine credibility during a formal pitch.
Frequently asked questions
- What is the primary problem Usupport is trying to solve?
- Usupport addresses the anxiety and misinformation associated with new medical diagnoses. According to Slide 2, patients often wonder if online information is accurate and feel a lack of emotional support. The platform aims to centralize accurate information and provide a community space to maintain 'mental strength' during treatment.
- What are the core objectives of the Usupport platform?
- As stated on Slide 3, the objectives are threefold: providing a social network for health discussions, generating more online resources for the healthcare community, and offering programs that help members offset the high costs of healthcare through mutual support.
- How does Usupport prioritize its product features?
- The deck uses a 'Must, Should, Could, Won't' framework (Slide 8). 'Must' features include a simple home page, terms of agreement, and social sharing buttons. 'Should' features include map integration and real-time buttons, while a 'Bookmark folder' is explicitly listed as a feature they 'Won't' include in the current scope.
- What market data does the deck provide to support its case?
- Slide 7 presents a bar chart titled 'Usupport Native Application Market.' It indicates that while 80% of users engage with native apps and 70% use notification features, only 19% currently use health-related apps, implying a significant gap in the market for a specialized health social tool.
- Who are the key stakeholders involved in the project?
- Slide 9 outlines a matrix of involvement. The Product Manager and Developers are involved in every stage from Pre-Launch to Launch. The CEO and CFO are involved in Pre-Launch, Development, and Approvals, while 'Investors' are specifically noted as stakeholders during the Pre-Launch and Approvals phases.
