Data Panda brings your Cal.com scheduling data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your sales, recruiting and customer-success teams use every day.
Cal.com was started in 2021 by Peer Richelsen and Bailey Pumfleet as an open-source alternative to Calendly, with a distributed team across Europe and the US. The product is positioned as scheduling infrastructure: a cloud SaaS for individuals and teams, an enterprise edition that self-hosts behind your own VPC, and a deep API plus webhook surface, with customers ranging from solo operators to teams at Vercel and Supabase.
For most go-to-market teams Cal.com is the booking layer behind the website, the CRM lead-routing flow, the recruiter outreach sequence and the customer-success quarterly review. That makes its event data worth a lot more in a warehouse than inside the Cal.com Insights tab. Book-rate per event type, no-show rate per traffic source, time-to-meet per segment and routing-form drop-off per question only matter when they sit next to the deals, hires and renewals that the meetings were supposed to drive.
Book-rate, no-show-rate and time-to-meet per event type, source and team.
Let a Cal.com webhook trigger the rest of the GTM stack.
Put booking and attendee data behind AI that helps the team route and qualify.
Small internal tools on Cal.com data for sales-ops, recruiting and CS leads.
A list of concrete reports, automations and AI features we have built on Cal.com data. Pick the one that matches your situation.
Which traffic sources end in a booked meeting?
Bookings per traffic source and per landing page, joined to the visit data already in the warehouse, with downstream close-rate per source. Marketing sees which campaigns produce a calendar event the sales team shows up to, rather than which ones win the click-through report.
Where is the no-show rate hiding?
No-show-rate per event type, persona, traffic source and reminder pattern, ranked by booked volume. The fifty-percent no-show on a free-trial demo from paid social looks very different from a five-percent no-show on a CS QBR, and the warehouse view makes that gap actionable instead of a quarterly anecdote.
Is the routing form helping or filtering qualified leads out?
Drop-off per question in the Cal.com routing flow, joined to downstream pipeline outcome for the attendees who did finish. Useful for the conversation about whether question seven (company size, budget, intent) is doing qualification work or quietly losing meetings the sales team would have happily taken.
Cal.com seat cost per booked meeting and per closed deal, set against pipeline contribution. Finance sees which teams turn the seat into a meeting that moves revenue and which ones treat it as a static link in an email signature.
Bookings per rep, no-show-rate and round-robin balance against pipeline created. Sales leadership separates reps who fill a calendar with the right meetings from reps whose link gets clicked but whose week stays empty.
Routing-form drop-off, event-type performance and workflow inventory in one view. RevOps runs booking-funnel audits on data that refreshes with the warehouse, not on a one-off Insights export per quarter.
A new Cal.com booking creates or updates the HubSpot contact, attaches the routing-form answers as fields, and either opens a deal or attaches the booking to an existing one. Sales reps walk into the call with the qualification answers in front of them, and pipeline reporting shows bookings per source against closed-won without a manual sync.
Each Cal.com booking lands as a Lead, Contact or Opportunity activity in Salesforce, with routing-form answers mapped to custom fields and round-robin assignment respecting Salesforce ownership. Sales-ops stops reconciling Cal.com exports against the CRM, and AE quota dashboards count meetings booked-and-held instead of meetings booked-and-vapour.
New bookings, reschedules and no-shows post into the Slack channel that owns the audience: an SDR pod gets new inbound demos, a recruiting channel gets interview confirmations, a CS pod gets QBR cancellations. The team reacts in the same place they already work, and the booking thread carries the routing-form answers so context is one click away.
Cal.com event types that take a Stripe payment up front (consult fees, paid coaching, premium support sessions) are matched back to the Stripe charge, refund and dispute records in the warehouse. Finance gets a single view of paid-booking revenue per event type, no-show write-offs and refund rate per host, instead of two systems with two different totals.
When a customer books a CS or onboarding call from inside Intercom, the booking shows up on the Intercom conversation timeline with event type, attendee and routing-form answers. CS reps stop swivel-chairing between Intercom and Cal.com, and account-level reporting shows time-to-first-call per plan and per onboarding cohort.
Recruiting teams that run their pipeline in Notion get each Cal.com interview booking written back to the candidate's Notion page: stage, interviewer, scheduled time and the link to notes. Time-to-offer and interview-load per interviewer become a Notion view that talent leads open every day, instead of a stat buried in the scheduling tool.
You keep the reporting tool you already have. We connect it to the warehouse where your Cal.com data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Cal.com's API exposes event types, bookings, attendees, users, teams, schedules, organizations, workflows and routing forms, and the connector mirrors that surface into the warehouse. That covers booking origin, attendee answers, reschedule and cancel events, and the team and event-type taxonomy, which is enough to run booking-funnel reporting and the automations on this page. Personal calendar content from connected Google or Outlook calendars is not part of the pull.
Yes. The connector talks to the Cal.com API, so a cloud workspace and a self-hosted enterprise deployment look the same from a data point of view. For self-hosted setups we point the connector at your instance URL and authenticate against your API tokens; the warehouse model and downstream automations are identical.
We review your Cal.com setup and the systems around it. Together we pick the first thing worth building.