Project and task management decision

zcal

A competent developer can build a useful single-user scheduling replacement (booking pages + calendar sync) using existing libraries in a few weeks, but reproducing zcal's full team features, integrations, polish, and brand trust would be costly to match.

Visit website
SubscriptionCustom pricing
Initial build80 hours
Monthly upkeep8 hours + $20
Evidence3/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Create shareable booking pages that show availability, let invitees pick a slot, write the event to calendars, and send confirmations/reminders.

What it still won’t have

  • Design polish and templating breadth
  • Reliability and uptime guarantees at scale
  • Enterprise-grade team features (round robin, collective scheduling) and advanced admin tools
  • Brand reputation and trust signals
  • Breadth of prebuilt integrations and ongoing maintenance

What remains hard

  • Brand trustTrusted by leading brands, from fast-growing startups to large enterprises.
Read the build prompt

First-year cost

No published price

zcal does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal scheduling SaaS using Next.js (React) for frontend, Node/Express for backend, PostgreSQL for storage (hosted on Supabase), deploy to Vercel, and integrate Google Calendar & Microsoft OAuth for calendar sync. Core features in scope: (1) user signup/login, (2) connect one calendar account, (3) create a single customizable booking page (branding color, custom questions), (4) availability computation with buffer times and time zones, (5) booking flow that creates events on host and guest calendars and sends confirmation/reminder emails via SendGrid, (6) admin UI to view bookings. Out of scope: multi-user teams/round-robin distribution, video conferencing room creation, payments. Include robust error handling for OAuth/token refresh, calendar API failures, and email deliveries; add unit tests for availability computation and integration tests for booking flow; provide deployment scripts and a README with setup steps and env var list.
How we checked2 sources · 3/3 runs agreed · evidence score 62

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score62

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat quoted from the page