Cal.com is currently telling four different stories on four different public surfaces. All four were captured live on 28 May 2026.

Position 1. Homepage H1. “The better way to schedule your meetings.” Calendly-killer voice. The voice the company used to win Series A in 2022. Sells the booking flow itself. Targets the individual-to-small-team buyer journey.

Position 2. About page. “Infrastructure for scheduling. It sits underneath your workflows, routing, and systems.” Developer and enterprise voice. The reposition the leadership team appears to be making. Sells the platform layer underneath the booking flow.

Position 3. Enterprise page. “The operating system for scheduling.” A third frame, neither booking flow nor infrastructure, but operating system. Distinct from the about page’s framing. Distinct again from the homepage.

Position 4. Cal.ai. Branded as “AI Phone Agent.” Sits on its own domain as a separate product feel. Doesn’t share the “infrastructure” or “operating system” framing of the about and enterprise pages.

The four positions are individually defensible. Together they tell the prospect, the LLM, and the journalist four different stories about what Cal.com is. That is the source of the reposition gap. Pick one lane and the gap closes.

On 28 May 2026 we ran the standard Q1/Q2/Q3 prompt battery against five leading AI models via OpenRouter. Source files: ~/SecondBrain/business/rational-magic-docs/data-bank/tier-1-corpus/bootstrapped-to-series-a/evidence/cal-com/q[1-3]-[claude|chatgpt|gemini|perplexity|grok]-2026-05-28.json. The pattern is consistent and is itself the audit’s headline finding.

Claude (Opus 4.7). Described Cal.com as “an open-source scheduling platform, often positioned as a Calendly alternative.” No mention of infrastructure framing. No mention of Cal.ai prominently. The reposition is invisible.

ChatGPT. Described Cal.com as an “open-source meeting scheduling tool, often described as an open-source alternative to Calendly.” Same pattern as Claude. The Calendly-comparison frame dominates.

Gemini. Described Cal.com as “an open-source scheduling platform.” Mentioned customisation and self-hosting as differentiators. Did not surface infrastructure positioning.

Perplexity (Sonar Pro). Described Cal.com as an “open-source Calendly alternative.” The model with live search grounding still defaulted to the older mental model rather than picking up the newer about-page language.

Grok. Q1 returned “California Communications,” a radio company. Q2 returned a “Calcom RMM platform.” Q3 only identified Cal.com correctly when the prompt explicitly mentioned Calendly. Two complete misidentifications before the third question landed on the right entity. Suggests brand-name fragility: the cal.com identifier doesn’t cue convergence on the correct entity without context.

The convergent finding: 4 of 5 models describe Cal.com using language from 2022 (open-source Calendly alternative). None describe Cal.com using language from 2026 (infrastructure for scheduling, operating system, AI-native scheduling layer). The reposition is real on the about and enterprise pages. The reposition is invisible in the surfaces buyers consult.

The cause is structural. LLM training data weights established language (the Calendly-alternative frame, established in 2022 press coverage and Reddit discussion) over recent site copy changes. The homepage still uses the older language, which compounds the lag. Until the homepage and the LLM-facing surfaces match the about page, the reposition will keep being 2 to 3 years ahead of the market mental model.

Reddit theme analysis run via Perplexity Sonar Pro on 28 May 2026 (Apify was unavailable for credit reasons; Sonar Pro provided the synthesis). The six dominant themes across r/selfhosted, r/SaaS, r/devops, and r/marketing discussion:

1. Open-source self-hosting vs SaaS. Dominant theme in r/selfhosted. The community treats Cal.com as the canonical open-source scheduling answer. The hosted SaaS is acknowledged but the self-host crowd is louder.
2. Customisation and developer-friendliness. Cal.com framed as “a platform for builders,” with discussion of APIs, embedding, white-labelling, and routing depth Calendly can’t match.
3. Calendly comparisons. Cal.com wins for teams and complex setups (routing, integrations, customisation). Calendly wins for simple personal links and brand recognition. The split is consistent across threads.
4. Self-hosting complexity. Docker setup, OAuth, upgrade pain, breaking changes between releases. The dominant pain point in the open-source threads. “Yours to control” hides operational labour.
5. AI and automation. Workflows and automated follow-ups mentioned positively. Cal.ai itself barely surfaces in Reddit discussion. The community knows the platform; the AI product is invisible to them.
6. Pricing vs self-hosting trade-off. Recurring debate about whether the $12/user/month team tier is worth it vs the operational cost of self-hosting. The honest answer in the threads: hosted wins for teams that don’t have a dedicated infra person.

