Cal.com
Open scheduling with routing forms and teams — Calendly-class flows without locking the repo.
Why it earns a place
Why I use it
Embed on site; keep booking rules explicit to protect focus time.
Use cases
Best for
- Keeping one operational source of truth in Cal.com
- Making a recurring process understandable enough to hand off
- Reducing scattered reminders, docs, or scheduling steps
Start small
Quick start
- 01Model the process before the workspace
Write the trigger, owner, required information, and finished state before configuring fields or views.
- 02Create the smallest shared setup
Use Cal.com for one real recurring workflow. Keep naming, ownership, and permissions explicit.
- 03Review after one full cycle
Remove fields, views, notifications, or steps nobody actually needed.
Repeatable workflows
Things I come back for
Set up a repeatable process
Turn an informal recurring job into something another person can follow.
- 1
List the trigger and desired outcome.
- 2
Create only the fields or steps required to reach it.
- 3
Run one complete real cycle and simplify what slowed it down.
Keep the system trustworthy
A productivity tool fails when everyone keeps a shadow version elsewhere.
- 1
Check owners, permissions, and stale items.
- 2
Archive duplicates and obsolete templates.
- 3
Leave one obvious place for the current state and next action.
Reference