We the Ravers

The description states:

• We The Ravers is a mobile application built with React Native and Expo.
• It uses Supabase and PostgreSQL for backend services including authentication, user profiles, event data, matching, messaging, social feeds, notifications, and media-related features.
• The app allows users to discover events, build personal artist lineups, mark attendance, find compatible companions, chat before events, share posts/photos/videos, and archive experiences.
• It includes an AI-powered event discovery workflow that checks public sources for updates and sends a daily report only when meaningful changes are found.

Inference The product is described as a mobile-first social platform focused on live music events with matching logic based on shared interests and preferences. The use of AI tools suggests an emphasis on automation and developer efficiency rather than user-facing AI features.

The description states:

• The platform helps users find people who are not only attending the same event but also match their desired experience (e.g., artists, timing, energy levels).
• It focuses on smaller, relevant connections instead of large group chats.
• The goal is to help users meet in real life and create memories together.
• The author emphasizes that the hardest part of a social product is creating the right context for meaningful interaction.

Inference Positioning appears to be centered around enhancing offline social experiences at live music events through targeted matching and community-building tools. The platform positions itself as a curated alternative to generic group chats or forums, focusing on relevance over scale.

The description states:

• The target audience includes music festival and live-event attendees.
• It specifically mentions electronic music events, club nights, and live shows.
• Users are described as those who want to attend the same event but may have different expectations about how they want to experience it.

Inference The ICP likely centers on young adults aged 18–35 attending festivals or live concerts, particularly in niche genres like electronic music. These users value both discovery and connection within a shared cultural context.

Not evidenced.

The description does not mention any pricing structure, monetization strategy, or business model. There is no indication of whether the platform charges users, sponsors events, or relies on advertising.

The description states:

• Built with React Native and Expo.
• Uses Supabase and PostgreSQL for backend infrastructure.
• Implements AI tools like ChatGPT and Codex for development tasks such as auditing, debugging, performance optimization, and feature implementation.
• Includes real-time messaging, notifications, blocking/reporting features, privacy controls, and internationalization.
• Has an automated event discovery agent that checks public sources and filters meaningful updates.

Inference The technical stack reflects a modern, scalable SaaS architecture with mobile-first delivery. The use of AI for engineering tasks indicates a focus on developer productivity and system optimization rather than user-facing AI features.

Not evidenced.

There is no mention of users, customers, revenue, ARR, or any form of traction beyond the author’s own description. No data points are provided regarding engagement, retention, or adoption.

Not evidenced.

The description does not reference competitors, market size, or competitive positioning beyond general claims about group chats and Reddit being alternatives.

• Single-founder model: The entire project is attributed to one person (Chloe Chen), raising questions about scalability, resource constraints, and long-term maintenance.
• No traction evidence: No data on users, revenue, or customer adoption exists in the description.
• Unverified claims: All statements are self-reported; there is no independent verification of product functionality or user behavior.
• AI dependency risk: Heavy reliance on AI tools like ChatGPT and Codex may pose risks if these tools change or become unavailable.
• Privacy/safety concerns: While mentioned as a core challenge, the description lacks details on how trust and safety are implemented or tested.

1. What is the actual user base? How many people have used the platform?
2. Are there any existing partnerships with event organizers or ticketing platforms?
3. Has the matching algorithm been validated through user feedback or A/B testing?
4. What are the key metrics that indicate success for this product?
5. How does the automated event discovery agent handle false positives or missing data?
6. Is there a plan to monetize the platform, and if so, what form will it take?
7. What is the timeline for scaling beyond the current single-founder model?