The structural reading: the open-source community sees Cal.com clearly and accurately. The infrastructure positioning isn’t resonating because the community already treats it as infrastructure; they just don’t call it that. The audience that needs to hear the new positioning is the enterprise buyer who is not on Reddit and who asks an LLM what Cal.com is. That audience gets the 2022 answer.

High: founder credibility (Peer and Bailey are visible, on-mic founders with public-facing presence), product depth (open-source, embedded SDKs, white-label, API-first, AI agent layer all in one), customer roster (Vercel, Supabase, Mintlify, Deel is a developer-tools dream team), engineering reputation (the platform is well-regarded technically in dev-tools communities), Open Startup transparency (cal.com/open publishes salaries plus metrics; powerful trust signal).

Low: brand consistency across surfaces (4 different H1s on 4 surfaces; the audit’s headline finding), AI-tool discoverability (4 of 5 leading models return the 2022 frame), Cal.ai prominence (sub-page on the main site; the strategic bet is buried), homepage-as-funnel design (no schema, no logo wall, no Cal.ai promotion above the fold), and structural GEO infrastructure (the /llms.txt file is one link long; the homepage has no JSON-LD; the surfaces LLMs scrape don’t carry the new positioning).

The trade-off Cal.com is making with the infrastructure reposition: walking away from the cleanest pitch in the company’s history. “Open-source Calendly alternative” is a four-word pitch that explains the product, the differentiation, and the buyer journey in one breath. It built the Series A. It built the GitHub star count. It built the Reddit reputation.

Infrastructure positioning is a longer pitch. It requires the buyer to already understand the concept (what does infrastructure for scheduling even mean?). It removes the comparison shortcut (no Calendly mention means no immediate frame of reference). It pushes the audience up-market from prosumer to enterprise, where buying cycles are 6 to 12 months instead of self-serve.

This is the right bet. The AI-agent era is the next category, and being the infrastructure underneath it is a much larger market than being a better Calendly. But the reposition only works if it’s on every surface, not on three of four. The current state (about page repositions, homepage doesn’t) is the worst of both worlds: the new pitch confuses the old audience and the old pitch confuses the new one.

We ran the empirical check on the day of this audit (28 May 2026). Here is what is and isn’t working underneath the visibility gap.

robots.txt. Standard. No surprises. Googlebot, GPTBot, ClaudeBot, and PerplexityBot all unrestricted at cal.com/robots.txt.

Sitemap. Multi-language coverage at cal.com/sitemap.xml covering English, German, French, Dutch, Portuguese, Spanish, and Italian. International coverage is solid. The Yoast-equivalent infrastructure is doing its work.

llms.txt (the GEO miss). The file exists at cal.com/llms.txt, which is more than most Series A SaaS companies can say. But it is one line long. A single link to docs/agents.md titled “How AI agents can use the Cal.com API v2.” That is useful documentation for AI developers building on Cal.com’s API. It is not a Cal.com summary for AI tools trying to answer “what is Cal.com?” The /llms.txt should carry a one-paragraph Cal.com summary, the canonical positioning sentence, a link to /open, a link to /enterprise, and a link to the calcom-vs-calendly comparison page. Tonight, not next quarter.

JSON-LD schema (the bigger GEO miss). No JSON-LD detected on the cal.com homepage. For a Series A company with the level of search and AI-tool visibility Cal.com is targeting, this is the single largest cheap fix in the audit. Adding Organization, SoftwareApplication, Product, and Person schema (for Peer and Bailey) to the homepage is roughly 2 hours of structured-data work. Until it lands, every AI tool grounding on the homepage has to infer the entity from copy alone.

