MinutesLink logo

How to vibe codeMinutesLink

AI Meeting Assistant for Zoom & Google Meet

minuteslink.com

Productivity

Web appBrowser extension
62/ 100
Solid side project

The verdict: can you vibe code MinutesLink?

Build a personal subset with Next.js, Turso, and OpenAI Whisper, but keep paying if you expect headless bots to reliably bypass Zoom and Google Meet bot detection.

Building a personal meeting note-taker that processes uploaded audio files or browser-recorded chunks is a straightforward weekend build. However, replicating MinutesLink's core promise—having an automated bot silently join live Zoom and Google Meet calls via calendar webhooks—involves painful engineering around bot detection, headless browser stability, and WebRTC media streaming. If you scope the personal clone to audio file upload and manual recording via a lightweight Chrome extension, it's a solid side project. Trying to build the autonomous joining bot will drain weeks into fighting platform rate-limits and CAPTCHAs.

Estimated effort: 2-4 weeks part-time

What you can't replicate

  • Proprietary meeting bot infrastructure that bypasses platform anti-bot protections
  • Native enterprise CRM integrations and verified OAuth apps

Founded

2024

Raised

Team

Micro-SaaS

Cheapest paid tier

$0

What MinutesLink does

An AI-powered meeting assistant and note-taking SaaS designed to record, transcribe, summarize, and archive online video calls.

Core features

  • Calendar integration (Google Calendar sync)
  • Automated meeting bots to join Zoom and Google Meet
  • Chrome extension for direct browser audio recording
  • Speech-to-text transcription with speaker diarization
  • AI-generated summaries, key decisions, and action items extraction
  • Searchable meeting archive and history
  • Chat with meeting context (RAG over past transcripts)
  • CRM integrations (HubSpot, Salesforce)

The business

Pricing

  • Basic$0
  • Pro$9 / month
  • Business$24 / month

Funding

Unknown / bootstrapped

Pay vs build, cumulative

Break-even at month 3 — after that, every month is money kept.

The hard parts of vibe coding MinutesLink

  • Bot infrastructure and concurrency: orchestrating headless browsers (Playwright/Puppeteer) or media bots that reliably join WebRTC calls without getting blocked or banned
  • Audio capture pipeline: handling live audio streams from virtual meeting platforms, audio chunking, codec conversion, and feeding Whisper/Deepgram cleanly
  • Speaker diarization: correctly attributing utterances to specific speakers across multiple callers in real time or post-processing
  • Calendar webhook sync: maintaining live polling or webhook integrations with Google/Outlook calendars to deploy bots automatically at exact meeting start times

How to vibecode MinutesLink

Prerequisites

  • Node.jsfree

    Required runtime for Next.js development and backend scripts.

  • GitHubfree

    Code repository and deployment source for Vercel.

  • OpenAI API Accountpay-as-you-go

    Provides Whisper for speech-to-text transcription and GPT-4o for meeting summarization.

AI coding tools

Recommended stack

FrontendNext.js with Tailwind CSS and shadcn/ui
BackendNext.js App Router API Routes
DatabaseTurso (libSQL)
Authbetter-auth
PaymentsNone (personal clone)
OtherOpenAI API (Whisper STT & GPT summaries), Vercel AI SDK

Hosting & infrastructure

VercelHosting the Next.js frontend and serverless API functions.$0/mo (Hobby Tier)
TursoServerless SQLite database for storing transcripts, notes, and user records.$0/mo (Free Tier)

