[verdict][curated prompt][source: meetergo.com]
Can I vibecode meetergo?
// buildable in a weekend, but real gaps stay open
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.
confidence: high
what it is: EU-hosted scheduling with built-in video, CRM sync, workflows, client portals, and a wider product suite
Buildability index · an editorial game
- Price 11 $/month · per seat weight: plus 1
- Time weekend weight: plus 2
- Category appointment scheduling no weight
- Moat integrations · execution quality · compliance and regulation weight: minus 4
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site meetergo.com (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
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.
what you need
- Google Calendar OAuth credentials
- hosted app with HTTPS
- SMTP credentials
- database and backups
- timezone test cases
Submitted by the meetergo team and judged against the same rubric: the booking UI is vibe-codeable; the maintained EU-hosted operating layer around customer meetings is the product.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
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.Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- 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
Why people still pay
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.
moat: Integrations Execution quality Compliance and regulation what a moat is
integration reliability/workflow depth/EU compliance operations
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Cal.com (opens in a new tab) — open-source scheduling platform that can be self-hosted
What it costs in a year
11 $/mese 132 $/anno
Listino 11 $ al mese a persona su meetergo. L’anno è dodici mesi pieni, senza sconti annuali.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
