Cal.com and Its Founders: Origins, Business Strategy, and the Open-Source Turning Point
Cal.com was founded in 2021 by Peer Richelsen and Bailey Pumfleet. Current public sources identify Bailey as CEO; Peer’s Y Combinator biography describes him as co-founder and chairman. Different historical titles—including co-CEO, CEO, and chairman—do not by themselves establish a breakdown in their partnership.
Their partnership combines two different paths.
Peer brought repeated startup experience, product judgment, branding, and founder networks. Bailey entered through hands-on development and gradually assumed responsibility for running the company. This is an interpretation of their careers, not an official allocation of responsibilities.
Crucially, Cal.com can no longer be described simply as “an open-source Calendly.” In April 2026, the company announced that its commercial production code would become closed source, while an open project, Cal.diy, would remain.
This report covers information available through October 22, 2026.
30、Peer’s family background: a German farm and an early lesson about work
In a Mercury interview, Peer described growing up on a small German farm. His father was a farmer and self-employed businessman. Watching him work continuously taught Peer that demanding physical work does not necessarily produce proportional financial rewards.
As a young person, Peer became interested in computers, gaming, and the internet. He ran a gaming clan, learned HTML to create its website, and subsequently made websites for friends and local businesses.
The significance goes beyond an early interest in computers.
His developing career choices reflected a contrast between two forms of work: farming depended heavily on time, physical effort, and local conditions; software could be replicated and sold to distant customers. Moving from website commissions to products followed that logic.
This background does not establish a precise family wealth category, however, and should not be turned into a claim that he started with no resources whatsoever.
31、Peer’s education and first brand: business informatics and Bordifies
In a German interview published in 2017, Peer dated the creation of Bordifies to 2014, while he was studying business informatics—Wirtschaftsinformatik.
Bordifies sold visually distinctive sleeves for trading-card players, including the Magic: The Gathering community. He described reaching an agreement with Ultimate Guard in December 2015 to bring the brand into wholesale distribution.
The venture exposed him to an entire commercial process: identifying a community’s needs, designing a product, obtaining feedback, and expanding through distribution partners.
It also helps explain his continuing interest in appearance, naming, identity, and distribution alongside software functionality.
Retrospective accounts and contemporary interviews do not present every early event in exactly the same sequence. They do not justify assigning him a precise graduation or dropout date.
32、From Bordifies to Snapcardster and Mage: organizing transactions
Peer subsequently moved into trading-card marketplaces. Early work involved Snapcardster; his most important company in this area was Mage Market, co-founded with Malte Delfs.
Mage joined Y Combinator’s Winter 2019 batch. It sought to make collectible-card trading more standardized through market pricing and expert verification. YC now lists the company as inactive.
This required more than operating a product brand.
Selling accessories primarily involves product and distribution. Running a marketplace adds matching, trust, liquidity, fulfillment, and transaction frequency. Peer was moving from a niche product business into a venture-backed platform.
The distinction matters: Mage participated in YC; that does not establish that Cal.com was itself a YC company.
33、Mage’s failure: an online marketplace exposed to offline disruption
In March 2020, Peer published an explanation of Mage Market’s shutdown. He reported an approximately 60% revenue decline during the pandemic, as physical events and game stores were disrupted. The company could not reach sustainable operations within its remaining financial runway.
He described an orderly closure, using remaining resources for severance and helping employees find work rather than continuing to spend while waiting for recovery.
The failure should not be reduced either to a bad product or entirely to circumstances beyond management’s control.
It exposed a structural dependence: although transactions happened online, activity still relied on physical games, tournaments, and stores. Disruption to that ecosystem quickly affected online revenue.
Peer’s later ventures addressed broader and potentially more regular software needs. That suggests strategic continuity, without proving that one failure inevitably produced Cal.com.
34、Lean Hire: turning the need for work into a business
Peer later told Mercury that after Mage closed, he stayed with a friend and had approximately €1,000 remaining. Lean Hire began partly because he needed work and income himself.
Lean Hire encouraged employers to begin with a paid project before committing to a longer employment relationship. Its website explicitly connected this approach to Eric Ries’s lean-startup methodology and served the YC and On Deck communities.
The project was subsequently acquired by On Deck, where Peer took a product role, according to public interviews and related investment materials.
The experience left two important resources: a network of founders and developers, and a method of assessing people through actual collaboration before making a long-term commitment.
That second idea reappeared directly in his initial work with Bailey.
35、Bailey’s family background: a working-class household near London
In his own LinkedIn post, Bailey described growing up in a poor family in a small town outside London. Nobody in his family had previously attended college, and his father worked long hours in manual labor to support the household.
He said this taught him to value hard work without romanticizing hardship, while seeing the internet as a way for young people to change their circumstances.
This creates a meaningful parallel with Peer: both had watched their fathers work intensely, and both saw software as a way to expand individual output and opportunity.
Their starting positions nevertheless differed. Peer had already accumulated several entrepreneurial experiences before Cal.com; Bailey entered a venture attracting capital and attention at a very young age.
36、Bailey’s education and early career: avoid the dropout stereotype
In a 2022 interview with Nathan Latka, Bailey said he was 17 when the relevant development work began in February 2021.
The interview discussed university choices, but did not clearly establish a story of enrolling in university and then dropping out. Describing him as a university dropout would therefore be imprecise. The supported conclusion is that he entered software development and entrepreneurship unusually early.
Bailey has also recalled participating in Cal.com sales conversations at 17, including speaking with the CEO of a large company.
His path was consequently not the conventional progression from established-company engineer to manager and then founder.
He encountered development, customer needs, sales, and management simultaneously. That can accelerate learning, while making operational experience—not years inside a mature organization—the main source of managerial training.
37、How the partnership formed: a paid trial before co-founding
According to Bailey’s interview, Peer sought a developer through an early project’s mailing list. They began with a two-week paid engagement worth $5,000, then became co-founders.
They were not longtime classmates starting a business together, nor was their partnership based only on credentials.
The arrangement closely resembled Lean Hire’s central idea: use a real project to observe execution, communication, and compatibility before making a lasting commitment.
Peer already had entrepreneurial experience and relationships; Bailey demonstrated his contribution through delivery. The paid engagement gave both a relatively quick way to test their complementarity.
38、The initial market entry: begin with established demand
The project originally operated as Calendso, entering the scheduling market through open source, self-hosting, and customization.
This reduced demand-discovery risk. Customers already understood booking links; the founders needed to demonstrate why different levels of control and extensibility mattered.
The later change to Cal.com also signaled a move away from a name closely associated with a competitor toward an independent category brand. The company’s rebranding announcement and contemporary domain-industry coverage document that transition.
Some older articles display later dates following website migration. A page’s current timestamp should not automatically be treated as the actual date of a financing, founding, or rebranding event.
39、The domain and brand: part of the distribution mechanism
Cal.com is short, memorable, and closely associated with “calendar.” For a scheduling product, users repeatedly expose the brand to other people when sharing booking links.
The domain is therefore both an access point and part of the distribution interface.
The reporting reviewed did not disclose a reliable purchase price, so assigning one would be speculative.
Analytically, this makes branding unusually relevant: using the product also distributes its identity. A concise name can reduce typing, memory, and communication costs simultaneously.
However, the domain is a company-level asset. Its value should not be equated with a founder’s disposable personal wealth.
40、The seed round: money, credibility, and relationships
Cal.com announced a $7.4 million seed round led by OSS Capital.
Named investors included Naval Ravikant, YouTube co-founder Chad Hurley, Balaji Srinivasan, Confluent co-founder Neha Narkhede, MongoDB co-founder Eliot Horowitz, Vercel’s Guillermo Rauch, and Supabase’s Paul Copplestone.
Their significance extends beyond recognizability.
They span open-source commercialization, databases, developer tools, and enterprise software. For a company moving from developer adoption toward enterprise purchasing, such relationships can support hiring, product feedback, introductions, and credibility.
An investment does not establish operational control, however. It would be unjustified to infer that any particular prominent investor directed Cal.com’s product decisions.
41、Series A: scaling beyond a popular developer project
In 2022, Cal.com announced a $25 million Series A led by Alexis Ohanian’s Seven Seven Six. Participants included Obvious Ventures, OSS Capital, Tobi Lütke, and Jack Altman.
Daily.co also appeared among investors and had a product relationship with Cal Video.
The two explicitly disclosed rounds total $32.4 million. This is a confirmed historical sum, not necessarily the company’s complete lifetime financing.
Venture funding changed the company’s obligations. It needed to demonstrate a substantial addressable market and recurring commercial demand, rather than merely sustain a well-liked open-source project.
42、Product structure: booking links are only the outer layer
For individual users, Cal.com handles available times, calendar synchronization, time zones, and meeting arrangements.
Inside organizations, its role extends to coordinating multiple people, allocating meetings, routing customers, and managing reminders and follow-up processes. Its listed use cases include recruitment, sales, education, support, and healthcare scheduling.
The API and Cal.com Atoms are particularly significant.
Atoms package functions such as calendar connections, availability settings, and booking forms into React components that customers can embed and customize within their own applications.
The company can therefore become part of a customer’s product rather than merely an application employees use. Deep integration with business rules can increase replacement costs.
43、Business model: free entry, paid seats, enterprise contracts, and integration
At the time reviewed, the website’s annual-billing prices were: a free individual plan, $12 per user per month for Teams, $28 for Organizations, and custom Enterprise pricing.
Higher tiers add value through organizational management, permissions, identity features, service commitments, and infrastructure options.
The commercial logic is straightforward: individuals enter cheaply, organizations pay as coordination becomes more complex, and enterprises pay for reliability, administration, and service.
APIs and embedded functionality introduce another purchasing rationale: customers buy a capability integrated into their business, not just an employee account.
Its business model should therefore be assessed through workflow adoption, not merely by counting features on a booking page.
44、Cal.ai: moving from accepting bookings to advancing them
Cal.ai adds AI telephone functionality for booking conversations, confirmations, reminders, and follow-up. The website lists $0.29 per minute.
This changes the interaction model. Previously, a person opened a link and selected a time; software can now help move the process forward through a telephone conversation.
Usage-based calling creates a potential revenue stream beyond seat subscriptions.
It also creates variable costs: voice, model, and telecommunications expenses rise with usage. The existence of the feature does not establish that it is already a major revenue contributor or reveal its profitability.
45、Assets versus influence
Company-level assets include the domain, brand, software, customer contracts, and associated commercial rights. The website identifies Cal.com and Cal as registered trademarks of Cal.com, Inc.
Influence assets include developer relationships, historical contributors, product reputation, founder communications, and associations with design and open-company practices.
Cal Sans and other design resources increase visibility among product designers. Their existence does not establish separate businesses generating substantial revenue.
Peer also appears among the investment supporters listed on Dub’s official website. This supports an investment relationship, but not an investment amount, ownership percentage, or controlling position.
Company assets, founders’ equity, personal investments, and public reputation must be kept distinct.
46、Organizational culture: open operations and open code differ
Cal.com’s company description emphasizes public business metrics, salary transparency, and distributed work.
Salary disclosure is voluntary. Its stated philosophy rejects paying differently for equivalent work merely because employees live in places with different living costs. The website describes a fully distributed team without a physical headquarters.
This supports international recruiting and a recognizable employer identity.
Nevertheless, public operating metrics, salary transparency, and open-source code are separate commitments. Closing the production repository does not automatically terminate every transparency practice. Conversely, publishing some metrics does not make the commercial software open source.
47、Revenue: growth estimates require clear labeling
Research firm Sacra estimates that Cal.com reached approximately $1 million ARR in 2023, $2.9 million at the end of 2024, $6.2 million at the end of 2025, and $11 million in September 2026.
It lists a $150 million post-money valuation for the 2022 Series A. These are third-party research figures, not public audited accounts or measures of the founders’ personal wealth.
ARR annualizes recurring business. It is not interchangeable with recognized annual revenue, cash flow, or net profit.
If the trajectory is broadly accurate, it indicates meaningful commercial demand. It still does not establish profitability, cash reserves, or eventual shareholder returns.
48、The Deel case: what enterprise customers are buying
A Cal.com customer case study says its solution supported more than 1,000 Deel employees and saved over 6,000 hours per week in aggregate, alongside improvements in scheduling and participation.
These are supplier-published case-study claims, not independent audit findings.
The case is most useful for understanding the purchase rationale.
Large organizations need to reduce the work of coordinating people, allocating meetings, finding appropriate participants, and managing delays—not simply acquire an attractive booking page.
Cal.com’s commercial value is strongest when scheduling becomes part of frequently repeated operational processes. Its published case studies also include AngelList and Retell AI, reflecting its enterprise and embedded-product direction.
49、Timeline: how the ventures and identities connect
In 2014–2015, Peer operated Bordifies while studying business informatics and expanded through distribution partners.
From 2016 onward, he further explored card-trading platforms. Mage joined YC’s Winter 2019 batch, then closed after the pandemic shock in 2020. Lean Hire subsequently moved him into project-based recruiting and talent collaboration.
In 2021, Peer and Bailey collaborated on Calendso, later renamed Cal.com; Bailey was 17. The company announced its Series A in 2022.
In 2026, the commercial production code became closed source, with Cal.diy continuing publicly.
Peer’s progression runs from community product operator to marketplace entrepreneur, repeat founder, and chairman. Bailey’s runs from young developer to CEO with commercial and organizational responsibilities.
50、The 2026 closed-source decision
On April 14, 2026, Bailey published the company’s explanation for closing its commercial code.
The stated rationale was that AI had lowered the difficulty of discovering and exploiting vulnerabilities, making public production code a growing security burden. The announcement also described substantial changes to authentication and data handling.
Fact and position must be separated.
The announcement is a fact. The conclusion that closing the code improves security is the company’s assessment of its circumstances, not an established industry consensus.
The immediate governance consequence is clear: developers can no longer use the public repository to continuously inspect, modify, and follow the commercial production version.
51、What Cal.diy preserves—and what it does not
The April 15 technical explanation states that the public repository became calcom/cal.diy, with its license changing from AGPL 3.0 to MIT.
Cal.diy retains core scheduling, booking flows, and the application framework, but excludes commercial capabilities such as teams and organizations, routing, automated workflows, and AI calling. Former Cal.com interns maintain it, while the company’s engineers focus on the commercial product.
An open project still existing does not mean the commercial product remains open source.
Cal.diy can remain useful for individual self-hosting and experimentation. Organizations needing complete enterprise functionality must reassess the boundaries of functionality, maintenance, security updates, and support.
The economic relationship with contributors has also changed: the public project they support and the company’s main commercial product no longer form one continuously synchronized codebase.
52、The principal controversy: security arguments and prior expectations
Discourse co-founder Sam Saffron publicly challenged this direction in April 2026. He argued that attackers do not necessarily need source code, AI can investigate systems through black-box methods, and openness can also help defenders discover vulnerabilities.
The dispute has several dimensions.
Publishing code may lower some attack-analysis costs, but hiding code does not replace security engineering.
A commercial company can change its operating model, while still facing expectations created by its earlier openness.
Community objections should not be reduced to wanting free software. They also concern contributors’ work, auditability, long-term control, and the continuity of commitments.
Speculation about commercial motives should not be presented as proven inside knowledge. Closing code alone does not establish unlawful conduct.
53、Documented vulnerabilities are not proof of mass theft
In January 2026, Gecko Security disclosed access-control problems in Cal.com, including an organization-invitation issue capable of enabling account takeover and authorization flaws in the older API.
The researchers said the problems were fixed within days of disclosure; the account-takeover fix involved v6.0.8.
The event establishes that the company faced serious security-engineering issues.
It does not independently prove that closing the source was the only solution. Nor should demonstrated potential access be described as confirmed malicious mass data theft.
Enterprise buyers should focus on authorization boundaries, remediation speed, auditability, and incident transparency, rather than source visibility alone.
54、Long-term promises and operating decisions
Cal.com previously published a “Longevity” commitment describing conditional code transfers, relicensing, and a proposed nonprofit maintenance mechanism if the company stopped supporting the projects.
That is a conditional undertaking, not evidence of an already established and fully funded independent foundation.
Separately, in July 2026 the company announced plans to close Cal.eu on November 1, 2026, with migration arrangements to Cal.com and possible extensions for certain enterprise contracts.
At this report’s cutoff, that date remains in the future.
These decisions illustrate operating constraints: deployment options, regional services, and long-term maintenance commitments consume resources.
Customers need to assess actual contracts and migration arrangements rather than assume that a brand promise guarantees every service configuration will remain unchanged indefinitely.
55、What Cal.com has accomplished—and what remains difficult
Cal.com’s representative achievement is entering an established market through openness, design, and developer relationships, then extending into enterprise workflows and embedded products.
It did not invent online scheduling. Community recognition alone does not prove that it has transformed the entire industry. Its clearer contribution is demonstrating a developer-infrastructure path for a scheduling product.
Its advantages and risks often share the same source.
Customization increases maintenance and support complexity. Enterprise requirements can increase contract value while raising security and reliability expectations. An open community helped distribution; closing the commercial code may weaken some of that trust.
Booking links distribute the brand, but should not automatically be described as a strong network effect. More revealing questions concern integration depth, renewal, and actual migration difficulty.
These are analytical conclusions about the product structure, not substitutes for unpublished retention, acquisition-cost, or contract data.
56、Where the founders stand today
Peer’s contribution lies in combining product taste, community understanding, repeated entrepreneurial experience, and capital relationships. His career is not an uninterrupted sequence of successes; Mage’s closure is essential to understanding it.
Bailey’s significance lies in moving from a very young developer to CEO, with responsibility for competing demands involving security, commercialization, and community expectations—not merely maintaining the image of a young founder.
Cal.com now has meaningful commercial scale but still needs to establish durable advantages. It has moved beyond being simply an open-source project; financing and estimated ARR alone do not make it indispensable industry infrastructure.
The three most useful questions to follow are whether enterprise customers renew and expand; API and AI products produce healthy revenue; and the company can preserve developer trust while improving reliability after closing its commercial source code.
More In-Depth
- VoteHub and Its Founders: From Election Enthusiasts to a Professional Data CompanyNov 11, 2026
- Linkfire and Its Founders: The Business Behind Music Links and Its Financial Ups and DownsNov 11, 2026
- DataFast and Marc Lou: Building a Software Business Through Products, Content, and AudienceNov 11, 2026
- TrustMRR and Marc Lou: Turning Verified Revenue into a Marketplace for Software BusinessesNov 11, 2026