Indexed surfaces. WebSearch site:cal.com returned roughly 10 surfaces at the top level on 28 May 2026. Well-indexed. The top-of-funnel pages are crawlable and indexed. The Google side of the search picture is healthy.

Title tag. “Cal.com | Scheduling Software for Online Bookings.” Clean and accurate. Doesn’t carry the infrastructure framing, but doesn’t actively contradict it either.

Meta description. “A fully customizable scheduling software for individuals, businesses taking calls and developers building scheduling platforms where users meet users.” Tries to address four audiences in one sentence, which is the structural problem the rest of the audit surfaces. Picks the booking flow framing.

OG image. A framerusercontent URL. Basic, not custom-designed. Adequate but not a competitive moat. Replace with a designed 1200×630 share card that carries the new positioning line.

The good news. Every gap above is fixable in a single sprint. JSON-LD is structured data. /llms.txt is a text file. The OG image is a single asset. The H1 unification is a copy decision. A focused half-day closes roughly 70% of the GEO debt at zero cost. Section 05 / Tier 1 lays out the specific fixes in order.

Three different framings of the structural risk underneath the reposition. We’re not picking. The Cal.com leadership team should rank these in the order they actually feel. The ranking determines the strategic emphasis of the next 12 months.

Shadow A. Pick-a-lane. Trying to win four brand fights at once dilutes all four. The Cal.com a consumer sees, a developer sees, and a CIO sees are different products. Until the four positions collapse into one, the brand is invisible as a single entity. This is the shadow the empirical AI-tool capture surfaces most clearly.

Shadow B. Self-hosting tax. Open-source is a marketing word with hidden labour underneath: Docker setup, OAuth, upgrade pain, breaking changes. The “yours to control” promise hides operational cost that the Reddit threads name explicitly. If Cal.com’s top-of-funnel is the open-source story, the bottom-of-funnel is the team that bounces off the self-host complexity and the SaaS pricing simultaneously.

Shadow C. AI-as-feature vs AI-as-positioning. Cal.ai exists but lives in the nav. If “scheduling for the AI era” is the bet, the bet needs the headline slot, not a sub-page. Cal.ai launching as a separate-feeling product with its own domain branding is the surface signal that the AI bet hasn’t been fully internalised as the platform’s identity.

Each shadow points to a different strategic emphasis: Shadow A says unify the positioning. Shadow B says productise the self-host story or push hosted harder. Shadow C says promote Cal.ai to the headline slot. Our reading is that A and C are the same underlying problem (the brand is multiple things) and the strongest move is to collapse them. But the Cal.com team should rank these for themselves.

The discoverability gap closes when Cal.com becomes the answer LLMs give when asked about scheduling infrastructure, AI scheduling, or developer-first booking tools. That happens through structural moves, not paid promotion.

Unify the H1 across homepage, about, and enterprise. Pick “Scheduling, as infrastructure” (or equivalent) and use it as the H1 everywhere. Today there are three different H1s on three surfaces. The cost of the gap is that LLM training data weights the most-indexed copy, which is the homepage’s Calendly-killer voice. Unifying gives the reposition a single signal to absorb.

Expand the /llms.txt file. Add a one-paragraph Cal.com summary, the canonical positioning sentence (“Scheduling, as infrastructure”), a link to /open metrics, a link to /enterprise, and a link to /scheduling/calcom-vs-calendly. The current single-link version is documentation for API builders. The expanded version is the Cal.com pitch for AI tools.

Add JSON-LD schema to the homepage. Organization (Cal.com Inc.), SoftwareApplication (the scheduling platform), Product (Teams, Organizations, Enterprise tiers), and Person (Peer Richelsen as Co-CEO, Bailey Pumfleet as Co-CEO). Two hours of structured-data work. Single biggest cheap fix for AI-grounded search.

