Tally ↗
ProductivityBuild a form as naturally as writing a document.
Scheduling for individuals, teams, and embedded bookings.
Cal.com provides booking pages and scheduling infrastructure, with tools for teams and developers. The separately maintained Cal.diy community edition has a different feature scope.
Free individual access and paid team, organization, and enterprise offerings.
Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.
Cal.com's about page argues that most scheduling tools were built for individuals and break down when scheduling involves teams, workflows and several people. It describes a range from a simple booking page to multi-team operations and scheduling embedded directly inside other products. That moves the buyer from a single professional to sales, success and product teams. The page states a mission to connect a billion people by 2031; that is a goal, not a measured result.
Free individual access and paid team, organization, and enterprise offerings. Cal.com provides booking pages and scheduling infrastructure, with tools for teams and developers. The separately maintained Cal.diy community edition has a different feature scope.
Observed channels and entry points; their performance is not inferred.
Cal.com presents its offer to Individuals, customer-facing teams, and platform developers. Its official product pages explain the workflow: Scheduling for individuals, teams, and embedded bookings. This is an observable discovery surface; public documentation does not establish the share of customers it acquires or the cost of acquiring them.
EvidenceA MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.
The public page embeds Bailey Pumfleet's announcement of crossing $10M ARR. Only relative publication timing is visible; exact cutoff remains unknown. Scheduling company Cal.com, not calorie app Cal AI.
Cal.com team post containing Bailey Pumfleet's founder announcementA simple individual workflow can become infrastructure when teams need routing and integration.
These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.