[verdict][generated prompt][source: setmore.com]
Can I vibecode Setmore?
// buildable in a weekend, but real gaps stay open
The visible appointment scheduling loop is buildable, but a credible replacement needs more than the first screen. Setmore earns its keep through OAuth, calendar reliability, so expect a weekend or multi-day build and a narrower personal scope.
confidence: medium
what it is: Booking pages, staff calendars, reminders, payments, and classes
Buildability index · an editorial game
- Price 12 $/month weight: plus 2
- Time weekend to multi-day weight: plus 2
- Category appointment scheduling no weight
- Moat integrations · execution quality weight: minus 2
- Confidence medium weight: zero
- What you lose 5 items weight: minus 2
- Site setmore.com (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Build a personal appointment scheduling tool that reads one calendar, publishes availability, reserves a slot, and writes the event back.
what you need
- Google Calendar OAuth credentials
- hosted callback URL
- email provider API key in .env
Useful boundary case: the first 60 percent of Setmore is approachable, but operating the last 40 percent is the real subscription.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build a deliberately narrow personal substitute for Setmore, not a full clone.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: Build a personal appointment scheduling tool that reads one calendar, publishes availability, reserves a slot, and writes the event back.
Start from an empty folder and create the complete working project.
Make the default mode single-user and private.
Store user data locally unless the core job requires the declared self-hosted database.
Do not add analytics, telemetry, ads, or third-party accounts.
Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled and easy to delete.
Implement the smallest polished interface that completes the core loop end to end.
Include clear empty, loading, validation, success, and failure states.
Add import and export so the user is not trapped in the app.
Use accessible keyboard navigation, labels, focus states, and sensible contrast.
Validate untrusted input and never log secrets or private file contents.
Deliberately exclude these paid-product advantages: race-free booking under load; team routing and round robin; reliable reminders and timezone edge cases.
Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims.
Where an external API is optional, keep the app useful without it and explain the degraded mode.
Write focused unit tests for the data model and the most important workflow.
Add one end-to-end smoke test that proves the core loop works.
Create a README with setup, permissions, architecture, data location, backup, and limitations.
Add scripts for install, development, test, build, and a production-style local run.
Run the tests and build before finishing, then fix errors rather than merely describing them. Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- race-free booking under load
- team routing and round robin
- reliable reminders and timezone edge cases
- calendar-provider edge cases and timezone correctness
- multi-calendar conflict handling
Why people still pay
Setmore: People pay because a booking tool must never double-book them, leak private events, or send the wrong time to a client.
moat: Integrations Execution quality what a moat is
OAuth/calendar reliability
Free alternatives
Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.
Rejected (2) — and why
- Easy!Appointments (si apre in una nuova scheda) — A credible open-source scheduler, but payments and class handling are not built in.
- Picktime Free (si apre in una nuova scheda) — Staff and classes are free, but reminders and custom forms are paid.
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) — Mature open-source scheduling platform and OAuth reference.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.