Get cited as infrastructure in the surfaces LLMs consume. The single highest-leverage source is Reddit (now licensed by Gemini and OpenAI; per our LLM-source-access matrix). Founder-voice posts from Peer and Bailey in r/selfhosted, r/SaaS, and r/devops about the infrastructure bet. Educational. Signed. Tool linked once. This is the same playbook that puts other founder-led brands into LLM training data over the 6 to 12 month window.

Wikipedia entry, properly resourced. Current Wikipedia coverage of Cal.com is thin. A proper entry referencing the Series A, the customer base, the open-source approach, and the Cal.ai launch unlocks the LLM training-data layer. Wikipedia is per the procedural canon roughly 26% of LLM citations. This is a 12-month play. Start it now.

Promote Cal.ai above the fold. Currently a nav link. Should be the second-most-prominent product surface on the homepage, after the booking-flow demo itself. The Cal.ai launch is the strategic differentiator. Burying it in the nav contradicts the bet.

Eliminate: the brand-position inconsistency. Pick one H1 and put it on every public surface in the same week. The cost of running four positions in parallel is that none of them lands. The team will feel the discomfort of choosing; the audience will feel the relief.

Reduce: the Calendly framing on the front door. Move “Cal.com vs Calendly” from front-and-centre to a dedicated /vs page that prospects find via search. The comparison shortcut helped win the Series A. Keeping it on the homepage now anchors Cal.com to the smaller market.

Raise: the customer logo wall. Vercel, Supabase, Mintlify, Deel, Theatre.JS, EpicWeb.dev should appear above the fold on the homepage, not only on /enterprise. The logos do disproportionate work for the infrastructure framing because the audience already trusts those names.

Create: a long-form case study series. “How Vercel uses Cal.com as scheduling infrastructure.” “How Supabase uses Cal.com for community plus sales.” “How Mintlify embeds Cal.com in their docs platform.” Three named customers, three long-form essays, each anchored by a dev-team interview. Becomes the canonical citation when an LLM is asked “who uses Cal.com as infrastructure?”

Three specific moves in the next 30 days: (1) unify the homepage H1 with the about page positioning; (2) ship the JSON-LD schema and the expanded /llms.txt; (3) move Cal.ai promotion above the fold on the homepage, with the customer logo wall directly beneath it.

The voice is held in place by these traits. Each is observable on a public Cal.com surface today; none of them needs to be invented.

1. Engineering-first. Built by devs, for devs. The product surface, the documentation, and the founder voice all read as engineering-grade. This is what the customer roster (Vercel, Supabase, Mintlify) signals about the buyer relationship.
2. Transparent. The Open Startup page at cal.com/open publishes salaries plus operational metrics in public. Almost no Series A company does this. It’s a structural trust signal that scales every other claim Cal.com makes.
3. Opinionated. “Free forever for individuals” is a stance, not a promo. The pricing structure carries the same opinion: free is the funnel, paid is the team, enterprise is the platform. The free tier doesn’t apologise for itself.
4. Privacy-grounded. HIPAA, SOC 2 Type II, ISO 27001, CCPA, GDPR. The compliance surface is unusual for a scheduling product in this revenue range, and it’s a precondition for the enterprise and infrastructure positioning.
5. Bet-forward. Cal.ai shipped before the market asked for it. That’s the posture that wins category leadership in the AI era. The trait needs to be visible in the marketing voice, not only in the product roadmap.

Today (cal.com homepage, captured 28 May 2026):

H1: “The better way to schedule your meetings.”
Sub: “A fully customizable scheduling software for individuals, businesses taking calls and developers building scheduling platforms where users meet users.”

Suggested rewrite (aligned to the about page voice):

H1: “Scheduling, as infrastructure.”
Sub: “Open-source, embeddable, AI-native. The scheduling layer Vercel, Supabase, and Mintlify already build on.”
CTA row: “Try Cal.com free” (left) · “See Cal.ai” (right) · “Read enterprise customers” (bottom).

The shift: same product, new framing. The booking-flow demo still goes below the fold for the prosumer who wants to see the tool work. The H1 now does the work of positioning the brand at the platform layer where the strategic bet lives.

