← All case studies
Cedar · Case study

How Cedar onboards new customers in days.

One implementation layer for every sales stack a customer brings.

Cedar is a YC-backed AI startup. It's a sales copilot that helps customers get work done across the tools they already use, and it's only as useful as the data it can reach. Cedar needed a scalable way to onboard customers that all operate on a different sales stack.

The problem

Every customer source meant another connector to keep alive

For Cedar, every new customer source meant a new implementation project and connectors to build, ship, and maintain.

Notetakers, CRMs, ticketing systems: each one has its own API, its own authentication model, its own webhook format, its own quirks. Every integration added to the long tail of code the engineering team had to keep alive, and every hour spent on that was an hour not spent on the copilot itself.

That's a high cost for a small team. Cedar's competitive edge is velocity. Pulling engineering off the product to maintain a growing catalog of connectors works against that.

What they did with superglue

One integration layer behind the agent

Cedar uses superglue as the data and integration layer behind its agent.

  • Each source becomes a tool the agent calls. superglue exposes connectors as scoped tools. Cedar's agent calls them by name, with structured inputs and outputs. No raw API wrangling in the agent's logic.
  • Handles the per-vendor complexity once. Auth flows, webhook formats, retries, rate limits are all different for every data source. superglue absorbs that complexity so Cedar's product doesn't have to.
  • Mapped into Cedar's own schema. Every source's data shape is translated into the structure Cedar's product expects. The agent works against one consistent data model, not a different one per vendor.
  • Event-driven, not just polling. Beyond on-demand calls, the integration supports acting on events (for example, kicking off a workflow when a meeting transcript is ready), so the copilot responds in real time.
  • Cedar keeps the data and the auth. superglue returns mapped objects to Cedar's product, which owns its database and customer OAuth tokens. The integration layer does the connector work. Cedar owns the customer relationship.
What changed
  • New customers are onboarded in days instead of weeks.
  • Engineering time goes back to the core product, not to connector maintenance.
  • The agent works against one consistent schema across every source.
  • Every action the agent takes against a customer's system is logged and controlled.

"superglue allowed us to onboard customers much faster, and speed up the implementation of any CRM, notetaker and productivity tool our customers use."

Isabelle Ilyia, CTO, Cedar
The outcome

Live in days, on any stack

New customers go live in days, regardless of which CRM, notetaker, or ticketing system they run on.

Want the same for your team?

Schedule a quick session with Adina, our CEO, to discuss how superglue can help you achieve the same.