Vibecode meetergo
track this build5 steps, step by step0%KINDA · weekend project
The public booking loop is weekend-buildable. The honest replacement, however, stops being a scheduler almost immediately: meetergo combines maintained multi-calendar sync, time-zone and conflict handling, round-robin and conditional routing, resource and multi-location booking, automated reminders, payments, video, CRM, client portals, e-signatures, invoicing, and AI across one EU-hosted system. An agent can reproduce the solo front door; replacing the operating layer behind customer meetings is an ongoing product and compliance job.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of meetergo. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # meetergo indie build ## Goal Build the smallest trustworthy replacement for the core meetergo workflow for one developer or a tiny team. ## Scope Publish a booking page, subtract calendar conflicts from configured availability, let a guest reserve a slot, create the calendar event, and send confirmation and rescheduling links. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - managed Google, Microsoft, and Apple calendar sync with conflict protection - round robin, routing forms, collective events, resource booking, and multi-location scheduling - built-in video, payments, coupons, reminders, and multi-step workflows - shared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant - EU hosting, support, integration maintenance, and compliance operations If those capabilities are essential, use Cal.com instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a personal appointment scheduler to replace meetergo's solo booking loop. Requirements: - One Node 22 + TypeScript app using Fastify, Nunjucks, Luxon, and better-sqlite3; server-rendered pages with a little vanilla JS. - A public /book/:slug page for 30- and 60-minute meeting types. Guests see the next 21 days locally, then submit name, email, and an optional note. - An /admin page behind one ADMIN_TOKEN edits weekly availability, date overrides, minimum notice, daily limits, and buffers. Store timestamps in UTC. - Google Calendar OAuth credentials stay in .env. Read busy intervals before showing slots, then recheck inside a BEGIN IMMEDIATE transaction and create the calendar event with the guest invited so two people cannot take one slot. - Send confirmation, cancellation, rescheduling, and one reminder email through SMTP. Links use signed expiring tokens; node-cron reminders are idempotent. - The admin agenda shows upcoming bookings, status, guest details, and manual cancellation, with a CSV export. Keep a nightly 14-day SQLite backup. - No public accounts or telemetry. Run as one process behind HTTPS; all OAuth, SMTP, signing, and admin secrets live in .env. - Out of scope: Microsoft and Apple sync, team routing, payments, built-in video, CRM, e-signatures, AI, and formal compliance claims. Do not stub fake versions. - Add Vitest coverage for DST changes, buffers, concurrent booking, cancellation, and reminder retries. README the Google console setup and warn that OAuth is the fiddly part, plus deployment, backup, and restore commands. ## Required capabilities - Google Calendar OAuth credentials - hosted app with HTTPS - SMTP credentials - database and backups - timezone test cases ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of meetergo. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # meetergo indie build ## Goal Build the smallest trustworthy replacement for the core meetergo workflow for one developer or a tiny team. ## Scope Publish a booking page, subtract calendar conflicts from configured availability, let a guest reserve a slot, create the calendar event, and send confirmation and rescheduling links. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - managed Google, Microsoft, and Apple calendar sync with conflict protection - round robin, routing forms, collective events, resource booking, and multi-location scheduling - built-in video, payments, coupons, reminders, and multi-step workflows - shared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant - EU hosting, support, integration maintenance, and compliance operations If those capabilities are essential, use Cal.com instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a personal appointment scheduler to replace meetergo's solo booking loop. Requirements: - One Node 22 + TypeScript app using Fastify, Nunjucks, Luxon, and better-sqlite3; server-rendered pages with a little vanilla JS. - A public /book/:slug page for 30- and 60-minute meeting types. Guests see the next 21 days locally, then submit name, email, and an optional note. - An /admin page behind one ADMIN_TOKEN edits weekly availability, date overrides, minimum notice, daily limits, and buffers. Store timestamps in UTC. - Google Calendar OAuth credentials stay in .env. Read busy intervals before showing slots, then recheck inside a BEGIN IMMEDIATE transaction and create the calendar event with the guest invited so two people cannot take one slot. - Send confirmation, cancellation, rescheduling, and one reminder email through SMTP. Links use signed expiring tokens; node-cron reminders are idempotent. - The admin agenda shows upcoming bookings, status, guest details, and manual cancellation, with a CSV export. Keep a nightly 14-day SQLite backup. - No public accounts or telemetry. Run as one process behind HTTPS; all OAuth, SMTP, signing, and admin secrets live in .env. - Out of scope: Microsoft and Apple sync, team routing, payments, built-in video, CRM, e-signatures, AI, and formal compliance claims. Do not stub fake versions. - Add Vitest coverage for DST changes, buffers, concurrent booking, cancellation, and reminder retries. README the Google console setup and warn that OAuth is the fiddly part, plus deployment, backup, and restore commands. ## Required capabilities - Google Calendar OAuth credentials - hosted app with HTTPS - SMTP credentials - database and backups - timezone test cases ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of meetergo. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # meetergo product brief ## Problem The public booking loop is weekend-buildable. The honest replacement, however, stops being a scheduler almost immediately: meetergo combines maintained multi-calendar sync, time-zone and conflict handling, round-robin and conditional routing, resource and multi-location booking, automated reminders, payments, video, CRM, client portals, e-signatures, invoicing, and AI across one EU-hosted system. An agent can reproduce the solo front door; replacing the operating layer behind customer meetings is an ongoing product and compliance job. ## Product outcome Publish a booking page, subtract calendar conflicts from configured availability, let a guest reserve a slot, create the calendar event, and send confirmation and rescheduling links. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Google Calendar OAuth credentials - hosted app with HTTPS - SMTP credentials - database and backups - timezone test cases ## Explicit non-goals for v1 - managed Google, Microsoft, and Apple calendar sync with conflict protection - round robin, routing forms, collective events, resource booking, and multi-location scheduling - built-in video, payments, coupons, reminders, and multi-step workflows - shared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant - EU hosting, support, integration maintenance, and compliance operations ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a personal appointment scheduler to replace meetergo's solo booking loop. Requirements: - One Node 22 + TypeScript app using Fastify, Nunjucks, Luxon, and better-sqlite3; server-rendered pages with a little vanilla JS. - A public /book/:slug page for 30- and 60-minute meeting types. Guests see the next 21 days locally, then submit name, email, and an optional note. - An /admin page behind one ADMIN_TOKEN edits weekly availability, date overrides, minimum notice, daily limits, and buffers. Store timestamps in UTC. - Google Calendar OAuth credentials stay in .env. Read busy intervals before showing slots, then recheck inside a BEGIN IMMEDIATE transaction and create the calendar event with the guest invited so two people cannot take one slot. - Send confirmation, cancellation, rescheduling, and one reminder email through SMTP. Links use signed expiring tokens; node-cron reminders are idempotent. - The admin agenda shows upcoming bookings, status, guest details, and manual cancellation, with a CSV export. Keep a nightly 14-day SQLite backup. - No public accounts or telemetry. Run as one process behind HTTPS; all OAuth, SMTP, signing, and admin secrets live in .env. - Out of scope: Microsoft and Apple sync, team routing, payments, built-in video, CRM, e-signatures, AI, and formal compliance claims. Do not stub fake versions. - Add Vitest coverage for DST changes, buffers, concurrent booking, cancellation, and reminder retries. README the Google console setup and warn that OAuth is the fiddly part, plus deployment, backup, and restore commands. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted meetergo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# meetergo indie build ## Goal Build the smallest trustworthy replacement for the core meetergo workflow for one developer or a tiny team. ## Scope Publish a booking page, subtract calendar conflicts from configured availability, let a guest reserve a slot, create the calendar event, and send confirmation and rescheduling links. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - managed Google, Microsoft, and Apple calendar sync with conflict protection - round robin, routing forms, collective events, resource booking, and multi-location scheduling - built-in video, payments, coupons, reminders, and multi-step workflows - shared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant - EU hosting, support, integration maintenance, and compliance operations If those capabilities are essential, use Cal.com instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a personal appointment scheduler to replace meetergo's solo booking loop. Requirements: - One Node 22 + TypeScript app using Fastify, Nunjucks, Luxon, and better-sqlite3; server-rendered pages with a little vanilla JS. - A public /book/:slug page for 30- and 60-minute meeting types. Guests see the next 21 days locally, then submit name, email, and an optional note. - An /admin page behind one ADMIN_TOKEN edits weekly availability, date overrides, minimum notice, daily limits, and buffers. Store timestamps in UTC. - Google Calendar OAuth credentials stay in .env. Read busy intervals before showing slots, then recheck inside a BEGIN IMMEDIATE transaction and create the calendar event with the guest invited so two people cannot take one slot. - Send confirmation, cancellation, rescheduling, and one reminder email through SMTP. Links use signed expiring tokens; node-cron reminders are idempotent. - The admin agenda shows upcoming bookings, status, guest details, and manual cancellation, with a CSV export. Keep a nightly 14-day SQLite backup. - No public accounts or telemetry. Run as one process behind HTTPS; all OAuth, SMTP, signing, and admin secrets live in .env. - Out of scope: Microsoft and Apple sync, team routing, payments, built-in video, CRM, e-signatures, AI, and formal compliance claims. Do not stub fake versions. - Add Vitest coverage for DST changes, buffers, concurrent booking, cancellation, and reminder retries. README the Google console setup and warn that OAuth is the fiddly part, plus deployment, backup, and restore commands. ## Required capabilities - Google Calendar OAuth credentials - hosted app with HTTPS - SMTP credentials - database and backups - timezone test cases ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# meetergo product brief ## Problem The public booking loop is weekend-buildable. The honest replacement, however, stops being a scheduler almost immediately: meetergo combines maintained multi-calendar sync, time-zone and conflict handling, round-robin and conditional routing, resource and multi-location booking, automated reminders, payments, video, CRM, client portals, e-signatures, invoicing, and AI across one EU-hosted system. An agent can reproduce the solo front door; replacing the operating layer behind customer meetings is an ongoing product and compliance job. ## Product outcome Publish a booking page, subtract calendar conflicts from configured availability, let a guest reserve a slot, create the calendar event, and send confirmation and rescheduling links. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Google Calendar OAuth credentials - hosted app with HTTPS - SMTP credentials - database and backups - timezone test cases ## Explicit non-goals for v1 - managed Google, Microsoft, and Apple calendar sync with conflict protection - round robin, routing forms, collective events, resource booking, and multi-location scheduling - built-in video, payments, coupons, reminders, and multi-step workflows - shared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant - EU hosting, support, integration maintenance, and compliance operations ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a personal appointment scheduler to replace meetergo's solo booking loop. Requirements: - One Node 22 + TypeScript app using Fastify, Nunjucks, Luxon, and better-sqlite3; server-rendered pages with a little vanilla JS. - A public /book/:slug page for 30- and 60-minute meeting types. Guests see the next 21 days locally, then submit name, email, and an optional note. - An /admin page behind one ADMIN_TOKEN edits weekly availability, date overrides, minimum notice, daily limits, and buffers. Store timestamps in UTC. - Google Calendar OAuth credentials stay in .env. Read busy intervals before showing slots, then recheck inside a BEGIN IMMEDIATE transaction and create the calendar event with the guest invited so two people cannot take one slot. - Send confirmation, cancellation, rescheduling, and one reminder email through SMTP. Links use signed expiring tokens; node-cron reminders are idempotent. - The admin agenda shows upcoming bookings, status, guest details, and manual cancellation, with a CSV export. Keep a nightly 14-day SQLite backup. - No public accounts or telemetry. Run as one process behind HTTPS; all OAuth, SMTP, signing, and admin secrets live in .env. - Out of scope: Microsoft and Apple sync, team routing, payments, built-in video, CRM, e-signatures, AI, and formal compliance claims. Do not stub fake versions. - Add Vitest coverage for DST changes, buffers, concurrent booking, cancellation, and reminder retries. README the Google console setup and warn that OAuth is the fiddly part, plus deployment, backup, and restore commands. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted meetergo capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
They pay because meetergo bundles what would otherwise be a stack of separate tools. Calendar reliability, routing, reminders, video, payments, CRM context, signed documents, and client follow-up share the same customer and meeting record, while EU hosting and ongoing integration maintenance remove operational risk. A DIY booking page can save a solo user money; a team pays to avoid rebuilding and operating the system around every customer meeting.
xmanaged Google, Microsoft, and Apple calendar sync with conflict protection
xround robin, routing forms, collective events, resource booking, and multi-location scheduling
xbuilt-in video, payments, coupons, reminders, and multi-step workflows
xshared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant
xEU hosting, support, integration maintenance, and compliance operations
share on X ↗"I just replaced meetergo ($11.44/mo) with one prompt"
meetergo pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | Unlimited users; 3 active booking types; 1 connected calendar/user; 10 CRM deals; 100 form submissions/month; 3 simple signatures, 3 invoices, and 3 client spaces; 45-minute 1:1 video. |
| light | — | $11.44/user | Unlimited booking types; 6 calendars/user; 3 workflows; 10 CRM deals; 100 form submissions/month; 3 simple signatures, 3 invoices, and 3 client spaces. |
| suite | — | $34.54/user | Unlimited CRM deals, form submissions, invoices, and client spaces; 50 advanced signatures/month. |
| premium | — | $57.65/user | WhatsApp workflows and Premium support; no single numeric WhatsApp allowance is published. |
free tierUnlimited users; 3 active booking types; 1 connected calendar/user; 10 CRM deals; 100 form submissions/month; 3 simple signatures, 3 invoices, and 3 client spaces; 45-minute 1:1 video.
billingmonthly + annual (-20% advertised); exact monthly prices were not exposed by the live static page; Suite and Premium introductory annual rates renew higher after 12 months
hidden costsOne plan applies account-wide; regular users and bookable resources consume seats; Suite/Premium renew at higher rates after year 1; WhatsApp/Meta conversation charges can be passed through.
verified 2026-08-14 · source ↗
Vibecode meetergo
Kinda. The core of meetergo is buildable in a weekend with the prompt on this page, but there are real gaps: managed Google, Microsoft, and Apple calendar sync with conflict protection, round robin, routing forms, collective events, resource booking, and multi-location scheduling. Read the honest list above before committing.
How much does meetergo cost?
meetergo costs about $11.44/month (Light, checked 2026-08-14), which is $137.28 per year.
What do I lose by replacing meetergo?
Honestly: managed Google, Microsoft, and Apple calendar sync with conflict protection; round robin, routing forms, collective events, resource booking, and multi-location scheduling; built-in video, payments, coupons, reminders, and multi-step workflows; shared CRM context, client portals, e-signatures, invoicing, meeting notes, and the built-in AI assistant; EU hosting, support, integration maintenance, and compliance operations. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to meetergo?
Yes: Cal.com (open-source scheduling platform that can be self-hosted). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.