Build guide

  1. 01Project Scaffolding and Database Schema

    Initialize the Next.js application, configure Tailwind CSS and shadcn/ui, and set up the Turso database schema for users, meetings, transcripts, and action items.

    Create a new Next.js 16 project using TypeScript and App Router. Install Tailwind CSS and set up Turso (libSQL) using Drizzle ORM. Write the database schema for users, meetings (id, title, date, duration, status), transcripts (meeting_id, speaker, text, timestamp), and action_items (meeting_id, task, assignee, completed). Configure environment variables for Turso connection string and ensure clean modular directory structures.
  2. 02Authentication with better-auth

    Implement local email/password and Google OAuth authentication using better-auth integrated with the Turso database.

    Set up better-auth in the Next.js app connected to the Turso database. Configure email/password authentication and Google OAuth provider. Create login and registration pages with shadcn/ui components, protect dashboard routes with middleware, and verify user sessions correctly on server components.
  3. 03Dashboard and Meeting Archive UI

    Build the main user dashboard to display past meetings, searchable transcripts, structured summaries, and extracted action items.

    Build a responsive dashboard layout with a sidebar navigation and main content area. Create a meeting list view with search and filter capabilities. Implement a detailed meeting view page displaying collapsible speaker-labeled transcripts, a structured AI summary card with bullet points, and an interactive checklist for action items where users can check off tasks.
  4. 04Audio Upload and OpenAI Whisper Pipeline

    Implement audio file upload handling and integrate OpenAI Whisper API to transcribe meeting recordings into speaker-labeled text.

    Implement an audio upload endpoint supporting MP3, WAV, and M4A files up to 100MB. Write a background processing job using the OpenAI Whisper API to transcribe the audio file. Ensure timestamps and segment data are captured and stored cleanly in the Turso database associated with the meeting record.
  5. 05AI Summarization and Action Item Extraction

    Use the Vercel AI SDK and OpenAI to parse raw transcripts into structured meeting notes, key decisions, and actionable task items.

    Write an AI processing service using the Vercel AI SDK and GPT-4o. When a transcript is finalized, send the text to the LLM with a structured prompt instructing it to output a JSON object containing: an executive summary, key discussion topics, decisions made, and a list of action items with assignees. Save the parsed results directly to the meeting and action_items tables.
  6. 06RAG Chat with Past Meetings

    Add a conversational 'Chat with Meetings' feature allowing users to query past transcripts and retrieve contextual answers.

    Create a chat interface component on the meeting detail page. Implement a backend API route using Vercel AI SDK's streamText that performs semantic search over the meeting's transcript segments stored in Turso, passes relevant context to OpenAI, and streams conversational answers back to the user interface.

Cost vs paying for MinutesLink

What will you build it with?

Est. 4.5M in / 1.2M out tokens· Includes access to introductory usage of the default model with dynamic rate limits.$0

Starting total with Claude Code$0 one-time

Starting costs (one-time)

  • Domain name (optional)$12 one-time

Total~$12 one-time

Ongoing costs (monthly)

  • OpenAI Whisper & GPT API usage (personal volume)~$3-5/mo

Total~$4/mo

Paying for MinutesLink

$9/mo (Pro plan)

Your time to build

25-35 hours

AI tool credits

$20 (Claude Code / Cursor Pro)

Break-even

Never (built for personal learning)

Vibe code MinutesLink: FAQ

Can you vibe code MinutesLink yourself?
Solid side project — 62/100 vibecodeable. Build a personal subset with Next.js, Turso, and OpenAI Whisper, but keep paying if you expect headless bots to reliably bypass Zoom and Google Meet bot detection.
How long does it take to vibe code MinutesLink?
2-4 weeks part-time — roughly 25-35 hours of hands-on time with an AI coding agent.
How do you build your own MinutesLink?
Scoped to personal use: Next.js with Tailwind CSS and shadcn/ui on the front, Next.js App Router API Routes behind it, Turso (libSQL) for data. Follow the 6-step build guide on this page — each step has a paste-ready prompt for an AI coding agent.
How do you code your own MinutesLink without being an expert?
Use an AI coding tool (Claude Code or Cursor) and work in small steps: scaffold, data model, core screens, then deploy. Realistic effort: 2-4 weeks part-time. The prompts on this page are written so the AI does the heavy lifting.
How much does it cost to vibe code MinutesLink instead of paying?
About ~$12 one-time to start and ~$4/mo to run, versus $9/mo (Pro plan) for MinutesLink. Break-even: Never (built for personal learning).
What stack should you use to vibe code MinutesLink?
Next.js with Tailwind CSS and shadcn/ui; Next.js App Router API Routes; Turso (libSQL); plus OpenAI API (Whisper STT & GPT summaries), Vercel AI SDK.

Sources

Alternatives & community builds

All alternatives →