Inspiration

Every office has the same problem — someone walks into a meeting room they booked days ago only to find another team already in there. Double bookings, scattered spreadsheets, and zero visibility into who has what room are universal pain points that kill productivity daily.

I wanted to build something that doesn't just digitize the problem — but eliminates it entirely using AI. That's what inspired MeetOps.


What It Does

MeetOps is an AI-powered office room booking system that gives any organization a single, intelligent platform to manage shared resources.

Key capabilities:

  • 🤖 AI Booking Assistant — Users type natural language requests like "Book me Room 11 tomorrow at 10AM for a standup with 5 people" and the assistant checks live availability, detects conflicts, and creates the booking instantly — no forms, no clicking
  • Real-time Conflict Detection — Overlapping bookings are blocked before they happen. When a conflict exists, the AI explains exactly who has the room, until when, and suggests the next available slot
  • Approval Workflow — Bookings flow through a structured state machine: Pending → Approved / Rejected → auto-archived as Completed when the meeting ends
  • 📅 Live Shared Calendar — Every booking visible to the whole team in real time, color-coded by status
  • 🌍 10 Languages Supported — Entire UI translates instantly via Google Text Translation. Arabic triggers full RTL layout
  • 👥 Role-Based Access — Admin, Manager, and User roles with permissions enforced at every level
  • 📊 Admin AI Insights — Plain English room utilization summaries generated by the LLM for Admins

How I Built It

MeetOps was built 100% using MeDo's conversational full-stack builder — zero lines of manual code were written at any point.

The build process followed an iterative, feature-by-feature conversation strategy:

  1. Foundation first — Authentication system and role-based access control (Admin, Manager, User) were described in natural language and MeDo generated the complete auth flow and permission system
  2. Core booking engine — Resource management, booking creation form, conflict detection logic, and approval workflow state machine were each built in focused individual conversations
  3. Calendar and notifications — Shared live calendar with month/week/day views and an in-app notification system scoped by role
  4. Plugin integrations — LLM plugin integrated for the AI Booking Assistant, and Google Text Translation plugin integrated for full multilingual UI support
  5. Landing page and design system — Public landing page and the neo-brutalist design system (checkerboard background, hard offset shadows, golden amber buttons) applied across all pages
  6. Bug fixing through prompts — Every bug encountered was diagnosed and fixed through precisely engineered prompts describing the root cause, expected fix, and acceptance criteria

Challenges I Ran Into

Timezone handling was the most persistent technical challenge. Because MeetOps targets Indian offices (IST, UTC+5:30), booking times created through the AI assistant were being stored as UTC timestamps — resulting in every booking appearing 5 hours and 30 minutes ahead of what the user requested. The fix required ensuring datetime values were always constructed as plain local strings (YYYY-MM-DDTHH:mm:ss) with no UTC suffix or timezone conversion at any point in the storage pipeline.

LLM data freshness was another key challenge. The AI assistant initially relied on conversation history rather than live database reads — meaning after a page refresh it couldn't recall bookings it had just created. The fix was injecting fresh database context (all rooms, all bookings, current user's history) directly into every single LLM request, making every response grounded in real-time data.

Full UI translation required replacing an initial partial implementation (that only translated the chat widget) with a complete centralized translation system covering every text element across every page — navigation, buttons, tables, badges, forms, error messages, and system notifications — all powered by real Google Text Translation API calls with per-language caching.


Accomplishments I'm Proud Of

  • Built a production-quality SaaS platform with zero manual code using only conversational prompting
  • The AI Booking Assistant that understands natural language, checks live availability, and creates bookings in one conversation turn
  • 10-language support where the entire UI — not just the chat — translates instantly including full Arabic RTL layout
  • A neo-brutalist design system that is immediately memorable and visually distinctive among hackathon submissions
  • Developing prompt engineering as a debugging methodology — every bug was fixed by precisely describing root cause, fix approach, and acceptance criteria in natural language

What I Learned

  • MeDo is most powerful when you treat each feature as its own focused conversation — not one giant prompt
  • Precise prompts with root cause analysis and acceptance criteria produce far better fixes than vague "fix this bug" instructions
  • Plugin integrations should be planned early — retrofitting them later requires more prompting effort to maintain consistency with existing features
  • The difference between a good hackathon submission and a great one is not more features — it's one feature that works perfectly and tells a clear story

What's Next for MeetOps

  • Email and SMS notifications for booking updates
  • Google Calendar and Outlook sync
  • Recurring booking support
  • Mobile native app
  • Advanced analytics dashboard for resource utilization reporting
  • Payment integration for external room rental

Built With

  • builtwithmedo
  • google-text-translation-plugin
  • llm-plugin
  • medo-full-stack-builder
  • medo-one-click-deployment
Share this project:

Updates