Skip to content

Getting Started at Beet

Building the solution to a problem 5 million (1M potential) Indian Americans face every weekend.


The Problem

Picture this: It's Thursday night. You want to find something fun to do this weekend. As an Indian American, you want events that actually speak to your culture.

What happens today? - Check Facebook for desi events (find 2) - Browse Eventbrite (mostly generic stuff) - Check WhatsApp groups (outdated info) - Visit theater websites for Bollywood movies (sold out) - Ask friends on Instagram (get 5 different answers) - Spend 30 minutes, find nothing good, give up

This is broken. Our community deserves better.


Our Solution: BEET

BEET = Bringing Everything Everywhere Together

One app that knows what the Indian diaspora actually wants:

  • Events — Cricket matches, Bollywood concerts, Garba nights, comedy shows
  • Movies — Every Bollywood, Tollywood, and regional film, all theaters
  • Dining — The best Indian restaurants with exclusive community deals
  • Culture — News, gossip, and trends from back home

The goal: Replace 10 scattered apps with one that actually gets our community.


What is Beetween?

Beetween = The space between scattered platforms

This documentation site is our team's bridge. It's where we document: - Why we're building what we're building - How we make decisions as a team - What we've learned from users and mistakes

Think of it as our collective brain - making sure everyone builds toward the same vision of solving this real problem for our community.


Ship-Fast Philosophy

We build like Elon builds rockets: - Ship from day one - Even if it's imperfect - Iterate obsessively - Every week makes it better - User feedback drives everything - We talk to users weekly - Speed beats perfect - First to market wins in our niche

Current mission: Beta launch August 1st with 100 SF Bay Area users who actually love using it.


Start Building

You already understand the problem. Pick your role and ship something TODAY:

Pick Your Role:

Start building in 60 seconds:

  1. Clone the repo and run setup (Dev Guide if you get stuck)
  2. Grab any issue labeled "good first issue"
  3. Ship a fix - however small

First day wins: - Fix a UI bug - Add error handling somewhere - Improve a function - Write a test

Context when you need it: User Auth Feature

Start designing in 60 seconds:

  1. Open our Figma (ask for access in team chat)
  2. Pick one user flow that feels clunky
  3. Mock up an improvement

First day wins: - Redesign a confusing button - Improve the signup flow - Create better error states - Sketch a mobile improvement

Context when you need it: Feature Docs

Start researching in 60 seconds:

  1. Join our next user interview (we do them weekly)
  2. Take notes on what users actually say
  3. Suggest one improvement based on feedback

First day wins: - Find one user pain point - Research one competitor weakness - Suggest one feature improvement - Write one user story

Context when you need it: Our Learnings

Just Start Building

Your first contribution doesn't need to be perfect: - Day 1: Ship something tiny - Week 1: Ship something useful - Month 1: Ship something users love

When you need context, it's all here - but don't read it all upfront. Build first, reference later.


Need Help?

  • Can't set up dev environment? Ask in team chat or check Development Guide
  • Don't know what to work on? Grab Ranga Reddy for 5 minutes
  • Need more context on anything? See reference docs below
  • Just have questions? Daily standup is at 9 AM or ping anyone anytime

Rule: Don't stay stuck for more than 30 minutes. Ask for help.


Documentation

Don't read these upfront. Consult them when you need specific info while building:


How We Work

Our mantras: - Ship daily - Always be building toward the next release - Users first - Every decision starts with "does this help our community?" - Document everything - If it's not written down, it didn't happen - Learn fast - Mistakes are fine if we learn and share the lessons - Be direct - Clear communication over being polite

Tools we use: - Daily standups for quick sync and blockers - Weekly user interviews to stay connected to the problem - This documentation as our single source of truth


Team: Building the future of Indian diaspora entertainment