SocialOps

💡 Inspiration

Discovering and planning social experiences is still manual and fragmented.

• Events live on Eventbrite, Meetup, and Luma
  
• Food lives on Yelp and Google Maps
  
• Calendars live somewhere else
  
• Preferences are never shared
  

Even in the era of AI agents, people still:

• Open 5+ tabs
  
• Copy-paste links into group chats
  
• Manually check calendars
  
• Miss great events
  

SocialOps lets agents handle discovery, filtering, scheduling, and coordination — while humans stay in control.

---

🧠 What It Does

SocialOps is not another events app.
It’s an orchestration layer on top of existing platforms.

• Aggregates events from Eventbrite, Meetup, and Luma
  
• Learns preferences via a lightweight profile
  
• Checks calendar availability before suggesting anything
  
• Respects taste, constraints, and availability by default
  
• Requires explicit approval before registering or booking
  
• Extends from events → food → group coordination
  

Think: personal social ops assistant, not a marketplace.

---

👥 Who It’s For

People new to a city

• Want social discovery beyond tourist spots
  
• Unsure which events are worth their time
  

Social planners & organizers

• Coordinating events, dinners, or activities
  
• Tired of back-and-forth and calendar conflicts
  

Busy professionals & builders

• Heavy calendar users
  
• Want zero-overhead, availability-aware discovery
  

Communities & micro-groups (future)

• Shared discovery for events and food
  
• Preference-aware group recommendations
  

---

🔍 Why This Is Hard

Platform limitations

• Luma, Eventbrite, and Meetup are built for organizers
  
• Personal discovery APIs are limited
  ➡️ Requires browser-based or hybrid agent skills
  

Messy data

• Inconsistent time, location, pricing, and RSVP formats
  
• Requires a canonical event schema
  

Intent matching

• Profile-driven by default, explicit input always wins
  
• Vague prompts, overfitting, and non-personalization
  ➡️ LLM reasoning, not keyword search
  

Agent orchestration

• Discovery, calendar, memory, confirmation, actions
  
• Order matters; failures must be recoverable
  

Scheduling complexity

• Free/busy windows, travel buffers, duration ambiguity
  
• Deciding if something is worth the time
  

Group preferences (future)

• Yelp + Google Maps + LLM reasoning
  
• Balancing diet, budget, distance, and behavior
  ➡️ Multi-agent preference negotiation
  

🧩 One Sentence

SocialOps exists because discovering, deciding, and scheduling social experiences is still manual — and no single platform is incentivized to solve it end-to-end.

Built With

• browseruse