Scheduling and meetings decision

Clockwise

A scoped replacement that offers Focus Time holds and simple scheduling links is realistic to build and self-host, but reproducing Clockwise's refined AI scheduling, enterprise features, and tuned heuristics requires more time and data than a small team likely has.

Visit website
Subscription$6.75/month
Initial build80 hours
Monthly upkeep10 hours + $0
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. All Clockwise alternatives, with the arithmetic →

What a replacement has to do

  • Sync users' calendars, compute/choose optimal free time windows, insert/update Focus Time/hold events, expose simple scheduling links that create events, store user preferences

What it still won’t have

  • Clockwise's proprietary AI and years of scheduling heuristics
  • Enterprise features and vetted security/compliance (SSO, SOC 2) provided by vendor
  • Seamless multi-calendar quality and heuristic tuning done by Clockwise
  • Migration conveniences and dedicated support promised during shutdown

What remains hard

  • Brand trustthe Clockwise team is joining Salesforce.
  • Brand trustserving some of the most impressive customers like Uber, Netflix, and Atlassian.
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

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 self-hosted Clockwise-like service using Node.js (Express), Postgres, React, and FullCalendar that: 1) implements OAuth2 login and calendar access for Google and Microsoft Graph; 2) reads free/busy and computes available slots respecting user-configured availability and meeting buffer rules; 3) creates/updates/deletes calendar events for Focus Time holds and booking via scheduling links; 4) exposes a simple public scheduling link endpoint that books a selected slot and sends a confirmation email (SMTP or SendGrid); 5) stores user preferences in Postgres and shows them in a React dashboard using FullCalendar. Out of scope: large-scale ML model training, advanced AI heuristics, enterprise SSO/SCIM, multi-tenant billing. Include error handling for API failures and token refresh, unit tests for slot-finding logic, and end-to-end tests for booking flows.
How we checked4 sources · 3/3 runs agreed · evidence score 64

How the score was reached

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

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 · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! Price not confirmed on the page - this pricing page renders its price in the browser✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page