Architecture Review: Brief My Meeting

Brief My Meeting claims to be AI meeting briefs delivered to your inbox, open source. Let’s look under the hood.

🛠️ The Tech Stack

Brief My Meeting is built by the creator of Inbox Zero, and it shares a similar robust, modern web architecture designed for speed and privacy.

• Core Framework: Next.js (TypeScript) handles the frontend and API routes, deployed on Vercel for edge scalability.
• Database: PostgreSQL (likely managed via Supabase or Neon) stores user preferences and calendar sync tokens.
• AI & Logic: The “brain” is an LLM orchestration layer (likely Vercel AI SDK wrapping OpenAI GPT-4o or Anthropic Claude 3.5) that processes calendar metadata and email threads to generate summaries.
• Email Infrastructure: Resend is used for delivering the beautifully formatted HTML briefs directly to your inbox.
• Integrations: Uses OAuth for Google Calendar/Gmail and Outlook access to fetch meeting participants and context.

💰 Pricing Model

The tool operates on a Freemium model, aggressive for a B2B productivity tool.

• Free Tier: Includes a limited number of meeting briefs per week (likely 3-5), sufficient for casual users or trial runs.
• Pro Plan (~$9/month): Unlocks unlimited meeting briefs, deeper email context search (looking further back in history), and priority support.
• Open Source: Uniquely, because it is open source, developers can theoretically self-host the stack to avoid subscription fees, though this requires configuring your own LLM API keys and OAuth credentials.

⚖️ Architect’s Verdict

Brief My Meeting is a polished Wrapper, but a highly functional one that solves a specific “pre-meeting anxiety” problem better than generic assistants.

• Wrapper vs. Deep Tech: It is definitely a Wrapper. It orchestrates existing APIs (Calendar, Email, LLM) rather than introducing novel model architectures. However, the value lies in the context window management-it knows exactly what data to pull (recent emails with participants) to make the LLM useful.
• Production Viability: High. The reliance on established primitives (Next.js, Resend) makes it stable. The “Email-First” delivery mechanism is smart because it fits into existing workflows without requiring users to log into a dashboard.
• Developer Use Case: This is an excellent reference architecture for building “Headless SaaS” tools. Developers should study its open-source repo to learn how to build background workers that trigger off calendar events rather than user interaction. It also offers a privacy-first alternative for teams who want AI briefs but are banned from connecting corporate data to closed-source SaaS vendors-simply self-host it on your own AWS/Vercel account.