For Peer Richelsen or Bailey Pumfleet’s personal LinkedIn account. Posted under their name, not the Cal.com company page. The template below is one example of the cadence the reposition needs.

“When we started Cal.com in 2021 we thought we were building a Calendly alternative. Open-source, customisable, dev-friendly. We were wrong about the framing. What we’ve actually been building is scheduling infrastructure. The reason Vercel, Supabase, and Mintlify use us isn’t that we’re a better booking page. It’s that we’re the layer underneath their workflow that handles bookings, routing, and now AI agents. The shift from tool to infrastructure is the strategic bet for the next 5 years. Cal.ai is the proof of concept. The cal.com homepage will catch up to the about page in the next sprint. Peer.”

Notes for the team: 1,300 to 1,900 characters is the LinkedIn dwell-time sweet spot. The post leads with the diagnostic shift (tool to infrastructure), names specific customers as proof, and signs off. No CTA link. No “DM me to learn more.” The point is to put the infrastructure framing into LinkedIn’s indexable surface in the founders’ voice, repeatedly, for 90 days. That’s what compounds into LLM training data and into the buyer’s mental model.

Don’t keep the four positions running in parallel. The single largest cost of the current state is brand-position multiplication. Picking one lane feels risky internally; running four feels safer. The empirical AI-tool capture proves the opposite. Four positions is the failure mode. One position with four entry points is the unlock.

Don’t bury Cal.ai while claiming the AI-era reposition. The contradiction between “we’re infrastructure for the AI era” and “Cal.ai is a nav link” is visible to anyone who looks at both surfaces in the same session. Promote Cal.ai or the reposition isn’t credible.

Don’t over-rotate to the Calendly comparison. The /vs page exists and should rank for the comparison search query. The homepage and the about page should refuse the comparison frame. The comparison is the floor of the brand’s ambition; infrastructure is the ceiling.

Don’t hire a CMO before the positioning lands. A new marketing leader who joins mid-reposition will spend their first 90 days running their own positioning exercise. That delays the work, splits the team, and adds a third voice to the four already running. Land the reposition first, then hire to scale it.

Don’t skip the 90-day window. SEO compounds over months. LinkedIn organic builds over weeks. Reddit posts compound into LLM training over 6 to 12 months. Pulling the plug on the Tier 2 cadence at week 6 because “it’s not working” is the most common reason early-stage marketing fails. The discipline is patience inside one channel, not motion across many.

Days 1 to 14: Tier 1 complete. JSON-LD shipped. /llms.txt expanded. Homepage H1 unified to the about-page voice. Cal.ai promoted above the fold. Customer logo wall lifted to the homepage hero. Visibility audit re-run; AI tool answers should start to shift within 4 to 6 weeks as the LLM training surfaces re-index.

Days 15 to 30: Tier 2 starts. Peer and Bailey publish 8 to 12 LinkedIn posts each (3 to 5 per week). Daily commenting habit established. First customer case study (Vercel or Supabase) scoped and interview booked. Wikipedia entry drafted and submitted.

Days 30 to 60: Tier 2 deepens. Reddit AMA scheduled. Two case studies published. /vs page refreshed and promoted to main nav. Measure: brand mention frequency in AI-tool answers (re-run the 5-LLM capture monthly), audit-page traffic by source, qualified enterprise pipeline.

Days 60 to 90: Reddit AMA executes. Third case study published. Tier 2 cadence continues. First measurement of which channels are actually producing pipeline. Channels that aren’t producing get assessed honestly. Tier 3 only opens up if Tier 2 baseline is clearly working.

Day 90 decision point: re-run the 5-LLM capture from the audit. Compare to the 28 May 2026 baseline. The success metric is whether the LLM answers have shifted from “open-source Calendly alternative” to something closer to “scheduling infrastructure used by Vercel, Supabase, and Mintlify.” If yes, double down. If no, the diagnosis is upstream (probably homepage copy didn’t actually change, or schema didn’t ship as planned). Fix and rerun.