Companies that use Cal Enterprise

Source: Analysis of Linkedin bios of 128 companies that use Cal Enterprise

I noticed that Cal Enterprise users span an incredibly diverse range of operations, but they share a common thread: they're deeply embedded in complex, human-centered services. These aren't simple product companies. I see healthcare providers managing patient care journeys, financial services firms navigating regulatory compliance, nonprofits coordinating social services, real estate companies managing multi-location operations, and professional services firms handling intricate client workflows. What they build or sell is less important than how they deliver it: through distributed teams, across multiple locations, with heavy coordination requirements.

The stage signals are fascinating because they're all over the map. I see post-IPO giants like PayPal alongside Series A startups, bootstrapped nonprofits next to private equity-backed firms, and established institutions operating for decades. Employee counts range from under to over 30,000. What unifies them isn't growth stage but operational complexity. They're at the point where manual coordination breaks down, whether that's 50 employees or 5,000.

Source: Analysis of tech stacks from 128 companies that use Cal Enterprise

I noticed that Cal Enterprise users are clearly technology-forward companies operating at significant scale with mature operational practices. The overwhelming presence of Slack Enterprise Grid, incident management tools, and cloud security platforms tells me these are substantial organizations that prioritize reliability, security, and coordinated team communication. They're not startups experimenting with tools. They're established companies with complex infrastructure needs and likely distributed teams.

The pairing of Incident.io and PagerDuty is particularly revealing. These companies are running services where uptime matters enormously, probably customer-facing applications with strict SLA commitments. They need sophisticated on-call rotations and incident response workflows. When you add Lacework FortiCNAPP to this mix, it becomes clear these organizations are managing cloud-native infrastructure at scale and treating security and reliability as business-critical functions, not afterthoughts.

Golinks appearing so frequently is fascinating because it signals a specific operational culture. Companies adopt Golinks when they have enough internal tools, dashboards, and resources that employees need shortcuts to navigate everything efficiently. This suggests organizations with extensive internal systems and a focus on developer or employee productivity. Combined with Kandji for device management, I'm seeing companies that invest heavily in their internal operations and employee experience, not just their customer-facing products.